On Mon, 2009-01-19 at 12:38 +0000, Matt Zimmerman wrote: > > The /dev/.udev/db have been touched as well, which heavily implies that > > udev was triggered. > > > > With the rules being moved, it is possible that the trigger would reset > > the permissions to 0660. > > Why would a trigger set the permissions to 0660 when the udev rule calls for > 0666? > Because the running udev can't parse the new configuration files? (It doesn't even look in the right place for them.)
If something forced udev to reload its configuration (which has gone away), then it would end up with none, so fallback on defaults (root:root/0660) > I'm currently grepping through the package contents for anything suspicious. > One thing which caught my eye was the new LSB init script dependency > comments (e.g. Required-Start: udev in pcmciautils). Could these have > caused the udev init script to be run somehow? > Not that I know of - that would have actually unmounted /dev which I would expect to have a few more drastic consequences Scott -- Scott James Remnant sc...@canonical.com -- Wrong permissions in /dev after Intrepid->Jaunty upgrade https://bugs.launchpad.net/bugs/317944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
