From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: shouldn't device names be "standardized"?
Date: Sun, 07 Nov 2004 17:20:18 +0000 [thread overview]
Message-ID: <20041107172018.GA14218@wonderland.linux.it> (raw)
In-Reply-To: <418E53BA.1030501@sgi.com>
On Nov 07, Kevan Rehm <kfr@sgi.com> wrote:
> Then I thought that maybe udev processes ALL matching rules, and so it
> would produce names for each inserted rule plus the default rule and
> then everyone would be happy, but this doesn't appear to be the case
> (unless I misunderstand). Besides, there could still be collisions
Yes. I think distributions should take some care with scripts which
generate custom names, only use them to create symlinks (which can be
provided by multiple rules) and always provide the standard names.
Or at least, this is what I do in the debian package and so far looks
like I have not annoyed too many users.
> So it seems to me that it would be better to have some sort of standard
> name for devices, sort of like the Linux Filesystem Hierarchy Standard,
> where there are names that an application could trust would be present
> on any Linux box it would care to run on.
We do: http://www.lanana.org/docs/device-list/index.html .
--
ciao, |
Marco | [9037 os/gINppPck0w]
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&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
prev parent reply other threads:[~2004-11-07 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 16:56 shouldn't device names be "standardized"? Kevan Rehm
2004-11-07 17:20 ` Marco d'Itri [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=20041107172018.GA14218@wonderland.linux.it \
--to=md@linux.it \
--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).