On Mon, Feb 15, 2010 at 01:35:53PM -0500, Brad Jorsch wrote: > On Mon, Feb 15, 2010 at 06:24:06PM +0000, Debian Bug Tracking System wrote: > > > > On Feb 15, Brad Jorsch <[email protected]> wrote: > > > > > When udev rules are updated, a user might want to trigger udev to > > > process those rules. "udevadm trigger" seems to be the tool for the job, > > > but apparently the default --action=add can cause bad things to happen > > > and --action=change is a better idea for normal use.[1] > > There is no normal use. If users do not understand how udev works they > > have no business in writing new rules. > > Running commands you do not understand as root is always a bad idea. > > That's BS. How is anyone ever supposed to *learn* how it works if the > documentation is incomplete?
Or, for that matter, outright *wrong*. On a hunch I checked the documentation provided with this package itself,[1] and sure enough that also gives the wrong command. Why not just fix the bug, instead of insisting that only members of the udev priesthood should consider writing and debugging a udev rule? [1] file:///usr/share/doc/udev/writing_udev_rules/index.html#testing -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
