From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Tue, 02 Dec 2003 00:55:57 +0000 Subject: Re: [ANNOUNCE] udev 007 release Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Mon, Dec 01, 2003 at 11:51:19AM +0100, Marco d'Itri wrote: > On Nov 26, Greg KH wrote: > > >> NUMBER, BUS="ide", id="0.0", NAME="ide/host0/bus0/target0/lun0/%N" > >> NUMBER, BUS="ide", id="0.1", NAME="ide/host0/bus0/target1/lun0/%N" > >> NUMBER, BUS="ide", id="1.0", NAME="ide/host0/bus1/target0/lun0/%N" > >> NUMBER, BUS="ide", id="1.1", NAME="ide/host0/bus1/target1/lun0/%N" > >> NUMBER, BUS="ide", id="0.0", type="cd", NAME="ide/host0/bus0/target0/lun0/cd" > >> NUMBER, BUS="ide", id="0.1", type="cd", NAME="ide/host0/bus0/target1/lun0/cd" > >> NUMBER, BUS="ide", id="1.0", type="cd", NAME="ide/host0/bus1/target0/lun0/cd" > >> NUMBER, BUS="ide", id="1.1", type="cd", NAME="ide/host0/bus1/target1/lun0/cd" > > > >Hm, two different rules for the same id. Not a good idea, udev can not > >handle this. How about a LABEL rule for a cd instead. > I tought that a sysfs attribute would have been enough to disambiguate > the rules. Yeah, that would work. I just fixed a bug where the NAME was the same, but the BUS was different. That previously didn't work at all. Care to send a patch? > >> And this could be a possible syntax for managing symlinks: LINK would > >> work just like NUMBER, but NAME would be a symlink to the device > >> specified: > >> > >> # a trailing / means that the link will be done to the parent directory > >> LINK, BUS="ide", id="0.0", NAME="discs/disc0/" > >> LINK, BUS="ide", id="0.1", NAME="discs/disc1/" > >> LINK, BUS="ide", id="1.0", NAME="discs/cdrom0" > >> LINK, BUS="ide", id="1.1", NAME="discs/cdrom1" > > > >No, I think multiple NAME values on a line would be the best thing, but > >that will take some major tweaks to udev to get there. We will get > >there... > Multiple names have the downside that admins will have to modify the > "standard" rules, while with different rules they could just add the > appropriate aliases at the end of the config file. True. Ok, well, as neither are implemented yet, it's not really a big deal right now :) > >And then as your last REPLACE rule do: > > REPLACE, KERNEL="tty*", NAME="vc/%n" > I tried it, but it does not work. (And what about /dev/tty?) Care to enable DEBUG_PARSE in namedev.c and send me the output when trying this? Along with your config files. thanks, greg k-h ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ 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