From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: 082 cdsymlinks
Date: Thu, 26 Jan 2006 19:16:35 +0000 [thread overview]
Message-ID: <200601262216.36677.arvidjaar@mail.ru> (raw)
In-Reply-To: <d64a48980601261109s1d3013efu3ca6acf024f7df45@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 26 January 2006 22:09, Aaron Griffin wrote:
> Hello all,
> With the removal of %e in udev 082, what do you all do with your
> cdsymlinks?
>
> 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.
> Does anyone have a solution or any ideas at all?
>
Well, I recently posted here a suggestion (with small patch) to create
persistent links for CD-ROMs in /dev/cd (actually in /dev/$env{ID_TYPE}).
This also solves the problem of pam_console - unfortunately it can match on
device name only and removing /dev/cdrom* removed also any distinguishing
name.
Having disks in /dev/disk and CD-ROMs in /dev/cd looks more logical and gives
you persistent names for CD-ROMs. See also recent discussion on lkml on how
to enumerate all available CD-ROMs :)
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD2SAUR6LMutpd94wRAmA9AJ4ibQwzNY/mimz6jnfnfV7yxZKLKQCeILw1
ZurGl/pApzwxTvwRE0kBFh8=wUU6
-----END PGP SIGNATURE-----
-------------------------------------------------------
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 19:16 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 [this message]
2006-01-26 20:27 ` Aaron Griffin
2006-01-26 23:24 ` Kay Sievers
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=200601262216.36677.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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).