USB mass storage backport status?
What's the real status of the mass storage backport to 2.2.18? Some people report it can corrupt your data, another that it rebooted his computer while doing a large trasnfer, and so on.
If it's not good, shouldn't it be removed or labeled DANGEROUS? BTW, where can I see a list of what's backported and working without major problems?
Signature · 5 lines
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/Depending on the type of device you have and how you use it, it can either:
(1) Work properly
(2) Corrupt your data
(3) Crash the driver
(4) Crash your system
It's allready labeled EXPERIMENTAL. Perhaps it should be labeled DANGEROUS, also, but how many labels can you put on things to warn people off?
Matt Dharm
Quoted 14 lines · Frédéric L . W . Meunier
What's the real status of the mass storage backport to 2.2.18? Some people report it can corrupt your data, another that it rebooted his computer while doing a large trasnfer, and so on.
If it's not good, shouldn't it be removed or labeled DANGEROUS? BTW, where can I see a list of what's backported and working without major problems?
Signature · 5 lines
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Signature · 6 lines
Matthew Dharm Home: [email protected] Maintainer, Linux USB Mass Storage Driver Umm, these aren't the droids you're looking for. -- Bill Gates User Friendly, 11/14/1998
Quoted 5 lines · Matthew Dharm
Depending on the type of device you have and how you use it, it can either:
(1) Work properly
(2) Corrupt your data
(3) Crash the driver
(4) Crash your system
The reboot was about Iomega's Zip Drive under 2.2.18pre21:
http://slashdot.org/comments.pl?sid=00/12/11/2355217&threshold=0&commentsort=1&mode=thread&cid=110
Quoted 3 lines
It's allready labeled EXPERIMENTAL. Perhaps it should be labeled DANGEROUS, also, but how many labels can you put on things to warn people off?
Hmm, where? I don't see an (EXPERIMENTAL) inDocumentation/Configure.help:
USB Mass Storage supportCONFIG_USB_STORAGE
Say Y here if you want to connect USB mass storage devices to your computer's USB port.
This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called usb-storage.o. If you want to compile it as a module, say M here and read Documentation/modules.txt.
USB Mass Storage verbose debug CONFIG_USB_STORAGE_DEBUG
Say Y here in order to have the USB Mass Storage code generate verbose debugging messages.
Maybe it's only enabled when you set CONFIG_EXPERIMENTAL? I don't know, because I enabled it to just set CONFIG_FB.
Quoted 8 lines · Frédéric L . W . Meunier
Quoted 7 lines
What's the real status of the mass storage backport to 2.2.18? Some people report it can corrupt your data, another that it rebooted his computer while doing a large trasnfer, and so on.
If it's not good, shouldn't it be removed or labeled DANGEROUS? BTW, where can I see a list of what's backported and working without major problems?
Signature · 5 lines
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/AAAHHHHHHHHHH!
Okay, this must have changed somewhat recently. When last I spoke to Alan Cox (the maintainer of the 2.2.x code), I told him (and he agreed) that this code should be marked EXPERIMENTAL. If it's not marked thus in 2.2.18pre21, then it's an error and should be corrected ASAP.
Matt Dharm
Quoted 51 lines · Frédéric L . W . Meunier
Quoted 5 lines · Matthew Dharm
Depending on the type of device you have and how you use it, it can either:
(1) Work properly
(2) Corrupt your data
(3) Crash the driver
(4) Crash your systemThe reboot was about Iomega's Zip Drive under 2.2.18pre21:
http://slashdot.org/comments.pl?sid=00/12/11/2355217&threshold=0&commentsort=1&mode=thread&cid=110
Quoted 3 lines
It's allready labeled EXPERIMENTAL. Perhaps it should be labeled DANGEROUS, also, but how many labels can you put on things to warn people off?
Hmm, where? I don't see an (EXPERIMENTAL) in
Documentation/Configure.help:USB Mass Storage support
CONFIG_USB_STORAGE
Say Y here if you want to connect USB mass storage devices to your computer's USB port.This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called usb-storage.o. If you want to compile it as a module, say M here and read
Documentation/modules.txt.USB Mass Storage verbose debug
CONFIG_USB_STORAGE_DEBUG
Say Y here in order to have the USB Mass Storage code generate verbose debugging messages.Maybe it's only enabled when you set
CONFIG_EXPERIMENTAL? I don't know, because I enabled it to just setCONFIG_FB.Quoted 8 lines · Frédéric L . W . Meunier
Quoted 7 lines
What's the real status of the mass storage backport to 2.2.18? Some people report it can corrupt your data, another that it rebooted his computer while doing a large trasnfer, and so on.
If it's not good, shouldn't it be removed or labeled DANGEROUS? BTW, where can I see a list of what's backported and working without major problems?
Signature · 5 lines
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Signature · 6 lines
Matthew Dharm Home: [email protected] Maintainer, Linux USB Mass Storage Driver God, root, what is difference? -- Pitr User Friendly, 11/11/1999
Quoted 4 lines
Okay, this must have changed somewhat recently. When last I spoke to Alan Cox (the maintainer of the 2.2.x code), I told him (and he agreed) that this code should be marked EXPERIMENTAL. If it's not marked thus in 2.2.18pre21, then it's an error and should be corrected ASAP.
It is marked experimental, but the help text is from 2.4test and doesnt say that. The experimental option is needed and the question asked does say (EXPERIMENTAL)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/