From: eric.valette@free.fr
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: updating kernel to 2.6.13-rc1 from 2.6.12 + CONFIG_DEVFS_FS + empty /dev
Date: Thu, 30 Jun 2005 15:12:41 +0200 [thread overview]
Message-ID: <1120137161.42c3efc93b36c@imp1-q.free.fr> (raw)
In-Reply-To: <20050629224040.GB18462@kroah.com>
Quoting Greg KH <greg@kroah.com>:
> On Wed, Jun 29, 2005 at 11:03:56PM +0200, Eric Valette wrote:
> > For years now my /dev has been empty. When upgrading to 2.6.13-rc1 from
> > 2.6.12, and updating my kernel config file via "make oldconfig" I got no
> > visible warning about CONFIG_DEVFS_FS options being set (or at least did
> > no see it).
>
> devfs has been marked OBSOLETE for a year now. It has also been
> documented as going away. Because of this, you should not have been
> supprised at all.
I knew it! I just the announce for 2.6.13-rc1 did not contain this fact and I
did not realize booting this new kernel will fail on my machine which is bad for
a stable serie.
> What are the speed differences that you see? I've tested it and on a
> slow old laptop, with a lot of devices, udev only takes 2 seconds to
> initialize the whole device tree. If you put it in initramfs, it will
> take no additional time, as it will operate on all of the hotplug events
> as they happen. Can't get faster than "nothing" :)
If I already have every device in /dev, I do not need udev and yes it is fast
:-) This is exactly what I did to boot my system again. Just via devfs, I do
not need an initial filesystem nor need anything in user space to boot a full
system which I like.
-- eric
next prev parent reply other threads:[~2005-06-30 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 21:03 Eric Valette
2005-06-29 22:40 ` Greg KH
2005-06-30 13:12 ` eric.valette [this message]
2005-06-30 15:54 ` Greg KH
2005-06-30 20:27 ` Eric Valette
2005-07-02 5:37 ` Greg KH
2005-07-02 7:22 ` Eric Valette
2005-07-02 8:22 ` Willy Tarreau
2005-07-02 9:09 ` Eric Valette
2005-07-02 10:03 ` Willy Tarreau
2005-07-02 20:13 ` Mike Bell
2005-07-02 23:03 ` Willy Tarreau
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=1120137161.42c3efc93b36c@imp1-q.free.fr \
--to=eric.valette@free.fr \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®