From: David Brownell <david-b@pacbell.net>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: kernel@mikebell.org
Subject: Re: [GIT PATCH] Remove devfs from 2.6.12-git
Date: Wed, 22 Jun 2005 21:08:50 -0700 [thread overview]
Message-ID: <200506222108.50905.david-b@pacbell.net> (raw)
Quoth Mike Bell:
>
> > Also, no disto uses devfs only (gentoo is close, but offers users udev
> > and a static /dev also.)
>
> It breaks a lot of my embedded setups which have read-only storage only
> and thus need /dev on devfs or tmpfs.
I'd agree that embedded setups are the ones that have been slowest to
switch over, for various reasons. One of them is that many LKML folk
ignore embedded systems issues; "just PC class or better". Another
has been that the basic hotplug scripts never worked well with "ash",
and who's going to want to ship "bash" and friends? :)
Those problems seem resolved with 2.6.12 and current modutils and udev.
Leaving basically an "upgrade your userspace" requirement.
> and thus need /dev on devfs or tmpfs. With early-userspace-udev-on-tmpfs
> being - in my experience - still unready.
Hmm, could you explain why you think udev-on-ramfs/tmpfs/... is still
unready? And what it's "unready" for? It can work fine without
needing to hack early userspace and initramfs, by the way. :)
I recently submitted patches to make buildroot support it. They're
mostly merged [1] but adding a simple patch fixes up the remaining
glitches. OpenEmbedded has supported it for a while too.
In short, I think udev-on-ramfs is simple enough to set up on 2.6.12
based embedded configs, and with "modprobe -q $MODALIAS" phasing in,
it seems to me [2] that hotplug-with-udev [3] can do most of what
folk have used devfs to achieve. I've quilted buildroot so that it
works that way by default for me; it's turnkey, with no problems.
Of course, 2.6.13 will be better with cardmgr finally gone. :)
- Dave
[1] http://bugs.busybox.net/view.php?id=290
[2] http://marc.theaimsgroup.com/?l=linux-hotplug-devel&m=111903617808816&w=2
[3] http://marc.theaimsgroup.com/?l=linux-hotplug-devel&m=111903647518255&w=2
next reply other threads:[~2005-06-23 4:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 4:08 David Brownell [this message]
2005-06-23 6:21 ` [GIT PATCH] Remove devfs from 2.6.12-git Miles Bader
2005-06-23 8:10 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2005-06-23 5:08 David Brownell
2005-06-23 5:22 ` Bill Gatliff
2005-06-21 6:29 Greg KH
2005-06-21 6:54 ` Andrew Morton
2005-06-21 13:50 ` Adrian Bunk
2005-06-21 15:10 ` Greg KH
2005-06-21 20:11 ` Andrew Morton
2005-06-21 20:52 ` Arjan van de Ven
2005-06-21 21:03 ` Andrew Morton
2005-06-21 21:16 ` Greg KH
2005-06-21 21:58 ` J.A. Magallon
2005-06-23 1:00 ` Mike Bell
2005-06-23 1:18 ` Andrew Morton
2005-06-23 2:13 ` Bill Gatliff
2005-06-23 4:59 ` Greg KH
2005-06-23 6:14 ` Miles Bader
2005-06-23 6:26 ` Greg KH
2005-06-23 6:36 ` Miles Bader
2005-06-23 7:03 ` Greg KH
2005-06-23 19:54 ` Kay Sievers
2005-06-23 6:34 ` Mike Bell
2005-06-23 6:37 ` Andrew Morton
2005-06-23 6:47 ` Mike Bell
2005-06-23 6:51 ` Greg KH
2005-06-23 6:38 ` Miles Bader
2005-06-23 6:28 ` Mike Bell
2005-06-23 6:48 ` Greg KH
2005-06-23 8:29 ` Mike Bell
2005-06-23 12:58 ` Theodore Ts'o
2005-06-24 8:24 ` Greg KH
2005-06-23 15:13 ` Per Liden
2005-07-18 16:36 ` Richard Gooch
2005-07-18 20:12 ` Jan Engelhardt
2005-07-18 22:29 ` Daniel Phillips
2005-07-19 2:51 ` Jim Crilly
2005-06-21 17:35 ` Carsten Otte
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=200506222108.50905.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=kernel@mikebell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox