Practical Technology

for practical people.

May 17, 2000
by sjvn01
0 comments

Can Linuxcare stay afloat?

The real story behind a potential open-source disaster.

Its CEO walked the plank. Employees are running for the lifeboats. And
an initial public offering has been put on ice. What went wrong at
Linuxcare?

Just about everything, as this exhaustive investigative report by
Sm@rt Reseller reveals. Interviews with more than one dozen current
and former Linuxcare employees — most of whom spoke under the
condition of anonymity — paint a dramatic picture of a company that
was doomed from the moment it left port.

Indeed, sources say Linuxcare was undermined by warring internal
factions, out-of-control spending and a management team hellbent on a
speedy IPO. The result: Linuxcare’s ship is taking on water, with
surviving executives scrambling to keep the company afloat.

Like Red Hat and Caldera, Linuxcare was positioned as a big ship on
the open-source seas. But instead of hawking commoditised software,
Linuxcare focused on higher-margin services and support gigs from its
inception. The 21-month-old company provides services, support and
training for open-source products. Proponents predicted that Linuxcare
would thrive on booming demand for the Linux operating system.

But Linuxcare’s strategy sprung several major leaks, and the fledgling
company has been taking on water in recent weeks. Among the
casualties: Linuxcare’s board has given CEO Fernand Sarrat and other
top management the boot, pink-slipped 25 percent of its workforce and
scrapped its IPO plans.

“Linuxcare’s management screwed up big-time,” says Eric Raymond,
open-source luminary and a member of VA Linux Systems’ board of
directors. “They had a lot of good people at the line level, too. This
was definitely a case of top-down incompetence.”

Other critics question Linuxcare’s strategy. “There are not enough
companies who have enough Linux deployed to justify support contracts
on just Linux,” says Ransom Love, CEO of Caldera.

As Linuxcare’s remaining managers race to plug holes in the company’s
internal infrastructure and business processes, its board is searching
for a new CEO.

The position won’t be easy to fill. “There’s not a lot of executives
in the world with open-source experience,” laments Linuxcare chairman
Ted Schlein, who is expected to look at some corner-office candidates
in the coming week.

Sell the ship?

Hiring a new CEO isn’t Linuxcare’s only option. According to a
well-placed source close to Linuxcare, the services company has
received acquisition offers in the past from Red Hat and hardware
provider VA Linux. “Either company would do well to acquire Linuxcare
right now,” says the source. Schlein declined to comment on the
possibility of a merger, saying only that additional funding is
imminent.

Meanwhile, many remaining Linuxcare execs blame the stock-market
downturn for the canceled IPO. Most execs, however, decline to discuss
the murky circumstances surrounding last month’s departures of CEO
Sarrat and CIO Douglas Nassaur. “The stock-market instability got to
us,” says Linuxcare’s interim CEO Pat Lambs, who usually runs the
firm’s services unit. “[Plus], you really need a CEO to do the [IPO]
road show.”

Part 2: Where’s the cargo?

Still, there were bigger problems.

From the get-go, Linuxcare boasted a swagger that fostered big
thinking and even bigger spending. The company was conceived in August
1998 by a trio of high-tech consultants with a penchant for
open-source software and deep connections within the Linux community.
“Two years ago, the question [regarding Linux] was, ‘Where am I going
to get support? Who can I call? Who can I sue if it breaks?'” says
Linuxcare co-founder and CTO David Sifry. “People loved [the idea of
Linuxcare] … They went gaga over it.”

The feeling was reciprocal. In March 1999, Linuxcare took out a
full-page ad in The Wall Street Journal declaring Linux inventor Linus
Torvalds the next “leader of the free world.”

But for Linuxcare to succeed, it needed a seasoned captain. Enter
Fernand Sarrat, a 23-year IBM veteran with an amiable style and a
solid record of team building. From his May 1999 hire, Sarrat drew
high marks from employees for facilitating teamwork and raising
Linuxcare’s profile. However, Sarrat also floored the IPO gas pedal,
accelerating the half-built company toward an IPO date it couldn’t
handle, according to current and former company insiders.

Simply put, an IPO became Sarrat’s white whale. The smash success of
Red Hat’s IPO last August and VA Linux’s December offering only served
to quell the voices of opposition inside the company.

“There was always a big rush on Fernand’s part to go public … He was
very concerned about looking good to investors,” says one former
employee who lost his job in the recent downsising.

Reached at his home by Sm@rt Reseller, Sarrat declined to comment on
his track record.

Despite all of the hype, Linuxcare never proved that its business
model was seaworthy. Revenue for 1999 was a meager US$1.5 million,
coupled with US$21 million in losses. Sources say Linuxcare didn’t
have proper cost controls in place. For starters, Sarrat set out to
build an internal technology infrastructure to facilitate customer
support, best practices and its nebulous “knowledge center,” which was
later heralded in its S-1 filing (despite being little more than a
simple search engine, according to two former employees).

Linuxcare hired former E*Trade technology chief Douglas Nassaur in
September 1999 to spearhead the tech-support centerpiece, code-named
Sorcerer. Not long after, many Linuxcare techies became confused as to
what exactly the new CIO was trying to accomplish. Much to the San
Francisco office’s chagrin, Nassaur — who was based in Atlanta with
most of his team — began outsourcing big chunks of work at “hundreds
of thousands of dollars” a pop, says a former employee. “It didn’t
make sense, because we had all this great technical expertise in
house,” says the ex-employee.

With the price tag reaching several million dollars (estimates from
several sources range from US$5 million to US$12 million), it became
quite clear the project wasn’t delivering enough bang for the buck. By
April, the project was scaled back and Nassaur was squeezed out. The
former CIO did not return Sm@rt Reseller’s calls seeking an interview.

“Sorcerer is a perfect, textbook case study for the failure of a
project,” says a former Linuxcare engineer, who says the company has
since scrapped most of the multimillion-dollar project. “[It] was
started without any higher-level architecture or engineering reviews
to prove whether it could really be useful for Linuxcare, or whether
it could be developed at all.”

Linuxcare officials declined to put a price tag on the Sorcerer
project but claim the company is still utilising much of its
technology.

Part 3: Extra ballast

Infrastructure wasn’t the only drain on cash. With the full
realisation that a services business needs quality people, Linuxcare
kick-started a hiring binge that more than doubled the size of the
company between September 1999 and April 2000. At its peak, the
company approached 280 employees, bankrolled in large part by a US$32
million round of venture funding, closed in December 1999.

“We hired and expanded pre-IPO in a very, very aggressive manner,”
anticipating that funds would come from an imminent public offering,
said interim CEO Lambs. When that money didn’t come, she said,
Linuxcare was forced to trim the workforce by one-quarter and curtail
spending across the company. “That’s always a very hard thing to do,”
said Lambs, who doesn’t anticipate further reductions in the
workforce.

To many employees, the downsizing was the inevitable result of a
reckless spending binge. “Almost every employee I knew had a
company-paid cell phone … and Palm [Pilot]. While those aren’t huge
costs, I view it as one sign of the out-of-control spending,” said one
former Linuxcare employee.

While management gambled big on an IPO that didn’t materialise, a
tense civil war seethed below Linuxcare’s placid surface, pitting
open-source purists against much of the CIO’s staff. Only now, after
the ousting of Sarrat and Nassaur, has the internal technology jihad
subsided.

In the eye of the hurricane, again, was Nassaur’s Sorcerer project.
The CIO increasingly backed the use of proprietary software in the
tech-support centerpiece. But open-source believers, led by Linuxcare
co-founders Sifry and Arthur Tyde, were irate, according to former
employees.

