Date: Tue, 16 Jun 2020 12:25:14 -0600 From: Rebecca Cran <rebecca@bsdio.com> To: Miguel C <miguelmclara@gmail.com>, freebsd-current@freebsd.org Subject: Re: CTF: UEFI HTTP boot support Message-ID: <0b38b537-9d9b-b3ae-bae3-bb5b4926bbaa@bsdio.com> In-Reply-To: <CADGo8CUrJaUdNpoJ3FwpNt09Eq3MEtc2R-TRWa44WizuS6GKFw@mail.gmail.com> References: <CADGo8CUrJaUdNpoJ3FwpNt09Eq3MEtc2R-TRWa44WizuS6GKFw@mail.gmail.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. -- Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0b38b537-9d9b-b3ae-bae3-bb5b4926bbaa>