From owner-freebsd-current Sat Oct 27 0:35:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id BE90C37B403 for ; Sat, 27 Oct 2001 00:35:23 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9R7YjS10431; Sat, 27 Oct 2001 09:34:46 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Silbersack Cc: current@FreeBSD.ORG Subject: Re: devfs question In-Reply-To: Your message of "Fri, 26 Oct 2001 22:15:11 CDT." <20011026220946.X88389-100000@achilles.silby.com> Date: Sat, 27 Oct 2001 09:34:45 +0200 Message-ID: <10429.1004168085@critter.freebsd.dk> From: Poul-Henning Kamp 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 In message <20011026220946.X88389-100000@achilles.silby.com>, Mike Silbersack w rites: >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? Yes, what else would you mount DEVFS on ? >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. It does. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message