|
|
Subscribe / Log in / New account

Why companies don't support Debian (LinuxWatch)

LinuxWatch investigates Debian's difficulties with corporate support. "Debian, either directly or through related Linux distributions such as Xandros, is used both by Linux enthusiasts and Fortune 500 companies. Of course, you couldn't prove that by the vast majority of Debian developers who never see a thin dime from their Debian work. Or, I should add, get access to new hardware, travel expenses to Debian developer conferences and so on. The reason for this is twofold. First, Debian, as a developer community, has never wanted any kind of "business" organization or corporate partnerships or sponsorships. It is purely a volunteer operation and woe unto any would-be developer who tries to change Debian's ways."

to post comments

Why companies don't support Debian (LinuxWatch)

Posted Jan 31, 2008 20:16 UTC (Thu) by NightMonkey (subscriber, #23051) [Link] (9 responses)

Hmm... The article seems to be saying that Debian is doing a bad job at making money for it's
community. But Debian's community just won't become wage slaves for Debian; they like the
freedom volunteering allows. Hasn't this lazy tactic of describing a volunteer group in ways
that would normally be used to describe a failing for-profit business been used many times
before?

Debian is always in a "crisis". Gentoo is always in a "crisis". Volunteer organizations are
both strong and fragile. Strong because they focus the common interests of a group of people
to meet common goals. Fragile because if the original goals are lost, volunteers disappear,
much faster than paid employees in similar project scenarios. So, Debian's community, by being
vocal and fighting tooth-and-nail to keep true to their vision are actually not putting Debian
in crisis, but are solidifying the mortar that keeps Debian's volunteers together to create
and maintain a productive project.

You are correct

Posted Feb 1, 2008 0:00 UTC (Fri) by jd (guest, #26381) [Link] (8 responses)

Gentoo's only crisis is that at the moment, it has no charter. Debian's only real problem at the moment is the same one all package-based distros face - there are too many stale packages, yet also far too few packages in total.

Developers are massively out-pacing the ability of packagers to package what is produced, way too many package permutations are possible but mutually exclusive, and there's way too much free software out there for a single vendor to coordinate, yet uncoordinated repositories are what caused the RPM hell too many of us have been burned with. Even "unified" repositories aren't immune. Ubuntu's packages aren't compiled against a uniform environment, creating some fascinating dependency conflicts.

I have considered starting a repository of otherwise-unpackaged software, to in an effort to solve some of this, but the bottom line is that this is an overwhelming problem. I have bookmarked as many unpackaged free software products that show signs of having plenty of users as Debian, *buntu and Fedora have actually provided in repositories. Their efforts have taken thousands - if not tens of thousands - of man-hours to accomplish, verify, test and supply. I could never keep up with any meaningful portion - at least whilst keeping a job and a roof over my head - the best I could do is some insignificant fraction, which is what others already do and which is the cause of incompatibility problems.

In other words, repeating other people's mistakes would at least be doing something, it would merely be doing the wrong something.

If corporate sponsorship was to enter into the distro picture, I'd say that it would need to enter at the weakest points: testing and packaging. These are the areas distros have never done well in and therefore really should consider handing off to wage slaves. If they don't want to, then they should find other solutions. What they currently do is broken. Fix it or replace it, just stop ignoring it.

You are correct

Posted Feb 1, 2008 0:38 UTC (Fri) by N0NB (guest, #3407) [Link] (4 responses)

Too much Free Software???  I think I understand your point that the Free Software community is
generating code faster than the distributions can keep up.  That is a fair assessment.

As I see it, Debian is drifting toward putting the best of the best into Main and putting less
emphasis on trying to package every piece of Free Software on the planet for the distribution.
This is a sensible approach but it does lead to the issue that distributions were created to
address, that of users having to build their own packages from source.

Ideally, Free Software projects would create their own Debian packages, but this becomes a
problem as well.  At some point a package may depend on something not available when Stable
was released and Unstable at some points moves fast enough that a package created today is
outdated next week, so it's unrealistic for Free Software projects to expend the man-hours to
sort this all out.

Perhaps this is an opportunity for an enterprising person or company--build unofficial Debian
packages of Free Software not in or not up-to-date in Debian and make them available for a
small fee.

Exactly.

Posted Feb 1, 2008 7:31 UTC (Fri) by jd (guest, #26381) [Link] (3 responses)

It is unreasonable for Free Software projects to put in that level of extra work, but it would be entirely reasonable for corporations (who rely on getting bugfixes and security fixes as fast as possible) to invest in precisely this sort of work. In fact, it's insane for them not to, because they suffer more than anyone else. An hour downtime costs far more than an hour of QA and patch development.

One relatively cheap solution (for a corporation) is to produce a huge server farm, where multiple versions of packages are built, dependent on different valid parent packages. Package managers would need to be somewhat smarter, because they'd need to search multiple alternative versions to find the optimum permutation of valid packages, which may mean swapping an existing package for an alternative of the same version but with subtly different dependencies.

There are plenty of other options. What's really not an option (in my opinion) is to have distributions become overly specialized to remain fully working, or highly generalized (good) but dependent on people not staying up-to-date (bad). Users are likely to end up having to compile some things for themselves, the aim (I believe) should be to keep this to a minimum and to make it as painless as possible when it does happen.

Exactly.

Posted Feb 8, 2008 2:09 UTC (Fri) by vonbrand (subscriber, #4458) [Link] (2 responses)

I'm sorry, but "the corporations" that you want to pick up the slack do have a much narrower view than "the community". If said community doesn't want to pay for something, be it testing, packaging, whatever, it won't get done for the all-encompassing interest of something like the set of Debian users. And by "pay" I mean not necessarily money, but in effort.

The "corporations"

Posted Feb 8, 2008 19:25 UTC (Fri) by jd (guest, #26381) [Link] (1 responses)

...want to sell their products to Linux business users. They are there to make money, after all. Linux business users get the same Linux software everyone else gets, more-or-less. If that software is unreliable, business users won't use it, which means Linux products won't sell.

Why sell to Linux users in the first place? Too many variants of Unix, too many of which only have a subset of the features needed or wanted, too much competition from Microsoft and generally not much security. A unified baseline that has Linux has a key platform has far better odds of long-term survival. Provided it can be brought to some provable (rather than anecdotal) quality level.

But to do that, money must be spent on Linux QA. You've got to make people want Linux, want it so bad that alternatives aren't worthy of consideration. That won't happen until there has been some serious QA.

What if no QA happens at all? Then businesses will regard Linux as something vendors aren't interested in, and those businesses will go elsewhere, costing those vendors potential sales. Sure, it would be nice if the Debian community did more QA work, but really QA is a full-time job and most Debian deveopers have two or three of those already. It's a dirty job, but someone has to do it.

The "corporations"

Posted Feb 8, 2008 21:38 UTC (Fri) by vonbrand (subscriber, #4458) [Link]

Who says that the people selecting packages and building "enterprise" distributions don't do QA? They have to restrict the breadth of software offered if they want to keep some sanity in all. Yes, that means that it is very probable that "my favorite package" isn't in the supported set.

You are correct

Posted Feb 1, 2008 3:57 UTC (Fri) by salimma (subscriber, #34460) [Link] (1 responses)

"Ubuntu's packages aren't compiled against a uniform environment, creating some fascinating
dependency conflicts."

Dependency conflicts are unavoidable in some cases, due to package churn. To avoid it you'd
have to state that the packages that ship with the distribution is not allowed to break API
during the lifecycle of that distribution.

Yes.

Posted Feb 1, 2008 7:13 UTC (Fri) by jd (guest, #26381) [Link]

For 100% avoidance, yes, you are right. For a superior level of avoidance, it should be sufficient for the following conditions to be met:

  • Package configuration files would need to be generated, not static. One way to do this would be to:
    1. Examine non-local dependency information in the makefiles
    2. Examine linkage information in the compiled binaries
    3. Examine build configuration files for libraries and utilities not referenced in the first two steps
    4. Reverse lookup what external packages are installed that supply the requisite headers, libraries and utilities
  • Dependency trees would need to be rebuilt. One way to do this would be to:
    1. Regard each dependency as a leaf node of an n-ary tree. Recursively apply this step until all root nodes for all trees have been obtained.
    2. If a package has changed OR any package further up the tree has been recompiled, the package is recompiled.
    3. If a package has not been recompiled, the only important dependent package is the one already known on that dependency tree. The previous step is then applied to that package alone.
    4. If a package has been recompiled, then all packages which depend on it must be identified and recompiled. Since a package is only skipped if a dependency has not been recompiled, this step alone is recursively applied until there are no further dependencies on anything in the tree that has been built.

This obviously doesn't work if there is a break in an API. Anything past a breakage point cannot be refreshed in this way. Not if you use LSB and dynamic linking. You could do it if you had version isolation (a working library can always be present) -or- if the build machine used version isolation and static linking on old libraries to hide legacy details.

There is, of course, another option - controlled slippage. Have a declared distro standard that libraries and utilities should provide a means of emulating old APIs some sensible number of generations back, and that packages have some appropriate time to be fixed or have a distro patch that brings them up to the active API. This doesn't constrain anyone in practice. If anything, it constrains fewer people, as it eliminates many constraints on the distro maintainers and users.

These are heavyweight solutions, yes, which means that you'd need some serious manpower (and compute power) on some of the most tedious areas of packaging. There simply aren't the resources to do anything like this without some corporate involvement, but since these are the sorts of things corporations do well (whereas coding isn't) and like (applications working well together), this isn't too much of a problem. It doesn't impact developers or their freedom, because that's not where the problem lies, but does boost areas of usability that are currently a pain.

unsupported.debian.net

Posted Feb 2, 2008 2:21 UTC (Sat) by pabs (subscriber, #43278) [Link]

I got pissed off with Debian QA people chucking out packages with "no users" so I'm
considering starting unsupported.debian.net. Recently there was a post about automatic
discovery of free software and creation of packages, which would tie in with it well.

If you are interested in reading the writeup of my idea, please mail me, address on
http://wiki.debian.org/PaulWise

Why companies don't support Debian (LinuxWatch)

Posted Jan 31, 2008 20:17 UTC (Thu) by andrel (guest, #5166) [Link]

Debian has a corporate partners program, though I'm not sure how active it is at the moment.

Why companies don't support Debian (LinuxWatch)

Posted Jan 31, 2008 20:17 UTC (Thu) by Zack (guest, #37335) [Link]

The article reasons solely from the ill-informed premisse:
-Debian is mostly made of anti-corporate volunteers

The truth is that Debian is made of debian developers (and a large network of non-dd besides
that), who all have their own reasons for participating (including: being employed by
corporations to do so).
Very few of these reasons actually include an "anti" agenda, rendering the article useless.

The main point seems to be that Debian is not exactly what the author thinks it should be, so
he writes an article that contorts facts and history to create an opportunity to bash Debian.
That is at least how it struck me.

Why companies don't support Debian (LinuxWatch)

Posted Jan 31, 2008 20:45 UTC (Thu) by justme (guest, #19967) [Link]

So, I'm guessing that this has been suggested before, but why not take contributions centrally
and distribute them through community-elected fellowships?

Of course, it may also be the case that there is no problem to solve here...

Ubuntu?

Posted Jan 31, 2008 21:31 UTC (Thu) by stevenj (guest, #421) [Link]

I find it somewhat odd that the article uses Ubuntu as an example of how Debian isn't corporation friendly. Ubuntu illustrates perfectly how Debian works as a base for a more "commercial" distro: Ubuntu was able to build on top of Debian while remaining in close cooperation with the Debian project, precisely because of the way Debian is structured.

Why companies don't support Debian (LinuxWatch)

Posted Jan 31, 2008 23:03 UTC (Thu) by jmm (subscriber, #34596) [Link] (3 responses)

What the article describes as a disadvantage is actually Debian's greatest 
strength: Having no significant money involved leads to full independence. 
Debian can't go bankrupt (think Progeny) or be bought out by a competitor 
(think Novell ;-) )

The same goes for Ubuntu: It's essentially a gadget of a dotcom 
millionaire, who also afforded himself a space flight. If he finds himself 
a new hobby, Ubuntu is doomed.

No other distribution than Debian (except maybe Slackware) has a track 
record of delivering quality releases for fourteen years.

Why companies don't support Debian (LinuxWatch)

Posted Feb 1, 2008 8:21 UTC (Fri) by branden (guest, #7029) [Link] (2 responses)

I should set the record straight as Progeny's fourth employee and the only 
one hired in 2000 who was there continuously until it closed.

Progeny didn't go into bankruptcy; Progeny just plain ran out of money and 
ceased operations.  As far as I know, it still legally exists as a 
business entity and will do so until dissolved by its principals, those 
being the Board of Directors--or, if certain paperwork is not filed with 
the states of Indiana and/or Delaware, until it is purged from their 
incorporation and operating license rolls.  But it may take years for that 
to happen.

You probably meant "bankrupt" in a colloquial sense, but lots of companies 
go into bankruptcy (e.g., United Airlines).

Bankruptcy was not Progeny's fate.

Hmmm. That gives me an idea.

Posted Feb 1, 2008 21:54 UTC (Fri) by jd (guest, #26381) [Link]

Maybe the board could be convinced to rent out the Proginy name to anyone starting a roofnet or metronet, for some very nominal value. Keeps the name as a commercial entity, makes them more money than they'd have otherwise, and has the potential of being as profitable in the long term as any chain store where the connection with the parent is essentially just a naming license.

Or, to get this back to Debian, since the name has no real market value any more, maybe they could donate it to Debian to give Debian the corporate credibility without having to have anything to do with corporations.

Why companies don't support Debian (LinuxWatch)

Posted Feb 3, 2008 2:24 UTC (Sun) by jbailey (guest, #16890) [Link]

Of course, the fact that Progeny refused to sell services didn't help.  The reason I wound up
getting involved with Ubuntu in the first place was because despite everyone saying that
Progeny's business was selling Debian support, the sales reps wouldn't allow someone to buy
that.

This was Spring 2004.

Why companies don't support Debian (LinuxWatch)

Posted Jan 31, 2008 23:42 UTC (Thu) by sprink (guest, #45735) [Link]

This is a horrible inaccurate article with extreme bias.

I don't complain about lwn posting crappy articles often at all. But this is one that
shouldn't have been posted.

Why companies don't support Debian (LinuxWatch)

Posted Feb 1, 2008 0:12 UTC (Fri) by N0NB (guest, #3407) [Link] (2 responses)

I will do my best to be civil.

This is probably the most mis-informed article I have read in some time.  And it comes from
someone who I thought understood his topic matter.  I guess I was mistaken.

As a long time user of Debian and not a developer or maintainer, I can say with confidence
that from where I sit Debian is not unfriendly toward corporations or other organizations, but
is unfriendly toward anyone who intends to restrict the freedom of us, the users.  The author
uses as one of his skewed examples the Firefox issue.  The fact is that the Mozilla Foundation
licensed their artwork in such a way that it is in conflict with the Debian Free Software
Guidelines.  An amicable agreement could not be reached regarding the licensing impasse with
the result that Iceweasel was created to protect the freedom of us, the users.  

It really wasn't the first choice of the Debian developers to do it this way.  The Mozilla
Foundation left the project no other choice if the browser code was to remain in the Main
Debian release and the project would continue to adhere to its core principles.  (In fact, the
Mozilla Foundation has certain restrictions on the use of the name FireFox, as I understand
it, which also conflict with the DFSG.)

This is the point the author consistently missed while he tried to build a case against the
Debian developers' alleged hostilities toward corporate entities (never mind the fact that the
majority of Debian Developers that I'm aware of have some means of gainful employment), that
first and foremost on the minds and in the actions of the Debian developers is the protection
of the software freedoms outlined by the Debian Free Software Guidelines for both themselves
and us, the Debian users.

With the list of Linux distributions known by Distrowatch, Steven, don't you think there is
room for just one that values software freedom above corporate expediency?  Evidently not.

Leave Debian alone.  It's just fine as it is.

P.S. Perhaps the author should look up Software in the Public Interest at
http://www.spi-inc.org/ if he would like to make a hardware or monetary donation to Debian.


Why companies don't support Debian (LinuxWatch)

Posted Feb 1, 2008 10:47 UTC (Fri) by slef (guest, #14720) [Link] (1 responses)

You thought SJVN understood the subject?  Where have you been?
http://lists.debian.org/debian-project/2007/04/msg00051.html

It is disappointing that LWN posted this article and didn't mention that it was by SJVN.  He
links his other (usually misinformed, nearly always biased) articles to support his case.  He
cites dunc-tank at least twice, in different ways, without making it clear that DWN is
dunc-tank-related.  Those should have been a big warning flag that this isn't LWN-quality!

Then there's the factual mistakes, AFAIK: I do have access to new hardware, usually as soon as
it's linked to db.debian.org; Google donates to SPI not the DPL; I think we had a working
agreement with Mozilla Foundation, which Mozilla *Corporation* then revoked.  Again, signs
this shouldn't be in LWN.

So, LWN: please label SJVNgrams clearly in future!

Why companies don't support Debian (LinuxWatch)

Posted Feb 1, 2008 12:05 UTC (Fri) by N0NB (guest, #3407) [Link]

Given the date of your linked message, at that time I was spending much time on motorcycle
related sites and not Linux or Debian related sites.  So, I plead "other interests" as far as
SJVN is concerned.

Thanks for providing info on his continued troll status.


Why companies don't support Debian (LinuxWatch)

Posted Feb 1, 2008 8:43 UTC (Fri) by branden (guest, #7029) [Link]

This article is really poorly informed, and I'm surprised at that as I 
don't recall Mr. Vaughn-Nichols being quite so hasty to publish before 
checking facts when I was Debian Project Leader.

Companies can and do support Debian, not only through donations of 
hardware, but conspicuously by supporting DebConf.  For years it has been 
the practice that a significant amount of DebConf's budget has gone 
sponsoring travel expenses to our annual conference, in direct 
contradiction to Mr. Vaughn-Nichols's assertion.

The DebConf organizing team has for the last several years published a 
detailed report, which includes budgetary matters.

We also make no secret of our sponsorships; journalists who attend DebConf 
would be hard pressed not to notice the ubiquitous T-shirts which list the 
year's numerous sponsors on the back.  (While many developers wear their 
hair long enough to obscure such a listing, this should not present an 
insuperable obstacle to the assiduous fact-gatherer.  At DebConf 5 in 
2005, for example, the sponsors were also listed in the official program 
of the conference.)

Not only is it not the case that "there's no one to write a check to", but 
big firms like Sun, Google, and HP have long known that, in the United 
States, Software in the Public Interest, Inc. (SPI), is the 501(c)3 
corporation of first resort if you want to Debian out.

Checks from Google for Debian, PostgreSQL, and other Summer of Code 
projects come directly to SPI, and the funds held in trust for the member 
projects.  Michael Schultheiss, a friend and fellow Progeny alum, is the 
current SPI Treasurer (as was I, at one time), and could no doubt clarify 
many of these matters.  As could Sam Hocevar, Anthony Towns, or other 
folks named in the article.

That the piece calls itself out as an "opinion" should not relieve the 
author of all responsibility to check his or her facts.  That big name 
op-ed writers like David Brooks and Jonah Goldberg (just to name two 
examples) fail to hold themselves to such a standard does not make them 
worthy of emulation--it makes them figures to be transcended.

yay, another attack piece

Posted Feb 1, 2008 18:12 UTC (Fri) by joey (guest, #328) [Link]

Well, it's a blatant attack peice, full of misinformation. A few things that stuck out at me, by no means a complete list:
  • Article claims that most developers never get travel expenses to Debian conferances paid. I think the 300 developers who made it to Edinburgh last summer from locations all over the world would disagree. 300 is probably about half the current number of *active* debian developers. Any DD who can come up with a good talk for debconf is a shoo-in for travel expenses, and they've had enough money to even pay for developers who were too lame to give a talk. (Where does this money come from? Er.. corporate sponsorship.)
  • If Debian turns against any developer who accepts a check for working on Debian, why have I lived for the past 9 years (and bought a house) doing just that, while still being apparently respected by Debian, despite having sold out?
  • Article points to Debian Weekly News as a sign that debian is disorganised. If we're so disorganised, how did we manage to publish one issue a week (each better researched than this linux-watch attack peice!) for 8 years? (In fact, we're replaced it now with http://wiki.debian.org/DeveloperNews )
  • Usual inaccrate stuff about the mozilla logo.
  • Chris Fearnley was once a Debian Developer, but he isn't working on it now AFAIK.
  • Article claims Debian has trouble finding corporate partnerships. http://www.debian.org/partners/ lists HP, Sun, trustsec, credativ, skolelinux, Genesi, MGE UPS SYSTEMS, simtec, etc, etc. These are companies who fund Debian developers and/or provide hardware to the project.

Why companies don't support Debian (LinuxWatch)

Posted Feb 3, 2008 19:11 UTC (Sun) by stockholm (guest, #3939) [Link]

I too would like to ask LWN to filter out these kind of "news" and keep them from being spread
further. This guy is so far off it almost hurts. 

I worked on collecting funding for both Debian Conferences and other things within the Debian
Community for three to four years and found that when you approached the companies with
specific requests and a sound plan for spending the requested funds that people were very
forthcoming and supportiv. Debian is regarded highly within the industry and its work is very
appreciated. It is a stong brand with positive associations (stability, reliability,
enthusiasm, vision, altruism, quality) attached to it. The author of that article is known for
writing in a dismissiv and negativ way about Debian. So much so that one would suspect a
hidden agenda by now. I doubt that facts could throw him off. 

Other reasons

Posted Feb 4, 2008 10:16 UTC (Mon) by hensema (guest, #980) [Link] (1 responses)

The Linux-Watch author may be wrong in some points, he completely missed some others, IMHO:

  * From a business perspective, a Debian installation is hard to support. 

This has two main reasons: first, it's extremely hard to define 'a Debian install'. Because of
the complete freedom to the user, you'd have to do a lot of investigation to ascertain what
configuration actually is installed. Second, Debian systems tend to be more customized (less
standardized) than other installations of other distro's.

  * No release cycle.

Corporations like predictability. Debian releases seem to happen randomly.

  * However, one thing is certain: slow release cycle.

You may not know when Debian is going to release, but you can be certain of one thing: the
release cycle is slooooowwww. This either forces you to run a development release (testing or
unstable) or at the very least compile some custom software yourself (the kernel comes to
mind).
Please note almost all distributions make a development version of their distro available.
Think Rawhide, think Opensuse factory. Most users of thos e distributions don't need to use
the development versions, while lots of Debian users seem to run testing or even unstable.
While you may argue testing is 'good enough' for most purposes, you really only want to run a
stable distribution in a business environment.

  * Conservative

Debian is created from a very conservative standpoint. The base system is guaranteed to run on
very modest hardware. While this is a good thing, businesses won't care. Their hardware will
almost never be older than 4 years.
This wouldn't be too bad if this wouldn't affect Debian on modern hardware. But it does. When
a developer assumes his software is going to run on moderately modern hardware, he can offload
the user and take his workload on the computer, for instance by creating a more efficient (to
the user!) interface to the software.
Even without user interaction, you still have to deal with a fundamentally different
environment in contemporary hardware.

  * Freedom without compromises

From a political point of view, Debian is completely right: Be Free!

However, when this harms business on the short term, principles tend to be thrown out of the
window very quickly. So they want their driver right now, and bug free. Not alpha 0.6 of some
Free reverse engineered driver, which may reach stability in another 6 months. Or so.



Debian is a very good distribution, for its purpose. But its purpose isn't to be used in a
corporate environment. It's developed to cater it's developer's needs, and none other. This
makes Debian an excellent distribution for developers (eg the audience of this site), and an
excellent basis for more business-like distributions like Ubuntu.

I think this kind of specialization is a good thing. It makes software ideally suited for its
purpose. A very broad, generic Linux distribution essentially would be good at nothing, it
would just not suck in almost all areas.
 

Other reasons

Posted Feb 4, 2008 14:59 UTC (Mon) by Zack (guest, #37335) [Link]

>first, it's extremely hard to define 'a Debian install'.

In my opinion it isn't. Every combination of software that is in a distributions 'main' is a
valid Debian install.

>Second, Debian systems tend to be more customized (less standardized) than other
installations of other distro's.

Almost all software debian distributes comes with proper 'out of the box' defaults. Anything
less standardized is put there explicitly.

> the release cycle is slooooowwww. 

It's just about adequate for corporate use I'd say . When stuff works, you really don't want
to touch it anymore. Debian "Stable" actually means "no regressions"; there's a reason for
that.

>Debian is created from a very conservative standpoint. The base system is guaranteed to run
on very modest hardware. While this is a good thing, businesses won't care. Their hardware
will almost never be older than 4 years.

Hardware that is stable and does the thing it was purchased for usually runs until the magic
smoke escapes.

>From a political point of view, Debian is completely right: Be Free!

From a business perspective they're right as well. When one finally needs to upgrade to a
newer version of the os, since the old version is no longer supported, debian is king. The
chances of a flawless upgrade are a lot larger when the entire system being upgraded consists
only of free software. And flawless upgrades result in less downtime.

Most of your criticisms are valid from a single end-user perspective and actually support a
business-case for using debian.
The only exceptions I can think of righ now are developer desktops, which tend to track the
latest hardware and businesses who have need of non-free software.

The only valid anti-business point you make is the unpredictable release cycle. It's why smart
businesses have competent in-house staff to keep tabs on debian, or hire someone who does.

>Debian is a very good distribution, for its purpose. But its purpose isn't to be used in a
corporate environment. 

Its purpose is to be a universal operating system, including the corporate environment, and it
is pretty succesful fulfilling that role.

>and an excellent basis for more business-like distributions like Ubuntu.

Maybe Debian lacks hype and friendly faces, but apart from these sales assets Ubuntu is just a
Debian that breaks down a lot (relatively). And 'breaks down a lot' is exactly the sort of
thing that serious businesses are trying to avoid.

Why linux-watch should be ignored

Posted Feb 4, 2008 19:28 UTC (Mon) by yoe (guest, #25743) [Link]

He's at it again...

Steven J. Vaughan-Nichols is someone who does not like Debian. For those of you who didn't
know so: just search on linux-watch.com for Debian, and see for yourself.

Of course there's nothing wrong with having an opinion; I'd just suggest that nobody take his
writings as "objective"...


Copyright © 2008, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds