[Bug 1522313] Re: Wrong /dev/null permissions after boot
Hinko Kocevar
1522313 at bugs.launchpad.net
Mon Feb 29 12:41:02 UTC 2016
Thanks. I fixed my rules and now /dev/null is OK.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1522313
Title:
Wrong /dev/null permissions after boot
Status in systemd package in Ubuntu:
Invalid
Bug description:
After running update today (on Ubuntu 15.10) and rebooting the OS
lightdm would not start. After some debugging I noticed that /dev/null
(and some other /dev files) do not have adequate permissions (compared
to another Ubuntu box I have) - e.g. 'others' could not read nor write
/dev/null.
After 'chmod a+rw' offending files, lightdm started up. Of course this
is not reboot persistent so I need to put this in some /etc/rc.* to
make it stick - which I do not want to!
To fix this problem after reboots I added /etc/init.d/fix-dev.sh
script with contents, and symlink to /etc/rcS.d/S14fix-dev.sh (last
entry):
chmod a+rw /dev/null /dev/random /dev/urandom /dev/ptmx /dev/tty
/dev/zero /dev/full /dev/fuse /dev/net/tun
My system now starts the lightdm as it did before.
$ lsb_release -rd
Description: Ubuntu 15.10
Release: 15.10
apt-cache policy udev
udev:
Installed: 225-1ubuntu9
Candidate: 225-1ubuntu9
Version table:
*** 225-1ubuntu9 0
500 http://se.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1522313/+subscriptions
More information about the foundations-bugs
mailing list