Date: Tue, 16 Jun 2020 08:48:34 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> Cc: Miguel C <miguelmclara@gmail.com>, <freebsd-current@freebsd.org>, <sjg@juniper.net> Subject: Re: CTF: UEFI HTTP boot support Message-ID: <5957.1592322514@kaos.jnpr.net> In-Reply-To: <202006161535.05GFZJFn081325@gndrsh.dnsmgr.net> References: <202006161535.05GFZJFn081325@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Rodney W. Grimes <freebsd-rwg@gndrsh.dnsmgr.net> wrote: > > 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? > > One problem you run into in attemtping this is even if you get an > image downloaded and started that image is being provided by some > memory device driver that emulates some type of iso device. > FreeBSD does not have a driver for that device so once the kernel > gets to the point of mounting its root file system it falls on > its face with a mountroot failure. Are you refering to something like: vfs.root.mountfrom="cd9660:/dev/md0.uzip" we boot that way all the time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5957.1592322514>