From owner-freebsd-questions  Fri Jun  2 17:21:34 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id RAA04908
          for questions-outgoing; Fri, 2 Jun 1995 17:21:34 -0700
Received: from vespucci.iquest.com (root@vespucci.iquest.com [199.170.120.42])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA04902
          for <questions@FreeBSD.org>; Fri, 2 Jun 1995 17:21:32 -0700
Received: (from dkelly@localhost) by vespucci.iquest.com (8.6.9/8.6.9) id TAA27887; Fri, 2 Jun 1995 19:21:49 -0500
Date: Fri, 2 Jun 1995 19:21:49 -0500
From: David Kelly <dkelly@iquest.com>
Message-Id: <199506030021.TAA27887@vespucci.iquest.com>
To: dkelly@vespucci.iquest.com, questions@FreeBSD.org
Subject: 2.0.5-ALPHA via NFS
Sender: questions-owner@FreeBSD.org
Precedence: bulk

I have tried several times to install the bleeding-edge 2.0.5-ALPHA via
NFS from a local SGI workstation. It hangs with the message:
"Loading root floppy from t_rex:/disk9/dkelly/2.0.5-ALPHA" Alt-F2's last
comment is "DEBUG: Generating /etc/fstab file"

Nosing around I saw the message suggesting there was a debugging shell on
console 4... Oh yes! Thank you, thank you, thank you. Maybe it will do
some good in this instance. Sure enough, /nfs is a mount of the directory
described above. And I can happily browse around in t_rex.

"df -k" lists my filesystems. An "ls /mnt" says /mnt isn't there. Same
holds true for "/mnt/*" But doggone, /nfs works just peachy. Maybe I
ought to run diskless?

Checking again, it says /mnt is /dev/wd0a. Hmm. My FreeBSD stuff is supposed
to be on slice 2, /dev/wd0s2a, b for swap, f for /usr, g for /usr/src. All
but / seem right. The first slice is (was) supposed to be a DOS partition.
It appears ok. I totally deleted my old FreeBSD FDISK partitions and
started over with this installation.

So, any suggestions?

--
David Kelly N4HHE,   n4hhe@amsat.org,    dkelly@iquest.com
----------------------------------------------------------------------
The human mind ordinarily operates at only ten percent of its
capacity -- the rest is overhead for the operating system.