PRAKHAR AGRAWAL'S BLOG

"I have seen the future and it works." – Lincoln Steffens

Linux Linux Linux — Part Two — Crossing the Linux Fault Threshold

If you can keep your head when all around you are losing theirs, you’ll be a man my son, as the poet wrote. On the other hand, if you were the first one to lose your head as soon as things get difficult, and if you’re already screaming at the victim of your pointless blame exercise and search for a scapegoat by the time the “manly” types realise that they are in shit deep enough to warrant a raised eyebrow, then come over here; you’re my type of guy. I’d freely admit that I’m not the nicest of people; many would say I’m a complete prick. A complete prick whose defining pair of traits is on the one hand, a complete inability to listen to anyone else, ever, and on the other hand, an almost pathological need to find someone else to blame for my problems. This type of personality is pretty common in the investment banking industry; it is certainly possible to make a career in finance by being a nice, rational, honest human being, but I never thought I’d be any good at that, so I decided to dance with the one that brung me. I’m a short-tempered, blinkered, pig-ignorant, self-obsessed prick. Don’t worry, we’ll talk about your faults next week.

Some might have said that, in the circumstances, it was mighty optimistic of me to enter the world of Linux, fundamentally throwing myself at the mercy of people who would both
play on my sense of intellectual inferiority and
be extremely likely to take offence and leave me to fend for myself if I didn’t treat them with respect.
They might have said that, but if they did, I didn’t listen. Here’s my story.

————————————————————————————

I had decided a few months earlier to install Linux because it was cool (I maintain to this day, that this is the only valid reason for a desktop user to install Linux). I was all set up, I had my beautiful beloved Vaio laptop, all I needed was a Linux. I decided to go for the “Mandrake Linux” distribution, because a) one of my email buddies had told me it was the easiest to install, and b) they were giving it away free on the cover of a computer magazine that week, and I was fucked if I was going to pay for “free software”. Yes, yes, I’ve read “The Cathedral and the Bazaar”, but let me point out to you that if you’ve been boasting to your honey for three weeks about how cool you are for installing “free software” and the first thing you do is come home with a box you paid $99.99 for, then she’s going to laugh pretty hard. And the laughter of a beautiful woman can feel surprisingly emasculating, particularly when you’re feeling a little dumb yourself, and a hundred bucks out of pocket. So Mandrake it was.

Here is my first comment of substance on the subject of Linux, which is certainly applicable to the so-called “newbie distro” produced by Mandrake, but which, I think, has more general application.

They broke my fucking computer.

Perhaps it is because they are French, and perhaps the words have a different connotation in that magical language, but I venture to say that when Mandrake use the word “resize”, as in
“Would you like to resize your Windows partition?

(best said with a subtly sardonic Parisian accent)
… they do not perhaps realise that most people are going to assume that they mean “resize” in the sense of “make bigger or smaller by stretching or squashing, perhaps affecting the internal bits somewhat in the process, but basically retaining the structural integrity of the thing”. When you use the word “resize” to a normal English speaker, he does not assume that the word means “delete a chunk of, irrevocably, without first checking whether something vital is on it, then render yourself unable to find that deleted block ever again”.

This is the basic problem with the much-vaunted “newbie-friendly” Mandrake Installer; five times out of the six I tried it, its two main functions appeared to be to
Seek out and render inoperable any copies of Windows hanging around and
Itself fail to install properly.
When operating systems are something about which you have never had cause to think in your pre-Linux career, and when you find yourself staring at a blank screen where a desktop should be, reading in an old school font the words “Missing Operating System”, and when you do not know what the hell those words mean, then I must tell you that you tend to go pretty sour, pretty quickly, on the people who put you up to installing the fucking thing in the first place. So it was with me and Linux. If you knew me during the Linux period, and if you gave me some advice on how to deal with my computer then know this; the only reason I didn’t threaten to sue you, call you a useless shit-heel and send you the very nastiest virus I could find, is that with my computer completely fer-zucked by Linux, I was unable to get in touch with you to do so. I don’t know anybody who knows a fucking thing about computers (the reason for this is that I am not working class). I am not prepared to shell out money for someone to mend my fucking computer; that’s what warranties are for. I chucked away the warranty card for my computer the moment I opened the box. Cut off the web connection of my one and only computer, and I am truly and utterly on my own. So that’s when I started buying books.

Books are one thing I will buy, because I am a bit of an old sap for the feel of the pages between my fingers and the wonderfully brainy weight of a briefcase full of paperbacks on esoteric subjects. On the other hand, I must confess to having developed a burgeoning resentment of the false advertising of “Free Software” and a growing sympathy for the transparently propagandistic Microsoft concept of “Total Concept of Ownership” when faced with the following calculation:
Microsoft Windows:
• Cost of operating system: $0 (came with the computer)
• Cost of applications: $299 (proper copy of Office, couple of games)
• Money spent on books relating to Microsoft Windows: $0 (the very idea of buying one would have seemed weird to me)
• Time spent reading books: 2hrs/year (occasionally looking up how to write macros in the manual)
Linux:
• Cost of operating system: $3.95 (the magazine was fucking useless except for the CD)
• Cost of applications: $0
• Money spent on books: $200 (vast numbers of them seemed to need to be bought to understand what the hell was going on and no one book explained anything properly)
•Cost of sitting around drinking nasty coffee in dingy internet cafes trying to work out how the fuck I was going to get my modem to work again: $40
• Cost of entire new fucking computer after I found out that I wasn’t going to be able to, because fucking Linux doesn’t support it: $500
• Time spent reading books: all my free time for a fucking week.

You see how the cost mounts up. And that was just to get my computer fucking working again. Christ knows how much time and expense I’m going to be put through if I ever decide to do anything with it.

In any case, I find it necessary to mention at this point the people who helped me get my computer back into action. These are a group of people to whom I feel a degree of gratitude, because they helped to rescue me from the peculiar hell which is the Mandrake installer with handy tips like “yes, the default size of partition is 2Mb for root and 0.5Mb for /usr, no, nobody knows why”. But only a degree, because they refrained from giving me the best piece of advice possible, which would have been “don’t fucking bother”. This merry bunch of pranksters go by the name in the online community of “Linux advocates”. The word “advocate” comes from the Scottish term for a lawyer charged with the hopeless task of defending an obviously guilty suspect, and is common parlance among computer types (see the Jargon File) for a mindless zealot who has mistaken the market share of his preferred computer operating system for the girth of his penis, and who believes it to be vitally important that “his” (no, never her) operating system is marketed as efficiently as possible by word of mouth to ludicrously inappropriate consumers.

