From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: 082 cdsymlinks
Date: Thu, 26 Jan 2006 23:24:22 +0000 [thread overview]
Message-ID: <20060126232422.GB24550@vrfy.org> (raw)
In-Reply-To: <d64a48980601261109s1d3013efu3ca6acf024f7df45@mail.gmail.com>
On Thu, Jan 26, 2006 at 01:09:32PM -0600, Aaron Griffin wrote:
> With the removal of %e in udev 082, what do you all do with your cdsymlinks?
%e is not removed now, it's just no longer in the man page and should be
avoided. But sure, some day I'll be happy to remove it, but we need a
simple replacement for the distros/systems that don't do centralized
management.
> You can't really remove them efficiently, because quite alot of apps
> default to /dev/cdrom0 or something similar.
>
> Using a small script to attach the appropriate number (i.e. cdrom2)
> doesn't work either because udev doesn't honor any sort of device
> order, so an end user may end up placing a cd in 3 different drives to
> get xmms to play some audio, for example.
>
> I've noticed none of the 'big distros' have solved this problem yet.
No, on SUSE YaST maintains a rule file, that matches with ID_PATH and
assigns the names for optical devices persistently.
> Does anyone have a solution or any ideas at all?
o Make a simple program, that can be used to edit a dedicated rules file
and let the user pick a device from the list and assign it a name. The
program should have simple subsystem specific knowlege, what properties
can be used for a device. So it could match on SYSFS{address} for network
interfaces and use ENV{ID_PATH} for a cdrom ...
o Or make it automatically write rules for new devices and assign them a
new name. That way you get at least everytime the same name, even when
hardware of the same class is removed from the system which would break
any simple enumeration.
o Use the persistent naming scheme to reference the devices, but that will
obviously not be cdrom, cdrom1, cdrom2.
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://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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:[~2006-01-26 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 19:09 082 cdsymlinks Aaron Griffin
2006-01-26 19:16 ` Andrey Borzenkov
2006-01-26 20:27 ` Aaron Griffin
2006-01-26 23:24 ` Kay Sievers [this message]
2006-01-27 17:08 ` Darren Salt
2006-01-27 20:58 ` Aaron Griffin
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=20060126232422.GB24550@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).