From owner-freebsd-hackers  Thu Feb  1 21:52:21 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from never.tellme.com (never.tellme.com [209.157.156.27])
	by hub.freebsd.org (Postfix) with ESMTP id 28FD537B491
	for <freebsd-hackers@freebsd.org>; Thu,  1 Feb 2001 21:52:04 -0800 (PST)
Received: by never.tellme.com (Postfix, from userid 501)
	id CE15671659; Thu,  1 Feb 2001 21:52:03 -0800 (PST)
Date: Thu, 1 Feb 2001 21:52:03 -0800
From: Danny Howard <dannyman@tellme.com>
To: freebsd-hackers@freebsd.org
Subject: pxeboot -> init does error 5
Message-ID: <20010201215203.A72803@never.tellme.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
X-Loop: djhoward@uiuc.edu
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

http://people.freebsd.org/~alfred/pxe/

But I get tired of dicking around with mfsroot vnode devices and such.

The first thing I tried was taking the contents of the boot floppies and just
sticking them in /usr/tftpboot.  No dice, because then you end up with a
read-only NFS root, which upsets sysinstall.  How to get around that?

The thing that bit me, I'm guessing, was removing the "load -T mfs_root
/mfsroot" from loader.rc.  I think load mfs_root creates an md filesystem.

Now my thought is that if I can boot a minimal "diskless" install over the
network, I can then fetch an appropriate install.cfg for the client and run
sysinstall with it.

So, I blew out /usr/tftpboot, and installed the bin distribution in there,
copied the tfpboot back, set 'vfs.nfs.diskless_valid="1"' in boot/loader.conf,
did a basic rc.conf and tried re-booting the client system.

No such luck.  It can't load init!!!

NFS ROOT 172.16.0.1:/usr/tftpboot
nfs_getpages: 13
exec /sbin/init: error 5

It then complains that init is not found in the path ...

I can put sysinstall in /stand, but since the magic "setting up an mfsroot"
never happened in /etc/rc.diskless1 there's no rw filesystem for sysinstall to
work with. :(

4.1.1-RELEASE, btw.

Any ideas?

Thanks,
-danny


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message