LinuxWorld Response to 'How to Kill Linux'

aneroid writes "In response to John Dvorak's "How to Kill Linux" column, LinuxWorld has a riposte to the columnist's assertations. From the article: "Because most of the time, with mainstream devices, I work out of the box. For the "savvy user" and OEM builder, the Linux driver "problem" isn't the problem it was. The days when my poor user had to sweat blood to get me onto a laptop are long gone. Sure, if I get slung onto some random old machine there are still wrinkles, but from what I see on the Windows support forums, that's hardly unique." <update> The story is actually from GrokLaw originally - credit where credit is due.

Comments

Um, do you even need to bother replying to Dvorak

[antifoidulus]

This is the man that a year ago predicted that in 6 months, not only would OS X run on x86, Apple would produce a dual PPC/x86 computer to help ease the transistion. He wasn't even remotely right on either of these.
IE he gets paid a decent amount of money to talk out of his ass, and it's not really even worth thinking about a response to the drivel that spews from his (mouth/pen/keyboard?)

groklaw ran this on friday...

[Mark19960]

here is a link to the groklaw story

Re: I have a jar of blood in the garage to prove i

[FidelCatsro]

Those days are long gone , my primary x86 laptop( Gericom , not well known outside germany ) runs debian unstable, after a quick ftp install all i have to do is type "apt-get install acpid" it really couldnt be easier , well infact it could and can be.
Simply use suse 9.2 , it fully recognised my laptop and configured it perfectly .
also iirc it has predefined configs for hundreds of laptops

Wireless on Windows?

[ca1v1n]

Has anyone tried making wireless work on *Windows* lately? Sometimes it works out of the box. Usually, on the same machine even, with high-quality hardware and complete driver support, it fails inexplicably, or worse, the error message report conditions inconsistent with observed behavior. Wireless on Linux may be a pain, but at least it's deterministic.

Re: I have a jar of blood in the garage to prove i

[Anonymous Coward]

Debian is not exactly a distro reknowned for its friendliness - Mandrake might have been a better choice as a first distro, IMHO...

Debian, however, is amazing if you're adminning 200+ machines for demanding scientific/engineering users. Nothing comes close to the attention to detail of the package system because debian treats even slight upgrade issues as bugs. Almost everything users ask for is already in main or contrib.

Wrinkles with old hardware?

[rxmd]

Sure, if I get slung onto some random old machine there are still wrinkles, but from what I see on the Windows support forums, that's hardly unique.

My experience is exactly the other way round. With older hardware, the chance that it's still supported under Linux is much better than under recent Windows versions. With new hardware, problems have been much more frequent. There's a reason why people choose Linux instead of Windows for older boxen.

With newer hardware, I think there's a future for driver wrapper projects. Look at FreeBSD's NDIS driver wrapper (aka "Project Evil"): that way, FreeBSD can use Windows network card drivers out of the box, it's convenient, and it's even reasonably fast.

Windows driver problems are the worst!

[SendBot]

From my own experience, I can attest to two separate windows driver nightmare situations.

The first is more of an annoyance than a nightmare. The place where I work has been buying new dell machines of various models. A fresh installation from the Windows SP2 cd it comes with does not have any drivers for the intel based network, video, and a couple other misc devices. I think the sound chipset is something else, and it doesn't support that either.

Fortunately, dell packs a separate cd with drivers on it, and it refuses to run on non dell machines if you have the same hardware and are stuck in that situation. Plus, if you dig hard enough you can probably find drivers on the internet.

I'd like to point out that in this situation, the mega trio of Dell, Intel, and Microsoft cannot provide a system that installs an OS off the cd and has working video/sound/network. Pretty lame.

The second situation involves a coworker's recent purchase of a sony vaio that is rife with severe annoyances. For instance, if you uninstall norton internet security before it expires and nags you to death, your entire network subsystem eats shit and refuses to do anything. That was fun.

But more relevant to this topic, windows has practically no builtin driver support for it, and it doesn't even come with any drivers on cd! They expect you to make a 10 cd backup (or 2 dvd's and one cd) so that you can restore your system if necessary. If you ask sony support for drivers, they direct you to purchase a cd (set?) that may solve the issue for $12. Absolutely no option to download drivers.

I'm not entirely sure, but I think the sound won't even work properly unless you have some magic sony-blessed drm drivers.

In both of these cases, knoppix and gentoo boot fine and support all of the devices (except maybe the vaio's wireless.. I didn't try).

ps. don't buy sony laptops, they are crippled with drm services and shitware.

L vs. W

[Anonymous Coward]

I think they're both at the point that people prefer them for a specific philosophy more than one being 'better' than another. I think if you really got down to it and pushed, each side would have to admit that the other side got some things right.

The thing is that in a few years, the technology is going to be to the point that both systems can do everything that the other system can.

I manage 300 + Windows 2003 servers, and I don't have any crashing issues at all unless hardware actually fails. So the BSOD thing doesn't hold any water anymore because current Windows operating systems are fairly stable. The downside is you have to reboot for patches and stuff - which is something I think Linux should promote as a big upside that I don't see much. I care more about that than I do about the BSOD arguments for Windows 98.

I think at this point one of the only real things I see as a drawback for Linux is that in a lot of ways it isn't one operating system. When I do get an error on something, I can't usually put in 'Linux' and the error (like I can with Windows) - because each specific build is like its own operating system. The setup of SuSE, Debian, Gentoo, etc is different enough that they're almost different operating systems from a support standpoint.

I also think that Novell has realized that a big thing that Windows has going for it is you can go to one vendor and get a complete enterprise system that works, is supported, has a directory management system, email, etc. They're on their way to making that a reality.

In short - they both have benefits, but I think THE benefit that I see is that as long as they both provide competition, it benefits the end user. I think most of us don't WANT to see either Linux or Windows dominate, because it would slow advancement - or at least to have 2+ systems as serious contenders (can Apple get there?).

So many arguments you could make, but it is all relative. Maybe Einstein had something there ;)

Re:Kudos to LinuxWorld

[Jussi K. Kojootti]

This sounded so wierd that I had to google for it, and no shit:

John C. Dvorak:
"IDLE-TIME PROCESS. Once in a while the system will go into an idle mode, requiring from five minutes to half an hour to unwind. It's weird, and I almost always have to reboot. When I hit Ctrl-Alt-Delete, I see that the System Idle Process is hogging all the resources and chewing up 95 percent of the processor's cycles. Doing what? Doing nothing? Once in a while, after you've clicked all over the screen trying to get the system to do something other than idle, all your clicks suddenly ignite and the screen goes crazy with activity. This is not right." (link)

The dreaded resource-hogging Idle process... I hope my computer never catches that.

Re: I have a jar of blood in the garage to prove i

[Canadian_Daemon]

So, basically ALL the benefits of having a laptop. Go linux! It's DEFINITELY ready for the mainstream
I am typing this from a laptop, and it runs Linux (Oh No!). Has APCI, CPU Throttling, Suspend, Wireless networking, etcetera.
How did I do it? Days of patches? No, popped in Mandrake 10.1 Community, generic install, everything ran perfectly, I don't think that you need to be a zealot to install linux on a laptop, Linux has come a long way in the last few years.

I see lots of claims, but no specifics.

[khasim]

Some people claim that Linux sucks.

Some people claim that Linux is great.

But I don't see much in the way of SPECIFICS.

Here are some. I can boot Knoppix 3.6 on the following laptops and have EVERYTHING work without additional tweeking.

IBM T23
IBM T40

Anyone who claims that Linux has problems on laptops needs to post
WHAT problems
WHICH laptops
WHICH distribution

I've provided two complete examples. I doubt the Linux-haters will be able to provide any themselves.

Re:Personal experience

[dbIII]

A friend of mine with a relatively new Dell machine wanted to install Linux. Fedora Core 3 did not recognize their mass-produced Dell-standard soundcard.

The problem is you have to work out what hardware is inside the Dell cheapest bits of the week box - because there will be difference between it and other Dells produced at other dates. Dell have gone to the trouble to find all the drivers and install it for you, since XP cannot be expected to identify hardware produced after it was written, and may need help to install the drivers for other things. Fedora was written more recently, but may need some help to install the correct drivers. The basic thing with any operating system is to know what your hardware is, and while most of us just try an install and see if it works, that is not the right way to go about things. We cannot say that any operating system is "not there yet" if we don't tell it what it has to do during installation - we should do the installation properly before we complain. Just trying another distro is not the way to solve the problem - know what you want it to do (eg. finding out what the sound card is) is the way to solve the problem.

It's not really all that complicated, so just seeing if things work is not the way to go about it. If there was only one type of Dell machine it would make it very easy to write the installation software for XP or linux - but you never know exactly what Dell has put in their boxes this week until you go to the trouble of reading the paperwork or looking inside the box.