linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: new version of udev has different cd/dvd devices
Date: Sat, 31 Dec 2005 00:04:19 +0000	[thread overview]
Message-ID: <20051231000419.GA7161@vrfy.org> (raw)
In-Reply-To: <43B313ED.40402@bl.com>

On Fri, Dec 30, 2005 at 07:56:52PM +0100, Kay Sievers wrote:
> On Thu, Dec 29, 2005 at 11:46:59PM -0800, Greg KH wrote:

> > Yeah, but we still need a way to enumerate devices in some kind of
> > order, like we do for the cdrom devices today.  So I don't think we can
> > drop it entirely.
> 
> We don't have any "order", that's why we can't do it that way. The
> persistent /dev/disk links are working without any "order", that's the
> model to follow, or writing out "automatic rules" to provide stable names.
> Everything else will just not work.

The problem is we need to "name" devices reliably, without depending on
discovery-order enumeration. %e is also used to enumerate over different
subsystems like hd* and sr*. That probing order can't provide "stable"
names.

On SUSE we never used %e for that reason and the system management creates
rules for optical devices which just match on ID_PATH. That works pretty well
in all currently known setups.

For systems/distros who don't have such a central system management, we
may want some kind of "auto rule creation" for optical devices to provide
stable names.

Something like a script that checks, if a device is already catched
by a persistent rule and if not, it names the device uniquely and at the
same time it drops a rule line to a file in /etc/udev/rules.d/. So the
next time the device shows up, the same name gets assigned. That file
can be edited by the user, if he wants a different name.

That "auto rule setup" could run from udev itself, but may not work in all
cases where /etc is not writable on bootup, or it can be triggered by
running the script manually, once after adding new hardware.

That sounds like the only sane and future proof option to me.

Anybody willing to try this? I shouldn't be hard to implement this as a
shell script. Any code, ideas, comments?

Kay


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&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

  parent reply	other threads:[~2005-12-31  0:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28 22:38 new version of udev has different cd/dvd devices Moshe Yudkowsky
2005-12-28 22:50 ` Marco d'Itri
2005-12-28 23:29 ` Kay Sievers
2005-12-29  0:10 ` Moshe Yudkowsky
2005-12-29  0:22 ` Marco d'Itri
2005-12-29  0:44 ` Moshe Yudkowsky
2005-12-29 13:20 ` Phil Howard
2005-12-29 13:36 ` Marco d'Itri
2005-12-29 15:18 ` Phil Howard
2005-12-29 16:57 ` Kay Sievers
2005-12-30  7:46 ` Greg KH
2005-12-30 13:45 ` Phil Howard
2005-12-30 18:09 ` Marco d'Itri
2005-12-30 18:16 ` Darren Salt
2005-12-30 18:49 ` Kay Sievers
2005-12-30 18:56 ` Kay Sievers
2005-12-30 19:12 ` Darren Salt
2005-12-30 19:16 ` Kay Sievers
2005-12-30 19:47 ` Darren Salt
2005-12-30 20:34 ` Kay Sievers
2005-12-30 21:00 ` Darren Salt
2005-12-30 21:45 ` Kay Sievers
2005-12-30 21:58 ` Kay Sievers
2005-12-30 22:51 ` Darren Salt
2005-12-30 23:02 ` Darren Salt
2005-12-30 23:47 ` Marco d'Itri
2005-12-31  0:04 ` Kay Sievers [this message]
2005-12-31  0:20 ` Darren Salt
2005-12-31  0:39 ` Marco d'Itri
2006-01-02 10:35 ` Martin Schwenke
2006-01-04 18:48 ` Patrick Mansfield
2006-01-04 21:23 ` Darren Salt
2006-01-05 12:27 ` Marco d'Itri
2006-01-05 17:03 ` Greg KH
2006-01-05 17:52 ` Greg KH
2006-01-05 18:50 ` patman
2006-01-06  0:50 ` Greg KH
2006-01-06  3:40 ` patman

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=20051231000419.GA7161@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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).