I have found that the problem lies in the udev package, which has
/lib/udev/devices/null
set to the wrong permission.
Just change the permission of this file to a+rw and at the next boot
/dev/null
will have the same permission.
Daniel
On 9/20/06, Jimmy the shoe <email address hidden> wrote:
>
> I can also confirm on kubuntu dapper. Permissions also get reset after
> reboot like Michael Hirsch. Also, I checked
> /etc/udev/rules.d/40-permissions.rules and have 'KERNEL=="null",
> MODE="0666"' as it should be.
>
> --
> /dev/null permission
> https://launchpad.net/bugs/58509
>
I have found that the problem lies in the udev package, which has devices/ null
/lib/udev/
set to the wrong permission.
Just change the permission of this file to a+rw and at the next boot
/dev/null
will have the same permission.
Daniel
On 9/20/06, Jimmy the shoe <email address hidden> wrote: rules.d/ 40-permissions. rules and have 'KERNEL=="null", /launchpad. net/bugs/ 58509
>
> I can also confirm on kubuntu dapper. Permissions also get reset after
> reboot like Michael Hirsch. Also, I checked
> /etc/udev/
> MODE="0666"' as it should be.
>
> --
> /dev/null permission
> https:/
>