Date: Wed, 17 Jun 2020 10:40:38 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: Rebecca Cran <rebecca@bsdio.com> Cc: Miguel C <miguelmclara@gmail.com>, freebsd-current@freebsd.org Subject: Re: CTF: UEFI HTTP boot support Message-ID: <202006171740.05HHecjX086405@gndrsh.dnsmgr.net> In-Reply-To: <0b38b537-9d9b-b3ae-bae3-bb5b4926bbaa@bsdio.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 6/16/20 5:17 AM, Miguel C wrote: > > > I've been trying out FreeBSD with raspberry Pi4 (4GB) and wanted to see > > what the state of HTTP BOOT is in FreeBSD, so I bumped into this! > > > > I'm curious if it should be possible to point to a img/iso directly (I > > tried to use the img.xz unpacked it and make it available on a local web > > server and that didn't seem to work for me) but maybe thats cause those > > images miss something, so arm64 aside does that work for amd64? I.E. using > > the bootonly.iso? > > Unfortunately HTTP boot only works as far as the kernel: UEFI fetches > loader.efi, the loader fetches and runs the kernel over HTTP -- and then > you need to use NFS to mount the filesystem (or have a local root > filesystem). > > > UEFI also has RamDisk support, but I don't think that's for remote > ISO/disk files, just local files. > Does FreeBSD kernel have a driver that can talk to the UEFI ramdisk? I believe that is how many of the other distro's are actually able to do this "load the stock .iso over the network and just run from that in memory." I have booted serveral things this way and it is a nice feature. > -- > Rebecca Cran -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202006171740.05HHecjX086405>