From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Mansfield Date: Wed, 04 Jan 2006 18:48:17 +0000 Subject: Re: new version of udev has different cd/dvd devices Message-Id: <20060104184816.GA4489@us.ibm.com> List-Id: References: <43B313ED.40402@bl.com> In-Reply-To: <43B313ED.40402@bl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sat, Dec 31, 2005 at 01:39:02AM +0100, Marco d'Itri wrote: > On Dec 31, Kay Sievers wrote: > > > Anybody willing to try this? I shouldn't be hard to implement this as a > > shell script. Any code, ideas, comments? > I have been thinking about this for a while. me too ... mainly for scsi disks. > So far I collected these factoids: > > - there is no other component which ? > - it would be nice if links to CD/DVD drives were assigned in bus order, > as it used to happen with %e. How? > - this does not need to be perfect, but it should not create surprises > for the common cases. > - OSS sound devices are harder, there are a set of different devices > whose indexes must be kept in sync. > - it should really be a shell script A simple script that generates rules to create /dev's under (perhaps) /dev/user that are the same as the current kernel name based on a match with ID_SERIAL (of course handling name collisions and more) would be useful. Users could then edit the rule file to create "nicer" names. IMHO, there should eventually be both command line and gui interfaces (built on top of the same underlying code), as a gui (even curses like interface) is probably better for displaying the device names and attributes, and selectively modifying policies if you have many devices/disks i.e. columns with check boxes for enabling particular policies and/or names. Also: - allow selection of policies, so for example, you can have by-id, by-path, or user-named. So we don't always create by-id, by-path or user-named. The items I stumble on are: How do you know if an attribute (mainly the id / serial number) for the device is useful as a persistent attribute? Do you assume all are invalid, valid, or what? Should or how do you integrate this into the installer? It is bad to *not* allow naming or use of by-id at install time, but then later require it to mount root. Mount by label solves this for many but can't handle a disk being duplicated/backed up. I guess you can just run the scripts from the installer. -- Patrick Mansfield ------------------------------------------------------- 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_id865&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