On Mon, 2009-11-02 at 21:10 +0100, Frank Schaefer wrote: > Matthew Dharm schrieb: > > On Sun, Nov 01, 2009 at 09:11:49PM +0100, Frank Schaefer wrote: > > > >> Josua Dietze schrieb: > >> > >>> 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? > >>> > >> It returns an error but the device is ejected. > >> But do you really want the users to open a terminal window and call > >> "eject" each time they plug their device in ;) ? > >> > > > > If 'eject' worked, then why not use a simple udev entry? That way nobody > > has to call anything by hand... > > > > Matt > > > And who will create this udev-entry ;) ? How can you make sure that this > is done on all systems ? You can't. The distros have to make sure it works. Personally, I think these should all be in the kernel, but the kernel doesn't contain policy. And unfortunately, for some devices (3G modems specifically) ejecting the driver CD thing *is* policy. Option for example protested mightily when I sent a patch to auto-eject their driver CD, because they apparently do use the driver CD thing to send Linux drivers and software to a few clients. But by and large, the driver CD is completely useless. Devices with fake driver CDs and how they are handled currently: Zydas WLAN - kernel Huawei 3G - kernel (unusual_devs entry) Sierra 3G - kernel (drivers/usb/serial/sierra.c) Option 3G - udev rules, 'rezero', or usb_modeswitch ZTE 3G - udev rules, simple 'eject' Dan -- 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
