On Thursday 31 January 2008 22:01:02 Stephen Gran wrote: > This one time, at band camp, Kel Modderman said: > > Am pretty well informed about ath5k movements with regards to mainline > > inclusion (am involved with madwifi.org team that handles development > > of the non-free madwifi and free ath5k module) but not with debian's > > movements. Thanks for the heads up. > > Cool, wasn't trying to teach you to suck eggs :) Thanks for looking > after madwifi and now ath5k - you've kept several of my laptops > connected over the years.
About the only way I can see Madwifi being a useful package now that ath5k is on the scene is to have madwifi actively claim priority over ath5k by blacklisting it via conffile file in /etc/modprobe.d/ (installed by madwifi-tools package). This is staged for next madwifi-tools upload pending discussion. This way, users of madwifi (who actively install it on their systems) won't be shocked by sudden changes with coming with new linux-image with ath5k. madwifi-tools is a hard dependency of the generated modules package, removing madwifi-tools would cause removal of all active madwifi components on system and allow ath5k a chance. New systems, of course, won't get madwifi-tools installed. Do you think this would be an ok action to take at this stage? Proposed updates are at: http://sidux.net/kelmo/debian/pool/non-free/m/madwifi/madwifi_0.9.4~rc1-1.dsc http://sidux.net/kelmo/debian/pool/contrib/m/madwifi-tools/madwifi-tools_0.9.3+dfsg-4.dsc for anyone interested in trying out with linux-image-2.6.24. Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
