From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LQtoV-000465-Ov for garchives@archives.gentoo.org; Sun, 25 Jan 2009 01:29:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 45808E063C; Sun, 25 Jan 2009 01:29:25 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 17594E063C for ; Sun, 25 Jan 2009 01:29:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 81ED86460A for ; Sun, 25 Jan 2009 01:29:24 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -3.4 X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.5 tests=[AWL=0.199, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FFO5V+xndbdG for ; Sun, 25 Jan 2009 01:29:18 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 5ED256472E for ; Sun, 25 Jan 2009 01:29:16 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LQtoF-0001kZ-2G for gentoo-user@gentoo.org; Sun, 25 Jan 2009 01:29:11 +0000 Received: from 67-220-10-117.usiwireless.com ([67.220.10.117]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 25 Jan 2009 01:29:11 +0000 Received: from grante by 67-220-10-117.usiwireless.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 25 Jan 2009 01:29:11 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Grant Edwards Subject: [gentoo-user] Re: No /dev entries in recent stage3 snapshots? Date: Sun, 25 Jan 2009 01:29:00 +0000 (UTC) Message-ID: References: <20090121155655.466edba0@zaphod.digimed.co.uk> <200901230555.10400.volkerarmin@googlemail.com> <20090124232911.660b597b@krikkit> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 67-220-10-117.usiwireless.com User-Agent: slrn/0.9.8.1pl1 (Linux) Sender: news Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Archives-Salt: 6258bdf3-683c-4a95-b0e1-8ac4bc46a935 X-Archives-Hash: 5e7d75adbf3e6c928533f1a63ca440b6 On 2009-01-24, Neil Bothwick wrote: > On Fri, 23 Jan 2009 05:55:10 +0100, Volker Armin Hemmann wrote: > >> I have a server running that hets that null/console missing >> message every boot - and it does not hurt it at any way. > > A missing /dev/console stops the boot process here. It boots > without /dev/null, but only after udev spews out a load of > messages. Ah, not to worry: I've been assured in the gentoo forum thread that the problems we see when the root filesystem doesn't have proper /dev/null and /dev/console nodes aren't really happening: Neither /dev/null nor /dev/console are needed at boot-time, therefore their absence doesn't cause problems. [You must admit the argument is flawless -- though I still question the premise.] In order to get rid of my problems that weren't happening, I initially tried the "mount -bind" and "cp -a" commands that show up in /etc/issue when your /dev directory is hosed. That didn't help: after setting /etc/issue back to the default file and rebooting all the same problems still weren't happening (and /etc/issue was again modified to tell me to do mount -bind and cp -a to fix them). Then I tried booting with root in rw mode and init=/bin/bash and then doing a MAKEDEV generic-i386. (I found that recipe in an old mailing list somewhere.) MAKEDEV complained a lot about not being able to read /proc/devices. When I rebooted, I still had the all same problems not happening as before. I finally booted from a minimal install CD, mounted my root partition, removed its /dev directory completely and then re-created it by untaring ./dev from a good stage3 tarball. Now the system boots up smoothly. I feel like a bit of a fool expending so much effort getting rid of problems that weren't happening -- but, now the problems that weren't happening are gone, so I'm happy. ;) -- Grant