Date: Fri, 08 Jun 2012 18:11:29 +0200 From: rank1seeker@gmail.com To: "John Baldwin" <jhb@freebsd.org>, hackers@freebsd.org Subject: Re: CD bootcode Message-ID: <20120608.161129.283.3@DOMY-PC> In-Reply-To: <201206081118.29399.jhb@freebsd.org> References: <20120606.161514.685.1@DOMY-PC> <201206071116.33215.jhb@freebsd.org> <20120608.143300.329.2@DOMY-PC> <201206081118.29399.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > First=0D=0A> > -----=0D=0A> > stage 2 boot '/boot/boot' AND = '/boot/cdboot' shouldn't be made into working with symlinks.=0D=0A> > = Just leave them, the way they are. First one can be navigated to loader = via 'boot.config' file.=0D=0A> > So only '/boot/cdboot' should be edited, = to react to the same 'boot.config' file as '/boot/boot' does.=0D=0A> > = Simply because they both target 'loader', 'boot.config' should work for = both bootcodes.=0D=0A> =0D=0A> Adding /boot.config support to cdboot is = non-trivial. Also, cdboot is=0D=0A> intended for read-only media, so = dynamic configuration via a file is not=0D=0A> quite as = useful.=0D=0A=0D=0Acdboot is a FreeBSD specific=0D=0AFact that it is = intended for RO media is irrelevant here, as stage 2 boot can also = reside on RO fs.=0D=0A=0D=0AFor cdboot, 'boot.config' file should give = instructions of full path to loader, nothing else (no other, stage 2 = boot's flags/functionality).=0D=0AHm, then again, if cdboot file would = inherit just that 1 functionality, then it can't share same config = file.=0D=0AHow about 'cdboot.config' file name?=0D=0A=0D=0AThanks to = boot.config, I specify full path to loader, so '/boot/boot' isn't = "halted" by symlink.=0D=0AIf cdboot would obey it in a same way, I = wouldn't have to patch it, by adding third path.=0D=0A=0D=0A=0D=0ADomagoj = Smol=E8i=E6
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120608.161129.283.3>