From: Grant Edwards <grante@visi.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: No /dev entries in recent stage3 snapshots?
Date: Wed, 21 Jan 2009 18:31:29 +0000 (UTC) [thread overview]
Message-ID: <gl7pm1$m7q$1@ger.gmane.org> (raw)
In-Reply-To: 200901211838.51056.dirk.heinrichs@online.de
On 2009-01-21, Dirk Heinrichs <dirk.heinrichs@online.de> wrote:
> Am Mittwoch, 21. Januar 2009 17:48:27 schrieb Grant Edwards:
>
>> Then all the stage3 tarballs I've ever seen are broken. They
>> either contain 5000+ entries, or nothing but these:
>
> Yes they are. Having 5000+ entries in there while udev is in
> used is just stupid. I'm glad they've fixed that know.
>
>> drwxr-xr-x root/root 0 2009-01-13 21:20 ./dev/
>> -rw-r--r-- root/root 0 2009-01-13 21:20 ./dev/null
>> lrwxrwxrwx root/root 0 2009-01-13 19:29 ./dev/MAKEDEV ->
>> ../sbin/MAKEDEV -rw-r--r-- root/root 0 2009-01-13 19:29 ./dev/.keep
>> drwxr-xr-x root/root 0 2009-01-13 19:29 ./dev/shm/
>> -rw-r--r-- root/root 0 2009-01-13 19:29 ./dev/shm/.keep
>> drwxr-xr-x root/root 0 2009-01-13 19:29 ./dev/pts/
>> -rw-r--r-- root/root 0 2009-01-13 19:29 ./dev/pts/.keep
>
> Yes, that's broken as well. All you need, as Neil wrote, is
> null and console.
>
>> What I do know is that using a stage3 with 5000+ entries allows
>> you to install using either the normal or quick install
>> instructions.
>
> And forcing you to remove them later, since they just waste
> inodes (on an inode based fs, of course).
>
>> Using one with just the above /dev entries causes problems
>> either way -- more so if using the quick install instructions
>> since there is no step where you mount udev to
>> /mnt/gentoo/dev.
>
> So you need to file two bug reports ;-)
Yup, I'll put them on my list of things to do:
1) bug report for quick-install
2) bug report for 2008.0 stage3 (too many useless /dev entries)
3) bug report for weekly autobuild stage3 (missing /dev/console)
--
Grant Edwards grante Yow! I'm ZIPPY the PINHEAD
at and I'm totally committed
visi.com to the festive mode.
next prev parent reply other threads:[~2009-01-21 18:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 4:04 [gentoo-user] No /dev entries in recent stage3 snapshots? Grant Edwards
2009-01-21 5:42 ` [gentoo-user] " Grant Edwards
2009-01-21 7:52 ` [gentoo-user] " Dirk Heinrichs
2009-01-21 8:31 ` Nickolas Fortino
2009-01-21 15:33 ` [gentoo-user] " Grant Edwards
2009-01-21 15:50 ` Nick Cunningham
2009-01-21 15:56 ` Neil Bothwick
2009-01-21 16:48 ` Grant Edwards
2009-01-21 17:38 ` Dirk Heinrichs
2009-01-21 18:31 ` Grant Edwards [this message]
2009-01-23 4:49 ` Grant Edwards
2009-01-23 4:55 ` Volker Armin Hemmann
2009-01-23 5:17 ` Grant Edwards
2009-01-23 5:39 ` Volker Armin Hemmann
2009-01-23 14:48 ` Grant Edwards
2009-01-25 7:12 ` Dirk Heinrichs
2009-01-24 23:29 ` Neil Bothwick
2009-01-25 1:29 ` Grant Edwards
2009-01-25 1:37 ` Grant Edwards
2009-01-25 6:19 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='gl7pm1$m7q$1@ger.gmane.org' \
--to=grante@visi.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox