On Sunday 01 November 2009 21:24:28 Frank Schaefer wrote: > Matthew Dharm schrieb: > > On Sun, Nov 01, 2009 at 07:29:20PM +0100, Josua Dietze wrote: > > > >> Frank Schaefer schrieb: > >> > >> > >>> I really think the mode-switching should be done in the kernel and not > >>> in user-space for reasons of usability. > >>> > >> What is wrong with an udev rule entry? By the way, did the "eject" > >> command line tool work as well? > >> > > > > And I think it should be done in userspace for issues of maintainability > > and useability. It is much easier for users to upgrade their udev then > > their kernel. > > > Maintainability for whom ? The kernel-devs or the distro-people and the > users ? ;) > > Please think about the users. They don't know that they have to create > udev-rules or have to install additional packages like usb_modeswitch > (which is nevertheless a great tool !). > And even if they know, they don't want to do that. So it's up to the > distros to do this automatically, which will in reality never come true > for all devices and distros. yes, please think about the users! All not-so-trival-changes have to go through wireless-testing / wireless-next, net-next, linux-next until it hits finally the mainline... And then only users which are able to update their kernels will benefit, *everyone else* has to wait until their distros to pick up the new kernel... this could be easily more than a year before the device will work right out of the box for *everyone else*. Therefore udev should be the way to go... and as a bonus: a userspace/udev solution does work with older kernels right away! Regards, Chr -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
