Date: Tue, 17 Aug 2004 12:07:54 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: freebsd-hackers@freebsd.org Subject: Re: actual boot device Message-ID: <20040817170754.GE53307@dan.emsphone.com> In-Reply-To: <20040817195414.D5554@oasis.uptsoft.com> References: <20040817185240.A5554@oasis.uptsoft.com> <20040817161516.GB53307@dan.emsphone.com> <20040817192552.B5554@oasis.uptsoft.com> <20040817163915.GC53307@dan.emsphone.com> <20040817195414.D5554@oasis.uptsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Aug 17), Sergey Lyubka said:
> > 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 :-)
What might work is reading the first 512 bytes of
/dev/{da0,ad0,fd0,cd0} and see if any of them have your picobsd
bootblock. Then you know where the filessytem holding /kernel is and
can mount it yourself.
--
Dan Nelson
dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040817170754.GE53307>