From owner-freebsd-hackers Sat Jan 11 16:57:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA21229 for hackers-outgoing; Sat, 11 Jan 1997 16:57:45 -0800 (PST) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA21224 for ; Sat, 11 Jan 1997 16:57:38 -0800 (PST) Received: (from davidn@localhost) by labs.usn.blaze.net.au (8.8.4/8.8.4) id WAA00807; Sat, 11 Jan 1997 22:57:11 +1100 (EST) Message-ID: Date: Sat, 11 Jan 1997 11:57:10 +0000 From: davidn@unique.usn.blaze.net.au (David Nugent) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: jfieber@indiana.edu (John Fieber), hackers@FreeBSD.ORG Subject: Re: Mounting devfs on /dev References: X-Mailer: Mutt 0.56 Mime-Version: 1.0 In-Reply-To: ; from J Wunsch on Jan 12, 1997 00:20:14 +0100 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: > As John Fieber wrote: > > > > options DEVFS_ROOT > > > > > > This will pass -r to init(8), which in turn causes it to mount DEVFS. > > > > So far so good. Now, what does: > > > > panic: ffs_mountroot: can't set up bdevvp for root > > Are you sure everything has been built correctly? FWIW, it happens here too. It seems that devfs does not (yet) create the device nodes for hard disks correctly. It may be related to having the FreeBSD slice on a separate partition (in my case it was sd1s2). I've recently built a new root on sd0 using sd0x devices and not sd0xsNx, so I will give it another try when I next do a kernel build. > j@uncle 55% ls /dev > /dev: > bpf0% fd0.820# log@ rfd0.1480% rvn4% ttyp2% ttyvb% > console% fd0a# lpctl0% rfd0.1720% rvn5% ttyp3% ttyvc% > cuaa0% fd0b# lpt0% rfd0.720% rvn6% ttyp4% ttyvd% > cuaa1% fd0c# mem% rfd0.800% rvn7% ttyp5% ttyve% > cuaia0% fd0d# null% rfd0.820% speaker% ttyp6% ttyvf% > cuaia1% fd0e# ptyp0% rfd0a% stderr% ttyp7% urandom% > cuala0% fd0f# ptyp1% rfd0b% stdin% ttyv0% vn0# > cuala1% fd0g# ptyp2% rfd0c% stdout% ttyv1% vn1# > drum% fd0h# ptyp3% rfd0d% tty% ttyv2% vn2# > fd/ gsc0% ptyp4% rfd0e% ttyd0% ttyv3% vn3# > fd0# gsc0d% ptyp5% rfd0f% ttyd1% ttyv4% vn4# > fd0.1200# gsc0p% ptyp6% rfd0g% ttyid0% ttyv5% vn5# > fd0.1440# gsc0pd% ptyp7% rfd0h% ttyid1% ttyv6% vn6# > fd0.1480# io% random% rvn0% ttyld0% ttyv7% vn7# > fd0.1720# klog% rfd0% rvn1% ttyld1% ttyv8% zero% > fd0.720# kmem% rfd0.1200% rvn2% ttyp0% ttyv9% > fd0.800# lkm% rfd0.1440% rvn3% ttyp1% ttyva% > > That /dev looks fairly tidied up, doesn't it? :-) Sure does. > Btw., i just notice that ft0 is missing, and: > > bpf: ppp0 attached > bpf: ppp1 attached > bpf: lo0 attached > > ...bpf1 and bpf2 seems to be missing, too. And where are the hard disk devices? :-) DEVFS_ROOT works great for netboots though. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/