Bug#749109: Bug#748679: Add autoconfiguration script for live-config
- To: Gaudenz Steinlin <gaudenz@debian.org>
- Cc: 749109@bugs.debian.org
- Subject: Bug#749109: Bug#748679: Add autoconfiguration script for live-config
- From: intrigeri <intrigeri@debian.org>
- Date: Tue, 19 Aug 2014 12:37:57 +0200
- Message-id: <[🔎] 85zjf0933u.fsf@boum.org>
- Reply-to: intrigeri <intrigeri@debian.org>, 749109@bugs.debian.org
- In-reply-to: <871tuukkv5.fsf@meteor.durcheinandertal.bofh> (Gaudenz Steinlin's message of "Thu, 12 Jun 2014 21:07:10 +0200")
- References: <20140519152413.32654.50174.reportbug@meteor.durcheinandertal.local> <53805D2D.6080805@progress-technologies.net> <87egyy6v8b.fsf@meteor.durcheinandertal.bofh> <5395C58F.9070804@progress-technologies.net> <871tuukkv5.fsf@meteor.durcheinandertal.bofh>
Hi Gaudenz,
meta:
* I'm replying on #749109, as this part of the discussion is about
code that's being added to live-config, not to broadcom-sta.
* Daniel: sorry for the useless ping sent earlier this month on
#748679, I was confused by the remaining tags left there
after cloning.
* I've tried to clarify the status of these two bug reports in the
BTS, and the relationship between them, which seemed very confusing
to me initially; sorry if I messed something up.
Gaudenz Steinlin wrote (12 Jun 2014 19:07:10 GMT) :
> - In some parts it looks like it should be a general wlan driver
> selection mechanism. Which would be great, but then overrides are
> stored in /usr/share/live/config/broadcom-sta/ and the script is
> called 1190-broadcom-sta.
I've seen broadcom-sta support requested quite often on the Tails user
support channels, while I don't remember anything similar for other
drivers, so I say let's get the ad-hoc support for broadcom-sta in
first, hopefully in time for Jessie, and then we'll see if/how it can
be generalized. Fair enough?
> - It uses 14e44 as a first filter in the script. While it's true that
> the ID of all currently supported devices starts with this string, the
> broadcom vendor ID is only 14e4. The last 4 is part of the device ID.
> - The blacklisting logic is the wrong way around. If broadcom-sta is
> selected as a driver, all entries in
> /etc/modprobe.d/broadcom-sta-dkms.conf should be blacklisted. If it's
> not selected, they should NOT be blacklisted. Additionally the wl
> kernel module should be blacklisted in this case.
> - checking for a state file makes this script basically useless with
> persistency on removable media. When moving to live media (ie USB
> stick) from one system to another you want to rerun this script each
> time. State files are nice for user preferences, but I don't see a use
> case for them for hardware configuration.
Care to provide a patch that fixes these problems?
Cheers,
--
intrigeri
Reply to: