From: Eric Valette <eric.valette@free.fr>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com
Subject: updating kernel to 2.6.13-rc1 from 2.6.12 + CONFIG_DEVFS_FS + empty /dev
Date: Wed, 29 Jun 2005 23:03:56 +0200 [thread overview]
Message-ID: <42C30CBC.5030704@free.fr> (raw)
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).
The result, however, was *for sure* a non functionnal system and adding
udev as a defvs replacement will of course not help as I understand this
kernel needs *anyway* a minimal filesystem to boot.
While I do not want to re-enter the endless devfs versus udev merit
(allthough I personnaly strongly believe udev is just too slow for
embedded system boot compared to devfs without devfsd) I think that this
potential problem should be clearly mentionned in the release note for
2.6.13 or at least something like "a minimal devfs able to boot emty
/dev installation" be integrated as a replacement.
For the rest of the problem, I will just waste some inodes to have a
minimal /dev back (which I think is a clear regression).
This mail intend to point out that removing a feature in the stable
series can break existing "real life" installations which, by the way,
did not break as badly as that for years. It sometimes broke using -mm
stuffs but was just a matter of waiting for a patch. I will not get a
patch for my problem.
No flame intended just feed back from end-user experience.
-- eric
next reply other threads:[~2005-06-29 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 21:03 Eric Valette [this message]
2005-06-29 22:40 ` updating kernel to 2.6.13-rc1 from 2.6.12 + CONFIG_DEVFS_FS + empty /dev Greg KH
2005-06-30 13:12 ` eric.valette
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=42C30CBC.5030704@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 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.