From owner-freebsd-current Fri Oct 26 20:15:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id B995537B407 for ; Fri, 26 Oct 2001 20:15:12 -0700 (PDT) Received: (qmail 88479 invoked by uid 1000); 27 Oct 2001 03:15:11 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Oct 2001 03:15:11 -0000 Date: Fri, 26 Oct 2001 22:15:11 -0500 (CDT) From: Mike Silbersack To: Subject: devfs question Message-ID: <20011026220946.X88389-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Quick question for those devfs inclined: I was just copying my -current box over to a new harddrive. I do the cp -R -p process, and it worked fine, except for one problem: I tried to make my job easier, and decided not to copy /dev over, given that we have devfs. When I rebooted on the new drive, the box froze at the Mounting root from: prompt. It turned out that simply creating a /dev with no files in it solved the problem and made devfs happy. So, my question is this: Does /dev really need to exist in a devfs world? I assumed not, since procfs doesn't have a pre-existing /proc, but I don't know where to look to find out what the correct answer is in this case. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message