Comment 14 for bug 317944
Revision history for this message
| Matt Zimmerman (mdz) wrote Re: [Bug 317944] Re: Wrong permissions in /dev after Intrepid->Jaunty upgrade | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
On Mon, Jan 19, 2009 at 12:59:39PM -0000, Scott James Remnant wrote:
> 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 haven't been able to identify any misbehaving packages. Is it feasible to
have it fail in a less horrible way?
--
- mdz