*** This bug is a duplicate of bug 38203 ***
** This bug has been marked a duplicate of bug 38203
40-permissions.rules includes non-existent groups
--
40-permissions.rules incorrectly has an nvram group
https://launchpad.net/bugs/51340
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
No idea but it's not on any of the machines I have here, and have polled
some friends about it.
--
40-permissions.rules incorrectly has an nvram group
https://launchpad.net/bugs/51340
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
oh, interesting; where did the nvram group go?
** Changed in: udev (Ubuntu)
Status: Rejected => Confirmed
--
40-permissions.rules incorrectly has an nvram group
https://launchpad.net/bugs/51340
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
While I'm at it, my /etc/nsswitch.conf contains this:
passwd: files ldap
shadow: files ldap
group: files ldap
i.e. check files for users and groups first, then fall back to ldap. The
nvram group doesn't exist locally so ldap is tried next.
--
40-permissions.rules incorrectly has an
My system does not have an nvram group. Nor does any other dapper box
I've used. I have not modified /etc/{passwd,shadow}, this group is
incorrectly referenced in 40-permissions.rules and beacuse of this nss
attempts to look for the group in ldap before the network has been
configured and introduce
You should leave the standard system users and groups in /etc/passwd
otherwise the system will not boot correctly -- this is standard
practice
** Changed in: udev (Ubuntu)
Status: Unconfirmed => Rejected
--
40-permissions.rules incorrectly has an nvram group
https://launchpad.net/bugs/513
