If anyone asks me, declaring removable devices in allow-hotplug would
make more sense, since we'll typically wanna run perform ifup actions
upon connecting the device to the computer. In the case of WiFi
dongles used as AP, we'll typically wanna load the configuration file
defined via the "hostapd
Package: bridge-utils
Version: 1.6-5+b1
Followup-For: Bug #981076
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Having further googled this and made a few tests, the key difference seems to
be whether the removable devices are declared in the auto or in the
allow-hotplug lines of
Package: bridge-utils
Followup-For: Bug #981076
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This mess is the result of the kernel maintainers changing their mind on how
the bridge module should work. This isn't bridge-utils' fault. bridge-utils
merely tries to adapt to those changes and
Package: bridge-utils
Version: 1.6-5+b1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de, n...@naturalnet.de
I’m shocked to read this in apt-listchanges so shortly before a release:
bridge-utils (1.6-4) unstable; urgency=low
Linux kernel has changed bridge MAC address selection.
In older
4 matches
Mail list logo
