From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: David Lang <david.lang@digitalinsight.com>,
Robert Love <rml@novell.com>, Mike Bell <mike@mikebell.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Greg KH <gregkh@suse.de>
Subject: Re: devfs vs udev FAQ from the other side
Date: Wed, 14 Sep 2005 22:07:17 -0500 [thread overview]
Message-ID: <200509142207.18478.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0509141911530.8469@qynat.qvtvafvgr.pbz>
On Wednesday 14 September 2005 21:13, David Lang wrote:
> On Wed, 14 Sep 2005, Robert Love wrote:
>
> >> Took an actual devfs system of mine and disabled devfs from the
> >> kernel, then enabled hotplug and sysfs for udev to run. make clean
> >> and surprise surprise, kernel is much bigger. Enable netlink stuff and
> >> it's bigger still. udev is only smaller if like Greg you don't count
> >> its kernel components against it, even if they wouldn't otherwise need
> >> to be enabled. Difference is to the tune of 604164 on udev and 588466
> >> on devfs. Maybe not a lot in some people's books, but a huge
> >> difference from the claims of other people that devfs is actually
> >> bigger.
> >
> > What modern system, though, could survive without hotplug and sysfs and
> > netlink? You need to have those components, you want those features,
> > anyhow.
>
> most servers and embedded systems can survive just fine without hotplug
> (in fact hotplug is frequently the slowest part of the boot).
>
I wonder why udev or devfs is so much needed for an embedded system with
a static and very limited set of devices? Make static /dev and get rid
of both.
And as far as servers go - you start them and you leave them alone. Who
cares how long this things boots if you do it once a month?
--
Dmitry
prev parent reply other threads:[~2005-09-15 3:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 0:51 devfs vs udev FAQ from the other side Mike Bell
2005-09-15 1:08 ` Robert Love
2005-09-15 2:09 ` Mike Bell
2005-09-15 3:17 ` Robert Love
2005-09-15 4:13 ` Mike Bell
2005-09-15 2:13 ` David Lang
2005-09-15 3:07 ` Dmitry Torokhov [this message]
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=200509142207.18478.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=david.lang@digitalinsight.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@mikebell.org \
--cc=rml@novell.com \
--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