Op 21 okt. 2011, om 08:54 heeft Phil Blundell het volgende geschreven: > On Fri, 2011-10-21 at 03:31 +0000, Otavio Salvador wrote: >> +USERADD_PACKAGES = "${PN}" >> +GROUPADD_PARAM_${PN} = "-r netdev" >> +USERADD_PARAM_${PN} = "--system --home ${localstatedir}/lib/dbus \ >> + --no-create-home --user-group messagebus" > > Why does dbus need "netdev"?
A little digging on the internet shows that some applications using dbus use netdev and as a result dbus will complain about a missing netdev group. Dbus itself doesn't seem to need it. A handfull of searchresults imply that not dbus but e.g. networkmanager and wpa-supplicant should create the group, but: root@beagleboard:/etc/dbus-1/system.d# ls ConsoleKit.conf org.freedesktop.PolicyKit1.conf NetworkManager.conf org.freedesktop.UDisks.conf avahi-dbus.conf org.freedesktop.UPower.conf bluetooth.conf org.freedesktop.hostname1.conf dbus-wpa_supplicant.conf org.freedesktop.locale1.conf gdm.conf org.freedesktop.login1.conf nm-avahi-autoipd.conf org.freedesktop.systemd1.conf nm-dhcp-client.conf org.freedesktop.timedate1.conf nm-dispatcher.conf org.gnome.GConf.Defaults.conf root@beagleboard:/etc/dbus-1/system.d# grep netdev * root@beagleboard:/etc/dbus-1/system.d# So it seems (but I am not certain!) that netdev is a relic of the past and can go away. What I would propose: 1) convert the existing *inst to useradd.bbclass 2) bump PR, remove netdev That should give us a nice bisectable stack of commits. regards, Koen _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core