On Wed, Nov 02, 2005 at 03:53:45AM +0100, Kay Sievers wrote: > Sure, that may be easier. > But such a tool is only useful if the devices are already present on the > system, right? Then you can read all current available ID_* variables from > the udev database and compose a nice rule from it. :) Yes looks like that can work (again I *was* thinking symlinks, and not env variables) . > > And is there a way to rename or add /dev entries without removing and > > adding back a device? > > You can run udevstart again, if its not configured to do some weird > stuff. That is rather slow, and didn't removing links (like a rename would want). > The current devel kernel has a "uevent" file, which triggers the > hotplug event again, this could be used to create additional configured > links. > > Also: > ACTION=add DEVPATH=/block/sdm /sbin/udev block > would do it. Those don't remove links either. > Or do you mean adding a link temporarily, so that it get tracked and > removed when the device goes away? No. Thanks, -- Patrick Mansfield -- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
