Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#3407 - WPA support in initscripts - NO example in template
Attached to Project:
Arch Linux
Opened by dtw (dibblethewrecker) - Monday, 31 October 2005, 15:04 GMT
Last edited by arjan timmerman (blaasvis) - Wednesday, 02 November 2005, 10:09 GMT
Opened by dtw (dibblethewrecker) - Monday, 31 October 2005, 15:04 GMT
Last edited by arjan timmerman (blaasvis) - Wednesday, 02 November 2005, 10:09 GMT
|
DetailsRather than reopen the task I figured this would be quicker: why was Andy P's patch for the profile template not included along with his netcfg patch?
http://bugs.archlinux.org/task/3140 We are starting to get really confusion about the wireless scripts in Arch. Judd has done a great job of them but no-one knows about it. Phrak and I are trying to increase awareness and leaving out a mention of the WPA functionaility in the sample profile is just daft! |
This task depends upon
Care to give me a generic WPAOPTS to use as a template?
+#WPAOPTS="" # use this to start wpa_supplicant with the profile
+ # use "" for normal operation or specify additional
+ # options ex "-D ipw"
+ # use /etc/wpa_supplicant.conf for configuration
I figured that was better than nothing and I wondered why it was originally excluded?
I've attached the relevant portion of Andy's patch.
Also added a USEWPA config directive. Otherwise, a blank WPAOPTS will not trigger the bash conditionals where wpa_supplicant is started.