From owner-freebsd-hackers@FreeBSD.ORG  Tue Aug 17 17:07:59 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C49D316A4CE
	for <freebsd-hackers@freebsd.org>;
	Tue, 17 Aug 2004 17:07:59 +0000 (GMT)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 661BE43D49
	for <freebsd-hackers@freebsd.org>;
	Tue, 17 Aug 2004 17:07:55 +0000 (GMT)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.12.11/8.12.11) id i7HH7taj034626
	for freebsd-hackers@freebsd.org; Tue, 17 Aug 2004 12:07:55 -0500 (CDT)
	(envelope-from dan)
Date: Tue, 17 Aug 2004 12:07:54 -0500
From: Dan Nelson <dnelson@allantgroup.com>
To: freebsd-hackers@freebsd.org
Message-ID: <20040817170754.GE53307@dan.emsphone.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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040817195414.D5554@oasis.uptsoft.com>
X-OS: FreeBSD 5.2-CURRENT
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.6i
Subject: Re: actual boot device
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Aug 2004 17:07:59 -0000

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