Bug#418641: [pkg-wpa-devel] Bug#418641: group netdev in wpasupplicant configuration file

2007-04-16 Thread Kel Modderman
Restoring CC's to bug + list.

On Saturday 14 April 2007 09:03, giggz wrote:
 I saw that there was a similar bug for avahi-daemon (#385495 for
 example). And a patch from dhcdb was given :

 --8---cut here---start-8---
 --- avahi-daemon.postinst   2006-10-10 23:28:51.0 +0200
 +++ avahi-daemon.postinst_gismo 2006-10-10 23:32:15.0 +0200
 @@ -26,6 +26,11 @@
  usermod -d /var/run/avahi-daemon avahi
  fi

 +# create the netdev group used by dbus
 +if ! getent group netdev  /dev/null; then
 +addgroup --quiet --system netdev
 +fi
 +
  # Ask the bus to reload the config file
  if [ -x /etc/init.d/dbus ]; then
invoke-rc.d dbus force-reload || true
 --8---cut here---end---8---

 what about a similar patch for wpasupplicant... ?

I think we may have to now that wpasupplicant exposes the config 
file /etc/dbus-1/system.d/wpa_supplicant.conf, we also must provide the group 
that is required by that file.

wpasupplicant itself really does not require that group to function, but 
perhaps we can try and take advantage of it in other areas != dbus related.

Thanks, Kel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#418641: [pkg-wpa-devel] Bug#418641: group netdev in wpasupplicant configuration file

2007-04-13 Thread Kel Modderman
On Wednesday 11 April 2007 08:49, giggz wrote:
 Package: wpasupplicant
 Version: 0.6.0~cvs20070224-2
 Severity: normal

 Hi,

 Since a recent update, I have this message during the boot :
 Starting system message bus :Dbus Unknown group netdev in message bus
 configuration file So I have done a grep -ir netdev /etc/* and I found
 that /etc/dbus-1/system.d/wpa_supplicant.conf have a reference to this
 group.

 So I don't known if this bug is a wpasupplicant bug or dbus bug...

wpasupplicant may provide that file, the only way it is used is via dbus.

Kel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]