However, in the case of Linux, it is inappropriate to call the zealots “OS advocates”, as the vast majority of their time is not spent on comparing the features of Linux with those of other operating systems, but rather on making up excuses for the shortcomings of Linux on the desktop, and boasting about the stability and speed of Linux installations (usually webservers) utterly incomparable from the one they are recommending you install. You may think I am making this up; I wish I were. I have lost count of the number of times a Linux zealot has seen fit to bring up the subject of the hosting of Slashdot (“and numerous big companies like IBM!”) in the context of a conversation about why I can’t read my fucking documents any more. It is for this reason that I have coined the following truism:
Windows and MacOS have “advocates”; Linux has “apologists”.
Conversations with Linux apologists tend to have three distinct phases:
Very erudite-sounding discussion of your problem in terms of software projects which are either pre-alpha vaporware or, more likely, entirely theoretical ideas once floated on Slashdot. (“Yes, what would solve your problem would be the integration of Samba into the kernel with the correct RFS extensions. I think that this is a problem that Alan Cox is working on in the unstable release of Debian 4.9.01a”)
Grudging acceptance that there is no very good or workable solution to your problem under Linux, coupled with castigation of the iniquities of the software industry. (“Well, of course the real trouble is that HP won’t open the driver source specifications so the project has to be carried out on the island of Nauru. Damn that DMCA! I heard Bruce Perens talking about a secret data repository under the sea like in this Neal Stephenson novel ….”
Banging on for hours and hours about how fucking wonderful Apache is, if you let them. (“… and even Microsoft runs it for 83% of their intranet servers according to recent Gartner surveys and it really shows that Free Software works in the business environment and it was just put together by this bunch of guys and it just goes to prove ….”
The important concept to bear in mind when discussing software issues with Linux apologists is the “Linux Fault Threshold”. Clever use of this concept helps you to avoid losing your temper with someone who might actually be able to render practical help, while ensuring that you give the correct dose of venom (60cc of scorpion juice, administered per anem with a rusty syringe) to the vast crowd of mindless apologists who just want you to use their pet operating system because it makes them feel good and gives them something to boast about on Slashdot. I provide this as a service to all the blind, alcoholic, incontinent grandmothers out there who appear to be installing Linux without any trouble if the Slashdot comments on any article remotely related to user interface design are to be believed.

The Linux Fault Threshold is the point in any conversation about Linux at which your interlocutor stops talking about how your problem might be solved under Linux and starts talking about how it isn’t Linux’s fault that your problem cannot be solved under Linux. Half the time, the LFT is reached because there is genuinely no solution (or no solution has been developed yet), while half the time, the LFT is reached because your apologist has floundered way out of his depth in offering to help you and is bullshitting far beyond his actual knowledge base. In either case, a conversation which has reached the LFT has precisely zero chance of ever generating useful advice for you; it is safe at this point to start calling the person offering the advice a fucking moron, and basically take it from there. Here’s an example taken from IRC logs to help you understand the concept.
<jsm> Why won’t my fucking Linux computer print?
<linuxbabe> what printer r u using?
<jsm> I don’t know. It’s a Hewlett Packard desktop inkjet number
<linuxbabe> hewlett r lamers. they dont open source drivers <——LFT closely approached!
<linuxbabe> but we reverse engineered them lol. check the web. or ask hewlett for linux suuport??<—— but avoided, he’s still talking about the problem
<jsm> Thanks. I already did that. But I can’t install the drivers on my fucking computer. I’ve got a floppy disk from HP, but my floppy drive is a USB drive and Linux doesn’t have fucking USB support.
<linuxbabe> linux DOES have USB support!!!!!!
<jsm> yeh for fucking infrared mice, and for about a thousand makes of webcam it does. Get real here. For my fucking floppy disk drive, I am telling you through bitter experience it does not. Even if someone has written the drivers in the last week
<jsm> which I sincerely doubt, how the hell am I going to install them given that my floppy drive doesnt work?????
<jsm> this ought to be in the kernel. what good is a fucking operating system that doesnt operate?
<linuxbabe> Imacs dont have floppy drives at all <—– useless point, but not LFT. All apologists make pointless jabs at other OSs
<linuxbabe> so you ought to be greateful that Linux does. drivers like that shouldn’t be bundled in the kernel
<linuxbabe> makes it into fucking M$ bloatware. bleh
<linuxbabe> download drivers from the web!!!! apt-get is your friend
<jsm> So everyone keeps telling me. Unfortunately the fucking modem doesn’t work under Linux either, and since the Linux installation destroyed Windows, that leaves me kind of fucked.
<linuxbabe> Linux doesnt destroy windows
<jsm>mandrake installer does. It “resized” my Windows partition and now the fucker won’t work
<linuxbabe> you shuold have defragmented. windows scatters data all over your hard drive so the installer cant just find a clean chunk to install into. it isn’t linux fault <—- distinct signs of LFT being approached
<linuxbabe> that windoze disk management blows
<jsm> so why doesn’t my fucking modem work?
<linuxbabe> what computer hav u got
<jsm> A Sony Vaio PCG
<linuxbabe> that doesn’t have a modem
<jsm> I assure you it fucking does. I used to use it to check my email back in the days when Windows worked.
<linuxbabe> its got a winmodem. thats not a modem <—– nitpicking over technical terms is a sign of impending LFT
<jsm> what do you mean?
<linuxbabe> a winmodem isnt a proper modem. it just uses proprietary windoze apis. doesnt do the work of a modem at all.
<jsm> Very interesting. Now how do I get the fucker to work with Linux?
<linuxbabe> well the trouble is that micro$oft won’t open up the drivers they just keep it proprietary and becos theyr a monopoly all the lameass manufacturers fall into line

LFT REACHED !!!!!

<jsm> So in other words, my fucking modem is never going to work with Linux at all?
<linuxbabe> no no no. in the first place you never had a modem you had a winmodem. in the second place its M$ fault that the drivers are closed and you can go to jail for trying to reverse engineer them like this guy dimitri skylab and the DMCA. its nothing to do with linux that M$ fills the world with its proprietary crap
<jsm> But in terms of actually getting my computer to work with Linux, I get the impression that it won’t?
<linuxbabe> M$ should have to open up the drivers have you read CatB? and vaio sucks because they won’t open up their standards either.
<jsm> Congratulations on wasting half an hour of my life, you fucking loser. And stop pretending to be a fucking woman. Your advice is useless. You, and the other hundred members of the so called fucking Linux community for which you stand, have broken my computer, wasted my time, patronised me senseless, revealed your lack of real knowledge, patronised me again and you *still* can’t get something as simple as a fucking laptop computer to fucking work. Your so called free fucking software, like your
<jsm> so called fucking free advice, is still too fucking expensive. I cannot believe that you have so little fucking self-respect that in order to find the attention you clearly crave, you have to spend your life lying about the usability of a fucking computer operating system, purely for the joy of creating problems which you can then pretend to solve. You are worse than a fucking fireman who sets buildings on fire. I have had enough of your fucking Munchausen-by-proxy version of tech support. Now get off
<jsm> this fucking channel, hunt down someone who knows what they’re fucking doing and bring them here or I will never, repeat never, use your fucking system ag ….

—DISCONNECT —

That’s basically what it’s like. Don’t ever, ever believe anyone who tells you that you can get technical support from “the community”. Because “the community” with whom a computer journalist, website operator or Open Source loudmouth interacts, is not the same community that is open to you.

(Source: adequacy.org ; Author: jsm)

December 9, 2007 Posted by Prakhar Agrawal | Geek Stuff | , , , , | 2 Comments

Linux Linux Linux — Part One — Trying to Be a Hero

Some people are never pleased with anything. Some people seem to be pathologically unable to not sweat the small stuff. Give them something for free, and all they can do is whine. I’m one of those people.

Which is why it was probably a mistake to for me to get rid of my professional, user-oriented Windows operating system and install an experimental techie-oriented replacement, despite knowing nothing about computers and not being willing to learn. But there you go …

This is Part One of a series detailing the installation of Linux by a bad-tempered securities analyst.

I believed the hype. By the time I decided to install Linux on my computer, there was no practical reason to do so whatever. I just wanted to do it in order to be cool. Quite why I thought I might become cool by associating myself with the Linux crowd (the stereotypical fat, pony tailed Quake-playing sysadmins of this world), I am not sure. It certainly wasn’t out of anything as misguided as the belief that there was an element of “radical chic” to the decision – sure, others might have been forgiven for seeing Linux as the idealistic software revolutionaries against Micro$oft hegemony, but I had spent enough time online talking to them to know what a spiteful bunch of Libertarian pricks they actually were. But there you have it. I wanted to be tech-savvy and cool, and nothing was going to stop me.

Of course, had I come to my decision a couple of years earlier, I could have claimed I was doing it for purely rational reasons. In the early days of Linux advocacy, everything revolved round the buggy, slow nature of Microsoft products. Open Source advocates like Eric Raymond and Rob Malda would loudly boast about the “uptime” of their systems (the amount of time they could leave their computer on while not using it without having to turn it off and on to stop Windows from freezing up). They would contrast this unfavourably with Microsoft, which crashed all the time. These criticisms were absolutely accurate, of course; Windows products did crash all the time, mainly because the different products in the Office suite were not well enough integrated into one another. I remember a particularly painful couple of episodes attempting to embed an Excel chart into a Word document in 1997, and swearing to myself at the time that I would change over to Linux and never suffer the problem again. Of course, in 1997 Linux didn’t actually have any equivalent programs to Word and Excel, and even today the nearest it can come is Star Office. Which, ironically, has a horrid reputation for crashing all the time and having poor object linking and embedding. But the fact remains that in 1997, there was a genuine technical case to be made, over and above the cool factor, for the superiority of Linux as a piece of software over Windows.

However, by 2001 and the release of Windows ME and Office 2000, these problems had more or less been solved. Even the elitest of the elite Linux gurus had to grudgingly admit that Microsoft had solved its teething problems and produced a reliable, high-quality product. It hurt them to admit it, of course, particularly those who had maintained an ideology of software development under which Microsoft’s developing a superior technology was almost a logical impossibility. But by 2001, the Linux battle had moved into the courtroom, where the Netscape browser, assisted by the Department of Justice, appeared to be kicking Bill’s ass. The Linux users were pinning their hopes on some sort of break-up of Microsoft which would force its software into the public domain, allowing them to merge the Windows 2K codebase into Linux.

Separately from this, the dot-bomb status of Indrema had more or less put the tombstone on Linux as a serious gaming platform – as I knew from Slashdot and the mailing lists, DirectX support was about ninetieth priority for a team of kernel developers desperately trying to keep pace with innovations in the hardware industry. So my ambition of leaving the rat race and becoming a professional game designer by starting off as a big fish in the small pond of Linux gaming looked pretty much a forlorn hope. Unfortunately, it seemed that being “open” to new suggestions wasn’t as much of a help as Eric Raymond had predicted it would be in his “Cathedral and Bazaar” essay — the number of elite computer programmers or “31337 hackers” who cared to devote their spare time to maintaining and updating Linux just didn’t seem to grow as quickly as the requirements of the Linux project. There really was no particular argument on grounds of technical merit for risking damage to my slick, professional ME/2K installation by installing the rushed compromise that was the Linux 2.4.1 kernel.

So why, for heaven’s sake, did I do it? Well, part of it was pure and simple contrarianism. There was something in the ornery, cussed nature of the Linux kids that appealed to me; the determination to drag a 1970s operating system kicking and screaming into the 1980s, and to take on the biggest bully in the schoolyard (Microsoft). It was a doomed quest, to be sure, but I’ve always been a fan of Don Quixote and the Linux “community” appeared to be his modern equivalents.

But personal admiration couldn’t have been that much of a factor. Although the original inventor, Linus Torvalds himself, seemed like a nice guy with an understated sense of humour, he seemed to have more or less disappeared from the Linux scene by 2001, leaving Linux dominated by opinionated blowhards like Raymond, Bruce Perens and Malda. These three Libertarian loons in particular destroyed whatever nascent goodwill I might have had for Linux as a social movement. By late 2000, it was more or less impossible to open a computer magazine without seeing one of this unholy trinity grinning out at you in pale malnourished splendour, attached to some ass-kissing profile, or to an ill-thought out manifesto, full of ludicrous grandiose statements about world domination, uninformed slurs about Windows, and head-in-the-sand optimism about Linux capabilities as yet unprogrammed.

We were all “lusers” and “sheeple” for going with a trusted product rather than the latest self-advertised “unstable” Linux release, and Eric Raymond claimed to have a secret development model which was twice as efficient as anything which had gone before, because, in his half-thought out position papers, Linux was based on the free market, whereas Microsoft (at that time the largest company by market capitalisation in the history of capitalism) was more like the old Soviet Union. Appalling twaddle, obviously, but just about then, the computer mags would print anything if it would help to hype the free Linux CD attached to the cover. In their defence, this was in the days pre dot bomb, so the arrogance of Malda and Raymond was underpinned by the extraordinary (and, it turns out, possibly manipulated) market capitalisations given to the companies on whose boards they sat (Perens missed the IPO window, and thus remains the poor man’s Eric Raymond).

But if it wasn’t the personalities involved, why was it? What possessed an otherwise rational financial analyst to install, on what was then his only working laptop, an operating system which would not support either Word or Excel, the twin six-shooters of the financial cowboy’s trade? What made me do it?

In the final analysis, it was, purely and simply, the cool factor. The buzz about Linux had spread from the Net to the specialist press, via a detour into the wildest hinterlands of the NASDAQ. In other words, it had started off among a bunch of nuts and diehards, floated a couple of “story stocks” and was now being touted in the industry as the Next Big Thing This is the exact same path trod by radio in the 1930s, bowling alleys in the 1960s, satellite communications in the 1970s and Charles and Maurice Saatchi in the 1980s. The next stop along this line was general fashionability in the financial markets, last stop en route to General Credibility, Backlash and Decline Into Obscurity. I’d seen it happen a couple of years earlier with micro-scooters and Pokemon, for example. This time, I was going to be in the vanguard. I had a reputation as something of a technical guru in my firm, based on a couple of Excel macros I’d written a few years earlier. I also wanted to project the kind of rebellious, cool image that was associated with Apple Macs a few years ago, and Linux seemed perfect for that (Macs were still the unconventional choice, but their association with the design industry made them seem more gay than rebellious per se). Despite the fact that all the technical arguments militated against, it, it was clear to me that now was the Time For Linux. This time, it was me who was going to be “elite” !

(Source: adequacy.org ; Author: jsm)

December 9, 2007 Posted by Prakhar Agrawal | Geek Stuff | , , , | 1 Comment