From: "J.A. Magallon" <jamagallon@able.es>
To: Hacksaw <hacksaw@hacksaw.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: udev: what's up with old /dev ?
Date: Sun, 10 Oct 2004 23:25:46 +0000 [thread overview]
Message-ID: <1097450746l.5993l.0l@werewolf.able.es> (raw)
In-Reply-To: <200410102315.i9ANF7OI019460@hacksaw.org> (from hacksaw@hacksaw.org on Mon Oct 11 01:15:07 2004)
On 2004.10.11, Hacksaw wrote:
> >The very first thing init does is open /dev/console, and if it doesn't
> >exist the entire boot hangs.
>
> This raises a question: Would it be a useful thing to make a modified init
> that could run udev before it does anything else?
I don't think it is needed. There is no problem (i am thinking on rootles
nodes and PXE and so on...) on building a simple initrd with /dev/console,
/dev/null and half a dozen standard devices if they are needed. Just
to get udev run and have your real devices mounted there and overwrite
them.
I just remember one other oddity. To clean up my system, I copied the
running /dev to /dev-new, moved /dev to /dev-old and /dev-new to /dev.
But on 'reboot', I got a complaint about /dev/initctl not opening.
This could happen also with init. It opens real /dev/initctl on boot,
mounts /dev and tries to use new /dev/inittclt on shutdown...
--
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 prev parent reply other threads:[~2004-10-10 23:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 22:08 udev: what's up with old /dev ? J.A. Magallon
2004-10-10 22:51 ` Zack Weinberg
2004-10-10 23:15 ` Hacksaw
2004-10-10 23:25 ` J.A. Magallon [this message]
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=1097450746l.5993l.0l@werewolf.able.es \
--to=jamagallon@able.es \
--cc=hacksaw@hacksaw.org \
--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.