On Tue, May 02, 2006 at 11:15:49PM +0200, Joachim Breitner wrote:
> Hi,
>
> Am Mittwoch, den 03.05.2006, 06:44 +1000 schrieb Kel Modderman:
> > Leaving /etc/wpa_supplicant.conf
> > intact if its been modified would go a long way to making the transition
> > a bit smoother.
>
> Doesn't that require leaving the /etc/init.d/wpasupplicant in place, if
> it is used, for exactly the same reasons?
This is exactly the point that confused me, but the bug submitter seem
to have confirmed that he uses custom scripts, which use
/etc/wpa_supplicant.conf, and he was okay with the removal of the system
service.
We are talking here only about the cornercase of some random custom
scripts, which start wpa_supplicant using /etc/wpa_supplicant.conf.
> Maybe a modified version of wpa_supplicant.conf indicates that the
> wpasupplicant setup on that machine should not be touched, including
> config files, init.d script and rc?.d links.
You mean we should leave 'zombie' files around on the filesystem on
package upgrades? Wouldn't that violate Policy?
Gruesse,
Reinhard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
