Date: Tue, 17 Aug 2004 11:39:15 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: freebsd-hackers@freebsd.org Subject: Re: actual boot device Message-ID: <20040817163915.GC53307@dan.emsphone.com> 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
In the last episode (Aug 17), Sergey Lyubka said: > 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 ? > > > > 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. > > certainly, sysctl kern.bootfile points to /kernel, but it does not > tell anything. > > The actual device may be floppy, CF card or harrdisk, and I do not > have any means of figuring it out. The best you can do is search your mountpoints and see whether any of them has a "/kernel" file. The bootblock (and loader) uses the BIOS to read the kernel file, so it's possible that the device may not even be accessible from the running system. If, for example, you booted off a floppy but didn't have the floppy drivers in the kernel. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040817163915.GC53307>