From owner-freebsd-questions Thu Apr 17 00:21:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA15541 for questions-outgoing; Thu, 17 Apr 1997 00:21:20 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA15536 for ; Thu, 17 Apr 1997 00:21:15 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id AAA11454; Thu, 17 Apr 1997 00:21:10 -0700 (PDT) Date: Thu, 17 Apr 1997 00:21:10 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Ludwig Pummer cc: questions@freebsd.org Subject: Re: Yet another booting problem In-Reply-To: <3.0.32.19970416203623.00818810@mail.sns.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 16 Apr 1997, Ludwig Pummer wrote: > I did something rather stupid recently, and now FreeBSD won't boot up > normally anymore. What did I do? MAKEDEV all. I thought it was going to > create all devices referenced in my kernel config, but apparently, it didn't. makedev all is deprecated and should be removed. It goes back to 1.1.x days-style devices, which will cause mount to blow up. You'll have to rebuild each disk and such manually. So walk through and do makedev wd0s0 makedev wd0s1 makedev wd0s2 makedev wd0s3 makedev wd1s0 ... and so forth as you require. You should be able to do this from single-user mode (the 'press return for sh' prompt), if you run 'mount /' to get it into read/write before running makedev. Hope this helps. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major