“It’s simply a question of eating our own dog food. How could we
maintain our integrity if we bypassed open-source products when it
came to running our own business?” said one former employee who was
laid off in the recent downsising.

But as opposition buzzed to a crescendo, the CIO’s team continued to
champion big pieces of proprietary software.

“Doug, especially, didn’t care what software was used,” another
ex-employee said. “At one point (his staff was) thinking about
deploying Lotus Notes … which isn’t the most Linux-friendly
application.”

At least one member of Nassaur’s camp concedes the IT unit shied away
from using some open-source apps, because they weren’t convinced that
the software was capable of running a world-class services
organisation. “When we got here, (the tech infrastructure) was a total
mess. All this spaghetti code patching everything together … It’s
all we saw,” the source said.

E-mail blockade

Sarrat, meanwhile, scrambled to contain the conflict. At one point,
the 49-year-old CEO disallowed e-mail communication between the
open-source founders and the Sorcerer team. “The founders were trying
to exercise control where they had no power,” a source close to Sarrat
said. “They are good, smart, very bright people, but also very young
and headstrong.”

By staking out the middle ground between the two camps, Sarrat was
hoping to prod each side for a compromise. Instead, he ended up
alienating both groups, all but sealing his own demise at Linuxcare,
sources said.

In truth, according to several current and past employees, Sarrat
never fully grabbed the company’s helm from the founders. With Sifry,
Tyde and co-founder David Laduke carrying big reps in the open-source
community and doing much of the company’s technology hiring, many
employees still looked to them instead of Sarrat for approval. Without
the founders’ support, Sarrat was essentially rendered a lame-duck
CEO.

“The board was scared of losing support from the founders … (in
part) because employees gave more credence to the founders than the
CEO,” said the source close to Sarrat. “It was just an impossible
situation.”

Aside from hastening the departures of two high-ranking execs, the
internal technology battles also disillusioned several rank-and-file
Linuxcare employees. “We were supposed to be fighting out in the
marketplace, not at home,” an ex-Linuxcare employee said. “How can we
compete when we can’t even get along?”

Part 4: Plugging the leaks

Linuxcare’s leaders are confident they have buried the religious war
in the past, but they still face a bushel of management problems
spurred by the company’s blistering growth rate over the past eight
months. Its biggest challenges: Beefing up its middle management and
business processes to be more responsive to its employees.

After adding some 150 employees in less than nine months, Linuxcare is
still struggling to incorporate these new hires into the fold and
fully tap their expertise. The processes and managers just aren’t
there. According to one former employee, basic necessities such as
intranet access for remote offices only became available in the past
two months.

Additionally, communications channels throughout the company have been
spotty at best-making the water cooler the most reliable spot to catch
up on company news. For instance, most employees were shocked to learn
of Sarrat’s departure on Web news sites, rather than in an internal
memo. “As an employee of this company, you want to be leveled with …
If things aren’t going as well as planned, we can handle it,” says a
former employee. “This was just another indication that something was
screwed up.”

The lack of communication, coupled with little involvement in
decision-making processes, caused some Linuxcare lackeys to view
management with an “us vs. them” mentality. One engineer, for example,
quit when Linuxcare management reclaimed his rooftop parking space to
give it to a newly hired VP. To the surprise of his co-workers, nobody
in management asked him why he was leaving.

“He was a good engineer … I was shocked,” says a Linuxcare veteran,
who was laid off soon afterward. “I don’t think [Linuxcare’s founders]
want to disrespect or mistreat their employees. However, they failed
to set up the correct processes for hiring, firing [and]
decision-making when [they were in charge].”

While its internal challenges remain formidable, Linuxcare is
sharpening its external focus with the help of a rapidly maturing
Linux market. As a result, Linuxcare’s professional-services revenue
surpassed its desktop-support business for the first time a couple of
months ago, according to Sifry.

“The bad news is behind us. We’re focusing on the future,” says Sifry,
whose zest for open-source software is nearly tangible, even over the
telephone.

In addition, the company still boasts several solid partners and
customers, who say they are unconcerned with Linuxcare’s recent
travails. And company officials say at least a half-dozen more
customers will be announced shortly. “I am not bothered at all by
what’s going on over there,” says Kris Rost, global IS manager at OK
International, which spends about US$36,000 per year on its Linuxcare
contract.

Another positive: The services pioneer boasts high morale among the
many employees who fancy themselves as open-source junkies. For them,
the chance to toil shoulder-to-shoulder with several open-source
pioneers on Linuxcare’s payroll carries considerable cache. “Working
with guys like [Samba author Andrew] Tridgell and [Linux guru Paul]
Mackerras is pretty cool … It’s incredible to see these guys work,”
says an employee with Linuxcare’s Italy office.

Analysts say Linuxcare may yet turn a profit, especially if the
company takes time this year to build out its business in a methodical
manner. “We’re going to [pursue] a much more conservative growth,”
promises Lambs. “My No. 1 job is keeping people focused.”

Linuxcare’s No. 2 job should be to finally build the company’s
infrastructure, a task that was neglected during its ill-fated IPO
scamper. According to a former engineer who left Linuxcare late last
year: “The company has always had a lot of promise … But I think
they would have been much better off without all the [venture] money
… It really drew them away from their original vision.”

Now, to get back on even keel.

A version of this story by Ben Elgin & Steven J. Vaughan-Nichols, was first published in Sm@rt Reseller

May 15, 2000
by sjvn01
0 comments

ILOVEYOU Microsoft

The best way to stop ‘ILOVEYOU’ is to stop using Outlook.

So how many times do people have to be whacked on their heads by a Melissa-like virus to get the point?

So far I’ve been “ILOVEYOUed” six times today. Unlike many of you, however, other than being annoyed, I don’t have the bug, I’m not going to get the bug, and I’m certainly not going to spread it.

Why? Because I’m some kind of computer-demigod who knows all? Hardly! But I do know the basics of avoiding bugs. Here’s how you do it.

First, you scan your systems every livelong day for bugs and make sure your mail server has an antivirus shield installed.

What if it’s too late for those sound measures? Say you couldn’t catch VBS.LoveLetterA the first time around because it sprang out of nowhere and it has attacked faster than any other e-mail virus/worm in history.

According to Symantec’s Marian Merritt, group product manager for Norton products, you wouldn’t be the only one. “This will be worse than Melissa, because it sends messages to everyone, not just the first 50 people, on your address book. We expect e-mail servers to be shut down across the world.”

But, wait. There’s more; the program also loads itself up in your MP3 music and JPG graphic files. Can you say “wrecked system”? I knew you could.

If the antiviral programs didn’t catch it, what should you do? Well, for starters, you can set your mail server or client to zap automatically any e-mail that comes along with “ILOVEYOU” in the subject head or has “LOVE-LETTER-FOR-YOU.TXT.vbs” in the attachment title.

You also should update your antiviral program within the next 24 hours. The antiviral companies are working like dogs to deliver fixes. Symantec, for example, expects to deliver a LiveUpdate fix to block ILOVEYOU infections by 2 p.m. EDT on May 4. A fix for already infected files should be out by May 5. Some antivirus companies already have fixes out; everyone will have them done by next Monday, at the latest.

Prevention Now

Without all that necessary protection, I still avoided getting a fatal ILOVYOU hug. How? First I delete all messages with attached files unless I’m expecting one. We all know people who want to send us Word or PowerPoint files for no good reason. I consider the potential risk from such messages to be high enough that I just blow them away on sight.

You should be doubly suspicious of any message with a cute name attachment. For some reason, mail bugs writers seem to always give their bugs dubious names. I know one guy who opened an e-mail with ILOVEYOU because it was from a Dow-Jones newsletter and he figured that they couldn’t possible send him a virus. Oh please. Big companies, a lone guy with an 80386 and a 2400-baud modem–any and all of them can give you an e-mail worm. (Although, my real question to this guy was why the heck did he think that Dow-Jones would be sending him a love letter?)

