From: Rob Love <rml@ximian.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] add sysfs mem device support [2/4]
Date: Tue, 23 Dec 2003 17:56:34 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107220250302555@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107213954018345@msgid-missing>
On Tue, 2003-12-23 at 11:39, Christoph Hellwig wrote:
> I disagree. For fully static devices like the mem devices the udev indirection
> is completely superflous.
I see your point, so I really do not want to argue, but here is my
rationale for why everything should be done seamlessly via udev:
In a nutshell, we want a single, clean, automatic solution to device
naming. If some "static" devices are hard coded, we introduce a special
case. Why do that? Why have special cases when udev can seamlessly
manage the whole thing? Say we decide to remove /dev/foo in the kernel
- that should be reflected in udev simply by way of it no longer being
created on boot.
That is my thoughts. I dislike special casing. And without it, udev
can seamlessly handle everything, automatically.
But I _do_ see your point. It is silly to generate a hotplug event for
a static device on every boot, etc. etc. But I think the cleanliness of
not special casing certain devices in the udev solution is worth it.
Rob Love
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-12-23 17:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 0:26 [PATCH] add sysfs mem device support [2/4] Greg KH
2003-12-23 13:15 ` Christoph Hellwig
2003-12-23 15:31 ` Rob Love
2003-12-23 16:07 ` Rob Love
2003-12-23 16:39 ` Christoph Hellwig
2003-12-23 17:56 ` Rob Love [this message]
2003-12-23 18:01 ` Greg KH
2003-12-23 19:16 ` Christoph Hellwig
2003-12-23 19:19 ` Rob Love
2003-12-23 19:22 ` Christoph Hellwig
2003-12-23 19:24 ` viro
2003-12-23 19:25 ` Rob Love
2003-12-23 19:28 ` Rob Love
2003-12-23 19:42 ` Jeff Garzik
2003-12-23 19:45 ` Rob Love
2003-12-23 20:00 ` Stephan Maciej
2003-12-23 20:33 ` viro
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=marc-linux-hotplug-107220250302555@msgid-missing \
--to=rml@ximian.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).