From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Mdk-Cooker <cooker@linux-mandrake.com>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: udev: what's up with old /dev ?
Date: Sun, 10 Oct 2004 22:08:49 +0000 [thread overview]
Message-ID: <1097446129l.5815l.0l@werewolf.able.es> (raw)
Hi all...
I have just remembered that udev mounts /dev as a tmpfs filesystem, _on top_
of the old /dev directory. I have just booted to single user mode,
and checked that the old /dev is wasting around 13000 files (inodes) in my
box. Space is not an issue, that is around 480 Kb.
A couple questions:
- Is it possible to boot with an empty /dev, until udev builds it ?
- If this is not the case, which are the minimal nodes that should be
present ?
- For any answer to previous question, shouldn't the distro set up minimal
/dev (empty or with a few nodes) and _delete_ the old /dev tree ?
I don't remember exactly, but there are scripts at initscripts run before
udev. As I understand it, udev should be the very first thing to run, as
anything after it will probably need a /dev/something....
Why my simple logic does not work ?
(As I CC both cooker and LKML, this is a cooker specific question: could anybody
who has installed 10.1 from scratch, ie not an update, boot to runlevel 1 and
list his /dev)
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.1 (Community) for i586
Linux 2.6.9-rc3-mm3 (gcc 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)) #2
next reply other threads:[~2004-10-10 22:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 22:08 J.A. Magallon [this message]
2004-10-10 22:51 ` udev: what's up with old /dev ? Zack Weinberg
2004-10-10 23:15 ` Hacksaw
2004-10-10 23:25 ` J.A. Magallon
2004-10-11 0:06 ` Hacksaw
2004-10-11 19:13 ` Denis Vlasenko
2004-10-11 9:14 ` Felipe Alfaro Solana
2004-10-11 10:29 ` Arkadiusz Miskiewicz
2004-10-11 12:02 ` Felipe Alfaro Solana
2004-10-11 11:11 ` Hacksaw
2004-10-11 12:04 ` Felipe Alfaro Solana
2004-10-11 20:06 ` Hacksaw
2004-10-11 20:51 ` Bartlomiej Zolnierkiewicz
2004-10-11 21:28 ` Hacksaw
2004-10-12 0:19 ` Greg KH
2004-10-12 8:11 ` Harald Dunkel
2004-10-12 16:58 ` Greg KH
[not found] ` <416C26B4.6040408@t-online.de>
[not found] ` <20041012185733.GA31222@kroah.com>
[not found] ` <416C3BB6.4040200@t-online.de>
[not found] ` <20041012203022.GB32139@kroah.com>
2004-10-12 21:35 ` Harald Dunkel
2004-10-13 13:08 ` Mathieu Segaud
2004-10-13 14:13 ` Harald Dunkel
2004-10-13 14:33 ` Mathieu Segaud
-- strict thread matches above, loose matches on Subject: below --
2004-10-10 22:41 Michael Thonke
2004-10-11 7:19 Zack Weinberg
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=1097446129l.5815l.0l@werewolf.able.es \
--to=jamagallon@able.es \
--cc=cooker@linux-mandrake.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.