But you know the most important reason why I’m not going to be part of the ILOVEYOU problem? I’m not running Microsoft Outlook. Now, if I ignored my advice from above, I could still get LOVEd with any e-mail client, but only Outlook passes it on.

I’m on record as saying that Outlook is a security hole that also happens to be an e-mail client. If this mess doesn’t convince of you of that, I don’t know what I can do. Just like Melissa, ILOVEYOU only transmits itself to others if you’re running Outlook. If it weren’t for the fundamental flaws of Outlook having minimal security and its too-close integration with Windows, we wouldn’t have a Melissa or an ILOVEYOU at all.

Now, a Microsoft security spokesperson is saying that while Microsoft is working closely with antivirus companies, it doesn’t have any plans to issue a patch or security warning. Thanks guys, good of you to pick up the ball like that.

So, because Microsoft isn’t going to fix the Outlook vulnerabilities, which leads to worms, you’ve got one choice. Change your e-mail client today. As an individual, you’re opening yourself up to losing use of your Windows computer for a day or two. As an IT professional, if you’ve deployed Outlook, you’re insuring that every so often a Melissa-like worm will give your company’s e-mail heart a heart attack. Try Pegasus Mail, Eudora, Notes, GroupWise, you can get a bug at any of them, but at least you won’t give it to everyone else in your company.

Frankly, considering how much money and time incidents like these waste, if you were my employee or integrator and you refused to change, I’d fire you. And, Microsoft, if you want to keep Outlook a top mail client, fix it and fix it now.

No, Microsoft is not the villain of this piece. That honor seems to belong to a kid in the Philippines. But so long as you leave the door open to our e-mail houses, others will follow him. And, bad as this is, next time will be worse.

Is Outlook itself to blame for the latest security meltdown? Talk back below and let me know what you think.

A version of this story was first published in Sm@rt Reseller.

November 17, 1999
by sjvn01
0 comments

Comdex ’99: Corel puts a penguin the desktop

Comdex is finally here and so is the first end-user Linux. At Comdex on Monday, Corel launched Corel Linux–the Linux for the rest of us.

Corel wasn’t the least bit shy with its launch. The press conference began with the announcement: “Welcome to the future of Linux” with a pounding rock beat and video.

Technically, there were no surprises. Corel Linux is based on Debian 2.2.12 Linux kernel. Corel chose Debian because of its code’s quality.

For the GUI, Corel uses the KDE 1.1.2 desktop environment. With this environment, like the Gnome Windows manager before it, KDE has fully embraced themes. Themes you ask? With themes, users can choose the look and feel of their desktops.

Indeed, for users who like to arrange their desktops just so, Corel Linux with KDE offers far easier-to-use customisation tools than its competitors. In particular, Corel Linux outdoes the other Linux distributions in its handling of video modes. Often a sore-point for new Linux users, Corel Linux makes it as easy as open, slide to the desired setting and click.

Indeed, if you know how to adjust a Windows 9x desktop, you’re well on your way to handling Corel’s front-end.

The resemblance is more than interface-deep. Corel Linux is file-compatible with Windows. With its graphical file manager, users can wander a Windows 9x like file manager that enables users to access floppy drives, CD-ROMs, Simple Message Block (SMB), Network File System (NFS), file transfer protocol (ftp) sites and normal local Unix file systems as easily as Windows users can wander about their network neighborhood. In particular, new Linux users will never need to know the pain of having to mount floppy and CD-ROMs before using them.

For hardware, Corel comes with automatic detection of Peripheral Component Interface (PCI) devices. If your users are still using Industry Standard Architecture (ISA) devices, though, it’s likely you’ll need to install some of these devices manually. Considering how difficult it is to do automatic ISA device installation correctly, this is a blessing in disguise.

