From: Michael Thonke <tk-shockwave@web.de>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: udev: what's up with old /dev ?
Date: Mon, 11 Oct 2004 00:41:01 +0200 [thread overview]
Message-ID: <4169BA7D.3030306@web.de> (raw)
A couple questions:
- Is it possible to boot with an empty /dev, until udev builds it ?
No, it isn't as far as I know.
- If this is not the case, which are the minimal nodes that should be
present ?
/dev/null and /dev/console is needed to boot into the envoirment
- 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 ?
At least I could do so, but at the moment /dev are also elemental for some distros..I have moved with gentoo and have had no problems along x86 32bit
but x86_64 driving me creazy
I you want more to know have a look at decibiles udev primer
Greets Michael
next reply other threads:[~2004-10-10 22:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 22:41 Michael Thonke [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-11 7:19 udev: what's up with old /dev ? Zack Weinberg
2004-10-10 22:08 J.A. Magallon
2004-10-10 22:51 ` 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
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=4169BA7D.3030306@web.de \
--to=tk-shockwave@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox