On Wed, Nov 02, 2005 at 07:30:18AM -0800, Patrick Mansfield wrote: > 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) . If that does not work well, let me know and we can make the needed changes. > > > 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). Sure. > > 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. ACTION=remove DEVPATH=/block/sdm /sbin/udev block ACTION=add DEVPATH=/block/sdm /sbin/udev block But sure, we may want to add something smarter than this, cause the node will disappear for a short time and the inode number of the node will change which isn't nice if you want to recreate symlinks only. We will need something like this anyway, cause if you change a volume label of a filesystem, you have a similar problem. > > Or do you mean adding a link temporarily, so that it get tracked and > > removed when the device goes away? > > No. Ah bad, that's what I like to have for a pam_console/udev solution. :) Kay -- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
