Date: Tue, 17 Aug 2004 19:25:52 +0300 From: Sergey Lyubka <devnull@uptsoft.com> To: freebsd-hackers@freebsd.org Subject: Re: actual boot device Message-ID: <20040817192552.B5554@oasis.uptsoft.com> In-Reply-To: <20040817161516.GB53307@dan.emsphone.com>; from dnelson@allantgroup.com on Tue, Aug 17, 2004 at 11:15:16AM -0500 References: <20040817185240.A5554@oasis.uptsoft.com> <20040817161516.GB53307@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. 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. > > -- > Dan Nelson > dnelson@allantgroup.com -- Sergey Lyubka, Network Security Consultant NetFort ISS Ltd, Galway, Ireland
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040817192552.B5554>