Date: Sun, 8 Nov 1998 16:30:01 -0800 (PST) From: Rajesh Vaidheeswarran <rv@fore.com> To: doc@FreeBSD.ORG Subject: Re: docs/8610: boot.config.8 man page Message-ID: <199811090030.QAA14631@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR docs/8610; it has been noted by GNATS. From: Rajesh Vaidheeswarran <rv@fore.com> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: rv@fore.com, freebsd-gnats-submit@freebsd.org Subject: Re: docs/8610: boot.config.8 man page Date: Sun, 08 Nov 1998 19:25:48 -0500 Oh.. didn't realize that. sorry. So, if I disklabel -b /boot/boot1 -s /boot/boot2 and reboot, my machine would actually recognise the ELF kernel? Cool. If so, what is the need for /boot/loader anymore? And, what is the need for boot.config.8 at all? Also, I would like to know what kernel.config does so that I can document it. rv -- using MH template repl.format -- In a previous message, "Jordan K. Hubbard" writes: > > Having gone through the pains of booting an ELF kernel, I realized > > that a man page for boot.config would have helped. > > Actually, the latest boot blocks do the right thing most clearly > when /boot.config has been completely removed - disklabel the latest > boot1/boot2 to your drive and check it out! :) > > > By defining /boot/loader as the program to boot, the loader will then > > take over the boot process and load the default kernel /kernel, with > > flags specified by /kernel.config. > > Not necessary if /boot.config does not exist at all. I think perhaps > the man page needs to be updated a little in light of the current > defaults when boot.config is absent altogether, but it's definitely > a good start! > > - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811090030.QAA14631>