From owner-freebsd-questions@FreeBSD.ORG  Tue Mar  2 17:50:06 2010
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5E7A8106566C
	for <freebsd-questions@freebsd.org>;
	Tue,  2 Mar 2010 17:50:06 +0000 (UTC)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.103.93])
	by mx1.freebsd.org (Postfix) with ESMTP id 337CB8FC0A
	for <freebsd-questions@freebsd.org>;
	Tue,  2 Mar 2010 17:50:05 +0000 (UTC)
Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1])
	by dc.cis.okstate.edu (8.14.2/8.13.8) with ESMTP id o22HnrHf018554
	for <freebsd-questions@freebsd.org>;
	Tue, 2 Mar 2010 11:49:53 -0600 (CST)
	(envelope-from martin@dc.cis.okstate.edu)
Message-Id: <201003021749.o22HnrHf018554@dc.cis.okstate.edu>
To: freebsd-questions@freebsd.org
Date: Tue, 02 Mar 2010 11:49:53 -0600
From: Martin McCormick <martin@dc.cis.okstate.edu>
Subject: Re: Remote Building of FreeBSD 
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2010 17:50:06 -0000

	The boot.config file I thought would boot mfsbsd on what
was the swap partition is not  working. On this particular
drive, ad0s1a is the normal FreeBSD partition and ad0s1b is
swap. The idea is to use dd to write the mfsboot.img file to
/dev/ad0s1b and then boot from there. My boot.config file is as
follows:

-P
rootdev="disk2s1b"
   root_disk_unit="0"

	I get the following message from the serial console:

/boot.config: -P
rootdev="disk2s1b"
   root_disk_unit="0"

FreeBSD/i386 boot
Default: 0:ad(0,a)root_disk_unit="0"
boot:
No root_disk_unit="0"

FreeBSD/i386 boot
Default: 0:ad(0,a)root_disk_unit="0"
boot:

The message Default: 0:ad(0,a)root_disk_unit="0"

does seem to be what one would expect for the ad0s1a partition
but I don't think I am telling the system to boot as the
mfsboot.img file does work if one writes it to /dev/ad0.