|
From: Heiko Z. <he...@zu...> - 2010-04-26 15:13:33
|
Hey, Quoting Dominic Raferd <dl...@ed...>: > Regarding udev, I found info at > http://www.reactivated.net/writing_udev_rules.html#why about how it > works which mentions some udev tools - udevinfo, udevtest, udevtrigger, > udevcontrol - which are missing in DL, and might be worth adding. Those are the old tools, they have been replaced by 'udevadm'. Excecute 'udevadm help' for details. > udevtrigger seems to be the way to reprocess udev rules without > rebooting. Altering (or deleting) 70-persistent-net.rules + udevtrigger > + /etc/init.d/network restart should be a way to fix a broken network > connection after a hardware change. At the moment I think you have to > save-config and reboot instead of udevtrigger. We use the the trigger and settle commands in /etc/init.d/boot. > If this worked, then a new option could be added for the network script, > say '-redetect' which would stop the network, delete > 70-persistent-net.rules, then run udevtrigger before starting the > network again. It should also post an advisory message that the change > will not persist under DL unless configuration is saved. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |