From owner-freebsd-hackers@FreeBSD.ORG  Tue Aug 17 16:54:16 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 8BA1016A4CE
	for <freebsd-hackers@freebsd.org>;
	Tue, 17 Aug 2004 16:54:16 +0000 (GMT)
Received: from oasis.uptsoft.com (oasis.uptsoft.com [217.20.165.41])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9484C43D1D
	for <freebsd-hackers@freebsd.org>;
	Tue, 17 Aug 2004 16:54:15 +0000 (GMT)
	(envelope-from devnull@oasis.uptsoft.com)
Received: (from devnull@localhost)
	by oasis.uptsoft.com (8.11.6/linuxconf) id i7HGsEb07536
	for freebsd-hackers@freebsd.org; Tue, 17 Aug 2004 19:54:14 +0300
Date: Tue, 17 Aug 2004 19:54:14 +0300
From: Sergey Lyubka <devnull@uptsoft.com>
To: freebsd-hackers@freebsd.org
Message-ID: <20040817195414.D5554@oasis.uptsoft.com>
Mail-Followup-To: freebsd-hackers@freebsd.org
References: <20040817185240.A5554@oasis.uptsoft.com>
	<20040817161516.GB53307@dan.emsphone.com>
	<20040817192552.B5554@oasis.uptsoft.com>
	<20040817163915.GC53307@dan.emsphone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20040817163915.GC53307@dan.emsphone.com>;
	from dnelson@allantgroup.com on Tue, Aug 17, 2004 at 11:39:15AM -0500
X-OS: FreeBSD 4.5-STABLE
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 16:54:16 -0000

> 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.