The installation routine is simpler than anything Linux has seen heretofore. While Corel no longer claims a six-minute install, with its three-step install on even the slowest machines it supports–Pentiums with 24MBs of RAM and half-a-gig of hard drive–it won’t take more than 20 minutes to go from popping in the CD-ROM to booting.

While Michael Copeland, Corel CEO, claims that with this release, “Linux is as user friendly as Windows.” However, work needs to be done. That said, for Windows end-users Corel Linux is certainly the closest thing they’ll ever find to a Windows look and feel that doesn’t come in a box from Redmond.

What it lacks, except for Corel’s WordPerfect 8 for Linux, are applications that look and feel like Windows applications. Linux users might not care, but this is not a Linux for Linux lovers; this is a Linux for Windows users.

Corel is working hard, though, on taking of that lack of familiar applications. By the first quarter of 2000, Corel plans on delivering both the complete Corel WordPerfect Office Suite and CorelDraw.

While these are still in alpha, a demo of the Quattro Pro spreadsheet and CorelDraw were impressive even by demo standards. Both alpha programs work smoothly and appear to be feature equal with their Windows counterparts.

For support, Corel plans to use its own internal support system at first. The company also will augment this by shortly inking deals with major Linux helpdesk firms. For end-users, the standard version comes with 30 days of free e-mail support. Buyers of the deluxe version will get free support for 30 days both by e-mail and phone.

Corel Linux, like all Linuxes, is available for immediate download from Corel’s Linux site. Commercially, Corel, long a reseller friend, plans to make full use of the channel.

The product will come in two versions. The standard will retail for $49 (£29). The deluxe version, which we’ll bet will be the most popular one, will sell for between $79 and $89. Why? Because, we think users won’t be able to resist the fact that it comes with a free stuffed penguin in every box.

Considering how easy and powerful this Linux is, administrators, too, may find it hard to resist putting the Linux penguin in desktop boxes.

A version of this story was first published in Sm@rt Partner.

November 17, 1999
by sjvn01
0 comments

Corel puts a penguin the desktop

Corel wasn’t the least bit shy with its launch. The press conference began with the announcement: “Welcome to the future of Linux” with a pounding rock beat and video.

Technically, there were no surprises. Corel Linux is based on Debian 2.2.12 Linux kernel. Corel chose Debian because of its code’s quality.

For the GUI, Corel uses the KDE 1.1.2 desktop environment. With this environment, like the Gnome Windows manager before it, KDE has fully embraced themes. Themes you ask? With themes, users can choose the look and feel of their desktops.

Indeed, for users who like to arrange their desktops just so, Corel Linux with KDE offers far easier-to-use customisation tools than its competitors. In particular, Corel Linux outdoes the other Linux distributions in its handling of video modes. Often a sore-point for new Linux users, Corel Linux makes it as easy as open, slide to the desired setting and click.

Continue Reading →

April 20, 1999
by sjvn01
0 comments

Gates and Torvalds face off at Comdex

Torvalds gave a keynote speech at the Linux Global Summit at Spring Comdex half an hour after Microsoft Corp. CEO Bill Gates opened the show in a much larger auditorium. While Gates, like Torvalds, addressed an overflow crowd, the two presentations couldn’t have been more different in style and substance.

Torvalds, who kept the sweltering crowd attentive by entertaining audience questions and concerns throughout his hour-long presentation, seemed like more like the Gates of years ago than did Gates himself. Greeted by a standing ovation, Torvalds calmed users’ concerns about potential splintering of “the little OS that could.” Torvalds also managed to throw in a few Microsoft slams, keeping the Linux faithful happy. When the lights temporarily went out, Torvalds wondered aloud, “What’s going on in this place? The whole show floor is controlled by Microsoft.”

