From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1Ei23Z-0000Uy-5c for garchives@archives.gentoo.org; Fri, 02 Dec 2005 03:57:57 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jB23vG0C032256; Fri, 2 Dec 2005 03:57:16 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jB23tTmH026421 for <gentoo-dev@lists.gentoo.org>; Fri, 2 Dec 2005 03:55:29 GMT Received: from spb42.christs.cam.ac.uk ([131.111.233.172] helo=localhost) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1Ei21A-0000RP-SZ for gentoo-dev@lists.gentoo.org; Fri, 02 Dec 2005 03:55:29 +0000 Date: Fri, 2 Dec 2005 03:57:20 +0000 From: Stephen Bennett <spb@gentoo.org> To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] contents of /dev after initial installation Message-ID: <20051202035720.0be09805@localhost> In-Reply-To: <20051202034459.GB2550@ols-dell.iic.hokudai.ac.jp> References: <1133490923.15611.31.camel@sputnik886.ruz-net> <20051202024755.0203586d@localhost> <20051202034459.GB2550@ols-dell.iic.hokudai.ac.jp> X-Mailer: Sylpheed-Claws 1.9.13 (GTK+ 2.8.7; i686-pc-linux-gnu) Precedence: bulk List-Post: <mailto:gentoo-dev@lists.gentoo.org> List-Help: <mailto:gentoo-dev+help@gentoo.org> List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org> List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: cd2ab301-6eba-4a18-8f2b-c7a767f2efc9 X-Archives-Hash: 4358fab8a23fdcc494f1a910215dfcac On Fri, 2 Dec 2005 12:45:00 +0900 Georgi Georgiev <chutz@gg3.net> wrote: > I don't need a fully populated /dev to get a working shell with > init=/bin/bash on the kernel cmdline. And at that point it is easy to > run /dev/MAKEDEV and get whatever devices are needed for > troubleshooting. Still more effort than booting into a system that is pretty much fully-functional already to fix it. > I of course assume that if the dynamic /dev management fails, then we > need to *recover* instead of trying to get the system up as usual. > And I also assume that the init scripts will anyway tell me "fatal > error: give root password for maintenance or Ctrl-D to continue" if I > have something vital missing from /dev. See above. And that still doesn't address the issue that some people don't even want dynamic device management in the first place. -- gentoo-dev@gentoo.org mailing list