linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Darren Salt <linux@youmustbejoking.demon.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: 082 cdsymlinks
Date: Fri, 27 Jan 2006 17:08:25 +0000	[thread overview]
Message-ID: <4DEFE20BD3%linux@youmustbejoking.demon.co.uk> (raw)
In-Reply-To: <d64a48980601261109s1d3013efu3ca6acf024f7df45@mail.gmail.com>

I demand that Kay Sievers may or may not have written...

[snip]
> 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.

... for some values of "break".

I'm thinking now, given your insistence on generated rules, that perhaps a
sequence number which does nothing more than provide the order in which the
devices should be numbered would be a Good Thing. That way, assuming
hdcÍrom and hddÍrom1 and there are no other cdrom* devices, physically
removing hdc would cause hdd to become cdrom after the next reboot - but hdb
would become cdrom2 regardless (even though this Just Feels Wrong), unless
the system was told that hdc was permanently gone.

This is a matter of compatibility: there are programs and libraries which do
things such as check only /dev/cdrom or default to /dev/cdrom: the VideoCD
input module in xine-lib defaults to /dev/cdrom, and its DVD input module
defaults to /dev/dvd.

Feel free to submit patches :->

-- 
| Darren Salt | d youmustbejoking,demon,co,uk | nr. Ashington,
| Debian,     | s zap,tartarus,org            | Northumberland
| RISC OS     | @                             | Toon Army
|   Let's keep the pound sterling

Money can't buy you friends, but you get a better class of enemy.


-------------------------------------------------------
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

  parent reply	other threads:[~2006-01-27 17:08 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
2006-01-27 17:08 ` Darren Salt [this message]
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=4DEFE20BD3%linux@youmustbejoking.demon.co.uk \
    --to=linux@youmustbejoking.demon.co.uk \
    --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).