On Tue, Jun 16, 2020 at 7:25 PM Rebecca Cran <rebecca_at_bsdio.com> wrote: > 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). > > Thanks for the reply , I can work with that for a live system still better than tftp, http+nfs should be that hard. > UEFI also has RamDisk support, but I don't think that's for remote > ISO/disk files, just local files. > > As for the ISO it does seem to work for remote ISO files, the bhyve con presentantion suggests the same and I was able to boot the ubuntu arm64 install iso using the direct link as a HTTP BOOT entry,. �>Start HTTP Boot over IPv4.... > Station IP address is 172.16.50.62 > > URI: http:/?172.16.50.106/uarm64.iso > File Size: 916357120 Bytes > Downloading...26% > But we also don't seem to have iso images for the raspberry pi, so it might not work there, this does sugget just a link to the .efi file would work: https://github.com/jljusten/tianocore/wiki/HTTP-Boot but I tired that with no succes In any case from what you're saying... for a live system I need http + nfs for rootfs. But I'm still clueless how to set that up for FreeBSD, the guide mentioned here is linux centric, what need to live on the http server side? > -- > Rebecca Cran > > >Received on Tue Jun 16 2020 - 19:36:15 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:24 UTC