[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Hardware hassles: Linux vs. Windows



Apparently, _Christian Convey_, on 15/12/04 14:48,typed:
Jacob S wrote:

You used a usb trackball as an example in a previous e-mail. But you
also mentioned how it might prompt you for the driver. That helps prove
another person's point about how the hardware vendors write the drivers
for Windows, but not for Linux. Linux programmers have to spend time
writing the driver - without documentation or help from the
manufacturer, Windows programmers just have to worry about plugging in
the driver as needed.


But in my case, there exists both a Windows driver and a Linux driver
for the device in question.  The difference seems to be that in Linux, I
have to go manually configure gpm and xf86 in order to use the
newly-plugged-in trackball.  On windows, it works automatically.

And suppose that for each OS, the OS didn't know how to handle the
device.  Windows will pop up a dialog asking you to supply a driver.
Linux (and KDE/Gnome, I suppose) just let the device sit there,
unusable, without suggesting any course of reparative action to the user.

For instance, if Linux would just say, "Hey, you plugged in a USB device
that I don't really know how to use. I can tell it's a mouse of some
sort, but I don't know how to use it. What's the name of a module that I
should try for it?" then it would be a lot more like my Windows experience.


I think you have a point there. But consider my following experience.

I installed Sid using the Sarge installer on a Dell Inspiron 5160 laptop which comes with Broadcome ethernet card. During installation, the installer said it couldn't recognize the ethernet card and asked me to choose a module from the list it provided. Since I *did* know it was broadcome card, it wasn't difficult to choose the b44 module. I guess this would come close to what you were describing.

But this happened during installation, in text mode. Something like this usually does not happen in GUI mode which you are logged in, i.e. if I am not mistaken. The case in point is when you plug in a USB stick to a USB port. Until the usb-storage module is not loaded, there is nothing you can do about it. And if you plug in your camera's USB cord, you need to have configured usb usermap first. However, I must point out that these issues are being addressed in Linux. Afterall, detecting a USB stick automatically cannot be, and shouldn't be, that hard that every user has to write udev rules (btw, personally I believe that is a quite powerful option).

->HS



Reply to: