Date: Tue, 17 Aug 2004 09:35:00 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: freebsd-hackers@freebsd.org Subject: Re: actual boot device Message-ID: <20040817163500.GC28054@odin.ac.hmc.edu> In-Reply-To: <20040817192552.B5554@oasis.uptsoft.com> References: <20040817185240.A5554@oasis.uptsoft.com> <20040817161516.GB53307@dan.emsphone.com> <20040817192552.B5554@oasis.uptsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--yLVHuoLXiP9kZBkt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Please don't top post, it breaks context. Post reformatted.] On Tue, Aug 17, 2004 at 07:25:52PM +0300, Sergey Lyubka wrote: > On Tue, Aug 17, 2004 at 11:15:16AM -0500, Dan Nelson wrote: > > In the last episode (Aug 17), Sergey Lyubka said: > > > How would one know the actual boot device after kernel successfully > > > booted ? > >=20 > > The kern.bootfile sysctl points to the kernel file that was loaded, > > according to the loader. If you booted off of cdrom or floppy, you can > > run "kenv loaddev" to find out which device was actually used to read > > the file. > > I am booting kernel directly from bootblock, and do not have > boot loader, so kenv does not work. You don't say which version you are running, but in 5.x booting without the loader is not supported in any way shape or form. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --yLVHuoLXiP9kZBkt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBIjOzXY6L6fI4GtQRAgsOAKCvn0wm0Ed5to2uiPMPAwACSkmNBQCgzvvF RyLmcTkNV2y3klb1xQQoAyg= =SUaj -----END PGP SIGNATURE----- --yLVHuoLXiP9kZBkt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040817163500.GC28054>