On Mon, 2009-01-19 at 08:51 +0000, Matt Zimmerman wrote: > > Do you think something might have actually done "find | chmod" and > > escaped and run across /dev for some reason? > > I've looked around the filesystem a bit, and nothing looks out of the > ordinary outside of /dev. > > You can see in the stat output that only the ctime changed, so it's the > original device node which was created by udev, but has been mangled by > something. > 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. This is a pretty bad side-effect, so we should probably at least stop the udev daemon on upgrade. But this doesn't solve what's done it for you - as that's another bug. I'd rather leave the symptom there for now otherwise we're hiding something else. > > Do you happen to have system logs from the upgrade time, there may be > > messages that give us a clue what happened. > > I have the dist-upgrader logs which look fairly complete, and will attach > those. The timestamps in the log confirm that the ctime on /dev/null was > during the upgrade, and narrows down the possible packages (somewhere from > netbase to gsm-utils): > Notably udev isn't in this list. 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