Gates’ keynote proceeded comparatively smoothly. Gates opened by showing a video of his last year Spring Comdex address, which was plagued by a blue screen in the midst of a Windows 98 Universal Serial Bus demo. This year, a demo of a demo of a beta release of Windows 2000’s Plug and Play USB support went on without a hitch.

Gates introduced a new Titanium mouse, called the IntelliPoint Explorer mouse, which the company plans to ship in Sept. The latest Microsoft mouse replaces the open case full of moving parts with a closed case design using an integrated optical sensor, eliminating the need for a mousepad. He also showed a forthcoming Natural keyboard under development at Microsoft which will include two USB ports as part of its design.

Gates spent most of his keynote reiterating the company’s vision for its various Windows platforms, including Embedded Windows, Windows CE, Windows 98 and Windows 2000. He officially announced Microsoft’s Corporate Preview Program for Windows 2000 Beta 3, which is due to begin shipping to OEMs and testers next week. Calling Windows 2000 “the biggest investment we ever made in a single piece of software,” Gates said Beta 3 will be supported by more than 20 OEMs; 100,000 channel partners; thousands of ISVs and independent hardware vendors, 140,000 developers and more than 500,000 customers.

Torvalds’ keynote was a bit less predictable, even though he focused primarily on Linux’ history and its well-established challenges. Like the Gates of old, Torvalds sparred with his audience and played up his image as a developer’s developer. When asked about his views on Java, Torvalds noted that he no longer is really excited about Java. At first, “I bought into the hype,” he acknowledged. “But now I’m fairly down on it because of the way Sun [Microsystems Inc.] mishandled it,” resulting in the current fragmentation of Java implementations from Sun, IBM, Microsoft and Hewlett-Packard Co.

Torvalds deflected concerns about the potential for similar fragmentation in the Linux space, noting that the copyright/license for Linux requires anyone who modifies the source code to make changes available to others under the same license. “This insures that the splinter ‘heals’,” quipped Torvalds. He added that the Internet development paradigm under which Linux has evolved has made it less likely to splinter, as well. Different programmers are working on different pieces of the OS. Linux has been ported to a variety of form factors, from the Palm Pilot to supercomputers, Torvalds said. Some developers, like Torvalds, are working on the kernel; others are more focused on user-space issues. He did acknowledge that more work needs to be done to make Linux a “serious mom and pop contender on the desktop,” but that, too, is possible in two to three more years, Torvalds predicted.

A team working under non-disclosure is working on porting Linux to Merced, Torvalds said, so that a Merced-optimised version of Linux will be available the day the chip ships. “Merced is really just more of the same,” Torvalds was quick to add. “Linux has been 64-bit for a long time. It can run on Alpha or UltraSPARC today. The main interesting parts are things like the compiler technology and that’s something that Intel is driving.”

This story first appeared in Sm@rt Partner and was written by Steven J. Vaughan-Nichols & Mary Jo Foley.

April 15, 1999
by sjvn01
0 comments

Highly tuned NT whips barely tuned Linux in Microsoft-backed test

It’s so simple, on the face of it.

