From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: Miles Bader <miles@gnu.org>, Mike Bell <kernel@mikebell.org>,
Andrew Morton <akpm@osdl.org>, Greg KH <gregkh@suse.de>,
torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] Remove devfs from 2.6.12-git
Date: Thu, 23 Jun 2005 21:54:30 +0200 [thread overview]
Message-ID: <20050623195430.GA16162@vrfy.org> (raw)
In-Reply-To: <20050623062627.GB11638@kroah.com>
On Wed, Jun 22, 2005 at 11:26:27PM -0700, Greg KH wrote:
> On Thu, Jun 23, 2005 at 03:14:08PM +0900, Miles Bader wrote:
> > Greg KH <greg@kroah.com> writes:
> > > And again, for embedded systems, there are packages to build it and put
> > > it in initramfs. People have already done the work for you.
> >
> > BTW, has anyone done a comparison of the space usage of udev vs. devfs
> > (including size of code etc....)?
>
> Not that I know of. If you want to do this, compare the original udev
> releases that were around 5kb of code, as the nice features it has today
> are stuff that devfs can not support at all.
Sure, the main udev target is not the embedded world, just because there
is not such a big requirement to adapt a system to so many possible changes
that a desktop system or big servers seeing today.
But we have prepared the kernel with hotplug-events over netlink and a
full featured environment carried with the event. Instead of whining
about devfs going, start implementing your own tiny "udev" that even works
without sysfs at all:
o Set /proc/sys/kernel/hotplug to "".
o Create a single daemon that listens for netlink/events. Use $MAJOR $MINOR
from the environment and create a node.
o Define a simple kernel-name <-> node-name + action lookup table in the daemon
If an action is defined, fork an event with the environment of the received
netlink/event and handle the event externally.
o For bootup, embedded setups can probably just use the minimal required set
of nodes, which are copied over to the tmpfs /dev - mount. After
real userspace is up, the daemon will take care of maintaining /dev.
That way, you have a nice replacement for devfs, /sbin/hotplug and using
$MODALIAS a replacement for most of the hotplug scripts.
Based on udevd.c in the current udev-tree one can do this in less than a
week, still enough time before devfs is removed. :)
Thanks,
Kay
next prev parent reply other threads:[~2005-06-23 20:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 6:29 [GIT PATCH] Remove devfs from 2.6.12-git Greg KH
2005-06-21 6:30 ` [PATCH] devfs: Remove devfs from the partition code Greg KH
2005-06-21 6:54 ` [GIT PATCH] Remove devfs from 2.6.12-git 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-06-23 4:08 David Brownell
2005-06-23 6:21 ` Miles Bader
2005-06-23 8:10 ` Russell King
2005-06-23 5:08 David Brownell
2005-06-23 5:22 ` Bill Gatliff
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=20050623195430.GA16162@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=kernel@mikebell.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.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.