Coercing users is *never* a good idea [LWN.net]

Coercing users is never a good idea

Posted Jun 8, 2006 12:43 UTC (Thu) by bjanz (guest, #1560)
Parent article: Putting a lid on USB power

I agree that standards should be followed as closely as possible.

That being said, this change may have one significant "political" factor that seems to have been ignored: if the same device works under MS Windows but doesn't work under Linux, Linux will blamed. Period. And, if one of the myriad of "technology reporters" finds out that he can't use his mouse (the author's example, not mine), the bad news for the Linux community will be hard to overcome.

For some of us "road warriors", a way to power our hubs is not always available. But, we still need to use our USB devices. Hence, without commensurate instructions ("scary warnings" *as well as* "what-to-do's"), you may be shutting me down while I'm using my laptop on its internal battery. This is a *VERY BAD THING*.

Doing "the right thing" is not always the best thing to do. In this case, the Linux community may have acted exactly the way it claims Microsoft acts: "We know what is good for you -- even better than you do."

Me? I'll be writing the necessary UDEV rules to ensure that the devices I'm currently using *continue* to work the way they always have. And, if I "blow out" my hardware, ok. It would have blown out under MS Windows, too.

Hardware is cheap, folks. Much cheaper than a damaged reputation.

\burt

(Log in to post comments)

Coercing users is *never* a good idea [Unless they already expect perfection]

Posted Jun 8, 2006 15:50 UTC (Thu) by smoogen (subscriber, #97) [Link]

The issue is that Linux will get the blame either way. The following is a real world example.

We had a user who had an external USB drive that got its power off of his laptop along with his keyboard, mouse and LED light so he could work on his red-eye flights on the plane etc. His data got corrupted on the USB drive and it was Linux's fault. Turns out that his data had been corrupted regularly on his Windows side.. but he had come to expect that as a standard Windows bug. Turns out that we had a whole class of users who had been having the same problem with their windows systems, but had found it to be a known bug for the USB drive and just took it as an oh-well. It only became a 'known problem' to central support once Linux started corrupting data.

So, if your data is corrupted on your remote USB drive in Windows because it couldnt get enough power.. well thats what 99% of the world has come to expect of Windows. If you have that happen under Linux.. it is Linux's fault because it is supposed to be better.

Coercing users is *never* a good idea

Posted Jun 8, 2006 16:05 UTC (Thu) by ebirdie (subscriber, #512) [Link]

Hardware may be cheap, but data put into it isn't.

Secondly in my technopolitical experience many people would put data loss under their legitimacy Windows system to law of nature and data loss under a Linux system to untrustable technology, reputation damaged.

What comes to political correctness, at times Linux community is blaimed to follow Windows trails. Here I find it responsible as any other act put into fs- and block-layer to protect user's data (ata-drive cache issue comes to mind here). Although I admit, there will be fierce moments of frustration due to policy change unknown or forgotten at the moment of unusable USB-drive.

At the moment USB-drive doesn't mount it is very simple and inherent on Linux system to "dmesg | tail" and you are reminded and on your way to make it work. Well, some kernel messages leave space for better glue into the event/issue - at least to mere mortal like me.

Previous brings me to GUI, where I haven't yet found a configurable tool (window), which pops up when noticable things hapen in syslog as easily as manually doing "dmesg |tail" thus making a kernel message "usb-core: USB device not connected due to too high power requirement from USB-bus, change kernel policy or connect your USB device to external power." wipe away whole issue.

Coercing users is *never* a good idea

Posted Jun 8, 2006 21:36 UTC (Thu) by bjanz (guest, #1560) [Link]

"That's right! So buy a $5.00 wall wart. Corrupted data causes farm more damage to reputation than the ability to run hardware outside of specification... doesn't it?"

You're missing the point. Someone who is running a device under MS Windows will question *and then abandon* Linux if the same device does *not* run under Linux.

If I buy a $5.00 WalMart cheap POS adapter, it'd blow up my system whether I was running MS Windows *or* Linux -- and I deserve what I get. But, if I buy a Logitech mouse or keyboard, or a SanDisk USB drive, or some other USB 2.0 "bus powered" device that is properly made and meets the USB 2.0 spec (like a Western Digital 120GB drive), and they *DON'T* work under Linux... that's a *very bad* thing.

This isn't about plugging in crap components. It's about compatibility. The only way to get new users comfortable with Linux is to provide *MORE* compability with existing devices -- not *LESS*. The way to keep "marginal" Linux users from migrating to other platforms (such as FreeBSD, or - Lord help us - Windows) is to be *BETTER* than the other platforms.

I opened my comments by saying that standards are a good thing. I'll even say that operating hardware according to standards is an even better thing. Protecting your system from unpredictable power events is an *excellent* thing.

But, a *backward* move in compatibility - "less" is NOT "more" - will only be seen as a *bad* thing.

Coercing users is *never* a good idea

Posted Jun 9, 2006 21:22 UTC (Fri) by Pedja (guest, #37794) [Link]

"But, if I buy a Logitech mouse or keyboard, or a SanDisk USB drive, or some other USB 2.0 "bus powered" device that is properly made and meets the USB 2.0 spec (like a Western Digital 120GB drive), and they *DON'T* work under Linux... that's a *very bad* thing."

If I understand corectly, kernel disables out-of-spec devices.So, how
can that WD 120GB drive, or any other properly made, by-the-specs, device
not work under Linux?
IMHO, this is a GoodThing[tm].
Why would Linux support badly made hardware?

Coercing users is *never* a good idea but protecting hardware usually is

Posted Jun 11, 2006 11:16 UTC (Sun) by jmayer (subscriber, #595) [Link]

I always assumed that the power protection was there. It never occurred to me, that Linux was skipping the check. Now I understand that the problems I'm seeing with the USB ports on my laptop is one of broken hardware: ehci worked fine in the beginning, but after I connected a usb-powered harddrive for the first time ehci would work only sometimes. To me it looks like my USB hardware got fried.
The correct way to implemnent this is to turn it on to protect the hardware and make it possible to either turn off the check manually (in a global or per device way) or to manually change the powerlevel, e.g. if your hardware works reliably up to 200mW, then why not be able to change the limit to that value.