Mindcraft Inc., in a new study [http://www.mindcraft.com/whitepapers/nts4rhlinux.html] commissioned by Microsoft Corp., found that “Microsoft Windows NT Server 4.0 is 2.5 times faster than Linux as a File Server and 3.7 times faster as a Web Server.”

In reality, however, it’s not simple at all.

Mindcraft, an independent test lab, pitted the two network operating systems against each other on a Dell Computer Corp. PowerEdge 6300/400, testing both NT 4.0 Service Pack 4 and Red Hat Software Inc.’s Linux 5.2 upgraded to the Linux 2.2.2 kernel. This quad 400MHz Xeon SMP (symmetric multiprocessor system) had a whopping 4GB of memory (a gigabyte of which was used in the test) and a PowerEdge RAID II Adapter, 32MB cache set to RAID 0. The tests used ZD’s own NetBench and WebBench benchmark tests for file and Web serving tests.

As tested, NT beat Linux like a drum. But, that’s not the whole story.

Singing the right tune

Mindcraft tested NT with NT tuning, benchmarking and technical support from Microsoft, and Internet Information Server 4.0 tuning information from the Standard Performance Evaluation Corp. In the case of Linux, though, Mindcraft President Bruce Weiner was “surprised that Red Hat Software didn’t help us in tuning the OS.”

Red Hat spokeswoman Melissa London explained that “there was a query to our contract technical support, but they didn’t know what to do with Mindcraft’s request. Had the question came through the right channels — the public relations or the engineering staff — we’re sure Linux would have at least have had a better representation.”

In the future, Red Hat “would love to repeat the tests with our input, support and involvement,” London added.

In addition, Mindcraft said it found “little real tuning information in the Linux knowledge bases.” What information they did find was scattered over the Web. And for Mindcraft, at least, the “word of mouth” Linux support of newsgroups, mailing lists and online conference sites didn’t work.

That said, Jeremy Allison, a leading member of the Samba Team, an open source consortium, checked his records and could find no trace of anyone from Mindcraft asking in Samba’s public forums about Samba tuning. Indeed, after looking over Mindcraft’s published Linux parameters, he said, “[Mindcraft] didn’t do any tuning on the Linux side.”

Consequently, Mindcraft has found itself buried in Linux tuning “suggestions.” Many of these are just flames from outraged Linux users, but many of them, as Weiner admits, are well-founded.

For example, Mindcraft turned the Samba parameter ‘widelinks’ off. But, according to Andrew Trigell, the Samba Team leader, doing so “lowers the performance enormously. It adds 3 chdir() and 3 getwd() calls to every filename lookup. That will especially hurt any SMP system.”

Mindcraft’s Weiner agrees: “Clearly, we wouldn’t make that tune if we were doing that test today.”

The result? Highly tuned NT beats a barely tuned (if that) Linux. But, there’s more to it than that.

For one thing, Linux tuning information is hard to gather. It’s there, but it really requires an expert Linux user to find it. If Linux is to win commercially, information known only to Linux gurus and hidden away in a dozen Web sites needs to be gathered together and made more readable and approachable. For new users, learning advanced Linux is still much too difficult.

Take the Apache server, for example. There are several files on the Apache Project’s Web site on how to tune Apache and Linux. Even so, these files aren’t easy to find. On the flip side, finding information on tuning Internet Information Server 4.0 is easy at Microsoft’s knowledgebase.

Beyond tuning: incompatibilities

For Linux, SMP is a new option, incorporated in the 2.2 release. This is not the current base OS release that Red Hat is shipping today or that was used in the test. Instead, the system was upgraded to 2.2 and SMP activated by inexperienced Linux administrators using early Red Hat documentation. Moreover, the Linux RAID driver was a beta release and not well tested with the “so new the shiny hasn’t worn off” 2.2 kernel.

As a source close to Ziff-Davis Benchmark Operations, the ZD benchmark’s authoring agency, said of Mindcraft’s testing, “A more accurate headline might have been Linux does not scale up” instead of “Windows NT Server Outperforms Linux.”

Sm@rt Reseller’s own tests, using the same benchmarks, on low-end uniprocessor machines, has shown that Linux combined with Apache and Samba beats NT and IIS handily. (See Linux Up Close: Time To Switch and Samba 2.0: A License to Kill NT).

That said, it’s likely that a highly tuned NT, on the Mindcraft SMP platform, would prove a bear for even a tuned Linux to defeat. For NT, this kind of machine is a home field. For Linux, at this point in its development, it’s an away field — far, far from home.

On single-processor systems, Linux wins. On SMP/RAID systems, Linux is just now getting in the game. Even so, even at the high end of stress testing, Linux’s numbers would have been much closer to NT — if not higher — had Linux been as well tuned as NT.

A version of this story was first published in Sm@rt Reseller.