Date: Tue, 17 Aug 2004 19:54:14 +0300 From: Sergey Lyubka <devnull@uptsoft.com> To: freebsd-hackers@freebsd.org Subject: Re: actual boot device Message-ID: <20040817195414.D5554@oasis.uptsoft.com> In-Reply-To: <20040817163915.GC53307@dan.emsphone.com>; from dnelson@allantgroup.com on Tue, Aug 17, 2004 at 11:39:15AM -0500 References: <20040817185240.A5554@oasis.uptsoft.com> <20040817161516.GB53307@dan.emsphone.com> <20040817192552.B5554@oasis.uptsoft.com> <20040817163915.GC53307@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. Yes, that makes sense, the boot device may not be even accessible. As I said, I am running picobsd-like system, it's / embedded into kernel so / mountpoint is /dev/md0 :-) I was thinking the kernel set some sysctl or something after getting parameters from bootblocks/loader, and user may read this something. Probably kenv loaddev is the answer, my problem is that I cannot fit loader into the image - it is already packed enough. Thanks for the answers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040817195414.D5554>