On Saturday, 2004-02-28 at 23:59:32 +0000, Alan Cox wrote: > On Sad, 2004-02-28 at 20:26, Greg KH wrote: > > > > Known problem, use 2.6 :)
> > > Har, har... > > I'm serious. What's keeping you from using 2.6 on your machines? If > > something doesn't work, please let us know so we can make it work. > I'm amazed anyone would recommend 2.6 for production use this early > without knowing how critical the system and its data are. > 2.6 is > just swapping one set of known bugs he's hitting for a mix of known and > unknown bugs, some of which such as acard scsi are corruptors. Actually this machine is not *that* critical. It's my workstation. But I normally install newer 2.4 kernels on that machine first before I upgrade my client's production servers, so I won't run anything I can't run on production systems. And those machines don't *need* anything from 2.6. I'm upgrading kernels mostly for security fixes. > Simply > removing the broken 2.4 usb serial code is a much safer approach. Does anybody have a fix for this? It's more an annoyance than a critical bug, but having the machine crash on a reboot when I forget to unplug the USB serial connection *is* quite annoying for the MD resynch and the manual fscks. I understand 2.6 *has* a fix for this. But it looks like 2.4 is not getting a lot of backporting anymore. Lupe Christoph -- | [EMAIL PROTECTED] | http://www.lupe-christoph.de/ | | "Violence is the resort of the violent" Lu Tze | | "Thief of Time", Terry Pratchett | ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
