Slashdot Mirror


Is CentOS Hurting Red Hat?

AlexGr writes "Jeff Gould raises an interesting question in Interop News: Why does Red Hat tolerate CentOS? The Community ENTerprise Operating System is an identical binary clone of Red Hat Enterprise Linux (minus the trademarks), compiled from the source code RPMs that Red Hat conveniently provides on its FTP site. It is also completely free, as in beer. CentOS provides no paid support, but it does track Red Hat updates and patches closely, and usually makes them available within a few hours or at most a few days of the upstream provider, which it refers to for legal reasons as "a prominent North American Enterprise Linux vendor." Free support for CentOS can be found in numerous places around the web, and a few third parties offer modestly priced paid support for those who want it."

370 comments

  1. nope, doesn't hurt RH by yagu · · Score: 5, Insightful

    I'm going to have to go with "doesn't hurt Red Hat" on many counts.

    • There's no such thing as bad publicity.
    • CentOS users are likely users who were looking for free anyway so the alternative would have been some other free distro.
    • A natural migration path for free CentOS users would be to require more support and since their universe is Red Hat-centric, the "pay for" version they'd likely choose would be Red Hat.

    I doubt too many sales are lost here.

    And the article's example doesn't really prove the point. So a shop of Red Hat users balked at upgrades and associated fees, and decided to go CentOS because they were a seasoned Linux shop. If it weren't CentOS, it would have been something else. The veteran shops will run Linux for free because they don't need the support, period. And they will find the distro that lets them do that.

    (And I'm not quite sure what the referenced Google graph is supposed to demonstrate. I suspect he's claiming the higher count and increase in hits for CentOS indicates more popularity, and lost revenues for Red Hat, but I see it as those needing to do their own support pretty much start with Google. Red Hat licensees will start with Red Hat support.)

    1. Re:nope, doesn't hurt RH by ScrewMaster · · Score: 5, Insightful

      I tend to agree with you. The article sounds a lot like the RIAA claiming that every illegally downloaded song directly equates to lost revenue, and it is just as flawed a perspective.

      --
      The higher the technology, the sharper that two-edged sword.
    2. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 2, Informative

      True. One thing you forgot to mention.

      RedHat does lots of partnerships with ISVs. That ensures that the ISVs will not support their software on CentOS, but genuine, licensed RedHat systems _only_. That's what made my employer buy some RHEL AS licenses.

    3. Re:nope, doesn't hurt RH by kebes · · Score: 5, Insightful

      And I'm not quite sure what the referenced Google graph is supposed to demonstrate. I suspect he's claiming the higher count and increase in hits for CentOS indicates more popularity, and lost revenues for Red Hat, but I see it as those needing to do their own support pretty much start with Google. Red Hat licensees will start with Red Hat support.
      Not only that, but it's entirely possible that people who have Red Hat systems (and Red Hat support) but are looking for a quick answer might do searches on CentOS sites. Similarly if you have an Ubuntu system you may very well do searches on Debian support (or vice versa) since the answers are usually interchangeable.

      As you said, if you have a supported Red Hat install, you're not very likely to be doing as many random Google searches in the first place. The rise in CentOS searches since its inception points to more interest in that distro, yes, but that by association also means more interest in Red Hat systems.

      I should also note that when I played around with Fedora, I found it somewhat unstable (not trying to start a flamewar here!)... which in a sense made me wonder about Red Hat as a distro. But then my experiences with CentOS showed me how stable and well put-together it actually is, which increased my opinion of RHEL.

      What I'm trying to say is, the fact that CentOS is such a solid distro is good publicity for Red Hat, because people get to sample the enterprise-quality polish and updating before they commit to support contracts. Red Hat's secret sauce has never been the binaries; it's always been the reputation for good support. And CentOS adds to this perception of a quality product; a net gain for Red Hat.
    4. Re:nope, doesn't hurt RH by boer · · Score: 2, Interesting

      Too bad you are conveniently "forgetting" the corporate customers who are likely to skip the RH license because of the free alternative. Say you have 20 identical server hardware? Why waste money for 20 licenses when you can buy one and install the free alternative on the other systems? In practise you get the support for all the 20 systems since the probelems are likely the same anyway.

      --
      (This sig intentionally left blank)
    5. Re:nope, doesn't hurt RH by cHiphead · · Score: 2, Interesting

      Too bad your are conveniently forgetting that REAL corporate customers want someone to sue when things go wrong. Short from some web based startup companies, not many will let a free OS with no support license or warranty get near their important data, especially when their less than technical lawyers read the terms of the GPL and say NO due to the viral nature of code linking to it (and not understanding how things can be linked with GPL code without getting sucked into the GPL).

      The problems among 20 identical servers might occasionally be the same, but Murphy's law always dictates that they won't be.

      Cheers.

      --

      This is my sig. There are many like it, but this one is mine.
    6. Re:nope, doesn't hurt RH by Cecil · · Score: 5, Interesting

      I don't know what kind of corporations you tend to work for, but every one I have ever worked for has considered OS licences part of the cost of doing business. They have no issue at all buying thousands of Windows licences, or a handful of $10,000 Oracle licences, why would they care about $100 RedHat licences? They really, truly don't. Besides, they're afraid of "free" things and that includes CentOS. They really like things that come with support, even if it's redundant and they have their own in-house team of developers. I've never worked at a company that whined about the cost of RedHat, most of them consider it remarkably cheap and an excellent bargain.

    7. Re:nope, doesn't hurt RH by Thwomp · · Score: 1, Offtopic

      Sorry I modded you down by accident. For some reasons the drop downs aren't working in firefox at the moment. This is the only way I know of undoing it. Cheers.

    8. Re:nope, doesn't hurt RH by mOdQuArK! · · Score: 5, Insightful

      Too bad your are conveniently forgetting that REAL corporate customers want someone to sue when things go wrong.

      That always makes me laugh. I've heard it repeated so many times, yet I don't think I've heard of a single high-profile case where a software-provider has been sued successfully for providing a defective product.

    9. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 0
      Redhat draws income from a lot more than selling Linux. They sell support, training among other things. That explains a lot of things.


      Second, contrary to what members of the community have suggested or thought over the years, Redhat is a community oriented company that has always given back and supported the community. Why shouldn't they allow/tolerate a community version of their code? They give it all away and know it's possible for that to exist.

    10. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 0

      you're right and its obvious. Is this article anything more than an advertisement for Cent OS? Redhat provides services over cent OS thats it. Redhat must comply with the GPL (which it is very happy to do) To top it off google is the determining factor? why not just judge a distro by hits on distro watch? PClinux is #1 on clicks.

      I'm not sure what the discussion should actually be here.

    11. Re:nope, doesn't hurt RH by moggie_xev · · Score: 1

      One reason corps buy real licenses is that they want to run packages which are only certified on Redhat and not on Centos. Its the support of the package which is important not the OS.

    12. Re:nope, doesn't hurt RH by argontechnologies · · Score: 1

      I think of it like this. Similar to MySql, smaller firms will start off with CentOS, then as money, and business demands allow and require it to, they move to RedHat. I think this is good for RedHat. The large an installed base, the more growing companies will migrate to it.

    13. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 0

      Yep, CentOS really isn't much different than Fedora, which Red Hat *gasp* sponsors.

      It's a stepping stone to the enterprise edition.

    14. Re:nope, doesn't hurt RH by jZnat · · Score: 1

      Ever read the EULA for proprietary software? They give no warranty and all other sorts of legalese which translates to, "You can't sue us even if our software causes a nuclear catastrophe."

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    15. Re:nope, doesn't hurt RH by nicolaiplum · · Score: 4, Informative

      Indeed! My company will (for the foreseeable future) need some RHEL licenses for the applications which the vendor only supports on RHEL, like SAP. We may run other things on CentOS, but if we didn't run them on CentOS, we'd probably run them on Debian; it's all either common free software or software we wrote ourselves and we don't feel like paying Red Hat for their product. SInce we can, effectively, run one quite similar OS all over without having to pay Red Hat for all of it, we do, and that's why we're not entirely leaving Red Hat. I can't believe we're the only company doing this. If Red Hat demanded that anything we ran that looked even vaguely like their OS had to be paid for, we would run entirely Debian/Ubuntu and start pressing application vendors to support Debian/Ubuntu and we would not be alone, and application vendors would give in, and then Red Hat's market would entirely evaporate.
      (Red Hat are not endearing themselves to us any by being further behind the feature curve than we would like, and by generally having quite unhelpful support if we have a problem - we perceive their added value to be small)

      --
      "For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled"
    16. Re:nope, doesn't hurt RH by vakuona · · Score: 4, Insightful

      It's not so much that they want someone to sue, but companies have to demonstrate that they took care to avoid unnecessary losses. Having a support contract with a company such as Redhat goes a long way to absolving managers of responsibility if something bad happens.

    17. Re:nope, doesn't hurt RH by meatspray · · Score: 1

      Meh, my vendors will not "support" it, but if you've paid for support from them, they'll "try" to get it working. Which of course almost always works identically to RHEL.

      and by my vendors I mean Dell, Commvault, EMC.
      and by metaphorically, I mean get your coat.

    18. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 0

      A well known company in my area has converted all Red Hat systems to CentOS systems, except where 3rd party vendor support contracts specify RHEL. They rarely used Red Hat support. From Red Hat's perspective this means a loss of $1.5 to 2 million per year that required virtually no effort on their part. Anecdotes aren't statistics, but surely this cannot be an isolated case, and it cannot be seen as a "positive" for Red Hat.

      That said, I love CentOS. I'd never be able to justify a RHEL license for my home servers, so CentOS lets me use the same OS at home and at work.

    19. Re:nope, doesn't hurt RH by matthewcraig · · Score: 1

      What about a shop that purchases a couple support Red Hat subscriptions, one for each of their hardware architectures, and then runs CentOS on the dozens or hundreds of similar servers sitting in the same server room? These shops leverage their single subscription to get technical support with all their servers, at a fraction of the "legitimate" price.

    20. Re:nope, doesn't hurt RH by schnikies79 · · Score: 2, Insightful

      I'm a bit off-topic here but I had to bring up what you stated, "There's no such thing as bad publicity." I don't know why people say that, the only thing I can think of is that they have no experience what-so-ever in marketing. A simply Marketing 101 will teach you otherwise.

      Bad publicity has destroyed products, bankrupted corporations and bankrupted people. Bad publicity definitely does exit.

      --
      Gone!
    21. Re:nope, doesn't hurt RH by Mahjub+Sa'aden · · Score: 2, Insightful

      Too bad your are conveniently forgetting that REAL corporate customers want someone to sue when things go wrong. This is either a moronic thing to write, or you're trying to write something else and this came out instead. Contrary to popular opinion, companies don't like to sue. Suing is expensive, time-consuming, and puts the issue in the hands of third-party: companies only like to sue when they're virtually assured of winning, or when some other consideration is in play that means they don't even have to win the battle to win the war, if you will

      What companies are trying to do is ensure
      • That they do due diligence to their shareholders
      • That they have the appropriate support channels available
      • That they cover their asses
      and not necessarily in that order.

      No-one, no-one wants to be in the position of having a critical system fail, and be caught holding the "oh I'm going to browse the CentOS forum for an answer" bag. No-one. The smart thing to do is buy a support contract, and when that critical system fails and you can't figure it out right away, you get the support you paid for.

      That's why people pay Red Hat money. Not because they want to sue Red Hat when things go wrong. Because they want to fix things when they go wrong.
      --
      What is is all that is. Isn't that obvious?
    22. Re:nope, doesn't hurt RH by SuperQ · · Score: 1

      Yep, I was running a Fedora box connected to an EMC array. We had a few issues with failover, and the people that supported the EMC kept saying "It's Fedora, you're not running redhat". So I re-installed the machine with CentOS. Still didn't work, so they said "CentOS isn't Redhat". Which is true, but bullshit. Finally one of the other guys supporting the server went over to the EMC admin's office, read the EMC manual for a bit and found that the EMC admin had no clue what he was doing and fixed the settings on the EMC that were causing the failover to not work.

    23. Re:nope, doesn't hurt RH by Chang · · Score: 1

      While I'm sure this does happen. The opposite does also happen.

      We pay for about 18 RHEL licenses. We also use plenty of CentOS.

      We don't call Red Hat for support. We tried it a couple of times in the first year and found the support isn't any better than what you get from the community.

      For the last 4 years we haven't made a call - we consider the RHEL licenses a donation for the many contributions that RH makes to the community.

    24. Re:nope, doesn't hurt RH by erroneus · · Score: 1

      The perception is that there is someone to be held accountable but we know there are clear and obvious limits just as in the case of Microsoft. Microsoft makes no guarantee that their software is suitable for anything at all and if it fails or causes a problem, it's on you. But it's certainly true that corporate decision makers lean in favor of the perception that there is someone that can be held accountable.

    25. Re:nope, doesn't hurt RH by Pollardito · · Score: 1

      besides it's hard to stay mad at those CentOS kids when they flash a big grin and hold up the roll of candy. it's not called The Freshmaker for nothing, what a clean-cut wholesome bunch

    26. Re:nope, doesn't hurt RH by Courageous · · Score: 1

      Redhat doesn't really sell their operating system. They sell an "entitlement," for support of their operating system. As long as you dance carefully around whatever few proprietary elements they intermingle, one doesn't even have to get packages from CentOS. Free support for your redhat is had as close as a Yum rebroadcaster away. I.e., get your patches once, with one entitlement, and rebroadcast all the updates for free.

      Redhat makes money basically because organizations are lazy.

      No big surprise, really. That's the Fedex's entire business plan. No one would believe the founder when he said people would pay more than triple for the rights to procrastinate until the last possible minute. Boy were they wrong. :)

      C//

    27. Re:nope, doesn't hurt RH by swillden · · Score: 1

      It's not so much that they want someone to sue, but companies have to demonstrate that they took care to avoid unnecessary losses. Having a support contract with a company such as Redhat goes a long way to absolving managers of responsibility if something bad happens.

      So, explain why they buy Windows, then.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    28. Re:nope, doesn't hurt RH by Jezz · · Score: 5, Insightful

      Well even if we accept that CentOS does hurt RedHat, what can RedHat actually do about it? The GPL stops them from squashing the product (which is exactly the point of the GPL). The GPL provides CentOS with a cast-iron defence from RedHat's legal team. Even if it didn't the reaction of users if RedHat did move against CentOS would be quite something.

      I'm pretty sure RedHat hate CentOS, why all the coy legal mumbo jumbo about who the upstream vendor is otherwise? But actually I see no real downside for RedHat. If you want to "learn" RedHat then CentOS is as good as the real thing (for that) and it really doesn't hurt RedHat to have more people skilled in their product.

      I actually like the CentOS product a great deal - and it fills the void left by RedHat Desktop 9.

    29. Re:nope, doesn't hurt RH by Sillygates · · Score: 1

      The analysis on the google stats is flawed as well.

      RHEL is not highly marketed to desktop PCs (the ones that would be searching google/browsing the net), and people are less likely to pay for that expensive service contract if they are not going to be running a datacenter, or at least a few mission critical servers.

      --
      I fear the Y2038 bug
    30. Re:nope, doesn't hurt RH by mOdQuArK! · · Score: 1

      Just another example of "managers" believing form-over-function then.

      Most of the people I've worked with in the past didn't give a damn whether you had signed up with some hoity-toity service company: if you couldn't fulfill your contractual obligations, they were going to come after YOU, not the service company.

      In a situation like that, blaming the service company isn't going to fly.

    31. Re:nope, doesn't hurt RH by Alsee · · Score: 1, Informative

      Did you read the same article I did?

      So the answer to the question in the title of this piece is: CentOS stings Red Hat just a little, but it doesn't hurt them badly enough to make them want to change the way they do business. Even better, it helps them hold the heads of the competing Linux server distros under water. The real victims of the roaring success of CentOS are Novell's SLES, Ubuntu Server and Larry Ellison's own RHEL-cloned Unbreakable Linux.

      Redhat is selling first class tickets with Champaign comfy seats and peace of mind at first class prices.
      the only customers Red Hat is really interested in are the ones who can fork over big bucks for a premium-branded product without even thinking about it, like the bulge-bracket Wall Street financial firms or the big telcos who run thousands or even tens of thousands of paid-up copies of RHEL in their data centers. In short, if you have to ask the price, you probably can't afford it

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    32. Re:nope, doesn't hurt RH by aonaran · · Score: 1

      Well, I know of at least one enterprise level product that used to use RHEL in their pre-packaged VMWare virtual appliance distribution option that has recently switched to CentOS simply to avoid licensing issues with the try before you buy appliance they were pushing.

      I imagine that other software companies that only supported their product on RHEL will probably also follow this trend as virtualization becomes more popular.

    33. Re:nope, doesn't hurt RH by dekemoose · · Score: 4, Insightful

      They have to make the source available, but not convenient. Currently they make SRPMs available, which makes the life of Whitebox, CentOS, et al, much simpler. If they really hated such efforts they'd just resort to making only tar balls available. Granted it's a short leap from tar ball to SRPM, but it's a step Red Hat doesn't have to take.

    34. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 0

      Except in this case it's **LEGAL**.

      Abjectly stupid article written by someone who doesn't get it.

      RHAT would look terrible if they came down on this. Their whle model is support based.

      So, this article is rank B.S.

    35. Re:nope, doesn't hurt RH by jimicus · · Score: 1

      I've worked in a few companies, and in my experience what you say is true... up to a point.

      "The point" in question is the point where the OS is of any importance. You may, for instance, have a core database/app server running something supported like Red Hat (or even a commercial Unix), then apache frontends which aren't really doing much running CentOS.

      In at least one case I can think of - granted, this was a few years ago - everything was so tied to the database that the database was commercial, paid for and supported. But the OS was treated as a commodity. (Mind you, it probably helped that we had a fairly extensive contract with IBM, all the servers were identical and barring hardware or power failure, it was practically unheard of for anything significant to happen to the running OS).

    36. Re:nope, doesn't hurt RH by fimbulvetr · · Score: 1

      Because you can get a support contract which effectively transfers blame from the low guy on the totem pole to the company providing the support.

      Somewhere in the mix, the CEO looks to the CTO/CIO to get problems fixed. When the problems don't get fixed, the CTO looks to the management who look to the workers who look to the support contract.

      If you're a worker bee in such a company, or even management, it behooves you add this job security cushion into the mix.

      I'd normally call such people who need to resort to calling support "incompetent" due to the fact that most larger companies I work for simply default to calling support, but there are times where such calls are necessary because you just can't know everything.

    37. Re:nope, doesn't hurt RH by ydrol · · Score: 1
      Funny, talking of bad publicity, just reading an article on Gerald Ratner today!

      Still he's back on his feet now And even getting paid for motivational speeches.

    38. Re:nope, doesn't hurt RH by renegadesx · · Score: 2, Informative

      Agreed, this is the primary purpose of the GPL and what makes open source so great. This idiot would be better off asking "Does Oracle Unbreakable Linux hurt Red Hat?" As they DO provide commercial support.

      By this guy's logic he should ask himself "Does Fedora hurt Red Hat?" "Does Linspire hurt Ubuntu?"

      The reason RHEL is in the #1 seat isn't just because they have a great product (which they do) but their support is brilliant as well. Companies that want paid support take that into consideration.

      --
      Make SELinux enforcing again!
    39. Re:nope, doesn't hurt RH by Antique+Geekmeister · · Score: 1

      Or they funnel all their support calls for duplicate installations of RHEL into the one registered license, and use that to download updates. I recently spoke to an engineer trying to talk his employer out of doing that, and switch to CentOS in order to eliminate the licensing violation.

    40. Re:nope, doesn't hurt RH by ePhil_One · · Score: 4, Insightful
      If they really hated such efforts they'd just resort to making only tar balls available.

      They need to make SRPMS available to customers. Its trivial for CentOS to be a customer, hence fighting that battle is a losing proposition.

      That said, plenty of evidence exists that Red Hat is OK with CentOS, they are just protecting the Trademarks to avoid losing them.

      --
      You are in a maze of twisted little posts, all alike.
    41. Re:nope, doesn't hurt RH by Daniel+Phillips · · Score: 2, Informative

      Currently they make SRPMs available, which makes the life of Whitebox, CentOS, et al, much simpler. If they really hated such efforts they'd just resort to making only tar balls available. The GPL says otherwise: "For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable." It would be a prohibitive amount of work to package up the installation scripts in tarball form (if that is even possible) and then there would be the PR cost of being perceived as a GPL evader.
      --
      Have you got your LWN subscription yet?
    42. Re:nope, doesn't hurt RH by swillden · · Score: 1

      Because you can get a support contract which effectively transfers blame from the low guy on the totem pole to the company providing the support.

      But most companies that buy Windows don't buy a support contract (excepting servers, usually).

      So why, then, do they buy Windows?

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    43. Re:nope, doesn't hurt RH by max+cohen · · Score: 1

      Yup, same here. We have over 300 servers and a couple of us in our dept. insisted that we pay Red Hat instead of going CentOS only, which we easily could've done. Never use the support but also know that Linux would be in a different position today if it weren't for Red Hat's work.

    44. Re:nope, doesn't hurt RH by Hognoxious · · Score: 1

      My company will (for the foreseeable future) need some RHEL licenses for the applications which the vendor only supports on RHEL, like SAP.
      Last time I looked, SAP was also certified on SuSe - at least, for certain versions of each. Getting it running on CentOS is on my copious free time stack.
      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    45. Re:nope, doesn't hurt RH by Hognoxious · · Score: 1

      You seem to be confusing 'companies' with 'corporate nmangers and decision makers'. Their interests aren't as aligned as you seem to think.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    46. Re:nope, doesn't hurt RH by Anarke_Incarnate · · Score: 1

      Unfortunately for them, Novell's support pisses on Red Hat's support from a substantial height. I have used both. The way I measure support from any vendor is to compare them to Novell's as well as pre-merger Veritas.

    47. Re:nope, doesn't hurt RH by Anarke_Incarnate · · Score: 1

      Because a good portion of the software they think they need runs on it. They don't know any better, otherwise

    48. Re:nope, doesn't hurt RH by tftp · · Score: 1

      Leaving servers aside, companies buy Windows because it works, and costs reasonably, and runs all the software. What other reasons did you expect?

    49. Re:nope, doesn't hurt RH by tftp · · Score: 1
      Imagine that you just bought a $10,000 server, and as it boots it says:

      00:00:00 foodrv *** ERROR 123, ABORTING EXECUTION ***

      and the whole thing crashes. If you do not have a support conract with the company who wrote foodrv.o and uses it for some, unknown to you, reason what you are going to do? And if a manager comes and blames me for this, I'd tell him something.

    50. Re:nope, doesn't hurt RH by TClevenger · · Score: 1

      CentOS has made sales in my company for Red Hat. I use CentOS for my lab and test systems, and Red Hat for my production systems that might need support.

    51. Re:nope, doesn't hurt RH by mark*workfire · · Score: 1
    52. Re:nope, doesn't hurt RH by TClevenger · · Score: 1
      Not only that, but it's entirely possible that people who have Red Hat systems (and Red Hat support) but are looking for a quick answer might do searches on CentOS sites.

      Good point. I find that I often find answers to my CentOS and Red Hat questions in Fedora or CentOS forums. More people hacking (and playing around) on the same/similar code case helps everyone, especially Red Hat.

    53. Re:nope, doesn't hurt RH by vakuona · · Score: 1

      Which is why Redhat concentrates on the server business. Most time if your windows desktop crashes and you have to restart, the losses are minimal. Annoying, but hardly earth shattering.

      If a company has to be down the whole day because your servers are down, then that is a bit more of a problem.

    54. Re:nope, doesn't hurt RH by m2943 · · Score: 2, Insightful

      Well even if we accept that CentOS does hurt RedHat, what can RedHat actually do about it? The GPL stops them from squashing the product

      Linux isn't entirely covered by the GPL; parts of it are BSD, Apache, and other licenses. Furthermore, RedHat could easily use a non-GPL license for some of their contributions.

      CentOS exists because RedHat made the choice to keep things open and available.

    55. Re:nope, doesn't hurt RH by cyberon22 · · Score: 1

      Left out one thing that struck me... maybe Red Hat will find a way to monetize the CentOS distribution channel in the future. There's no reason to crush something that you might be able to leverage in the future, or cause problems for it at all.

      Get the traffic/usage and then figure out how to monetize it. Especially if someone else pays for the bandwidth.

    56. Re:nope, doesn't hurt RH by sumdumass · · Score: 1

      Off topic,
      but how is your experience with commvault? Would you recommend it to others. I keep having issues that never get resolved. On a side note, I have to go through Dell's support because I purchased their file server edition with an LTO2 drive. It has been going unresolved since august but some of that is my fault for not being able to take the servers down except at specific times.

      Over all, in your honest opinion, should I continue to work on getting it going (is it worth it?) or should I just ask for a refund and use another solution? I have a windows 2000 server and 2 linux boxes I need to backup. No active directory but I house 2 of the servers in a building across town that is connected by a T1 and the one server (where the LTO2 drive is) hits 4 different network subnets. I'm thinking it is more my set up then their software but I'm also thinking that it has to be damn good software for me to waste much more time on it. (their activation software is part of the problem)

      Thanks for any opinions you might have.

    57. Re:nope, doesn't hurt RH by jamstar7 · · Score: 1

      It's not so much that they want someone to sue, but companies have to demonstrate that they took care to avoid unnecessary losses. Having a support contract with a company such as Redhat goes a long way to absolving managers of responsibility if something bad happens.

      It also helps cut down on insurance premiums against data loss if the company can show a support contract to a recognised software vendor. RedHat is one, so is Microsoft.

      Nobody ever got fired for specifying Microsoft...

      --
      Understanding the scope of the problem is the first step on the path to true panic.
    58. Re:nope, doesn't hurt RH by doktorjayd · · Score: 1

      Getting it running on CentOS is on my copious free time stack

      this is often pretty simple. just change ( or create ) /etc/redhat-release to have the same contents of whichever RHEL you are 'emulating'.

      this has allowed me to run numerous 3rd party apps on centos and fedora ( a quick eyeball of the installation shell scripts will show ya what it looks at to determine the distro its trying to install on...)

    59. Re:nope, doesn't hurt RH by dbIII · · Score: 1

      It's like saying you pay more to buy Dell so you would get support. People actually did say that some time ago.

    60. Re:nope, doesn't hurt RH by RunzWithScissors · · Score: 1

      I don't know whether or not CentOS hurts Red Hat or not, /. readers make good points on both sides of this arguement. However, the "It's GPL Red Hat has to tolerate CentOS!" argument is somewhat flawed.

      CentOS is built from the src RPMs that Red Hat provides which puts them in compliance with the GPL (v2). From what I hear, the CentOS folks have scripts that search through the source code tars contained in the src RPMs and strip out all the Red Hat logos, Trademarks, etc. and then compile the packages for CentOS. Which, consequently, is how CentOS is able to make the updates available for their distro so quickly. But realize that the GPL does not dictate the format of the source code that has to be provided. In fact, the GPL (v2) simply states that the source code must be supplied in an "easily accessible format" to requestors. So Red Hat _could_ cat all the source code that makes the RHEL distro into one giant text file. In doing so, they would still comply with the requirements of the GPL, but would totally bork folks like CentOS who are making derivitive distributions from it and would make Red Hat unbelievably large jerk wads...

      -Runz

    61. Re:nope, doesn't hurt RH by sumdumass · · Score: 1

      Simple,

      start selling generic "best effort" support for CentOS servers if the customer already has RHEL support contract. Then they would be making money from a customer having both. Just don't advertise it so people think future purchases can be avoided.

      They can claim they don't officially support CentOS but are willing to give it "the old college try with no promises" if an existing customer needs it. and for that matter, why limit it to just CentOS, they can offer cutrate or crossover support for any redhate like OS they handle.

    62. Re:nope, doesn't hurt RH by ragefan · · Score: 1

      Yep, CentOS really isn't much different than Fedora, which Red Hat *gasp* sponsors.

      It's a stepping stone to the enterprise edition. This is completely wrong. CentOS *IS* the Enterprise Edition of Red Hat, and therefore very different from fedora. CentOS is exactly the same as RHEL. Fedora and CentOS have very different goals. Fedora is the testing distro for RHEL and gets software version updates, where as RHEL (and therefore CentOS) only get security backports. While there are yum repo's available for CentOS to add additional software or newer versions, the default [base] and [updates] repo's are same as upstream.

    63. Re:nope, doesn't hurt RH by sumdumass · · Score: 1

      You forgot that the technicians to fix it are a dime a dozen compared to finding a competent *nix admin. This was the defining factor in a couple MS TCO studies where they basically claimed that *nix support and admins cost more.

      And your forgetting that the employees they hire will have somewhat of a working knowledge of windows compared to linux/BSD (for desktop or server) because it is what they used at home and at school where their other exposure to computers was.

    64. Re:nope, doesn't hurt RH by ScrewMaster · · Score: 1

      They really like things that come with support, even if it's redundant and they have their own in-house team of developers.

      I would say that long-term availability is even more important to corporations than support. Your in-house support staff is useless if the product itself vanishes from the marketplace. That's really Windows sole perceived advantage from the beancounter perspective: yes it costs a lot for what you get but at least the vendor will still be selling it for the foreseeable future. Now, that doesn't account for the fact that Microsoft has no problem obsoleting entire classes of third-party applications with new releases of Windows, or in the case of Vista basically shipping an entirely new OS (what is it? 70% rewrite?). It also doesn't account for the fact that, with GPLed software at least, the software will always be available even if the original vendor folds. I think that awareness of those two facts would do much to promote the cause of open source software in the commercial world.

      --
      The higher the technology, the sharper that two-edged sword.
    65. Re:nope, doesn't hurt RH by gdek · · Score: 5, Informative

      "I'm pretty sure RedHat hate CentOS."

      1. No, we don't. At least, not most of us -- because most of us actually *understand* the business we're in. That's why we're making all this nice money. If we did hate CentOS, we could make it awfully difficult for them in any number of ways -- delaying updates, hiding marks and making them play "where's Waldo" every release, that sort of thing.

      2. The "coy mumbo jumbo" about the upstream vendor has to do with trademark protection, not hate. We don't want "Red Hat" to turn into "Kleenex".

      3. Here's a question: why is there no CentOS equivalent based on SuSE products? Think about it.

      4. A lot of the significant people in the CentOS community are actually important and respected members of the Fedora community as well. That way, Red Hat benefits from the work of the more savvy CentOS users. That's how open source works, you see.

      5. It's Red Hat, with a space. Not RedHat. Get it right, or we'll send you a cease-and-desist letter. (I'm kidding. Probably.)

    66. Re:nope, doesn't hurt RH by turbidostato · · Score: 1

      "A well known company in my area has converted all Red Hat systems to CentOS systems, except where 3rd party vendor support contracts specify RHEL. They rarely used Red Hat support. From Red Hat's perspective this means a loss of $1.5 to 2 million per year that required virtually no effort on their part. Anecdotes aren't statistics, but surely this cannot be an isolated case, and it cannot be seen as a "positive" for Red Hat."

      I think you yourself should re-read your own text. They moved from Red Hat to CentOS because Red Hat made no bussiness case for them. Why they didn't move from Red Hat to i.e. Debian? On your own account those 1.5;US$ were *already* lost: Red Hat added nothing and their client just moved away. *But* thanks to CentOS they didn't moved too far away: they still retain Red Hat for their certified platforms instead of going i.e. with Debian/Ubuntu. They are still focusing their technical abilities on Red Hat so you can bet next time they need a certified platform for a third party hardware/software avaliable for SUSE, Ubuntu and Red Hat they will go with Red Hat.

      CentOS allowed Red Hat to minimize their looses, quite a good thing for them on my account.

      "That said, I love CentOS. I'd never be able to justify a RHEL license for my home servers, so CentOS lets me use the same OS at home and at work."

      Once more, due to CentOS what platform are you proficient with? What do you think would happen to Red Hat bussiness if you and all your likes were using Ubuntu at home instead of CentOS?

    67. Re:nope, doesn't hurt RH by 'nother+poster · · Score: 1

      Damn, where do you get $10k Oracle licenses? We have to drop an average of $26k PER CPU for oracle.

    68. Re:nope, doesn't hurt RH by meatspray · · Score: 1

      Off Topic
      Well we have very different needs. I have 70 servers in 26 sites comprising about an 8TB footprint.
      Synthetic fulls and high throughput are saving my bacon. I upgraded from backup exec and a 132T with
      2 LTO2's to a 6 drive 128 tape LTO3 solution. We spent a few bucks.

      Dells Commvault (CV) support is lacking. It's been hinted that I can go through Dell to renegotiate direct CV support
      but I don't know how that works with the lite versions. I'm not even sure the interface is the same.

      I also took the class which was fantastic. I'd still be wandering around the app blindly.

      A little hint... The one thing they drilled in to our heads at the class... I thought it was propaganda at the time:
      If you're having a problem, it's most likely going to be in your hardware or your network. Reverse DNS HAS to be PERFECT. Connections have to be solid. Tape drives need to be the latest firmware revision, drivers have to be up to date. When in doubt, use Microsoft Backup and try to back up target, if that works at decent speed, it's CV or a CV setting.

      The most impressive thing I've seen so far, right after install we were doing our first full. It was about 80% done and in the middle of a multi-terabyte set. We were dorking with the commserve at a very low level and destroyed it. Backups all locked up. We ended up reloading from scratch and restoring the DR. After the DR finished and rebooted the backups picked back up, right at the 64KB block they left off. It was surreal, like nothing happened at all.

      The only two things I have bad to say are: 1. It could be a little more forgiving on network issues. and 2. The default mode for a failed backup is no data protection. By default if the backup completes with failure, you cannot restore from it without a special license and a data explorer. I'm used to BE failing all the time but being able to get whatever i can back out of it as if nothing went wrong. You need to stay on top of your backups with CV.

      If you want to chew the fat about it, I'm doormouse where that g mail happens.

    69. Re:nope, doesn't hurt RH by ivan256 · · Score: 1

      All they need is the spec file, really... But it's trivial to generate SRPMs from those.

    70. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 0

      > It's Red Hat, with a space

      Hunting the spaces (or lack thereof) would probably be a bad idea.
      In some languages "d" and "t" in the end of the word sound the same.
      So, at least be thankful they don't call it Rat Head :-)

    71. Re:nope, doesn't hurt RH by Monsuco · · Score: 1

      If they really hated such efforts they'd just resort to making only tar balls available.
      If they really hated CentOS, couldn't they simply do tarballs but get rid of the makefiles?
    72. Re:nope, doesn't hurt RH by Dark_Gravity · · Score: 0

      "I'm pretty sure RedHat hate CentOS."
      3. Here's a question: why is there no CentOS equivalent based on SuSE products? Think about it.

      There is. It's called openSUSE.

    73. Re:nope, doesn't hurt RH by swillden · · Score: 1

      Because a good portion of the software they think they need runs on it. They don't know any better, otherwise

      Read the thread. The claim was that companies buy Microsoft so they have someone to sue.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    74. Re:nope, doesn't hurt RH by Mr.+Heavy · · Score: 5, Informative

      This is a pretty bad comparison. The relationship between SUSE and openSUSE is much closer to that of Red Hat and Fedora than of Red Hat and CentOS. openSUSE is a fully Novell-sponsored initiative that basically functions as a testing sandbox for the enterprise OS, much like Fedora serves as the base for much RHEL functionality. CentOS is a third-party effort with no official backing from Red Hat whatsoever.

    75. Re:nope, doesn't hurt RH by goodtim · · Score: 2, Interesting

      You hit the nail on the head with this one. No IT manager wants the hammer to fall on them when the shit-hits-the-fan and they have to explain to senior management that a mission critical application went down because the free (as in beer) operating system they were running offered no support. The cost of a RHEL license ($1200) is nominal when you look at the cost of downtime of a major application running in a large business. Not only in terms of revenue, but time spent by IT staff to correct the problem. Having someone to call (in this case RedHat) and say "Fix it", is just good business.

      On somewhat related note...

      I have to ask, who writes these articles? They really have no bloody clue what they are talking about. I swear I am going to find the dude who invented the "blog" and kick him in the nuts. It has resulted in nothing but an endless crapshoot of self-rightious wankers who get off listening to themselves spew garbage on topics which they have not the slightest clue. To make matters worse, there seems to be a plague of mass-stupidity running ramped through the internet where people actually read this shit, and even worse, submit it to Slashdot. Oh how I long for the days where there were these people called "journalists" who did "research" and wrote about "news". Somehow we've ended up somewhere where any old retard can become a "blogger" and pollute our news sites and RSS feeds with their diarrhea-of-the-mouth.

      --
      "Flee at once, all is discovered."
    76. Re:nope, doesn't hurt RH by sumdumass · · Score: 1

      I thank you for your reply. Looks like you have a lot larger setup then I do. I'm looking at backing up 60 gigs per server x3 that will have another 520 gigs with only minor changes happening to it on two of the servers as soon as the aerial photo's come in. Nothing major, just oddities in the setup (one building is a xxx.xxx.7.X network, the other is a xxx.xxx.8.X with the routers going to the T1 having a xxx.xxx.9.X).

      It sounds like I am just going to be better off going with something else. I'm hesitant to say exactly what troubles I am having because I'm fairly confident that it has to do with my setup and not the program. I cannot even find google searched listing my problems which lends the belief that they are unique to my setup. But basically, I cannot get the server portion (media agent) of the software to even give me the option to install on the windows 2000 server so we rigged up another box with a gigabyte Ethernet in a sans like configuration which has 4 separate network cards with separate networks (that connects to 2 different offices inside the same building but not directly related to us). Now I cannot install the client portion of the software on the 2000 machine (which I was able to before giving up on the server portion).

      The makeshift mess of a box won't activate, every time we attempt to install the license file it gives an error about not listing all the network IPs.

      Thanks for your input and opinion. You have basically confirmed my suspicions that even if I end up with it installed correctly, the issues are probably just beginning. I'm sure the network is going to be up to par but I am already frustrated enough over the install issues that I don't want to find out.

    77. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 2, Interesting

      In my particular instance, CentOS has actually helped Red Hat. If not for CentOS I would be using some other free distribution on the servers I manage. Because we use CentOS my company pays for my RHCE and will be paying for my upcoming RHCA certification. If we were using some other distribution then there wouldn't be value in taking the Red Hat classes. So Red Hat makes more from us with CentOS around.

    78. Re:nope, doesn't hurt RH by QuasiEvil · · Score: 3, Interesting

      I'm glad Red Hat's folks "get it". Personally, I have no need for a multi-gazillion dollar support contract for my home webserver. But it's sure nice to have one that has the same sort of product support lifecycle as RHEL, and is set up exactly the same. In return, you know what gets specified as the OS of choice on all of my mission-critical boxes at work? You got it - RHEL, with support contracts. Because at work, my boss feels I have more important things to do than compatibility testing and chase around weird OS bugs, and we've been pretty happy with RH so far.

      A big thanks to RH for continuing to support the community by not throwing a wrench into projects like CentOS, Whitebox, etc...

    79. Re:nope, doesn't hurt RH by sg_oneill · · Score: 1

      If they really hated CentOS, couldn't they simply do tarballs but get rid of the makefiles?


      Because the make file is part of the source, thus it'd be a GPL violation.
      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    80. Re:nope, doesn't hurt RH by Zeio · · Score: 0, Offtopic

      I agree with the "not hurting."

      We CentOS users generally buy at least one copy of the fully supported RHEL and file bugs and work like crazy to get the CentOS product to be better by working with RedHat on their bugzilla and on their OS. If you "aren't very good with Linux/*nix" and you buy RHEL you are getting a **lot** of testing and bug squashing by not only RedHat but also all the CentOS folks. Without CentOS, people would be defecting from RedHat to things like SuSE and other distros in my estimation.

      --
      Legalize the constitution. Think for yourself question authority.
    81. Re:nope, doesn't hurt RH by marafa · · Score: 0

      good points but you forgot one though:
      if a company wants an SLA that basically means they have production critical need for support. which also means they have to be within the support matrix ergo. they need redhat.
      for example. to stay within the oracle support matrix, you need a certified linux distro like redhat AND certified hardware.
      so their want is actually a need for redhat

      --
      _ In Egypt Networks: Network Solutions with a Twist
    82. Re:nope, doesn't hurt RH by petermgreen · · Score: 1

      If they really hated CentOS, couldn't they simply do tarballs but get rid of the makefiles?
      RTFL

      RMS was very clear on his definition of source code to head off this sort of problem.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    83. Re:nope, doesn't hurt RH by G+Morgan · · Score: 2, Interesting

      "The source code for a work means the preferred form of the work for
      making modifications to it."

      Clearly YANAL. Red Hat cannot make excessive changes to the source that are obviously made to obstruct modifications or building. The GPL does indeed specific what constitutes source code for a work.

    84. Re:nope, doesn't hurt RH by Chemicalscum · · Score: 1

      So, at least be thankful they don't call it Rat Head :-)

      Wow! I have been desperately looking for the name for a Red hat clone I am about to Launch, now I have found it !

    85. Re:nope, doesn't hurt RH by jez9999 · · Score: 1

      Well even if we accept that CentOS does hurt RedHat, what can RedHat actually do about it? The GPL stops them from squashing the product (which is exactly the point of the GPL). The GPL provides CentOS with a cast-iron defence from RedHat's legal team.

      Well quite. What is this trollish nonsense about Redhat 'tolerating' CentOS? CentOS is benefitting from the GPL just as *Redhat* benefitted from it by getting a free GPL kernel and 10001 free GPL userspace tools. Redhat have no right to stop people using their GPL source, and anyone who says so is pretty much a dumbass.

    86. Re:nope, doesn't hurt RH by galoise · · Score: 1

      Red Hat _could_ cat all the source code that makes the RHEL distro into one giant text file. In doing so, they would still comply with the requirements of the GPL, but would totally bork folks like CentOS who are making derivitive distributions from it

      IANAL, but isn't "making derivative distributions" one of the explicit objectives of the GPL? i would think that taking steps to prevent the making of derivative anything (work/distributions/binaries, whatever...) would be indeed a violation of the GPL.

      isn't the GPL kinda a contract? if such, it is regulated by the "good faith" principles of civil law, isn't it? I'd think that such schemes would be a violation, as their sole purpose good be to humper or technically prohibit the modification or work upon of the licensed work, wich is what the GPL specifically aims to protect.

      --
      entia non sunt multiplicanda praeter necessitatem
    87. Re:nope, doesn't hurt RH by phaze3000 · · Score: 1

      As someone who runs a small Linux consultancy firm I can tell you it's very true that many customers like to check there's someone to sue, and not just big corporates. I'm often asked by customers if we have professional indemnity insurance, and for how much. No-one's ever tried to sue us yet, but then we've never got anything major wrong either. I initially took out the policy on the basis of prudence, but I've since found that it seems to be a good sales tool.

      --
      Blaming GW Bush for the Iraq war is like blaming Ronald McDonald for the poor quality of food.
    88. Re:nope, doesn't hurt RH by dpilot · · Score: 4, Funny

      Please stop having such reasonable and enlightened attitudes.

      People here want to see Red Hat as turning EVIL, and you're making problems with that perception.

      --
      The living have better things to do than to continue hating the dead.
    89. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 0

      Yeah, if you could file suit over a defective OS, MS would have been bankrupt 15 years ago. If you ever read the fine print of any software license you should realize that the "provider" is relieving themselves of all responsibility for the product and any harm it may do. The truth is you can't sue.

      The "throat to choke" theory is based on economic retaliation and only works if you are big enough or visible enough. ie. If you don't get this to work right, I won't buy anymore and I will make sure everyone in my industry knows not to buy your product.

    90. Re:nope, doesn't hurt RH by idontgno · · Score: 2, Funny

      Blame is still transferable in this case. C'mon, we've all seen it done.

      "What's wrong with the Financials DB?"
      "Meh, Windows."
      "Ooohh..."

      Blame... TRANSFERRED.

      It even works at higher levels.

      "PHILBY! WHY HAS THE FINANCIALS DATABASE BEEN DOWN FOR THE LAST SIX HOURS!??!?"
      "Errrrm.. Geekly in Server Support says it's a Windows thing."
      "GRrrrrr...."

      Blame... TRANSFERRED.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    91. Re:nope, doesn't hurt RH by AmyRose1024 · · Score: 1

      What about those of us who don't want to see Red Hat turn evil?

    92. Re:nope, doesn't hurt RH by David_Hart · · Score: 1

      I agree that CentOS doesn't hurt RedHat. I've begun using CentOS in our enterprise environment for application testing. We can bring CentOS up on a VMWare System, apply all of the latest patches, and then load the application that we are testing. When we are finished testing, we then put the application into production using RHEL. David

    93. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 0

      Nail this moderation in meta-moderation. This is not offtopic. This moderator should be removed from the eligible moderator pool.

    94. Re:nope, doesn't hurt RH by mnmn · · Score: 1

      You forgot the most important one:
      CentOS is the Fedora that Fedora should have been.

      --
      "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    95. Re:nope, doesn't hurt RH by nuzak · · Score: 1

      Actually, RMS has insisted on full sources being available at the point of distribution, not just diffs. He was really quite inflexible on this point with regards to the sole SuperH developer for gcc at the time (I think it was SuperH), and actually chased him off the project because the bandwidth and storage costs for it at the time were infeasable for the developer to accede to the demands. Obviously things have evolved since then (and RMS no longer personally does GPL enforcement), but it does show that the interpretation could go either way.

      Now there's certainly nothing stopping redhat from making updated SRPM availability contingent on having a copy of RHEL, though they can't stop them from being redistributed. Redhat figures that if all it takes is a "leak" to redistribute, they may as well not try to restrict it anyway -- they just don't loudly advertise it.

      Redhat's largely a services company. RHN is semi-decent for asset tracking to see what servers need what updates at a glance. Nothing like what Sun offers, but certainly a fraction of the price.

      --
      Done with slashdot, done with nerds, getting a life.
    96. Re:nope, doesn't hurt RH by nuzak · · Score: 1

      Whoops, it was Coldfire, not SuperH.

      --
      Done with slashdot, done with nerds, getting a life.
    97. Re:nope, doesn't hurt RH by nuzak · · Score: 1

      > isn't the GPL kinda a contract?

      Only "kinda". It's a license, and is covered by copyright law, and not contract law. They overlap a bit, but not as much as you might think.

      --
      Done with slashdot, done with nerds, getting a life.
    98. Re:nope, doesn't hurt RH by dpilot · · Score: 1

      Consider the entire article to be (-1) flamebait and move along.

      --
      The living have better things to do than to continue hating the dead.
    99. Re:nope, doesn't hurt RH by rk · · Score: 4, Insightful

      'I swear I am going to find the dude who invented the "blog" and kick him in the nuts. It has resulted in nothing but an endless crapshoot of self-rightious wankers who get off listening to themselves spew garbage on topics which they have not the slightest clue.'

      I'm going to take a guess and say you've never seen Usenet, have you?

    100. Re:nope, doesn't hurt RH by Volta · · Score: 2, Interesting

      I work for a company that does whine about the cost of RHEL. Unfortunately, we are not talking about $100 licenses here (at that price we would just buy licenses for every server), we are talking about either a $349 per server per year subscription for the cheapest option on 2 socket or smaller servers, or a $1499 per server per year subscription for the larger servers. When the annual OS subscription cost for a server is higher than the annual hardware maintenance contract cost, it gets hard to justify.

    101. Re:nope, doesn't hurt RH by nuzak · · Score: 1

      > CentOS is the Fedora that Fedora should have been.

      Erm, Redhat is the Fedora that Fedora was 6 months ago. Fedora exists for that reason.

      --
      Done with slashdot, done with nerds, getting a life.
    102. Re:nope, doesn't hurt RH by swillden · · Score: 1

      Perception IS reality, isn't it.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    103. Re:nope, doesn't hurt RH by ivan256 · · Score: 1

      I understand your example, but I'm not sure how it fits in context.

      You realize that an SRPM is just a CPIO archive containing pristine sources, maybe some diffs, and a spec file, right? Redhat *doesn't* provide modified sources. They *only* provide diffs. It just so happens that they also provide a tool that will automatically apply the diffs and compile the program.

    104. Re:nope, doesn't hurt RH by iRegister · · Score: 1

      Thanks to the RIAA, I hardly buy music anymore, ever since I stopped downloading from illegal sources. Their lawsuit profiteering directly hurts the artists.

      --
      A fast cowboy since 2007
    105. Re:nope, doesn't hurt RH by ScrewMaster · · Score: 1

      Did you read the same article I did?

      Nope. Just read the summary ... I'm amazed that my comment got modded Insightful.

      --
      The higher the technology, the sharper that two-edged sword.
    106. Re:nope, doesn't hurt RH by ScrewMaster · · Score: 1

      Their lawsuit profiteering directly hurts the artists.

      Yeah. Doesn't do a whole lot for the suees either.

      --
      The higher the technology, the sharper that two-edged sword.
    107. Re:nope, doesn't hurt RH by Anonymous Coward · · Score: 0

      CentOS doesn't hurt RedHat but
      CentOS pirates RedHat software.

      What is the problem?
      No problem, the RedHat software is GPL'ed, so CentOS was forking it.

      But, CentOS was removing the trademark "RedHat", what is the problem?
      No problem, it's not a "copyright law" because CentOS wan't to violate the "trademark law" so CentOS made the correct procedure.

      The solution for RedHat in this case is nothing. It was FUD, FUD, FUD since announce of the RedHat's trademark.

      If the client wants supporting then he can to deal with RedHat, but if he wan't then the supporting IS NOT an obligation.

      Sr. Pzarro: TCO = US$ 0.00, i've 100'000 machines x US$ 0.00 of TCO = US$ 0.00 What is the problem with my zero T.C.O.?.

    108. Re:nope, doesn't hurt RH by Cecil · · Score: 1

      My company has a "vendor partner agreement" with Oracle. Which means basically that we whore ourselves for cheaper rates by agreeing to inflict Oracle on all our customers too. For the record, I despise Oracle, and if we weren't so in bed with them, I would be eagerly sticking Postgres everywhere whether they like it or not. But I don't really like where I'm working anyway, so, let them and their customers suffer as far as I'm concerned. Yay apathy!

    109. Re:nope, doesn't hurt RH by Raenex · · Score: 1

      because most of us actually *understand* the business we're in Yes, you do. You guys are the open source version of Microsoft. You're doing exactly what RMS was worried about when he started GNU -- building on top of the source and becoming the "standard" version of a GNU-based system. You do it via trademark poisoning. It's completely against the spirit of the GPL that binary copies of Red Hat CDs can't be redistributed. Instead the source has to be carefully scrubbed and recompiled. I remember the days when you could get an exact copy of Red Hat for a buck from Cheap Bytes, before all this "enterprise" lockdown.

      The question isn't "Why does Red Hat tolerate CentOS?", but why does FSF tolerate Red Hat? I suppose it's because they eventually get the source back, even if it means they have to they have to manually "clean" it before they can re-release it. Who ever said RMS is an extremist that doesn't compromise?
    110. Re:nope, doesn't hurt RH by quanticle · · Score: 1

      Linux isn't entirely covered by the GPL; parts of it are BSD, Apache, and other licenses.

      Right. However, the main thing is that the kernel is protected by GPL. As long as you have the kernel, you can get the other stuff from primary sources. It'd take more work, but its hardly impossible. After all, its what all the primary distros (e.g. Debian, Slackware, etc.) do.

      Furthermore, RedHat could easily use a non-GPL license for some of their contributions.

      That also depends on what pieces of the Linux kernel they're modifying. IANAL, but I think that the GPL mandates that code linking to strict GPL libraries also be under the GPL. Its the LGPL that allows linking from different license schemes. Given that much of the kernel is protected by GPL, RedHat has to make its additions under the GPL as well.

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
    111. Re:nope, doesn't hurt RH by jbolden · · Score: 1

      I used Red Hat even before those days and the Red Hat that was available pre Enterprise is essentially Fedora which you can get from CheapBytes.

    112. Re:nope, doesn't hurt RH by Raenex · · Score: 1

      Two points. There was a long time before Fedora where no version of Red Hat was freely distributable without "scrubbing". Second, the existence of Fedora does not mitigate the "enterprise" lockdown of GPL'd software.

    113. Re:nope, doesn't hurt RH by jbolden · · Score: 1

      Fedora 1 released November 6, 2003
      RH Linux 9 released March 31, 2003

      Given bug fixes and prerelease versions I'm hard pressed to see any break at all. Moreover it should be remembered that Fedora 1 was a major shift in the code base from RH linux 9 because the purpose had changed. So frankly I don't see any evidence that RH hasn't been providing a freely available version for years.

      As for RHEL... the GPL has always specifically avoided aggregation restrictions. RHEL is not a GPLed product. RHEL is an aggregation of a large collection of free software under a wide range of licenses along with some trademarked material. GPLed material can be part of such a product and RMS was aware of that, "In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License." Back in the late 1980s when people were using GPL software (like gcc or emacs) under SunOS there was no argument that SunOS was open source or should be. The open source community was happy when Sun when assisted in redistribution of Solaris versions of GNU products. Similarly for IBM and AIX versions. Aggregation with a GPLed piece of software does not make the entire software GPLed.

    114. Re:nope, doesn't hurt RH by Raenex · · Score: 1

      Fedora 1 released November 6, 2003
      RH Linux 9 released March 31, 2003 December 2001: "Since the release of Red Hat 7.2 in October, the company has been more actively pursuing what it sees as trademark violations by CD resellers such as UnixCD.com and CheapBytes.com."

      As for RHEL... the GPL has always specifically avoided aggregation restrictions. That's "mere aggregation" of separate works -- like the old shareware bundles of independent programs that you used to get on floppies. GPL version 2 also says "If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it."

      Back in the late 1980s when people were using GPL software (like gcc or emacs) under SunOS there was no argument that SunOS was open source or should be. Your analogy is bad. Red Hat would have nothing to sell without Linux. Quite clearly Red Hat is selling an OS, one based completely on GPL code with enterprise features added on top of it. To claim that it is a separate work not based on GPL works is wrong, and even Red Hat recognizes this because they release their enhancements under the GPL. The fact that Red Hat releases their source as GPL is probably why the FSF gives them a free pass over the trademark poisoning.
    115. Re:nope, doesn't hurt RH by jbolden · · Score: 1

      Linux the kernel is under a GPL license. Here RedHat is an active contributer and maintains the RedHat tree / Alan Cox tree fully openly. No one AFAIK complains.

      Linux the operating system is not under any license. No single individual or entity has standing with respect to copyright and thus there is no license. Parts of the OS are under the TeX license, parts under the GPL, parts are in the public domain, parts are under MIT-X license, parts under the BSD, parts under the artistic license. It is simply an aggregation of software. There is no such thing as a derived work of Linux the operating system only Linux the kernel.

      The FSF can't accuse them of trademark poisoning because they aren't poisoning anything the FSF has copyright to.

    116. Re:nope, doesn't hurt RH by Raenex · · Score: 1

      Linux the operating system is not under any license. Huge parts of any Linux operating system are from GNU and under the copyright of the FSF. Linus chose to distribute his kernel under GPL because of that. To call an operating system distribution "mere aggragation" is disingenuous.
    117. Re:nope, doesn't hurt RH by jbolden · · Score: 1

      Its not disingenuous its the law. For something to be more than an aggregation there needs to be someone with standing for the total product. Who would have the legal standing? As for Linus he has explicitly rejected the FSF as representing him. In the mid 1990s he was pro FSF but by the late 90's he had already broken with Stallman.

    118. Re:nope, doesn't hurt RH by Raenex · · Score: 1

      Its not disingenuous its the law. For something to be more than an aggregation there needs to be someone with standing for the total product. The only thing that gives Red Hat the right to redistribute FSF code is the GPL. So the FSF would be completely within its rights to tell Red Hat that their Enterprise distributions are violating the GPL ("mere aggregation" vs "part of a whole") and that they are forbidden from distributing FSF code. You are mistaken that FSF needs to have copyright to everything in the product. They have rights to the code they own, and if they feel the inclusion of their code extends beyond "mere aggregation", it is completely within their rights to sue.
    119. Re:nope, doesn't hurt RH by jbolden · · Score: 1

      You are correct they have the right to sue on the parts. Pick something like emacs. What term of the GPL is RedHat violating with respect to emacs? Clearly RedHat distributes source for all changes they've ever made. So under your scenario they would need to prove that something that isn't in emacs and isn't under the GPL is a derived work of Emacs's. For example if RedHat embed trademarked material into say aucTEX. Then they would need to find a specific violation of the license. That is a redistribution of aucTEX or emacs that RedHat had stopped via. this trademarked material. What they can't do is make claims on the entire OS.

      Now it sounds like you would like the FSF to make a claim a claim on all of RedHat. This case might very well break FSF. You'd have Linus (the kernel), the X-Free tream, Knuth (Tex), Lampart (LaTex), the KDE group.... lining up to testify that their code is most certainly not under the supervision of the FSF and they don't consider their code conjoined with emacs. If the judge found that the claims were fallacious enough to constitute fraud (which is possible IMHO) RedHat might very well end up owning the FSF from the damages.

    120. Re:nope, doesn't hurt RH by Raenex · · Score: 1

      Pick something like emacs. From Linux and the GNU Project:

      "The GNU Project was not, is not, a project to develop specific software packages. It was not a project to develop a C compiler, although we did that. It was not a project to develop a text editor, although we developed one. The GNU Project's aim was to develop a complete free Unix-like system: GNU."

      Now it sounds like you would like the FSF to make a claim a claim on all of RedHat. No, I want them to make a claim on the parts they own. It's obvious Red Hat is distributing an operating system as a single product. A very large portion of that is based on GNU. Linus chose to make his kernel GPL for exactly this reason -- so that he could distribute it with GNU. It is not "mere aggregation", and to claim so is completely disingenuous.
    121. Re:nope, doesn't hurt RH by jbolden · · Score: 1

      The GNU project has been successful Linux exists, Debian exists more in line with what you claim. But mission statements do not create legal obligations on other entities; otherwise Microsoft's "A computer on every desk running Microsoft software" would create obligations on Debian because they use OpenType.

    122. Re:nope, doesn't hurt RH by Raenex · · Score: 1

      What creates legal obligations are copyright law and licenses. Red Hat only has rights to distribute FSF code via the GPL. It's quite obvious that Red Hat is selling an operating system as a whole, derived in large parts from FSF owned GNU. Without the FSF code Red Hat would have no operating system to sell. Your claims of "mere aggregation" are specious, and don't stand up to any scrutiny.

      Buh bye.

    123. Re:nope, doesn't hurt RH by hughesjr · · Score: 1

      You didn't post the most important part ...

      "The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable."

      The SPEC file is the most important "script used to control compilation and installation of the executable."

      Red Hat is all the time doing things in the SPEC file that produces the RPM ... if they distribute the RPM to people, they HAVE to also distribute the SRPM to those same people.

      SURELY you don't think that CentOS developers do not have access to RHN. At a cost of $379.00 a year, CentOS becomes a valid customer and the FREE ftp server is then a moot point.

  2. Because they don't have any choice? by ThrobbingGristle · · Score: 3, Informative

    I would have thought that would have been obvious... maybe I'll go RTFA now.

    1. Re:Because they don't have any choice? by slyguy135 · · Score: 1

      maybe I'll go RTFA now.

      You must be new around here... Ah, yes, a 5-digit ID, I was right.

  3. Simple: Support by emgeemg · · Score: 4, Insightful

    The type of organizations that want Red Hat Enterprise Linux want it for the support Red Hat offers. Take that away and there's not really any competition.

    1. Re:Simple: Support by fitsnips · · Score: 2, Interesting

      Have you ever tried Red Hat support? I have used RH for year and most companies are know are moving to CentOS for things like web servers. Oracle,Websphere, and the like still get Red Hat license for Oracle support but Red Hat support is horrible and always has been. I have never gotten a good answer from them, and usually its the same thing that the first hit on google finds. Last time they took me though a whole mess to run dumps for them and such and told me it was a bad power supply, luckily I did not believe them and when IBM ran the diags it was a bad cpu ... nice job guys.

      Looks like the kernel is not the only one who was "Dazed and confused"

      Joshua SS Miller

      --
      I am a republican not by choice, but rather by lack there of.
    2. Re:Simple: Support by rucs_hack · · Score: 1

      The type of organizations that want Red Hat Enterprise Linux want it for the support Red Hat offers. Take that away and there's not really any competition.

      Which is exactly what Red Hat have always been mindful of. After all they have Fedora too, and Red Hat have released everything they do as open source from the very beginning. They really sell the support infrastructure, although they do add a lot to the linux they provide.

      I don't doubt they'd love their version of Linux to become the next Debian, used as a base for new distro's. That means they absolutely must not hammer anyone else who uses their stuff. I don't see it as likely that they will pursue anyone to end an unofficial version, that would likely be something they wouldn't even consider, so long as their Mark is respected.

    3. Re:Simple: Support by Anonymous Coward · · Score: 0

      In their defense, the "Dazed and confused" messages typically do come from bad power supplies since abnormally low or high voltages on the mobo cause them. Our appliances (saying AC, sorry) have that issue a lot, and many times pulling out and re-seating the replaceable power supplies fixes the issue.

    4. Re:Simple: Support by rucs_hack · · Score: 2, Interesting

      Red Hat support is horrible and always has been

      Ah, so that explains how they've built a multi billion dollar business on providing software services and support. Wait, what?

    5. Re:Simple: Support by evilviper · · Score: 1

      Last time they took me though a whole mess to run dumps for them and such and told me it was a bad power supply, luckily I did not believe them and when IBM ran the diags it was a bad cpu ... nice job guys.

      You think that RedHat support, over the phone, could CONCEIVABLY be able to tell the difference between a defective CPU and a flaky power supply, particularly when they have no association with the hardware maker, and PSUs don't have any kind of data interface to the rest of the system?

      The fact that they conclusively informed you it was a hardware fault, rather than a software bug, is the most you could possibly ask from the best support service, anywhere. This is the direct opposite of Microsoft, who CONSTANTLY blame perfectly good hardware, when (eg.) 99% of the time it is in fact some bug in their software.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    6. Re:Simple: Support by Anonymous Coward · · Score: 1, Interesting

      Ah, so that explains how they've built a multi billion dollar business on providing software services and support. Wait, what?

      Red Hats support is not their selling point. Their software services and training may be; their updates and RHN another. Their so called support is a joke for all but the very largest enterprise customers. I should know, I manage the Red Hat relationship for a Fortune 500 company with thousands of RH seats. We have currently 100+ open support issues on the Evolution mail reader alone where Red Hat support have does absolutely nothing. Their standard response is that "it will be corrected in a future release" but that makes their service not what I would call support, it is accepting bug-reports.

    7. Re:Simple: Support by monoqlith · · Score: 1

      Yeah, totally unprofessional. He mentioned that he was working for a Fortune 500 company. That narrows down the number of companies he could possibly work for to.......500....

      It's amazing the company you can't identify doesn't fire him right now for violating the unspecified NDA you don't know he's under.

      Maybe you should consider trolling as an AC.

    8. Re:Simple: Support by weierstrass · · Score: 1

      Did you buy the CPU from Red Hat???!!??

      --
      my password really is 'stinkypants'
    9. Re:Simple: Support by the_B0fh · · Score: 1

      Speaking as a rhce - umm... what kind of support?

    10. Re:Simple: Support by Anonymous Coward · · Score: 1, Funny

      I manage the Red Hat relationship for a Fortune 500 company with thousands of RH seats.

      Really? -- Me too!!
       
      I'm also a millionaire cowboy astronaut. ;)

    11. Re:Simple: Support by Anonymous Coward · · Score: 0

      Unfortunately, RedHat support has fallen behind that of the freeware community at large which CentOS caters to. And that bad excuse for up2date dressed in granny Yum's old nightshirt doesn't work, it simply preserves their new RedHat Network service as a single point of failure for software handling, one that often goes off line, doesn't work for my European clients, and doesn't allow any way to use the yum directives to "protect" or "prefer" repositories.

      CentOS not only provides distributed software access, they have an actual installation DVD which RedHat refuses to provide and only provides broken documentation for making your own installation mirror from the set of CD's, and they're willing to update major components to something released within the last three years (such as the MySQL and PHP for RHEL 4, which were seriously out of date) and doesn't do stupid things like leave OpenOffice out of the "server" version of their operating system.

      Save the money on RedHat licenses to pay your own engineer to do what they'll need to do anyway for either RedHat or CentOS, because that "RedHat support" is more expensive to waste your engineer time explaining things to than to fix it yourself. And frankly, the next release usually *doesn't* contain the fix! Instead of fixing their kickstart system, they say "Pay us $20,000 and we'll set up your own RedHat Network Satellite, which runs Oracle and is therefore entirely unstable without a $150,000 engineering team to support it! Won't that be a good idea!"

    12. Re:Simple: Support by Antique+Geekmeister · · Score: 1

      No, it's not. Really. There are a whole suite of memory and CPU testers in both the open source world and in the commercial market. Power supplies are one of the *least* likely components to fail: memory is the most vulnerable, CPU's are second especially with cooling issues. The failure to use silver thermal compound on an expensive and not well-ventilated CPU, for example, is a great source of transient CPU failures where the CPU's never show flaws on the test bench, and the flaws under load are intermittent.

      Yes, I expect them to guess right, or to say "we don't know". I don't expect a wrong guess from "commercial support".

    13. Re:Simple: Support by Macthorpe · · Score: 2, Funny

      Wait... you're a fake! That cowboy hat comes right off!

      --
      "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
    14. Re:Simple: Support by evilviper · · Score: 1

      Power supplies are one of the *least* likely components to fail: memory is the most vulnerable, CPU's are second especially with cooling issues.

      That's precisely the opposite of all my years of experience.

      (If not counting fans) PSUs are by far the #1 component to fail, and motherboards are #2, right about the same level as hard drive failures. From there, RAM failure is a much less frequent problem, and CPUs far less frequent still.

      Of course, this is from my experience with shops that have halfway decent techs. Terrible cases, insufficient cooling, cables improperly installed (blocking fans) can always cause a system to self-destruct, but then it's not a question of failures, it's a question of what part some incompetent idiot in tech put a screwdriver through this time...

      Yes, I expect them to guess right, or to say "we don't know". I don't expect a wrong guess from "commercial support".

      There's no way they can possibly be expected to make such determinations, across a range of 3rd party hardware. Of course they should have said "hardware failure... possibly the PSU" or something along those lines. But in any case, you shouldn't be getting hardware advice from your software support company, no matter how much you are paying them.

      Ever called your gas station for advice because your car stalled? Ever called NBC to ask why your TV doesn't turn on? Ever called Betty Crocker because your stove won't stay lit?
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    15. Re:Simple: Support by rucs_hack · · Score: 0

      Hmm, so I got modded troll for voicing an opinion as to his dodgy ethics. Fortunately my karma can absorb the hit, so I don't mind.

    16. Re:Simple: Support by drsmithy · · Score: 1

      No, it's not. Really. There are a whole suite of memory and CPU testers in both the open source world and in the commercial market. Power supplies are one of the *least* likely components to fail: memory is the most vulnerable, CPU's are second especially with cooling issues. The failure to use silver thermal compound on an expensive and not well-ventilated CPU, for example, is a great source of transient CPU failures where the CPU's never show flaws on the test bench, and the flaws under load are intermittent.

      This sounds like a commentary from someone who deals mostly with DIY, or DIY-by-proxy (cheap whitebox vendors), hardware.

    17. Re:Simple: Support by Anonymous Coward · · Score: 0

      Ever called your gas station for advice because your car stalled? Ever called NBC to ask why your TV doesn't turn on? Ever called Betty Crocker because your stove won't stay lit?

      No I haven't but I don't have a support contract with them to maintain my shit either.

    18. Re:Simple: Support by windex82 · · Score: 1

      I'm not really sure why your blaming Red Hat for not correctly diagnosing a problem with their software when you clearly state the problem ended up being hardware. They diagnosed that there was no problem with their software and suggested it could be your power supply. They could have qualified it by saying something like, "We're not finding any problems with the software, could you check your hardware? Maybe the power supply is failing."

    19. Re:Simple: Support by Antique+Geekmeister · · Score: 1

      Are you keeping in mind that there was enough of a system available to do dumps? The power supply failures I've seen have been more profound and immediate, and I kept that in mind. I've seen whole stacks of RAM failures, usually due to someone secretly skimping on the cost of RAM and buying weird third-party versions and not telling anyone. It shows up in testing, but you have to do the tests.

      I've also seen quite a few CPU's that start failing after six months because the vendor provided barely enough cooling, but didn't use good quality thermal paste, and cooling degraded. When their techs came out to replace the CPU's, they installed the new ones themselves with good thermal paste, and voila! The issue went away, even when they turned out not to have the replacement in hand and temporarily put the old one back.

      I believe you that you've seen different hardware failure patterns. Believe me that I've seen mine, over the course of years.

      But for software commpanies reporting hardware problems, yes, I expect it because the failures we see are software failures. If I don't have network connections at home, I look at whether the computer's on, and yes, I call my ISP. If they turn around and say it's due to my computer, I don't expect them to just guess "it's because you run Linux". If my car fails, and I've paid for AAA service, I expect the person who tows my car to not say it's due to bad gasoline when it's actually a bad carburetor.

    20. Re:Simple: Support by Antique+Geekmeister · · Score: 1

      Sadly for me, yes. My clients, with encouragement, do stay one grade above the cheapest 1U vendors, but it helps to actually test the hardware and recommend against vendors who cut the wrong corners.

    21. Re:Simple: Support by evilviper · · Score: 1

      The power supply failures I've seen have been more profound and immediate, and I kept that in mind.

      Sometimes that happens. Often, though, a marginal PSU provides stable power until it has been stressed for a while, only then you start getting bus errors and the like.

      If they turn around and say it's due to my computer, I don't expect them to just guess "it's because you run Linux".

      That's fine. Expecting them to be able to remotely diagnose the problem (that is not with their system) isn't reasonable, however.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    22. Re:Simple: Support by Antique+Geekmeister · · Score: 1

      I've seen the kind of "marginal bus errors" you describe on equipment near the end of its effective life, when it's more easily replaced with newer, often more capable or noticeably less power hungry components, say after 3 years. I've also seen similar results when upstream power was not as clean as expected, such as when actually plugging in to the whole rack to the slightly undersized UPS, rather than running it on the test bench. But after 3 years, it's due for replacement anyway by the standards I work with, and is reclaimed by the vendors or sold off to hobbyists. Are you seeing it earlier than that?

      From the earlier poster's message, I assume that RedHat was quite firm in saying "it's the power supply". I don't expect them to make a wrong guess and be certain of it. It's possible that RedHat's support people said "the lm_sensor tests and errors are consistent with a power supply issue: contact your hardware vendor to address that", which I would consider just fine, even if it turned out to be something else hardware based. I may well be reading too much certainty into RedHat's support line from a third party report. I don't want to blame some poor tech who did his best, gave an educated opinion, and gets blamed for that best guess being off.

      I will blame the tech if he professes hard and fast certainty and turns out to be dead wrong, which is what the poster seemed to describe.

    23. Re:Simple: Support by evilviper · · Score: 1

      But after 3 years, it's due for replacement anyway by the standards I work with, and is reclaimed by the vendors or sold off to hobbyists. Are you seeing it earlier than that?

      Absolutely. Whenever there's a large batch of new equipment (ie. with 100+ new PSUs) I'll find a couple with defects immediately, and even then, it's occasionally just subtle errors. Then, when they're nearing a year old I start expecting to see a few (less than 5%) of the machines experiencing unexplained reliability problem, like segfaults (and bus errors), or just a couple spontaneous reboots. A PSU swap almost always completely fixes it.

      A few years ago, when bad caps were such a problem, PSU failures were even more common, but they were certainly much more obvious.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    24. Re:Simple: Support by Antique+Geekmeister · · Score: 1

      Oh, you mean that run of bad caps from the stolen tantalum capacitor design? That was a sad problem for a lot of reputable vendors, which I managed to avoid but saw at some distance from the panicked motherboard replacements.

      I'm really surprised you're seeing so many failures of PSU's, though. Don't you do at least a 2-day burn-in, or make sure your vendor does it? And avoiding brand-new designs is a good help for overall reliability.

    25. Re:Simple: Support by nuzak · · Score: 2, Informative

      Power supplies are one of the *least* likely components to fail: memory is the most vulnerable, CPU's are second especially with cooling issues.

      Holy freakin shit. CPUs? Have you ever actually worked with hardware? The last time I had a CPU actually burn itself up was when I was testing experimental Sparc 15MP CPUs. Those things were on riser cards, stacked above each other.

      Memory gets zapped when you install it. ESD is a bitch, even if you wear a strap. On most utility boxes, memory doesn't get installed, you just get more memory when you get a new server. Bigger servers with >4gig are a different matter, but are perhaps a tenth of total servers in most places, which usually fill up racks with Dell 1950's or the like.

      PSUs go all the time. I've learned to get redundant PSUs whenever possible. The only thing that fails more often than CPUs are HDD's... which you didn't even mention.

      "Failure to use thermal compound" ... geez louise, your overclocked gamer rig is not what they fill datacenters and labs with.

      --
      Done with slashdot, done with nerds, getting a life.
    26. Re:Simple: Support by Anonymous Coward · · Score: 0
      issue 1: Doug thinks Evolution stinks.

      issue 2: Eve thinks Evolution stinks.

      ... issue 100: Jones doesn't care about computers at all, but is a Creationist.

    27. Re:Simple: Support by Antique+Geekmeister · · Score: 1

      Please don't read in things I didn't say. I did not say "burn up". I referred to the thermal issues common with marginal cooling, especially when the installer fails to use the silver-based thermal paste. Re-install the CPU and heat sink, with better thermal paste, and they're restored.

      And no, I'm not talking about gamer rigs. I've seen whole banks of commercial pizza box servers have members start dropping out as the thermal issues of too much CPU, poor airflow, poor cabling practices, too dense of packing, etc. combine to put them on the edge of their thermal tolerance, and start causing failures even while the motherboard thermal monitors read them within spec. And I've seen it with at least two different vendors in the last 5 years.

      My experience has been that PSU's fail outright, especially at reboot. But I also do a serious burn-in for new hardware, which helps prevent many of these problems from happening later. And I find dual PSU's to be *extremely* expensive, in power consumption, rack space, UPS provisioning, cable management, support for monitoring, and basic cost of the servers themselves. For the cost of 10 racks of fully dual-supplied systems, I can typically install another 2 distinct sets of 10 racks of cheaper servers, often with more disk or RAM or CPU, in 2 entirely distinct locations.

  4. It is helping Red Hat by uuxququex · · Score: 1
    Not everyone needs or can't afford the support of Red Hat for themselves. Having a free (as-in-beer, gratis) alternative can be a solution.

    The user benefits because it is almost a binary copy of an enterprise class GNU/Linux. And Red Hat benefits because of the increased familiarity in a potential userbase.

  5. why??? by WwWonka · · Score: 4, Insightful

    "Why does Red Hat tolerate CentOS?"

    um...because they have too?!

    "open source" look it up on wikipedia...on second thought...

    1. Re:why??? by ynososiduts · · Score: 1

      You beat me to it. This really isn't a story as this is what OSS is all about.

      --
      622677120
    2. Re:why??? by empaler · · Score: 1

      If it wasn't for the FOSS part of RHEL, there wouldn't really *be* RHEL - the article is pretty much a moot point.

    3. Re:why??? by Bitmanhome · · Score: 1

      No, they don't have to. If you sell a binary, the GPL requires only that you supply the source to that buyer. It doesn't require you to give anything away at all, free or otherwise.

      --
      Not that this wasn't entirely predictable.
    4. Re:why??? by HumanPenguin · · Score: 1

      Yeah it also states that the buyer has the right to distribute that source under the same license. IE if you release RHEL under GPL then anyone else can release the code used in RHEL under GPL. Hence they have to.

    5. Re:why??? by Dahamma · · Score: 1

      All it takes is for centos.org to buy 1 support license for RHEL and then it's effectively the same thing.

      Red Hat obviously understands this, and it isn't worth $1000 a year in extra revenue for all the ill will it would generate if they made it harder to acquire their source RPMs.

    6. Re:why??? by just_another_sean · · Score: 1

      um...because they have too?! [citation needed] :-) You're absolutely right of course.
      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    7. Re:why??? by harlows_monkeys · · Score: 1

      Yeah it also states that the buyer has the right to distribute that source under the same license. IE if you release RHEL under GPL then anyone else can release the code used in RHEL under GPL. Hence they have to

      That's been worked around before, by blacklisting. Basically, you sell the binary and source to your customers. Any customer who passes on the source or binaries, you blacklist. You refuse to sell them any newer versions, and refuse to sell them support. Customers quickly learn that they should not give out your code, even though it would not be a GPL violation for them to do so.

      This works best when the code is for something that doesn't have much outside developer interest, so that as a practical matter, the company selling it is really the only good place to get it, unless you want to fork the thing.

    8. Re:why??? by rainhill · · Score: 1

      well, they dont have to, if they provide the RHEL for free.

  6. RH lost 10k licenses from us by mikek2 · · Score: 1, Funny

    In my previous gig, we ran ~10,000 RH7.3 servers. Like the author's colleagues, we got to the point where we needed to upgrade. We were amazed that RedHat refused to give us a break on cost; they wouldn't shave off a single dollar. On 10k licenses, mind you! So, we waved goodbye to RH & migrated the whole thing to Debian. Much less headaches & drama. I'm not at the point where I want to tell RedHat to go screw, but you gotta question what they're thinking.

    1. Re:RH lost 10k licenses from us by Anonymous Coward · · Score: 1, Funny

      migrated the whole thing to Debian. Much less headaches & drama. AHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA
    2. Re:RH lost 10k licenses from us by Anonymous Coward · · Score: 0

      At 10k licenses on RH8 your income would have been a significant row on their balance sheet that year. Not saying I don't believe you, but I don't believe you. Even now, 10k licenses would be a significant income for any OS vendor.

      Just out of interest, how much did it cost and how long did the project take, to convert those 10k machines to a totally different system?

    3. Re:RH lost 10k licenses from us by mikek2 · · Score: 0

      No, really: 10k machines. RedHat refused to budge on their cost. My CTO, who loved the art of The Deal, got nowhere after months of haggling.

      As for time to convert: around 6 months. Could've been quicker, but there wasn't a terrible sense of urgency. We automated a lot of it with FAI & PXE.

    4. Re:RH lost 10k licenses from us by t0rkm3 · · Score: 1

      That's funny. My last major gig had the same sort of numbers using RHEL (render farms for major motion pictures) and we were able to swing a discount.

      Not questioning your tale, just wondering what the difference was.

      Were you a high-cost user? Did you require a lot of support? If that was the cost, then perhaps the RHEL enterprise support team was trying to centralize the cost of your support to your account rather than spread it out over other accounts. if their margins are running very slim, it might be hard to cover the overages caused by one customer with another customer's underuse of the support team.

  7. Because it's essentially advertising? by jimicus · · Score: 4, Insightful

    CentOS essentially acts as advertising for the Enterprise RedHat editions. It allows sysadmins to stick with the same familiar set of tools on both systems where it is considered desirable to have a support contract and systems where this is less of an issue.

    RedHat can't do much to curb this anyway - most of what they produce is standing on the shoulders of other GPL software - but if they did, I'd imagine we'd see a commensurate rise in the use of Debian, Ubuntu and (gasp!) SuSE/OpenSuSE.

    1. Re:Because it's essentially advertising? by fearlezz · · Score: 2, Interesting

      Indeed, it is.
      After running Zoot (Redhat 6.2), I decided RH wasn't the distribution for me. I've run (and still are running) several other distributions after that, including Slackware 7-10, Debian Potato, SLES and OpenSuSE. Since the Novell-MS deal, I cannot trust SuSE enough, and I switched again... to CentOS. And now I'm considering the next servers to get a paid-for RedHat.

      If it weren't for CentOS, i would not have bought anything from RH...

      --
      .sig: No such file or directory
  8. It's the license, stupid by rjamestaylor · · Score: 2, Insightful

    GPL FTW.

    --
    -- @rjamestaylor on Ello
  9. A little matter of the GPL by Lulu+of+the+Lotus-Ea · · Score: 2, Insightful

    It is a bit of an asinine question why Red Hat "tolerates" CentOS. Red Hat has no option here--nor should they. By distributing code or binaries that were created by people other than Red Hat, and licensed under GPL, Red Hat has explicitly agreed that CentOS (or anyone) has the right to do the same.

    Red Hat is welcome to hold whatever opinion they want on whether they *like* CentOS to do what they do... but in the end, it's none of their damn business how someone else decides to distribute GPL'd code (within the license terms, of course... Red Hat is also a creator of a significant body of GPL code).

    1. Re:A little matter of the GPL by kasperd · · Score: 1

      Red Hat is also a creator of a significant body of GPL code
      And in that area, they do have a choice. For all those GPL components where Red Hat owns the copyright, they could decide to change future versions to a different license. So far they haven't done this, and I don't think they are going to. I can think of a few reasons why Red Hat would not close those components:
      • There might be small parts of the code which is not owned by Red Hat.
      • They might think the improvements that other parties can make to the code is more valuable to Red Hat than the few customers they could lose because of CentOS.
      • There might be Red Hat customers who actually wants those parts to be GPL and would find a different distribution if they were closed.
      • Closing some components of Red Hat might piss off some of their own developers.
      --

      Do you care about the security of your wireless mouse?
  10. Centos brings back the 'play at home' by (H)elix1 · · Score: 4, Interesting

    I looked into RHEL when they dropped support for RH 8/9, and they wanted far more money than I was willing to pay to kick around the tires at home or on my development box. When time came to look at 'enterprise' grade distributions, SuSE made it much easier on the developers. Fast forward and I found that I never bothered to even try RHEL 3, 4, and 5. Same went for Oracle's branded version. With no easy way to patch and having to deal with accounting to get a license, meh.

    What changed it for me was Centos. I found that I could use the free as in beer versions for all my personal/internal needs, and it was so dang close to OEL and RHEL it became a no-brainer for testing and some dev work. With the internal blessings from our side that our code would work, QA did the formal testing on the branded versions of Linux. Folks running our product, of course, would want OS support - so they purchased the formal 'supported' OS from the commercial vendors. I suspect Centos is saving RHEL/OEL sales that might have gone to Ubuntu or other variants.

    1. Re:Centos brings back the 'play at home' by Anonymous Coward · · Score: 0

      This is similar to how it is used (at times) where I work.

      QA and I&T work with the "real RHEL", and pay for support we will never use, a few developer machines get RHEL too, and the rest get CENTOS.

      We pay for RHEL everywhere it is loaded but I doubt that we've ever called support more than once.

      Additionally, CENTOS allows us to load up a new machine within a hour or so of our needing it, without having to go through the lawyers and purchasing.

    2. Re:Centos brings back the 'play at home' by Alpha830RulZ · · Score: 1

      My company delivers software on RHEL. We use CentOS extensively at customers and internally. I don't need access to support, but my customers often do. CentOS reduces my costs and our customers' costs and gives me a warm fuzzy that I'm using something close to what my customers use, if they are on RHEL. I'd actually prefer to use Fedora, but Fedora and CentOS differ enough that our installer won't run (due to a bug in Install anywhere).

      CentOS is definitely driving incremental RHEL business, in my experience. It certainly keeps me in the RHEL camp.

      --
      I was taught to respect my elders. The trouble is, it's getting harder and harder to find some.
    3. Re:Centos brings back the 'play at home' by Atacama93 · · Score: 1

      At my company we host applications for many large enterprise customers on boxes running CentOS. CentOS works great for us and we have enough experts on staff that we can support ourselves. However, some of our customers choose to license our applications to run on premise in their data centers. In 100% of the cases so far, they have chosen to license RHEL. Sometimes this is because while they may have competent system administrators for day to day tasks, they don't have people with enough experience to figure out how to fix things when a patch goes seriously awry. In other cases, corporate policy requires that everything running on production systems has a current support agreement. Just like with the old cliche of no one ever getting fired for choosing IBM, fear and CYA sell the known.

  11. Doesn't hurt them at all..... by budword · · Score: 1

    Red Hat makes money selling services to big companies who can't afford to be wrong. They sell CYA insurance to suits. CentOS is probably a plus, as it lets people test drive the real thing for free. When you have to put your career on the line in a large company, you pay Red Hat to Cover Your Ass. They are good at it, and the rate of pay reflects it.

    1. Re:Doesn't hurt them at all..... by Tuoqui · · Score: 4, Interesting

      Yeah when I was doing a Computer related degree in College they used CentOS because of that fact. The thing is you're more likely to encounter RHEL than Debian, Ubuntu and such for server work. They exploited the fact that CentOS was a free version of RHEL and now RHEL has about 20-30 more people with college degrees that have been introduced to their work.

      Myself I've used Ubuntu series of Linux on my home machine because its better for desktops but if I were to run a server I'd probably choose CentOS for myself (or a small business), RHEL if I had a big budget in a major company.

      --
      09F911029D74E35BD84156C5635688C0
      +2 Troll is Slashdot's way of saying groupthink is confused
    2. Re:Doesn't hurt them at all..... by Lord+Kano · · Score: 1

      Red Hat makes money selling services to big companies who can't afford to be wrong. They sell CYA insurance to suits.

      It's more than that. I'm personally through with Red Hat, the whole RHEL/Fedora split turned me off I'm a Mandriva guy but my employer is all about the Red Hat. Red Hat also provides easy to track updates for all of the packages that they include with their product. Big players like oracle tune their product releases to Red Hat. If you want support for the Oracle database that you're paying for, it had better be on Windows or Red Hat. For quite a while now, I've been thinking about giving Gentoo a try, and eventually I might, but Red Hat is the big dog of the Enterprise because they were the first to blow up big and other mission critical apps are designed to work on Red Hat.

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
  12. Umm, that's the point by allthingscode · · Score: 5, Insightful

    Did we miss the point of the GPL? The instance of the software is owned by the user. They can do what they want with it. If they feel like doing everything on their own, they can do so (CentOS). If they want to pay someone else to make their life easier, they can do so (RedHat). RedHat knows this. "Choosing" to tolerate is the one choice RedHat doesn't have: If RedHat wants to use GPL'd software, they have to let other people play by the same rules they do. CentOS isn't going to hurt RedHat any more than Debian does.

    1. Re:Umm, that's the point by Anonymous Coward · · Score: 0

      They have to provide the source not the source RPMs. They could simply provide a directory of tarballs and patches and be good, now if they did that it'd take exponentially more time for the CentOS team to put back together a real distribution.

    2. Re:Umm, that's the point by Anonymous Coward · · Score: 0

      There's more than that, it's pretty easy to comply with the GPL bits and make it very expensive for third-parties to recreate your work. You only need one critical component under a non-free license (Suse was a past master of 'not really free' distribution with yast, current patented Mono Novell bits is the same, SUN playes the same game, etc).

      Red Hat made the strategic choice years ago to release a free/libre distribution. Knowing perfectly well it would give rise to derivatives like Centos, Oracle Enterprise Linux, etc. They do not cheat with the free/libre character of stuff they reuse and they release all their work under free/libre licenses.

      They got forked many times by competitors (about as often as Debian). They keep being crucified by analysts that write it's insane they do not work at all to prevent this (the same analysts praise the "pragmatism" of entites like Caldera or Ubuntu, who don't hesitate to play with the free/libre lines).

      Yet they're still at the top of the commercial Linux market. A huge part for this is customers which have learnt to trust Red Hat to do the right thing (and currently Centos is living proof Red Hat does the right thing. You want Centos to continue you pay a few RHEL licenses). Red Hat is a pure free/libre Linux player. (but don't expect analysts to understand this).

    3. Re:Umm, that's the point by Schraegstrichpunkt · · Score: 1
      This analyst did understand it:

      So the answer to the question in the title of this piece is: CentOS stings Red Hat just a little, but it doesn't hurt them badly enough to make them want to change the way they do business. Even better, it helps them hold the heads of the competing Linux server distros under water. The real victims of the roaring success of CentOS are Novell's SLES, Ubuntu Server and Larry Ellison's own RHEL-cloned Unbreakable Linux.
    4. Re:Umm, that's the point by BillyBlaze · · Score: 1

      The source has to be in the preferred form for modification, and it has to include the install scripts, per the GPL. And it's pretty obvious that going out of their way to make it difficult is against the spirit of the license. Keep in mind that as a Linux distro, and not an OS monopoly, goodwill is actually important to them.

    5. Re:Umm, that's the point by xouumalperxe · · Score: 1

      Preferred form for modification basically means "the actual source, in a reasonable format". I doubt an RPM counts as an "install script", and most applications have an install script in the form of a makefile either way. So I don't really think that providing source tarballs would be a problem.

      On the other hand, the goodwill thing is indeed a good point. And there's the part where, given they actually need to make the source available, as per the GPL, their clients would probably rather have it in RPM format. No point in cutting off your nose to spite your face, kind of thing.

  13. Red Hat has no choice by rice_burners_suck · · Score: 2, Insightful

    I don't think Red Hat is tolerating it. They simply have no choice. The OS and most of the components installed with it are licensed under the GPL, which states that exactly this sort of thing can happen.

  14. What CAN Redhat do about it? by Digital+Pizza · · Score: 1

    It's all (I believe) GPL, so they HAVE to provide the source, and there's nothing to prevent someone else compiling and releasing it as CentOS does. They'll just have to deal with it.

    --
    We apologize for the inconvenience.
    1. Re:What CAN Redhat do about it? by Rob4127 · · Score: 1

      I thought the GPL required Red Hat to provide the source to their RHEL customers. Are they really obligated to run an open FTP site?

    2. Re:What CAN Redhat do about it? by Bitmanhome · · Score: 1

      If you sell a binary, the GPL requires only that you supply the source to that buyer. It doesn't require you to give anything away at all, free or otherwise.

      --
      Not that this wasn't entirely predictable.
    3. Re:What CAN Redhat do about it? by Digital+Pizza · · Score: 1

      Perhaps not; but then there'd be tons of complaints from the "community", and the CentOS folks could just pool their money and buy a copy anyway. Really, I doubt RedHat has a problem with this; the reason people buy RHEL is for the support.

      --
      We apologize for the inconvenience.
  15. CentOS to RH migration by caseih · · Score: 4, Insightful

    One of the things that makes CentOS a clear winner is that because it is a completely compatible recompilation of RH, going from a test CentOS install to a fully supported RH entitlement is very easy. Thus I install CentOS initially on all my servers initially and then when I put them into production, I convert them to RHEL and buy an entitlement for them. Some of my less important servers remain CentOS. One of the main reasons for converting my servers to RHEL is that I can watch over them all, in terms of patches and security eratta, from the RHN.

    In other cases, I can convert a RHEL box to CentOS, then build the replacement server with its entitlement, allowing me to keep the original server in production for a few weeks or months while the new server is ramped up.

    So if anything CentOS actually increases RH usage because it is so easy to, at any time, buy entitlements from RH, convert the CentOS machines, and get whatever level of support you deem necessary at the time.

    1. Re:CentOS to RH migration by merreborn · · Score: 4, Insightful

      CentOS also has a much larger set of available binary software packages than redhat.

      Of course, you can use those packages with either redhat or CentOS. So while CentOS benefits from all of redhat's core OS work, Redhat benefits from all of CentOS's package maintenance work.

      Without a doubt, each project benefits the other directly.

    2. Re:CentOS to RH migration by Antique+Geekmeister · · Score: 1

      Yes, the difference between Fedora (which has a lot of bleeding edge software) and RHEL is too great to port things directly back to RHEL. But CentOS has been a very useful intermediate stage: some of us have even used RHEL with the Centosplus repository enabled, to get current versions of tools like MySQL. (That was a big deal in RHEL 4, which had the badly out of date MySQL 4 and serious perl module deficiencies.)

      I couldn't have used RHEL 4 without the Centosplus repository, or building up compatible MySQL RPM's myself and maintaining them (which I lacked time to do).

  16. Licensing costs by c_g_hills · · Score: 1

    The author seems to think that the cheapest subscription available is $799. This is not the case. You can purchase a 1 year subscription for $349. While it is not quite $99, it is still a darn sight cheaper. There are also discounts available for certain organizations (charities and education, for example.)

  17. Big companies will buy redhat anyway... by SynFlood · · Score: 1


    I used to work for a large company, and even if CentOS is freely available software such as Oracle, Legato Networker, and others do not provide support for its products on other operating systems that those certificates, redhat, suse or other paid distros.

    If you are running an expensive product like Oracle, Legato Networker, HPOV NNM, HP DataProtector and others, and we want to be able to get the support , then you had to buy Redhat.

    My humble opinion, I do not believe that CentOS is hurting RedHat, if CentOS did not exist, other distributions take place, and not necessarily clones redhat.

  18. It works both ways by bjkrz · · Score: 2, Interesting

    I work for a company with ~20 employees that sells a software package that needs its own unix server.

    It doesn't matter how many times I say 'CentOS is 100% compatible, and FREE! (w00t)' to my boss. When a machine goes to a customer, it goes out with Red Hat. Even if no one ever calls Red Hat for support, that warm fuzzy CYOA feeling of having a big well known company behind your product is irreplaceable. At the same time, we have a stack of CentOS machines and VMs in the office for testing and development for no additional cost to us.

    I can honestly say that CentOS made Red Hat a much more palatable choice as we switch away from our previous UNIX- SCO Openserver.

  19. Hurting who..? by Wowsers · · Score: 1

    A more important question, are either of them hurting Microsoft?

    --
    Take Nobody's Word For It.
  20. Huh? by rindeee · · Score: 3, Insightful

    That's like asking why I "tolerate" the speed limit, or why I tolerate my bank demanding I pay my mortgage after signing the contract to do so (okay, so those are kind of crappy examples). Their product is licensed such that CentOS can and (I must say I am very grateful for) does make use of the source code. What's the problem? It's not as though RedHat has any say in the matter. The article even points out; "After all, the vast majority of the packages in RHEL were not created by Red Hat, and they are all governed by the GPL, which is absolutely clear about the obligation to redistribute code." Well duh! Someone could just as easily claim that MySQL is losing money because distro XYZ includes it when the end user could be paying MySQL for installation and configuration support. And so on. The article is basically drivel IMO by someone who comprehends what the GPL is, but doesn't "get it" or the real value it represents.

    1. Re:Huh? by iggy_mon · · Score: 1
      That's like asking why I "tolerate" the speed limit, or why I tolerate my bank demanding I pay my mortgage after signing the contract to do so (okay, so those are kind of crappy examples)

      you are right, let's fix that now. "That's like asking why I "tolerate" the speed limit in my Pinto, or why I tolerate my bank demanding I pay my mortgage on said fine automobile after signing the contract to do so (okay, so those are kind of NOT crappy examples)"

      see...? your examples are now less crappy because they reference cars AND simultaniously rise to the /. level.

      ;-)

      --
      --iggy_mon - www.ananonymouskiller.com - Die Trying -
  21. Because Red Hat isn't MS by webmaster404 · · Score: 1

    Red Hat tolerates Cent-OS because they are two different types of OSes. Red Hat is for mostly businesses who need solid support, Cent-OS is for hobbyists and smaller businesses who don't need much support. Also, Cent-OS gives more or less a "trial version" of Red Hat because Red Hat isn't selling the OS like MS and Apple does, they sell support for the OS and theres nothing worse then having a potential big customer decide that the differences between Red Hat and Windows are "too great" and they don't use Red Hat when Cent-OS can get them the look-and-feel along with the programs Red Hat has. But lastly, Red Hat is an open company, they try not to be evil unlike MS, sure they like to make money but building a solid OS is their first priority and an OS cannot be stable, secure and fully functional without it being open.

    --
    There is no "disagree" moderation, and troll, flamebait and overrated are not valid substitutes
    1. Re:Because Red Hat isn't MS by the_B0fh · · Score: 1

      Man, not only did you smoke, but you inhaled too. Redhat does not "build" the OS. They may have some employees that contribute to the kernel, and other software.

      And on your last 3 points, look at things like Trusted Solaris, z/OS, VMS, OS/2, etc.

  22. Redhat support by SolusSD · · Score: 5, Interesting

    I work from a company that runs most of its products on top of Redhat EL3 and EL4. While there is something to be said about Redhat's quality of support- for inhouse development wortk it isn't so important. Its value comes form supporting our customers at an OS level alleviating us from supporting the OS. (We require our customers to purchase Redhat support contracts). What I believe _is_ hurting redhat is how their sales department insists that making copies of Redhat is illegal. We have been told time and time again that it is illegal for us to run copies of Redhat that are not paid for within our support contract. The truth is- as long as you aren't expecting support for the unpaid for copies and you are not selling them to other companies (alone or as part of your product, because of redhat trademarks) it is fine to use as many inhouse copies as you want. It took me monthes to convince management at our company that Redhat Licensing is completely different beast than, say, Windows Server licensing while at the same time fighting a battle with the software programmers trying to convince them that Linux is _not_ freeware. The concept of GPL'd software seems to be lost on members of the IT management sector. CentOS has become a good inhouse alternative to redhat since it is binary compatible, but it does not displace any copies of Redhat sold with our product. So, while Redhat may be losing some marketshare for inhouse deployments, they are only losing cusotomers that didn't want the support or that they were essentially *lying* to by requiring them to purchase licenses they were not obligated to purchase.

    1. Re:Redhat support by Wylfing · · Score: 1

      Its value comes form supporting our customers at an OS level alleviating us from supporting the OS.

      That's definitely a plus. But I think more important is that Red Hat moves units for you. With any kind of enterprise-level pricing system, even though something may have a natural price of $500, you sell it for $10000 instead because it makes PHBs think they're getting a better quality product. You simply cannot sell PHBs on free. They just won't go for it. If you put CentOS on a unit, PHBs don't want it. If you put Red Hat on the same unit, the PHBs buy.

      What I believe _is_ hurting redhat is how their sales department insists that making copies of Redhat is illegal.

      Of course I don't know what they told you, but they could be trying to give a simple answer to a thorny question. It's better to tell PHBs "It works like Windows licensing," even if that's not quite true, because then they have clear expectations, which helps sales. The alternative -- the truth -- is really something like: (1) the support contract forbids you from making more than X copies; (2) the GPL says that placing restrictions on what end-users can do with the software nullifies the right to distribute, so technically we would allow you to go ahead and make extra copies (i.e., break the contract), but then we'd have to terminate your support. This hurts the PHB's brain, which in turn hurts sales.

      So I think it might be a net gain for them to pretend there's only one license (when really there are 2).

      --
      Our intelligent designer has never created an animal that we couldn't improve by strapping a bomb to it.
    2. Re:Redhat support by alexborges · · Score: 1

      Who at redhat told you such a thing? THat would be very well against their whole corporate philosophy. Yeah, theyd prefer if you didnt tell customers "you dont need to buy another rhel license for this particular thing", but they ship everything under the gpl. They cannot, should not and im sure, would not, stop you from redistributing it.

      --
      NO SIG
    3. Re:Redhat support by Billly+Gates · · Score: 1

      It is illegal if your redhat contract prohibits it.

      Seems SuSE is stealing alot of users because of Novels great support. It shows as its a dumb contract and the support is mediocre at best.

    4. Re:Redhat support by SuseLover · · Score: 1

      Redhat explained it me like this: If your company has any valid support subscriptions with Redhat, the terms of that agreement say that your company will not run any unlicensed copies of the o/s. If you have no subscriptions anywhere in the company, you can run the o/s as long as all of the RHN (up2date, rhnd, etc.) software removed from the system. If you run unlicensed copies of RHEL and Redhat has knowledge of it, they can refuse support for your valid copies.

    5. Re:Redhat support by turbidostato · · Score: 1

      "What I believe _is_ hurting redhat is how their sales department insists that making copies of Redhat is illegal"

      Well, they are marketroids, not legal drones, so while not too precise, they are right... to a point.

      "We have been told time and time again that it is illegal for us to run copies of Redhat that are not paid for within our support contract. The truth is- as long as you aren't expecting support for the unpaid for copies and you are not selling them to other companies (alone or as part of your product, because of redhat trademarks) it is fine to use as many inhouse copies as you want."

      Probably you are not a legal drone either. Why don't you please have a look at Red Hat support license *first*? This way it's much easier to make informed opinions. Of course you can make copies of Red Hat... as long as you aren't expecting support for *NEITHER* your paid nor your unpaid copies, and you are ready for Red Hat to ask you for an audit and you are ready to pay for any other copies of Red Hat running on your premises found by such an audit. It's just a matter of reading all that funny text *before* you press the "I accept" button.

    6. Re:Redhat support by turbidostato · · Score: 1

      "Redhat explained it me like this"

      It's funny they "explained" it to you the same way almost "word by word" as it is "explained" on their support EULA text. I had once a teacher like this: his concept of "explaining" was just reading the text book word by word.

  23. Wrong question by rrohbeck · · Score: 5, Informative

    You might ask just as well why the Linux community tolerates RedHat.
    It's the way it's supposed to work.
    On the other hand, the only reason why CentOS exists is that RHEL can't be downloaded for free like the older versions. If RedHat wanted to kill CentOS they would just have to allow that.

    1. Re:Wrong question by Anonymous Coward · · Score: 0

      I've seen this "us vs them" relationship between corporate distributors and the community mentioned so many times, and it's just so ignorant.

      The Linux community "tolerates" companies like Red Hat and Novell because they are *part* of the community. Both companies have huge development staffs that not only contribute to open source projects but lead them as well. The fact is that a great deal of the work in the community is from companies like Red Hat, Novell, IBM, and others.

      I'd really love to see numbers on how much Ubuntu/Canonical contributes to open source projects. My impression is that there is actually very little, yet they're seen as the "community" distribution.

    2. Re:Wrong question by Mr.Ned · · Score: 1

      "You might ask just as well why the Linux community tolerates RedHat. It's the way it's supposed to work."

      Or because Red Hat gives a huge amount to the GNU/Linux community, and employs some of its most prominent figures?

      http://fedoraproject.org/wiki/RedHatContributions

  24. No it isn't by scheme · · Score: 2, Insightful

    Red Hat is welcome to hold whatever opinion they want on whether they *like* CentOS to do what they do... but in the end, it's none of their damn business how someone else decides to distribute GPL'd code (within the license terms, of course... Red Hat is also a creator of a significant body of GPL code).

    Redhat doesn't have to distribute the packaging or configuration information to satisfy the gpl. For example, they could provide a cvs or svn repository with just the code or tarballs of the source. The gpl would be satisfied, but it'd be very difficult to recreate the configuration information required to get a working system. E.g. the selinux policies required to get a working system would take a fairly large project in and of itself.

    --
    "When you sit with a nice girl for two hours, it seems like two minutes. When you sit on a hot stove for two minutes, it
    1. Re:No it isn't by Danathar · · Score: 4, Informative

      Not entirely correct. Installation scripts and interfaces definition files must be included. Access to CVS/CVN of the code without these would not satisfy the GPL (v2).

      "The source code for a work means the preferred form of the work for
      making modifications to it. For an executable work, complete source
      code means all the source code for all modules it contains, plus any
      associated interface definition files, plus the scripts used to
      control compilation and installation of the executable. However, as a
      special exception, the source code distributed need not include
      anything that is normally distributed (in either source or binary
      form) with the major components (compiler, kernel, and so on) of the
      operating system on which the executable runs, unless that component
      itself accompanies the executable.

    2. Re:No it isn't by eldepeche · · Score: 1

      But if a RHEL subscriber acquires the configuration information, there's no way to stop him or her from giving that information to CentOS.

    3. Re:No it isn't by Sudheer_BV · · Score: 1

      Perfect. And CentOS has one RHEL license.

      --
      Sudheer Satyanarayana
      www.techchorus.net
    4. Re:No it isn't by scheme · · Score: 1

      But if a RHEL subscriber acquires the configuration information, there's no way to stop him or her from giving that information to CentOS.

      The files aren't covered by gpl, so why would the subscriber or centos have the rights needed to distribute that information?

      --
      "When you sit with a nice girl for two hours, it seems like two minutes. When you sit on a hot stove for two minutes, it
    5. Re:No it isn't by scheme · · Score: 1

      Not entirely correct. Installation scripts and interfaces definition files must be included. Access to CVS/CVN of the code without these would not satisfy the GPL (v2).

      Wasn't aware of that, but you still need the configuration files. E.g. sendmail.cf, httpd.conf, etc. for the various configurations. A lot of these are readily available but things like Selinux policy files, pam configurations, etc. are redhat specific and wouldn't need to be distributed or may be distributed using a restrictive license.

      --
      "When you sit with a nice girl for two hours, it seems like two minutes. When you sit on a hot stove for two minutes, it
    6. Re:No it isn't by Antique+Geekmeister · · Score: 1

      In many if not most cases, the packaging itself is certainly under GPL. I've certainly submitted RPM's to various repositories, and patched them and given them back to RedHat as a good corporate citizen, all under GPL. It's also much easier and safer to be consistent about publishing all of it except those very few components that are not GPL (such as their latest clustering software).

      Sadly, RedHat also leaves some available features out of their software, such as NTFS components in their default kernels. Fortunately, CentOS takes up that slack and provides them in the centosplus repository.

    7. Re:No it isn't by Daniel+Phillips · · Score: 1

      Not entirely correct. Installation scripts and interfaces definition files must be included. Access to CVS/CVN of the code without these would not satisfy the GPL (v2).

      Wasn't aware of that, but you still need the configuration files. E.g. sendmail.cf, httpd.conf, etc. for the various configurations. A lot of these are readily available but things like Selinux policy files, pam configurations, etc. are redhat specific and wouldn't need to be distributed or may be distributed using a restrictive license.

      The config files are set up by the rpm installation scripts which must be included according to the GPL, so no loophole there either.

      --
      Have you got your LWN subscription yet?
    8. Re:No it isn't by init100 · · Score: 1

      but things like Selinux policy files, pam configurations, etc. are redhat specific and wouldn't need to be distributed or may be distributed using a restrictive license.

      How hard do you think it would be to take them from Fedora and adapt them to suit your needs? It's not like you would have to start with a blank slate, as RHEL effectively is Fedora with some minor tweaks and enhancements.

    9. Re:No it isn't by Daniel+Phillips · · Score: 1

      It's also much easier and safer to be consistent about publishing all of it except those very few components that are not GPL (such as their latest clustering software). As far as I know, Red Hat's clustering software is entirely GPL.
      --
      Have you got your LWN subscription yet?
    10. Re:No it isn't by kimvette · · Score: 1

      Is a config file copyrightable?

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
  25. Because they're not the a record company? by BlueParrot · · Score: 4, Insightful

    Red Hat probably realises that people using CentOS are people who may just like it so much they they come back for more, and since they don't make their money on the software, but rather supporting it, CentOS just means more potential customers in the long run...

    Some companies are control freaks who prefer to sue potential customers, Red Hat has picked a slightly more sane aproach.

    1. Re:Because they're not the a record company? by Anonymous Coward · · Score: 0

      Whose users always claim, proudly. their company use open source but forget to note the walled DRM'd hardware surrounding it?

    2. Re:Because they're not the a record company? by JoshJ · · Score: 1

      Tivo?

  26. Why did MS like piracy? by goombah99 · · Score: 5, Insightful

    In the early days, MS gave the impression of tolerating piracy. Whether they did or not it's widely believed it helped them more than it hurt them. Centos is not piracy but it can help Redhad spread itself.

    --
    Some drink at the fountain of knowledge. Others just gargle.
    1. Re:Why did MS like piracy? by timeOday · · Score: 2, Insightful

      I'll go a step further, I don't think whether CentOS hurts RedHat matters. If RedHat wants to have a go at writing and selling proprietary software, fine, and good luck. But so long as they sell others' software, they can't demand exclusivity.

    2. Re:Why did MS like piracy? by VGPowerlord · · Score: 1

      You mean in the early 70s, before Gates' 1976 Open Letter to Hobbyists?

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    3. Re:Why did MS like piracy? by muyuubyou · · Score: 1

      Actually, Gates himself confirmed this point when asked about Chinese piracy.

    4. Re:Why did MS like piracy? by Daniel+Phillips · · Score: 1

      Actually, Gates himself confirmed this point when asked about Chinese piracy. Indeed, and likened the process to drug dealing: "They'll get sort of addicted, and then we'll somehow figure out how to collect sometime in the next decade." -- Bill Gates
      --
      Have you got your LWN subscription yet?
    5. Re:Why did MS like piracy? by knorthern+knight · · Score: 1

      > Indeed, and likened the process to drug dealing: "They'll get sort of addicted, and then
      > we'll somehow figure out how to collect sometime in the next decade." -- Bill Gates

      Showing my age a bit... I remember a time back in the late 1980's and early 1990's whenever you bought a mouse or a hard drive, you got a *FREE AND LEGAL* copy of Windows 2 thrown in. The main reason was to enable people to run Excel. This was sorta like the late 70's and early 80's when MicroPro sold a subsidized low-price Z80 "Star Card" plus CP/M to enable the Apple ][ to run MicroPro's "Star Office" (no not Lotus' product). How many of you heard of...
      - the spreadsheet "CalcStar" (what???)
      - the flatfile databse "DataStar" (what???)
      - the word processor "WordStar" (whole bunch of hands go up)

      --

      I'm not repeating myself
      I'm an X window user; I'm an ex-Windows user
    6. Re:Why did MS like piracy? by rainhill · · Score: 1

      Well, yes but not this way. It would have been far more effective name recognition campaign if RedHat itself provided the RHEL for free, and not someone else with no credit to RedHat as it requests.

    7. Re:Why did MS like piracy? by 'nother+poster · · Score: 1

      I used Wordstar, but when it came to spreadsheet work I prefered Visicalc.

    8. Re:Why did MS like piracy? by Calinous · · Score: 1

      Not so long ago you could have a Windows XP license at a quarter of its retail price when buying a new computer - or a new internal component. Windows XP at a quarter of its retail price, when buying a $3 network card

    9. Re:Why did MS like piracy? by Anonymous Coward · · Score: 0

      Centos is not piracy but it can help Redhad spread itself.

      You mean spread like the goatse guy? Ouch! My imagination hurts!

    10. Re:Why did MS like piracy? by petermgreen · · Score: 1

      The GP was probablly wrong to say early days.

      It seems Bill worked out early (correctly IMO) that trying to make money writing and selling software targeted at hobbyists wasn't going to be very sucessfull.

      What buisness software vendors realised later was they could set up a compliance auditing agency that would scare all but the smallest buisnesses into trying to stay as compliant as possible while still makng it easy for people to get hooked on thier software through pirate copies. This worked well for many years but eventually the market maxed out.

      So the only way to grow further was to force markets that were pretty immune to the BSA threat (home users and buisness users in the third world) to pay up. In other words product activation/wga.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    11. Re:Why did MS like piracy? by AmyRose1024 · · Score: 1

      Ironically, it's those who didn't pirate their copies of Windows they are scaring the most. The legit users seem to be more interested in trying Linux. Of the three non-geeks I've converted so far, none of them were pirates, but they were more fed up with the privacy invasions than pirates were, since pirates will find a way around it anyway.

    12. Re:Why did MS like piracy? by slashdotlurker · · Score: 1

      I wonder if the person who modded it up to "Insightful" was high when he did so.
      Whether Red Hat is following the Microsoft/drug dealer mode of marketing is quite moot - Red Hat could not get harsh on CentOS even if wanted to - except the logos and update related stuff, everything Red Hat packages is GPL'ed, and the moment Red Hat tried to pull a trick, it would lose its own license to distribute Linux.
      People at Red Hat might have their episodes of being dumb - like shutting down their desktop versions after RH 9, but their license precludes them from doing something quite as stupid / destructive as what you are talking about.
      Of course, Red Hat could spend months obfuscating the code and moving libraries around (a highly deprecated procedure when you have a working product) but the moment they tried to distribute, GPL would at once apply (derivative work) and it would be back where it started.
      As someone else on this thread, who sounded like a Red Hat employee, said, Red Hat understand the kind of code they are handling, and there is not a thing they can do to CentOS even if they wanted to (and I do not think they even want to, given how much bad publicity it would generate - cancelling out the huge amount of sympathy they won from the community and from consumers by refusing to be a second Judas after Novell).
      That said, this entire discussion is a trifle meaningless and the original article highly misleading (at least the slashdot summary).

  27. A Very Tough Business by RobBebop · · Score: 4, Interesting

    RHEL, CentOS, and Fedora are all competing brands under the same umbrella. Fedora is great for cutting edge developers and home users. CentOS is good for people who desire the better tested software. RHEL is targeted at enterprises (hence the 'E' in the acronym) who need things working all the time (99.9999%). The three different markets are comparable to the different brands offered by Microsoft (Server, Workstation, Home). The only difference is that Red Hat doesn't make any money from CentOS or Fedora.

    But take a step back and think about Microsoft a bit more. Imagine you have a business laptop which was provided to you by your company. It runs 2000 or XP or (god forbid) Vista and the company has a site license for you to run that software. Microsoft is happy to slash margins for the individual site license which you have as long as they can continue to service the servers and infrastructure which run the business critical systems of your company. Similarly, if you are a developer or home user... your copy of Windows came from an OEM or you pirated it. Sure, Microsoft gets money from Dell and the other OEMs... but (I imagine) so do the Linux companies who have been able to get involved in that method of distribution.

    In the end, you help Red Hat by using CentOS or Fedora just like you help Microsoft by using pirated Windows. Simple enough?

    --
    Support the 30 Hour Work Week!!!
    1. Re:A Very Tough Business by crush · · Score: 1

      The CentOS Project is a completely independent organization, separate from Red Hat, so it's not really accurate to say that it's under the "same umbrella" in the way that the Microsoft OSes are.

      Also, Fedora differs greatly in that it has a very rapid development cycle and effectively acts as a preview and test-bed for features which often make it into RHEL.

      Your statement that "CentOS is good for people who desire the better tested software. RHEL is targeted at enterprises (hence the 'E' in the acronym) who need things working all the time (99.9999%)" implies that CentOS is not an enterprise distribution ... and nothing could be further from the truth, in fact its very name is "The Community enterprise OS"

    2. Re:A Very Tough Business by RobBebop · · Score: 1

      Thank you for your clarification about CentOS. I stand-by my assertion that if I have a need for a system that needs to work that my target is still RHEL and that Fedora is like OEM/pirated Windows.

      Unless there are system administrators who would defend state that they would prefer CentOS over RHEL, I don't think Red Hat's core market is at risk... because those big customers running mission critical systems are where the money is.

      --
      Support the 30 Hour Work Week!!!
    3. Re:A Very Tough Business by Anonymous Coward · · Score: 0

      No.

    4. Re:A Very Tough Business by the_B0fh · · Score: 1

      Man, that's so much bullshit. If Centos and rhell is binary compatible, then there's no freaking functional difference between them.

      And your comparison between rhell and fedora vs pirated windows is hookie too. Fedora and rhell run different kernels! Windows (look at the version numbers, not the marketing names) of the same versions run the same freaking kernel (data center versions are different). In fact, there's been a number of articles on converting your winntworkstation into winntserver.

      Or are you saying fedora users are pirates?

      Unfortunately, /. is full of rhell weenies, and anytime you say something good about rhell, you get +karma, and anytime you say anything negative about rhell, you get -karma.

      Bleh.

      -rhce and linux user since kernel 1.2. Still thinks rhell is the worst distro I've touched.

    5. Re:A Very Tough Business by RobBebop · · Score: 1

      the B0fh,

      My post was from a business/profits/marketing perspective. I'm sorry if you failed to get that. From a technical perspective, as long as source code is available then who cares about the business... if the product is worthwhile then the community will develop it even if the business fails.

      Isn't Red Hat's core business servicing RHEL and developing it is secondary to being able to provide that support?

      --
      Support the 30 Hour Work Week!!!
    6. Re:A Very Tough Business by turbidostato · · Score: 1

      "Unless there are system administrators who would defend state that they would prefer CentOS over RHEL"

      On one hand there *are* system administrators that would defend CentOS over RHEL because there is more software directly avaliable and they can deploy it without filling a ton of interal paperwork for approval. On the other hand and in more general terms it is not a sysadmin the one that would risk the "Red Hat grasp" within the company but beancounters if they ever discover all their technical people would tell is "Red Hat and CentOS are absolutly identical -byte by byte; it's only CentOS is cheaper".

  28. $50,000 a year? by iknownuttin · · Score: 1

    Cheaper than hiring a guy.

    --
    I prefer Flambe as apposed flamebait.
  29. RHEL + RHN by Loconut1389 · · Score: 1

    RHEL also provides the RHN which is a powerful framework for managing updates for large quantities of machines, among other things.

    CentOS provides an audience for bug reporting and even a source for patches. Closing the source to RHEL customers only may be possible (is that legal?), but the'll pay a price. The mega enterpise is RHELs market and CentOS won't hurt that market much.

  30. For those who will comment without Ring TFA... by AdamWill · · Score: 1

    This comment especially for those clever asses who will say "because they have to!" before reading the article: the author is not contending that Red Hat could somehow prevent CentOS from being made. He is wondering why Red Hat doesn't provide a low-cost, no-support, barebones edition of Red Hat to try and take some of the CentOS user share. And he has a fairly good answer to the question, too.

    1. Re:For those who will comment without Ring TFA... by WwWonka · · Score: 1

      I tried to ring the TFA first but Anita Ward wasn't around to help me out.

    2. Re:For those who will comment without Ring TFA... by Greg_D · · Score: 1

      Why would Redhat waste their time releasing a "low-cost, no-support, barebones edition" when CentOS releases the full enterprise version of Redhat's OS? There's not many large businesses out there who would install a beast like Redhat on their servers without support, and small businesses are generally going to have intelligent people who have more say, and why would any intelligent person pay for a non-supported, pared down version when they can get the full thing for free?

      Even when you consider businesses like web hosting, most clients consider the brand of Linux secondary to IIS vs. Apache, PHP vs. Python vs. Ruby, MySQL vs. SQL Server vs. PostgreSQL.

    3. Re:For those who will comment without Ring TFA... by the_B0fh · · Score: 1

      they did before. They concluded it wasn't worth it, and spawned fedora.

  31. Bunch of BS... by evilviper · · Score: 1

    Although I don't have data to prove it, I'm convinced

    What a great basis to bash an organization...
    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  32. Only terrorists use CentOS by JackMeyhoff · · Score: 3, Funny
    --
    http://www.rense.com/general79/wdx1.htm
  33. Fedora? by melonman · · Score: 4, Insightful

    Not only does Redhat 'tolerate' CentOS (see above), it also puts money into encouraging people to use Fedora, which is not only free but generally significantly more advanced than RHEL. For people who want free software and enjoy recompiling their kernel, Fedora is a much more obvious choice than a clone of CentOS.

    There was never any money in selling distros to dorm-room techies, and RHEL was never a good distribution for that market, because it's so conservative. I run Ubuntu on my desktop machines, because it's free, and it works, and it has all the multimedia stuff that RedHat don't ship as standard. On my company's production servers it's RHEL every time, because it's stable, because it will still be supported in 5 years' time if necessary, and because RHEL is a de facto standard in hosting terms. If a client's code doesn't work with RHEL, we can tell them to fix their code. If we were running some wacky, customised version of Gentoo they'd tell us to fix our server (whether or not anything was broken).

    Running CentOS would give us the conservatism of RHEL without any of the respectability. I can't see how that would be useful to us.

    --
    Virtually serving coffee
    1. Re:Fedora? by Anonymous Coward · · Score: 0

      Actually, recompiling the kernel is hardly ever necessary with Fedora, as Fedora provides the latest kernels as updates (for example I'm now running 2.6.23.1), sometimes even with additional backports (always the latest wireless drivers, and e.g. the CFS scheduler was backported to Fedora 2.6.22 kernels).

    2. Re:Fedora? by the_B0fh · · Score: 1

      Do you even understand what "binary compatible" means?

      And wonderful gentoo strawman.

    3. Re:Fedora? by Hamstaus · · Score: 1

      because it will still be supported in 5 years' time if necessary

      Interesting, do they guarantee that somewhere? I'm curious actually, because I just finished dismantling a Redhat 8.0 production box that I built in 2003. I've switched to CentOS, simply because I didn't like the way that Redhat ended their product line and support for the old distros, and I was worried that they might do that again in the future when the bean-counters get out the scissors.

      --
      I moderate "-1, Fool"
    4. Re:Fedora? by melonman · · Score: 1

      I know what binary compatible means. Do you know what 'importance of brand names to non-technical people controlling chequebooks' means? And Fedora isn't Gentoo, but it still smells of hobbyist to customers used to paying $$$ for server software.

      --
      Virtually serving coffee
    5. Re:Fedora? by melonman · · Score: 1
      From here:

      # Open source technologies rigorously tested and matured through the Red Hat sponsored Fedora project
      # With each major version, stable application interfaces and 7 years of product support
      --
      Virtually serving coffee
    6. Re:Fedora? by Anonymous Coward · · Score: 0

      Running CentOS would give us the conservatism of RHEL without any of the respectability. I can't see how that would be useful to us.

      It's free and very reliable. For those of us who don't want to recompile a kernel yet can get by without commercial support, Centos is a great choice.

    7. Re:Fedora? by Cro+Magnon · · Score: 1

      Fedora is fine if you want cutting edge. But if you want something conservative that doesn't get upgraded every few months, CentOS is a better choice. Obviously, in a real business with PHBs and the need to CYA, RHEL is the best choice, but if you don't need RH support, CentOS is a great choice for people who value stability over latest-and-greatest.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  34. Redhat, like MS support, sucks by Anonymous Coward · · Score: 0

    Redhat in my opinion has been the Microsoft of Linux distros. I worked at a large company with a large online presence, and a problem in the TCP/IP stack of the RHEL we were using was causing us problems, mostly long random networking pauses. Our guys tracked it down, devised a fix, and asked if Redhat would look into rolling it into their next RHEL release. They said no. Before we found out the cause, they dragged their heels in investigating it too.

    So obviously, we asked why we were paying for support we obviously weren't getting. And we started the switch to Centos ( since our software could run on it ) along with investigating other linux distros.

    You pay alot for official RH support, like MS, get little in return.

    1. Re:Redhat, like MS support, sucks by VENONA · · Score: 1

      I'll want to see a lot more detail before I'll believe the RHEL TCP/IP stack was causing "long random networking pauses."

      --
      What you do with a computer does not constitute the whole of computing.
    2. Re:Redhat, like MS support, sucks by the_B0fh · · Score: 1

      I believe there was such an issue, something to do with some older network equipment and some window size issues in the network frames, or was it something with jumbo frames. damnit, now that I'm in manglement, I keep forgetting shit now.

    3. Re:Redhat, like MS support, sucks by VENONA · · Score: 1

      OK, if that was the issue in the original AC post, and RH support couldn't deal with it, I'd say he had a valid complaint. You can deal with most issues (everything I've ever seen, though I haven't certainly seen everything) as either a kernel tunable, or on a per-interface basis. An OS support group should have been able to get that sorted.

      Now I'm curious. Hopefully the AC, or someone else that's seen it, will post back.

      --
      What you do with a computer does not constitute the whole of computing.
    4. Re:Redhat, like MS support, sucks by the_B0fh · · Score: 1

      It was quite a big deal for a while. Linus himself thought it shouldn't be "fixed" or "hacked around". Here, hang on. google...google... Ah, here ya go. This may have been the issue.

      http://kerneltrap.org/node/6723

    5. Re:Redhat, like MS support, sucks by VENONA · · Score: 1

      That's an interesting issue, and one I didn't know about. Thanks. There's some misinformation in the article (the main posts), partially cleared up in the comments. It looks like a recurrence of the window scaling issue from a couple of years earlier. See http://lwn.net/Articles/92727/ for that one. In both cases this is about non-Linux systems not doing scaling correctly, and some philosophical points about working around other people's problems. Which, unfortunately, can be an issue with any community-developed OS.

      OTOH, I've had problems with a TCP/IP stack on a commercial Unix, and Windows XP also had a window scaling issue. But none of this is an excuse for Red Hat not getting on the ball quickly for a client with a service contract, if they failed to do so. It looks as if there were options they could have taken, including adjusting tunables, which worked in some cases.

      I'll have to look at the current implementation next week, on the theory that a problem that's recurred once might recur twice. Bummer. I did *not* need more stuff to do. But, seriously, thanks again for bringing this up.

      --
      What you do with a computer does not constitute the whole of computing.
  35. Nope... by EvanK · · Score: 1

    Think of it this way...Much like Apple doesnt make their money off of OS X, but rather off of hardware sales, Redhat also doesnt make their money off RHL, but rather from their support contracts.

    1. Re:Nope... by Anonymous Coward · · Score: 0

      For this analogy to work RedHat would have to DRM their hardware.

  36. people still don't get it by burnin1965 · · Score: 5, Insightful

    1) Its open source, its not a question of tolerating Centos, its the way open source works.

    2) The anecdotal evidence is seriously flawed. His buddy was running an old and unsupported version of Red Hat Linux (7.3), and they were not paying for a service subscription, and they decided to go with Centos and continue to not pay for a support subscription. Uhh, clue here, this did not effect Red Hat in any way, they are not Red Hat's target market, if it wasn't Centos it would have been some other distro.

    3) And again, the conclusion is completely clueless. Red Hat does not change the way they do business becuase their business is based on open source. If Red Hat decided to develop their own closed source proprietary operating system they would lose the support and synergy of the massive open source community and their business would flop.

    These articles are tiresome and poorly researched. Why is it that everyone believes the only way to have a viable business today is to create a monopoly and change the way you do business to ensure there is no competition that can "sting" you. Red Hat is doing an outstanding job of monetizing a viable market, linux service, support, and training. If Jeff wants to understand why Red Hat does not change their business model all he has to do is read up on the history of Caldera/The SCO Group to see what happens when a linux distributor changes their business model and tries to monetize off the "IP" instead of the service and support they were originally established to provide as a business model.

    burnin

  37. It should be obvious by WhyMeWorry · · Score: 2, Funny

    They are nice guys

  38. CentOS doesn't hurt Redhat, up2date does by straponego · · Score: 4, Insightful
    The CentOS userbase is an incentive to make your software Redhat-compatible. If there were not a free and painless option that is compatible with RH, many more people would have switched to SuSE, Ubuntu, etc.

    CentOS is actually significantly better than RHEL in one respect, though. The package management system, yum, has always been more reliable for me than RHEL's up2date. Even now that RH uses yum, their reposistories seem to be down or slow fairly often. And I can't stand using RHEL's web site. It's much faster to deploy a CentOS server than a Red Hat one, enough so that the price difference seems almost secondary. On the other hand, if you install a lot of machines, you shouldn't be doing it from scratch.

    Eh, but Red Hat's done far more good things than bad things. I think CentOS (and to a lesser extent, White Box and others) have a nice symbiotic relationship with them. Some users will prefer or need officially supported software, and that's why they're still turning nice, but not monopolistic insane profits. It would be a mistake to think that they'd get many of the CentOS users if they could only work around that pesky GPL and force them to buy from Redhat. Quite the opposite; they'd ruin themselves.

    1. Re:CentOS doesn't hurt Redhat, up2date does by the_B0fh · · Score: 0

      I'll have to give you that. Despite all my rantings about rhell and redcrap, they have done some good things.

      If only they'll fix up2date, and rpm. There're *OPEN* issues against rpm, ones which will corrupt the freaking rpm database, and they refuse to fix it. Bastards.

  39. Because other software vendors require Redhat by PDG · · Score: 2, Insightful

    Nobody will read this since its at the bottom of the page, but lots of major software vendors will not provide support on CentOS.

    For example, Oracle will only provide support if its installed on the RHEL version of Linux.

    My IT department isn't concerned about the support involved with Linux, but they DO want to make sure they are supported for the big dollar, and incredibly important (data!) side of the business--so they pay for RHEL for production servers.

    In test and development arenas we use CentOS.

    --
    "Where is my mind?"
    1. Re:Because other software vendors require Redhat by Anonymous Coward · · Score: 0

      So you buy one copy of RHEL and install it on all your servers. Of course you only get RH support for one of your servers, but you get software support for all of them.

    2. Re:Because other software vendors require Redhat by Anonymous Coward · · Score: 0

      For example, Oracle will only provide support if its installed on the RHEL version of Linux.

      Not true. Oracle also supports its own Linux, which is a rebranded RedHat. See http://www.oracle.com/technologies/linux/index.html


      Yes, I am an Oracle employee, but not in the Linux division.

    3. Re:Because other software vendors require Redhat by PDG · · Score: 1

      I only meant they don't support the CentOS version, only the authentic RHEL version.

      --
      "Where is my mind?"
  40. This hurts my head by lluBdeR · · Score: 2, Insightful

    From TFA:

    Until fairly recently they ran this web site on an old version of Red Hat with essentially no outside support.

    and:

    But even if they run RHEL on a mix of two and four socket machines, they're still looking at $50K per year minimum for the privilege of sticking the little red logo on their servers.

    From what I gather (and I haven't been awake very long, so I might be wrong) they've been maintaining Linux boxes on their own for years (about 5, IIRC Redhat 7.3 came out 2002-ish), and the reason they're ditching Redhat is it costs too much for support they didn't need previously? If I might go on a limb and make a bizarre suggestion: Don't pay it.

    They know that the engineering effort at Red Hat costs serious money and that someone has to pay for it

    I don't really think this is that true. I was under the impression (and unless this is wrong too) RHEL forked off Fedora whenever they feel like it, so in effect (according to this) isn't Fedora just a testbed where people do free QA work for Redhat?

    My friend and his staff are Unix veterans, but they are not Linux geeks and they are definitely not the kind to muck around in the innards of their server OS just for the fun of it.

    So they're UNIX veterans, have been administering Linux systems for years, and they haven't mastered './configure && make && make install'? TFA claims they're LAMP-based, with the exception of the L, I can start on the AMP portion first thing in the morning and have all three upgraded in time for lunch (My day starts at 10, Lunch is noon without fail). Sounds to me like they're just too lazy to upgrade the 2 or 3 dependencies something might have. That's a great reason for ditching a known good and stable kernel, right?

    Hell, the first thing I do when I install a new OS is replace their Apache/MySQL/PHP with versions I compile myself (based on known-good versions we use on staging/test servers), that way I know 100% it's going to do what I want and I'm not going to see any crap in my error logs about PHP not loading it's GD extension because I opted not to install X on a server which really doesn't need it.

    If they really wanted set-it-and-forget-it why not use Slackware? Or ditch Linux entirely and go to FreeBSD?

    Sometimes people hurt my head.

    1. Re:This hurts my head by the_B0fh · · Score: 0

      Because most people do not know what the heck they're doing. The great unwashed masses that're using linux today - you think all of a sudden these people grew a brain?

      Remember what George Carlin said - If you think about how stupid the average person is, then remember that half the people are stupider than that...

      Just because someone throws on a geeksquad uniform doesn't mean they can do hardware repairs, and just because someone can stick a rhell install cd in a computer doesn't mean they understand what it does.

      -rhce because I can, and so that I can slag rhell as a rhce.
      -mcp because I can, and so that I can slag microsoft as a mcp.
      -notmcse because I am not that masochistic.

  41. some companies like "free" and "easy" by nicolaiplum · · Score: 2, Informative

    My company, which is not so small (some hundreds employees, some hundreds millions Euro revenue/year, growing fast), uses CentOS (as well as RHEL) because it's cheaper, the cost difference is noticeable. We also use MySQL partly because it's cheaper. But we also like the ability to deploy rapidly, and not have to manage licenses, and so on, and we do pay for MySQL support and RHEL support when we use it.
    Not all companies consider $10k Oracle licenses to be an inevitable cost of business, nor having to have people to track the licensing to be an inevitable drag.

    --
    "For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled"
    1. Re:some companies like "free" and "easy" by Anonymous Coward · · Score: 0

      yea, i used to work for those same types of companies.

      they liked cheap and easy too.

      fckgw...

      maybe cheap and easy is really just cheap and on the verge of an audit, can an employee is about to blow the whistle

    2. Re:some companies like "free" and "easy" by Anonymous Coward · · Score: 0

      I agree with you, except comparing MySQL to Oracle. Maybe if you said PostgreSQL, but MySQL isn't in the same league as Oracle.

      Access is to SQLServer as MySQL is to Oracle.

    3. Re:some companies like "free" and "easy" by wellingj · · Score: 1

      so where does SQLite fit in?

    4. Re:some companies like "free" and "easy" by sumdumass · · Score: 1

      Yep, I forget which politician said it, but there was a saying of "a coupl of million here, a couple there, before long it all starts adding up"

      This was in response to simple questions about cutting increases in programs and to why the budget was so high. It doesn't just pertain to millions or billions or government. when bean counters are looking at why or how to save money, license costs come up. I have walked into multi million dollar companies still using windows 98 or NT4 as late as 2005 because it worked and there was no compelling reason to do anything about it. Of course hardware failures and program updates and all started in, so they went to XP but not until after it was out for 4 or more years.

    5. Re:some companies like "free" and "easy" by Anonymous Coward · · Score: 0

      I've worked for a company of about 12, a company of several hundred, and three companies of several thousand (permanent, not a contractor). Except for the company of 12, the others avoided free (as in beer) software like the plague. "If they're not charging for it, there must be something wrong with it." Or, "If something goes wrong, we want to be able to call the vendor (and possibly sue them?)." YMMV.

      For the record, the small company heavily relied on RedHat, MySQL, and various other FOSS. They've since tripled since I worked there (no sentiment for me leaving, I suppose).

  42. Piracy by hackus · · Score: 1

    I still believe that the reason why Microsoft software is so widely used is because of the piracy or the economics of piracy that surround Microsoft products.

    It is a natural extension to get your product into as many hands as possible and then collect on all of the "possibilities" that might develop.

    For example, if you do not economically restrict the number of machines that you can deploy a product on, this naturally creates a demand for software from the creation of such a large number of users.

    That is just one example, but I think this is a big postive move for RedHat.

    Fedora can be equated in a similar fashion.

    -Hack

    --
    Got Geometrodynamics? Awe, too hard to figure out? Too bad.
  43. Why does RedHat "tolerate" CentOS? by serviscope_minor · · Score: 1

    Because RedHat have always been a good citizen in the Linux world, that's why. They use GPL code, and they release their developments under the GPL. Like any good Linux distro, you can compile any of the Redhatified binaries from the Redhatified source and install them as RedHat packages. That's because their distro is fully open, just like it should be.

    Of course, that means anyone can copy it, and they know that. That's why they don't really sell Linux as such. What they really sell is support. You can't copy that for free.

    --
    SJW n. One who posts facts.
    1. Re:Why does RedHat "tolerate" CentOS? by the_B0fh · · Score: 0

      Bullfuckingshit. RedCrap has always been the one trying to corner the market. They went with gcc 2.96 - http://gcc.gnu.org/gcc-2.96.html against the wishes of *EVERYONE* They tried to screw KDE over, creating that fucked up gnomeified bastardized kde. And go talk to the glibc developers about the whole glibc2 "lets push it out before it is ready" bullshit.

      They have done a number of truly rotten things.

      However, on the whole, they have contributed back to the community as well. If only they can stop to think - they can make money without trying to screw their customers, and the community over as well.

  44. One hand washes the other. by argent · · Score: 1

    The benefit to the end user of using a Red Hat clone rather than Red Hat is that it's a well supported ecosystem within the larger Linux ecosystem. The benefit to Red Hat of an end user using a Red Hat clone rather than another Linux distro is that it increases the size of the Red Hat ecosystem.

    If someone buys Red Hat's supported linux product, they're buying it for the support. That's the product Red Hat is really selling. If someone uses CentOS or Fedora or White Box they're more likely to buy support from Red Hat if they need a supported Linux. If someone uses C/F/WB they're potential customers for other companies that serve the Red Hat ecosystem, which increases the number of companies it can support and makes Red Hat's supported Linux more attractive. And Red Hat don't even have to pay the bandwidth charges for all the extra downloads if someone chooses CentOS or White Box instead of Fedora.

    It's coopetition. One hand washes the other.

  45. Red Hat do tolerate CentOS by Lemming+Mark · · Score: 1
    Although the GPL gives RH some obligations, they go beyond the requirements therein. The key point is that: the GPL requires you to distribute source to people you distribute the binaries to. Red Hat goes beyond this by making their source available online to all, not just to RHEL customers (which is all they were strictly obliged to do). To the best of my knowledge, they make proper Source RPMs available (rather than a less convenient format from the point of view of rebuilders like CentOS) on their FTP servers and they do so at their own expense.

    In short, RH go beyond mere due diligence and strict adherence to the GPL. They really do make an effort.

    To me this looks like healthy symbiosis: CentOS don't name RH as their upstream, so they don't trade off Red Hat's advertising. Folks who want a free-as-in-beer OS weren't going to buy the RHEL license anyhow. But people who are used to CentOS will be more inclined to favour RHEL as a product. By creating a user community, it also stimulates the creation of repositories of RHEL-compatible third party RPM repositories. I doubt there'd be such a volume of RHEL-compatible RPMs (as currently provided by various CentOS repositories) if it wasn't for the existance of a freely available derivative of RHEL.

    A combination of collaboration in development, free advertising, ease of customisation and mutual benefits, whilst still making money - sounds like a fine example of the Open Source game being played well, as long as they can make it pay for them long term!

  46. How do you validate CentOS? by Anonymous Coward · · Score: 0

    One of the things that makes CentOS a clear winner is that because it is a completely compatible recompilation of RH, going from a test CentOS install to a fully supported RH entitlement is very easy. Thus I install CentOS initially on all my servers initially and then when I put them into production, I convert them to RHEL and buy an entitlement for them. Some of my less important servers remain CentOS. One of the main reasons for converting my servers to RHEL is that I can watch over them all, in terms of patches and security eratta, from the RHN.


    How do you make sure that CentOS really is identical to what RedHat has provided? In other words, is there an automatic validation process to make sure some joker somwhere in the chain of distribution hasn't thrown in some strange code?

  47. Are you sure? by Anonymous Coward · · Score: 0

    What I believe _is_ hurting redhat is how their sales department insists that making copies of Redhat is illegal. We have been told time and time again that it is illegal for us to run copies of Redhat that are not paid for within our support contract. The truth is- as long as you aren't expecting support for the unpaid for copies and you are not selling them to other companies (alone or as part of your product, because of redhat trademarks) it is fine to use as many in-house copies as you want.

    Are you sure about that? Compilations can be copyrighted too (phonebooks, etc). Just because all the individual parts of RHEL are Free/Open Source (Are they?? All of them?? You sure?? All docs too? Everything on the CD? Otherwise it's copyright infringement you know) doesn't mean you can make as many copies of the whole RHEL CD as you like. Besides, when you install RHEL on multiple machines, do you get security updates on all those machines? In that case, you might be using a service without paying for it.. Now, it may be that the examples I've named above don't apply in this case, but nonetheless, you're on a slippery slope making/installing copies when RedHat tells you you can't. You'd be wise to listen to their sales department, unless your company lawyer said it was okay.

    1. Re:Are you sure? by SolusSD · · Score: 2, Informative

      Redhat's legal department confirmed what I had already believed (after all, my boss insisted I found out for sure, which makes perfect sense given the consequences). Redhat, like all other kernel/OSS developers owns copyrights on the code they have produced, but the code is licensed under the GPL. In fact, Redhat, being the great OSS supporter that they are, licenses all of their in house code under the GPL. Their sales department, unfortunately, is run by complete morons that don't understand simple things like the difference between trademarks, copyrights, and licenses. Since Redhat owns its trademark and, in order to preserve that trademark, must protect it, selling Redhat without following their licensing terms is illegal. In house use, however, is fair use.

  48. Centos keeps Redhat relevant by Anonymous Coward · · Score: 0

    You're spot-on.

    My startup is running Centos on our servers. If we couldn't easily get that for $0.00, we'd be using something else. We're not rich or stupid enough to run a server that's not free-as-in-{speech,beer}.

    The non-revenue Redhat-based systems are the only thing that's keeping Redhat's systems relevant, for an awful lot of us. Even when Redhat was The Linux Distribution To Use, most people used it through the free download, not the $50 boxed set.

    It's great if you can make money off free software -- more power to ya -- but if you don't make it easy for cheap people like me to run it for $0.00, you won't be selling those expensive versions for long, either.

    1. Re:Centos keeps Redhat relevant by Anonymous Coward · · Score: 0

      It's great if you can make money off free software -- more power to ya -- but if you don't make it easy for cheap people like me to run it for $0.00, you won't be selling those expensive versions for long, either.

      I don't know what your startup sells, but if I can't use it for $0.00 you have utterly failed. Good luck with that whole "revenue" thing.

  49. I just can't trust RedHat by The+Breeze · · Score: 0, Offtopic

    I ran RedHat Linux (not enterprise) for years on a few servers, and cheerfully paid the subscription fees for RedHat network (something like $30 a year or something) just because it was easy.

    I knew that RedHat's main focus was on Enterprise, which was total overkill for what I needed. Still, I also knew that they were making a profit on RedHat Linux - not a huge profit, but a profit nonetheless. I figured I could continue running RH Linux on my small servers for a long time, paying my subscription fees and everyone would be happy.

    Well, some beancounters at RedHat made a lot of noise about "brand dilution" or some such crap, rightfully pointing out that one nice big enterprise customer is worth about 10000 little customers like me (true). The same beancounters then made a decision that since I could get RH Linux cheap that it somehow made RHEL less attractive as a "brand" or some such marketing doublespeak - rather doubtful, but hey, it sounds impressive in a board meeting I guess.

    What happened? They end-of-lifed RedHat Linux extremely abruptly, I think within MONTHS, not years of the release of RedHat 9. They left me in a position where I had to go from telling clients, "oh, yeah, Linux is great, we set up the server, monitor it and update it every now and then, but mostly we just leave it alone" to telling clients, "uh, yeah, this is going to go away real soon so I need to upgrade all those servers that I told you we wouldn't have to make changes to for years."

    Well, damn. They betrayed me. They sold a decent product at a fair price, and I assumed that practice would continue. Silly me. They could have at least given me a decent lifecycle on the last release - hell, even Microsoft supports an operating system for a minimum of five years - but no....

    I talked to customers about Redhat being an affordable, decent product, and they made me look like an ass. I don't forget that.

    Now, many hardware manufacturers out there only support RedHat. And while RHEL is boring as hell, it's also stable as hell. It's a good product, but they are clearly not interested in catering to small customers. And CentOS is big enough that I can call Dell and say, "I have a Linux server" and they'll say "We only support Redhat" and I'll say, "Well, I'm running CentOS, the clone of RHEL."

    And Dell says, "Sounds good to us. How can we help you?"

    I think Redhat made a giant mistake back in 2003 when they dumped all us little guys.

    Sure, they have several nice big giant customers shoveling cash at them. But they could have kept the little guys too, a multitude of them, and STILL made a profit on the low-cost subscriptions they were selling us. Big corporations throwing cash at you is all well and good, but when you're going up against Microsoft, which is as much a political battle as a financial battle there's something to be said for strength in numbers. And there's something to be said for goodwill, which RedHat squandered.

    Don't even get me started on Fedora. Nice to play with, but I can't install an OS with a six-month or year lifecycle in a production environment.

    Redhat pissed on me and thousands of other small customers, when it would have cost them NOTHING to keep us. We don't forget. It's sad, really. I still try to keep up with RedHat sometimes. I registered for a RedHat seminar and someone from RedHat called me up to ask about my perception of RedHat and I started trying to explain why I could no longer trust RedHat. They didn't seem to know what I was talking about. They were most likely wondering, "if this guy dislikes us so much why is he attending a RedHat seminar?"

    I didn't feel like explaining it's because I use CentOS. Occasionally I'll sell a server to a customer and include a "donation amount" on the invoice, which I subsequently pass on to the CentOS project. It would be easier, slightly, I suppose to use the old RedHat Network basic subscription model - I wouldn't have to explain to customers why there's a "donation" field on their invoice instead of a "support contract" field - but hey, that's life.

    1. Re:I just can't trust RedHat by ErikZ · · Score: 1

      "Redhat pissed on me and thousands of other small customers, when it would have cost them NOTHING to keep us."

      How do you know that? Do you have direct access to their books, accountants and top managers?

      If they did something wrong by no longer supporting the little guy, it would have been very easy to go back and offer the 30$ a year subscription package again. But they haven't. There's probably a very good reason for that, and it involves profit.

      --
      Democrats or Republicans. They are both taking us to the same place and they are not afraid of us anymore.
    2. Re:I just can't trust RedHat by The+Breeze · · Score: 1

      I can't source it, but I remember at the time there were several statements from RedHat employees referring to the fact that Redhat Linux operated at a profit. It's most likely also buried somewhere in an annual report or something. I don't remember, but at the time they end-of-lifed RH 9 there was a lot of talk about it.

      Redhat can't get away from the fact that the EOL'd RH 9 faster than Microsoft ever thought of EOL-ing an operating system. That's why I use CentOS.

  50. Re: A few obvious answers by Anonymous Coward · · Score: 0

    I tend to agree that CentOS isn't likely to hurt Red Hat's RHEL sales. In fact, like Fedora, CentOS is likely to help Red Hat in the long run.
    For example, I run Fedora on my desktop and CentOS on personal or non-profit servers. However, the company at which I work would never
    consider using a free/community distro. So when it comes time to install server software at work, I can recommend what I know (Red Hat systems)
    with a price tag and the support that makes them feel comfortable.

    Red Hat gets the dollars from the big business and I get a free desktop OS, so everyone wins.
    Keep in mind that Red Hat has done very well financially over the past few years. Since they dropped their
    offical free version, their stock has soared. I cant' see them being unhappy about that.

  51. CentOS actually helps Red Hat by filbranden · · Score: 1

    In my opinion, CentOS actually helps Red Hat. I work as Linux admin, and in all the companies I've worked so far, we usually choose to run RHEL for the Oracle machines and CentOS for all the others.

    We choose RHEL for the Oracle machines because it's the platform Oracle supports, and the cost of RHEL is insignificant near to the cost of Oracle, so it's not worth to install CentOS and then have a support request dismissed from Oracle because it's running on a non-supported platform.

    On the other hand, for everything else, we basically support it ourselves, or google for answers when we have problems. Although the Red Hat support is very good, we actually don't need it, we're really OK on our own.

    But Red Hat actually benefits from we using CentOS, because as we can use CentOS for most of our machines, we'll turn to Red Hat when we need a supported platform, as we do with Oracle machines, and we don't even look at SuSE or others because we're already using (more or less) Red Hat, so we mostly know it well already.

    In any way, if CentOS weren't there, for the non-Oracle machines we would probably use Fedora, or even try Ubuntu. Yes, it would be different, but we'd prefer to do that than pay for RHEL licenses. And if we started looking to the other side, say, Ubuntu, or even OpenSuSE, as soon as we saw that we could get good Oracle support with Ubuntu or even buy SuSE, we would probably switch from RHEL, because then we would be able to unify (more or less) the platform.

    So, in the long term, I guess CentOS actually helps Red Hat, in allowing people to get used to Red Hat and deploy it without spending much in licenses, and then turning to Red Hat whenever they have the need to buy licenses to a supported OS.

  52. One additional by HangingChad · · Score: 1

    I'm going to have to go with "doesn't hurt Red Hat" on many counts.

    Then there's the PHB factor. The mid-level manager mindful that no one ever lost their job buying Microsoft. Many would pay the RHEL license cost just to have a throat to choke in the event something goes wrong. I've heard that discussion with my own ears. Decision makers wanting to know who was on the hook if something went bad.

    If RedHat itself fielded an exact, unbranded, unsupported copy I bet many companies would still opt for the support licenses. Most companies just don't get open source.

    --
    That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
  53. You are right by weierstrass · · Score: 1

    The fact that Red Hat do alright by selling software which is available and accessible costfree to anyone, means that the assumptions made in this article (and by much of the proprietary software industry) are obsolete.

    --
    my password really is 'stinkypants'
  54. This is the whole point of the GNU GPL. by Jessta · · Score: 1

    This is the whole point of the GNU GPL.

    --
    ...and that is all I have to say about that.
    http://jessta.id.au
  55. Because they use GPL Software?!?!? by schlick · · Score: 1

    Was this guy born yesterday? The reason RH "conviently" provides the source code on their FTP site is because they are REQUIRED to under the term of the GPL. RH didn't write all their software and still don't. They built a business from offering support for software they packaged. Is CentOS hurting RH? WTF RedHat wouldn't exist if it wasn't for projects like CentOS to begin with. I work for an Open Source company. This guy is operating under some big time misconceptions. The product is not the software, the product is Red Hat's expertise. If you don't need it, don't buy it.

    --
    "It's because they're stupid, that's why. That's why everybody does everything." -Homer Simpson
    1. Re:Because they use GPL Software?!?!? by SwashbucklingCowboy · · Score: 1

      "The reason RH "conviently" provides the source code on their FTP site is because they are REQUIRED to under the term of the GPL."

      Incorrect. Do not pass GO. Do not collect $200.

      The GPL requires that at least an offer of source be made to those who receive the binaries. This does not REQUIRE Red Hat to publish the code on an FTP site where ANYONE could can download it.

  56. Mu by swillden · · Score: 0

    The question "Why does Red Hat tolerate CentOS?" presumes that Red Hat has any choice in the matter. They don't, at least not with respect to all of the open source code in RHEL, and they know better than to include significant non-free components in their OS. Even if it didn't go against their own principles, it would generate a great deal of bad publicity for them.

    Red Hat does have one type of intellectual property which they can enforce against CentOS, trademarks. And Red Hat *does* enforce its trademarks, so vigorously that CentOS is extremely careful never to mention Red Hat or use any image that looks anything like a hat. Red Hat does do everything they can to shut down CentOS -- it's just that "everything they can" isn't much.

    Aside from that, I think it's pretty clear that CentOS doesn't hurt Red Hat much, and might even benefit Red Hat in lots of cases, but none of that has any bearing on the question in the first sentence of the article.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  57. Because Red Hat Has No Choice by SwashbucklingCowboy · · Score: 1

    "Why does Red Hat tolerate CentOS?"

    Because the GPL requires that they do so.

  58. Good for a chuckle.. by msimm · · Score: 1

    Centos is great and definitely helps drive Redhat on to enterprise. We run mainly Centos on our production systems with Redhat licenses on all the big gear. If Centos wasn't an option we'd run whatever the next most stable free os was and probably get comfortable with *that* then start paying them licenses for the big gear. Centos helps fill a void that keeps Redhat squarely on the radar for business. If we didn't have this option we wouldn't use Redhat at all.

    --
    Quack, quack.
  59. Hmmm by Vexorian · · Score: 1

    CentOS provides no paid support,
    And what's RedHat's bussiness again?

    If anything it is helping redhat get more people to test their software...

    --

    Copyright infringement is "piracy" in the same way DRM is "consumer rape"
  60. I can smell the innovation...not by sigzero · · Score: 0

    "CentOS mainly changes packages to remove upstream vendor branding and artwork" It is sad that so many of you are "ok" with this. RH does 99.999% of the work and CentOS takes it all and rebrands it and that is about it. Nice. I guess you would consider that a "benefit" of the GPL.

  61. How could someone even think of the possibility... by whatevah · · Score: 1
    .. that CentOS(or whatever) could actually hurt Red Hat sales?

    I don't want to sound like a troll, but I am really thinking about entering the journalism turf. It seems like an easy job. No reality check, no knowledge of business logic. You just write and you get paid. At least that's what many of them do.

    I mean has he ever wondered about why would someone pay a license for... anything? Maybe ... support? Has he ever heard of Oracle? Or SAP? Does he even have a clue what platforms these software manufacturers support?

    I know many said the same thing. But I am not arguing about the premise of the article, rather how come an article like that gets published and even worse, how come it's posted here.

    The only competitor to Red Hat is Novell, period. Maybe Ubuntu will join in the future. In other words the sky is blue and water is still refreshing. So... where's my money?

  62. GPL works several ways by kitgerrits · · Score: 1

    In one way, GPL allows anyone to use the sources of any GPL O/S to 'build' a new O/S, as long as all copyrighted material is left out.
    This has allowed a few people to 're-release' the combination/dependency/compatibility work of a commercial GPL O/S

    In another way, it has also allowed another company (a certain Database company comes to mind) to do exactly the same thing.
    All the original company can do (and did) is to tell the people that they have a deeper understanding of the O/S itself.
    Internal knowledge, it seems, is unfakeable.

    Technically, Red Hat would prefer home-coders to use Fedora Core.
    That way the home coders have access to all the latest Linux Bling (Yippee!) and Red Hat has a large testing crowd,
        to see how well all those Bling features work out in the 'real world'.
    Red Hat Enterprise Linux is, essentially, a (previous) version of Fedora Core that has proven itself to be rock-solid.

    On the other hand (like the post above), CentOS allows people to have a good look at RHEL without having to request a temporary 'test licence'
    (Yes they are available on request, you just have to dig a little deeper to find them).

    On the subject of Red Hat actually tolerating CentOS, I have spoken to some people of RH and they seem to get along
        rather well with the CentOS people.

    --
    "I was in love with a beautiful blonde once, dear. She drove me to drink. It's the one thing I am indebted to her for."
    1. Re:GPL works several ways by thegrassyknowl · · Score: 1

      In one way, GPL allows anyone to use the sources of any GPL O/S to 'build' a new O/S, as long as all copyrighted material is left out. This has allowed a few people to 're-release' the combination/dependency/compatibility work of a commercial GPL O/S

      If they left out all the copyrighted stuff there would be nothing left. What they are obliged to leave out is all the stuff that they are not at liberty to reproduce. This can include non-foss code, trademarks (Redhat, the redhat logo, etc), patented things if the original distribution has paid to license and distribute the patented material, etc.

      Internal knowledge, it seems, is unfakeable.

      You haven't dealt with many technical vendors lately have you? They all claim to have an immense knowledge of the internals of whatever it is they're selling but most have a support staff that are nothing more than trained monkeys. We've dealt with too many companies where they assume you're a moron and the level 1 support monkeys ask you to do dumb thinks like reboot or run 'make clean' and a long list of other equally useless suggestions when trying to solve a clearly defined problem.

      I could list the handful of good companies I've dealt with and the list would be very short. I will say that Trolltech and Ada Core tech were two of the most helpful in terms of real solutions to real problems (not OS vendors, I know). Most of the time Trolltech even came back with "we are aware of this and it's fixed in the next version, this patch should fix our software or you can do this workaround in your own code". Redhat falls somewhere between good and bad. I've dealt with hundreds of other support services and they range from good to really really bad.

      On the other hand (like the post above), CentOS allows people to have a good look at RHEL without having to request a temporary 'test licence' (Yes they are available on request, you just have to dig a little deeper to find them).

      When I evaluated RHEL for the company I used to work at test licenses were available without digging. They were linked from the main product page. The test license license agreement was enormous though, and only lasts 30 days. In some of the work I was doing (ClearCase) we needed to prove that the server and modules would be reliable over a longer term than that (the Clearcase kernel modules seemed to have a habit of bringing down the whole machine at seemingly random times). In the end we installed CentOS and ran the tests over some number of months. My evaluation machines eventually turned into productions machines with a tonne of NX sessions hanging off them. CentOS was pretty neat.

      Redhat wins with their support and their cool Redhat network. It was nice to log into that as an admin and see "all" of the PCs we had listed out along with which ones needed software updates. You could use the RHN console to schedule updates on machines, install a new package one one or many machines or do a bunch of other things. It was all pretty cool. As an admin it would have simplified my job of having to check all the RH machines for updates or to roll out a new package that everyone needed because they were listed all in one place neatly for me. I can see why it is useful to pay for a license for each machine when you have something like the RHN. It gives you nothing you can't do yourself with a bit of ssh and some scripting, but it makes it pretty and has wank factor to impress non-technical people as well.

      --
      I drink to make other people interesting!
    2. Re:GPL works several ways by kitgerrits · · Score: 1
      Well spoken.

      If they left out all the copyrighted stuff there would be nothing left. My bad, IANAL and the distinction between copyrighted, licensed and completely free code is still a bit vague to me.

      most have a support staff that are nothing more than trained monkeys Actually, I'm intimately familiar with the quality of code and support of a few vendors.
      I'll not delve deeper into this issue, because I still want to sleep tonight.

      Internal knowledge, it seems, is unfakeable. This was actually a jab at the unbreakable/unfakeable Linux game going on between RedHat and Oracle.
      From what I have read, Unbreakable Linux is not as stable as the original (Red Hat/CentOS).
      RedHat does not know every package by heart, but they can be a useful resource in finding that one (clustering) setting that's not in the documentation.
      They are prepared to talk to you and help you fix a problem, which is more than I can say for a lot of companies.
      (others usually tell you to re-install and update a clean system, before considering helping you).

      They were linked from the main product page Each time I needed an evaluation license, they changed that name/location of the request.
      Last time I checked, it was a Developers test subscription.

      Redhat wins with their support and their cool Redhat network If you liked RHN, you should see Satellite Server in action.
      Aside from acting as a proxy to reduce traffic and exposure,
          it allows you to roll out your own RPMs and configuration files to groups of computers.
      That way you can update apache and roll out httpd.conf to all your webservers with a minimum of effort.
      --
      "I was in love with a beautiful blonde once, dear. She drove me to drink. It's the one thing I am indebted to her for."
  63. CentOS helps Red Hat by Sadsfae · · Score: 0

    The fact that they exist further exemplifies Red Hat's goals and mission in FOSS.

    If people want enterprise support on RHL based systems they can simply opt for RHEL.

    --
    Have a squat over at the hobo house.
  64. Redhat prefected Time Travel by flyingfsck · · Score: 1

    Whenever I use Redhat (which is every gawddam day), it feels like I have gone back about 3 years in time. They are so far behind the feature curve it is really annoying the hell out of me. Redhat is a middle aged Linux - everything is slower and more painful...

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  65. pretty far fetched idea. by timmarhy · · Score: 1
    for a start, the vast majority of everything on RHEL is gpl and freely availible, so red hat doesn't have to like it since they have no choice.

    RHEL is about support and custom code fixes, not about selling a boxed software product

    --
    If you mod me down, I will become more powerful than you can imagine....
  66. Due to IT management thinking, no by br00tus · · Score: 1
    I previously worked for a large IT department in a Fortune 100 financial company, and their process of deciding to use a product is not the same as at a small company. The IT managers wanted support, business-compliant processes, and that sort of thing for the products they were buying. A good example of this was they preferred the technically inferior Sun ('nee Netscape) web server to Apache, simply because they were not happy with the official support for Apache. Or for an example from my current company, one of the reasons they run Jboss instead of Tomcat is the support. If there is a problem, an adminstrator can tell his manager, and a manager his manager, that they have a trouble ticket open with a company that sold them the product.

    The main reason we want Red Hat support now if for JBoss support, and for access to Red Hat CD's and packages. Also we have a goal of having all our systems patched with the latest necessary patches, and want support for that. Finally, if our server crashes on systems which are Red Hat certified, we might want to send the crash dump to Red Hat and our hardware vendor to find out why our system crashed.

    Our systems are not all patched, but on another note, are fairly stable. However, if I was in a different enterprise, I would want to know that if there was a serious and persistent problem affecting stability, that if that was sent back up the pipeline it would be worked on. For the hardware supplier, be it Dell or HP/Compaq, I would expect they would fix the problem, and on the OS side, if something was causing the system to crash on that end, that Red Hat would be able to push the stability fix into the kernel - or at least be aware of it and have a patch for it so we would be unaffected.

  67. Growing the pond by jeks · · Score: 1

    Say what you will about Eric S. Raymond. His writings in the cathedral and the bazaar have some strength to it, if you are to believe neo-OSS acolyte Jonathan Schwartz of Sun who often refers to this segment when defending their share price.

    It is applicable it the case of RedHat vs. CentOS as well.

  68. Nothing to see here, Please move along... by hollywoodb · · Score: 5, Informative

    RedHat does *not* hate CentOS... the issue has come up on the mailing lists over the years, and some see CentOS as the "gateway drug" that eventually brings more users to RHEL. Others feel that having CentOS around increases the RHEL{,-derived} userbase and therefore indirectly helps increase the quality of RHEL itself.

    In fact, CentOS and Fedora shared a developer booth at FOSDEM this year.
    http://wiki.centos.org/Events/Fosdem2007
    http://spevack.livejournal.com/2007/02/25/

    Additionally, it would have taken the author of TFA about 10 minutes of reasearch to turn up the FOSDEM tidbit and these little bits that make TFA completely irrelevant:
    http://www.linux.com/?module=comments&func=display&cid=1161341
    http://www.linuxformat.co.uk/modules.php?op=modload&name=News&file=article&sid=511
    (scroll down to the RH Q&A) on the second link.

    --
    I may have to share this planet with animals, but I'm doing my damn best to eat every last one of them.
    1. Re:Nothing to see here, Please move along... by Anonymous Coward · · Score: 0

      RedHat does *not* hate CentOS

      Um, yes they do.
      Developer activity on mailing lists does not reflect the attitude of the corporation.

      Wise up.
    2. Re:Nothing to see here, Please move along... by 'nother+poster · · Score: 1

      Hmmm. Couldn't "put up", and wouldn't "shut up", so it posted AC. YEA!

  69. Probably not much. by NerveGas · · Score: 1

    Folks who use CentOS are mostly the folks who wouldn't pay RedHat anyway. And folks who want to pay RedHat are the kind who want just the sort of hand-holding that RedHat offers. They're targeting two different market segments.

    --
    Oh, you're not stuck, you're just unable to let go of the onion rings.
  70. No, but it may kill the need for Fedora by alexborges · · Score: 1

    THere, in the subject, is my whole point. RHEL's sales are pushed by the certified apps it runs. It is used to kick Unix out, not to compete with other linuxes.

    I dont think centos hurts redhat at all. Now if oracle wanted to hurt, instead of pursuing their rather measly attempt at a rhel clone, they would support centos.

    --
    NO SIG
  71. CentOS is the best part of RHEL! by plazman30 · · Score: 1

    If you had to pick between RHEL and SLES, which would be a better choice. Sure, you can install SLES on a unlimited number of workstations for free. Now try and patch those copies after 30 days.

    CentOS lets RHEL customers install an OS they can patch on their dev testing boxes, and only buy licenses for the boxes that need support.

    Andy

    1. Re:CentOS is the best part of RHEL! by miffo.swe · · Score: 1

      I can second that, SLES is a real PITA to manage. I have had numerous problems with Yast/rug/ZYPP. Frankly, packet management on SLES is broken.

      --
      HTTP/1.1 400
  72. Something you don't know about CentOS by Anonymous Coward · · Score: 0

    CentOS is made and maintained by F5 Networks (Seattle) as the distribution they use in their "Big IP" product. It's a pure Business to Business fuck-you because F5 Networks doesn't want you to know they are to cheap to pay for what they use, but they aren't too cheap to pay a bunch of guys to clone Red Hat.

  73. Another attempt at FUD for OSS by 3seas · · Score: 1

    Typical war tactic, divide and conquer.

    Only problem with this is that the License is very clear and eliminates such possibilities.

    As is well known in the OSS industry, you make money off of support.

    I'm sure there is more to RedHat distros that was not developed in house as there was in house development.

    And that is the benefit of and to RedHat.

  74. Is there an echo in here? by Macthorpe · · Score: 1

    Is there an echo in here?

    --
    "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
  75. They tolerate it because they have to by cenonce · · Score: 1

    Isn't this what Linux and the GPL are all about? That is why Red Hat tolerates CentOS, because they agreed to the GPL when they created their own Linux distribution. As long as CentOS removes the front-end trademarks, it seems to me the GPL applies.

    Doesn't Red Hat derive a benefit from CentOS. Maybe a business running CentOS (like that described in the article) gets over its head in configuring or managing a CentOS server, and the moves to RHEL with paid support.

    1. Re:They tolerate it because they have to by gujo-odori · · Score: 1

      Exactly. Jeff Gould sounds like he gets neither Red Hat, nor Linux in general. Of course, Red Hat has to tolerate Centos because of the GPL, but it's even more than that. There's nothing stopping Red Hat from putting a binary license on some bits of RHEL. They simply refuse to do so. Red Hat's philosophy is now, and has always been, that they will GPL all their stuff. Red Hat is one of the oldest names in the Linux world, and their "religion" has always been to GPL everything, on the basis that a rising tide lifts all boats. Contrary to what Gould may think, distros like Centos are not something Red Hat tolerates; they are something Red Hat tacitly encourages. What's going to do next, ask why Red Hat would put out Fedora, which must surely be robbing some business from RHEL? Wouldn't surprise me in the least if he did.

  76. Does red hat have a choice? by sentientbrendan · · Score: 1

    Red hat refuses to ship anything that's no GPL'd, so it seems like their short on luck if someone chooses to ship the same thing for free.

    They already do a pretty good job of making it impossible to download the distro in binary form from their website for free, so I think they've done about as much as they legally can.

    Really, if a distro doesn't want to be undercut in this way, they need to be willing to add on closed source parts of their distro that can't be sold by someone else in this way. Suze does this, as does Xandros. Realistically, Suze may not have the best distro right now, but in the long run they have the better business model and have been more aggressive about pursuing new technologies (like mono and xen) and will probably beat red hat out of the market.

    1. Re:Does red hat have a choice? by PhilipPeake · · Score: 1

      Suze/Novell may get bitten badly at some point by their embrace of mono (and other Microsoft technologies). Aggressively forcing those into their core product is a risk. For them and for their clients.

      Xen is interesting, but as a non-transparent virtualization system it probably has a limited future.

      Novell have systematically screwed up every attempt they have made to become a real player in the *nix market. I don't think they are going to do much better with Suze from all I have seen.

    2. Re:Does red hat have a choice? by wikinerd · · Score: 1

      They already do a pretty good job of making it impossible to download the distro in binary form from their website for free, so I think they've done about as much as they legally can.

      A point to remember when discussing about the advantages of GPL over BSD licences.

  77. I guess I'm a little slow by epine · · Score: 2, Interesting

    I've been hearing this "throat to choke" meme circulate for twenty years, yet I've never managed to form a concrete image of it working out as advertised.

    In fact, working mostly for very small companies, I've never seen any throat of upstream vendor take as much as a deep gulp. Even with fairly expensive software products, you still get a junior tech who usually insists for the first week (or more), despite comprehensive technical attachments to the contrary, that somehow you aren't using the expensive product correctly, because a product that expensive made by such a large and powerful corporation with such a long history couldn't possibly be that incredibly broken.

    A recent nightmare that comes to mind was the Xilinx ISE Webpack ignoring pin constraints, claiming in most outputs to have satisfied them, but if you dug down deep enough, you could find a report that told you where the pin was actually bound. Of course, Webpack ISE is not an example of an expensive support contract, but even so, Xilinx has a $7B market cap., with a long history, and if they can't get something this basic correct, what exactly has their corporate stature done for you?

    By the time the error in our prototype system was detected and fixed with much recriminations and pulling of hair, the damage was done, we had discovered our own work-around tweaking the source code, and what was to be gained by turning the thumb screw on Xilinx? In small companies, I've rarely had the level of support where I could choke a throat without first filling out an application form. Oh, the primal satisfaction.

    In the cases where I've seen expensive support prove its worth at an engineering level, the companies involved have a deep enough business relationship to fly engineers back and forth for training, support, and knowledge exchange. Any support contract below this tier, no matter what metalic luster is applied by the marketrons, has good odds to waste more time and talent than it salvages. The exception where it can pay off is for orgs (esp. high-powered revolving-door consulting orgs) that hire at the bottom of the experience pool, people who can't actually use the software correctly, and where the money you save by hiring unqualified workers pays for the expensive support, with the added bonus that your unqualified workers acquire portable skills far more slowly than if they ever solved a problem themselves.

    Where I have seen the implied law-of-the-jungle "choke the throat" aggression play out is mid-level a-hats in development meetings insinuate "we are paying tons of support money on this expensive support contract from this powerful company, so how come you can't get it to work?" This only serves to nourish all the standard corporate dysfunctions, drives the wedge between marketing and development ever deeper, mandates CYA behaviour from every quarter, and tilts the landscape in favour of those whose job descriptions are primarily political in nature over those who have technical obligations to complete, and who can't play politics on a full-time basis. What's not to like?

    I've heard this meme for twenty years--usually tendered by the fetishists of corporate jargon--and I'm still asking myself "whose neck is actually being choked here?" It has always struck me that the primary function of these contracts is to make it easier for the suits to denigrate the geeks.

    Here is a telling observation. When is the last time any bean-counting suit ever asked "did we get our money from that support contract or not?" Of course they got their value: the empowerment to drip condescension toward their technical staff over every snag and delay. "Of course these problems are not a management failure, we bought the gold platinum titanium support package from every vendor we sourced. It must be our own clunkhead engineers who can't get anything right."

    1. Re:I guess I'm a little slow by Chops · · Score: 1

      FWIW, I've seen plenty of expensive support contracts that add up to "the right to talk to clueless support people who deny that your problem exists" in my time. I have, though, also heard a few conversations between my boss and our vendors of the nature, "Look, we're paying you guys X thousand dollars for support, and we're having a problem and you're not bloody fixing it. We're going to start looking at other vendors because you're not working out for us." In a lot of those situations, we got to talk to someone who knew what they were doing and/or could fix our problem reasonably quickly. It might have helped that he wasn't bluffing; that he actually had the power and was pissed enough to switch vendors because our current one was falling down on the job (which they were).

    2. Re:I guess I'm a little slow by t0rkm3 · · Score: 1

      I don't have time to reply to all of your points, but I think you'll find that your mileage varies... Sometimes even within the same company.

      For instance, I deal with Cisco on a very regular basis. We have spent a lot of money on Cisco product and support. When I want a throat to choak because the documentation is wrong (LDAP mapping to RADIUS attributes in the ASA) or there is a stupid bug (MARS cannot use the 'Test Connectivity' function in ver 5.3.1 to connect to IPS 6.x) I get a throat. Fortunately, my account team trusts me when I say that something very wrong and very unacceptable so they get the BU team lead on the phone with me, which allows me to show a developer where the product went awry. Then we work out a schedule for the fix. This allows the other customers within the stream to benefit from my persistence and hard work documenting every aspect of the problem. It's not optimal, if you don't have a global team you wouldn't get the same access unless you started to build a relationship with one of the developers (which I have done in the past).

      Checkpoint seems to be a little less responsive with their dev team, but at the same time they don't seem to have the same problems with bugs in the first layer of the software. (However there is an interesting bug in the NAT state table).

      So far for me it's been a matter of relationship management. Support contracts can be worth it.

      Regarding management's denigration of the technical people using the support contracts as leverage. That's BS. If the technical people kept management informed and correctly managed their expectations then there wouldn't be any misunderstanding. If your management isn't reasonable in this regard, please circulate your resume, there are plenty of other places to work.

  78. RH9, Fedora by Anonymous Coward · · Score: 0
    OK I agree CentOS is good, but it doesn't fill the void left by RH9, it follows along the same path as RHEL, in that it is a server focused OS (and is compiled from the same bits as RHEL).

    Fedora fills the void left by RH9. Whether you agree it does a good job of it or not is another issue, but the purpose of Fedora is to 1) be a testing ground for new stuff that will eventually end up in RHEL and 2) serve as a good "community" desktop focused OS.

    I run Fedora as we speak, and I have run RedHat since 6.0.

  79. Comment removed by account_deleted · · Score: 4, Insightful

    Comment removed based on user account deletion

  80. The E is for Enterprise by Eskarel · · Score: 2, Insightful
    It's very simple. Red Hat Enterprise Linux is for the Enterprise, that's what they sell. Same thing for SuSe(though with some extensions). They sell rather expensive support contracts to organizations large enough to require them, folks don't pay that kind of money because they can't get the product some other way, they pay it to not have to have linux developers on staff, and to have support and limited culpability from a third party. Red Hat might lose a few boundary cases(people who want an enterprise style system but don't want support), but it's not going to be a major drama for them.

    That said I think that Enterprise systems are pretty terrible and I've never really liked Red Hat's product. But that's a story for another time.

  81. Probably redundant, but.... by mlwmohawk · · Score: 1

    The article is quite right that RHEL is a "top of the line" corporate support platform. Button downed IT professionals at large banks and businesses buy RHEL, probably never even looking at the price.

    Back in RedHat 9.0 days, they had support and free versions. The free version under cut their commercial version. With RHEL, Cent OS provides the perfect answer. RedHat *has* a free version of its REHL that does not dilute its commercial offerings.

    As said in other posts, CentOS (which I use) helps RedHat because it is essentially RHEL. Bugs I find get fixed in RHEL. Apps I develop for CentOS are RHEL ready.

    I can't see how RedHat loses anything with CentOS. Each customer has a calculated cost. Reduce the numer of customers while maintaining the same income level means more profit. (In general, there are always some exceptions).

  82. Reinstall by CustomDesigned · · Score: 1

    (others usually tell you to re-install and update a clean system, before considering helping you). My favorite was trying to install SCO 286 Xenix on brand new ESDI disks. The install software when into an infinite loop on encountering the first bad sector. No problem, we had the premium support.

    Me: We're trying to install Xenix on ESDI, and it goes into a loop at the first bad sector.

    Support: First I'll need you to install a fresh copy of Xenix.

    Me: But that's what were trying to do!

    Support: Look, I can't help you unless if you're not willing to follow my instructions.

    Me: (Loses it and yells insults into the phone ... )

    We went back to ST506 for the moment, ditched SCO, and signed up as a Motorola var to sell 68k unix systems...

  83. CentOS drives people to RH by noldrin · · Score: 1

    We use CentOS because it's free. If their was no CentOS, we'd use Debian or something else. We describe it to our customers as a free community version of RedHat, some of our customers will then opt on their own to request we use the official RedHat and pay extra for it. If we did Debian, that would probably not happen.

  84. CentOS is a good community member by yorgasor · · Score: 1

    When I worked at RH, I never heard anyone say anything bad about CentOS. CentOS is a good community member. As they rebuild and test packages, they find lots of bugs themselves. They either fix it themselves and send the patches upstream to RH, or file bug reports. Again, it's like having free QA.

    And RHEL is after a different market than CentOS. RHEL is for companies that need the insurance of support. These companies need to know that if something goes wrong, someone will be there to help them fix it, or come out and fix it. Sure, you might be able to get someone on a community mailing list to solve the problem, but that kind of support is kind of hit and miss. You need better insurance than that if you've got projects being delayed because of a major issue.

    CentOS also has the benefit that the rising generation of geeks without $$$$ can get experience using a RHEL-like OS. So when they start working for big companies who need RHEL, they already have all the expertise they need.

    RHEL also has some things that don't make it out to CentOS. RHEL's Satellite Server is nothing short of amazing when it comes to managing large networks of RHEL boxes. They took their up2date server, which all RHEL boxes register with to get updates, and then made that a separate product. So instead of RHEL boxes registering with RH, they can register with their own satellite server to get updates. And with that, they've added all sorts of provisioning options, so you can push out all the updates from the server. Or you can have a group of computers all be installed, upgraded, downgraded, etc, without having to physically visit each system or even manually log into each one. You can control everything from the satellite server.

    --
    Looking for a computer support specialist for your small business? Check out
  85. why they biting Red Hat's style? by Anonymous Coward · · Score: 0

    I can kind of see why Red Hat would get pissed off, seeing as how they spend all this time and energy creating their distro, then someone else just recompiles it and takes credit for it... oh, and rips out all the stuff identifying it as the Red Hat distro.

    I wonder how people would feel if someone just recompiled Ubuntu and just ripped out any reference to it. Seeing as how Ubuntu is now the Lunix distro flavor of the month, I'm guessing the darling of Slashdot would get quite a spirited defense.

    Red Hat's only crime is expecting to get credit for their work from the FOSS community.

  86. Enterprise is usually provided free anyway by Mobius_6 · · Score: 0

    Working in webhosting support I get many clients who run RHEL on their server simply because it was provided as a choice by the datacenter where they lease their server(s). There is no price difference between the OS's they choose from during their server sign-up; so it's plausible that they could choose any one of several OS's which may or may not free to the general public. The RHEL boxes commonly are registered via a satellite service that is provided by the datacenter themselves and the user never has to pay for this part separately. It seems that this type of free provisioning of the OS would do the same amount of damage as a clone like CentOS.

  87. I'll accept all of your points except 2 by Sun · · Score: 0

    There is nothing in the Trademark law that prevents CentOS from truthfully describing where they got the source of the distribution from. Red Hat is attempting to expand Trademark protection to places it was never meant to cover, and in that regard it is as bad as the last of the proprietary vendors.

    And you know it.

    In fact, just like proprietary vendors, you had some versions where you had to click "I agree" to the preposterous "trademark use agreement". Just like we do for proprietary vendors, I have to ask you: Why do you want to shift the protection from trademark to contract law? Is it because you actually know that trademark law does not allow you to demand what you demand?

    Shachar
    IANAL, but I did consult one about this point in the past.

    1. Re:I'll accept all of your points except 2 by Anonymous Coward · · Score: 1, Insightful

      I'm sure the high powered RH legal team will be swayed by your potent argument.
      You don't protect trademarks, you lose them, the end. And you know it.

    2. Re:I'll accept all of your points except 2 by nuzak · · Score: 2, Informative

      > You don't protect trademarks, you lose them, the end. And you know it.

      You don't quite lose them. What you do lose is the ability to claim damages due to dilution. You still get to pursue blatant infringement -- Kimberly-Clark could still sue your cojones off if you sold paper products called "Kleenex".

      --
      Done with slashdot, done with nerds, getting a life.
  88. The way i read the article. by pjr.cc · · Score: 1


    1. "waaaah, centos makes redhat RHEL more accessible"
    2. "waaaah, redhat should do something about centos mmmkay?"
    3. "waaaah, redhat is bad mmmkay??"
    4. "waaaah, none of the other distro's have a chance to supplant rhel because centos is free".

    And you wonder why redhat do nothing about centos? seriously??? I dont mean that because of his comments. But from a RHEL perspective everyone wins. RHEL get someone else to distribute a version of their OS that they dont have to support but comes with all the other bonus's of running RHEL. When a customer can afford it they move to RHEL for reasons that make sense to them. At the end of th day, ragardless of whether your running RHEL or CentosOS - your still running an OS who's ideals are wrapped around RHEL's. Which gives RedHat alot of leeway in things that wrap around RHEL (like enterprise desktop maybe?) "yeah, our enterprise destkops work with centos, just dont ask us to support your centos servers, but here's a migration strategy...".

  89. i don't believe so by voidy · · Score: 1

    I think people go with RedHat because they want someone else to be responsible for the support. People don't get the level of professional support in CentOS, so businesses are more likely to go with RHEL. Having said that, my work place recently moved over rather a number of servers to CentOS from RHEL. The licensing fees are probably quite a bit, especially if you don't need the support.

    --
    I do not fear computers. I fear the lack of them. Isaac Asimov
  90. Umm, explain? by cheros · · Score: 1

    I just got up so I probably still have too much blood in my caffeine :-)

    3. Here's a question: why is there no CentOS equivalent based on SuSE products? Think about it.

    What about OpenSuSE?

    Having said that, I did have to work with SLES 9 for a while and it's not an experience I want to repeat. Ever. Well, OK, unless the alternative is Worries for Windows or Windows ME. But even then. OpenSuSE is quite pleasant to work with, barring the apparent risk of Microsoft proximity.

    Since I appear to hear from an expert, here's a question: where are the OS controls in CentOS/Red Hat? In SuSE you've got a thing called YAST which you can access via command line as well as GUI, and it pretty much does anything except EVMS setup or make coffee (which I need right now, dang) - I used to use RH until I found just how easy it was to manage a SuSE box (I'm usually too short on time to mine manuals too often). I looked at Fedora but discovered that the latest version would NOT work correctly on the HP DL 230 server I had (it only saw one SATA disk, for some reason /dev/sdb was absent which sort of screwed things up for mirroring :-). Don't think I tried CentOS then.

    My needs are simple: I need a box which acts as a file server, email and LAMP engine (and Postgresql) for a couple of domains I'm playing with (Postfix, and access to mailboxes via IMAPs). It may also act as a KDE/Gnome desktop when I'm doing something mad with the desktop I use. Firewall and VPN duties will soon be taken care of by a Smoothwall box when I find a box small enough :-).

    The argument for this change is that I'm trying to get a couple of things online in a fashion stable enough not to worry about it for a year other than the daily security patching (and I'm happy with that being automated, as long as the backup has worked correctly beforehand :-).

    If I switch the main OS over I may cut over to Fedora on the desktops as well. I like Ubuntu but I tend to use desktops for trying out things that I subsequently put on a server (like groupware) which is simply easier by using the same platform.

    Any help appreciated, I'm already breaking out the IRC clients :).

    --
    Insert .sig here. Send no money now. Owner may sue, contents will settle. Batteries not included.
  91. No difference by OrangeTide · · Score: 1

    CentOS is just taking what Red Hat gave away for free and does something with it, just like what Red Hat did with the hundreds of packages they collected. Customers get what they pay for too. For free you get no support and nobody to sue.

    --
    “Common sense is not so common.” — Voltaire
  92. bump for gateway drug theory by theonetruekeebler · · Score: 1

    Some see CentOS as the "gateway drug" that eventually brings more users to RHEL. That's certainly been the case for us, only we had a third-party pusher in the guise of an RDBMS vendor.

    We've used CentOS on our app servers for a while now and were going to use it on our DB servers as well until we called $DB_VENDOR asking about CentOS support. They acknowledged that it's functionally identical to RHEL, but that really didn't matter: they'd tested on RHEL, Suse, and Ubuntu, so that's what they support. We have quite a lot invested in CentOS expertise already, so RHEL it had to be. After all, if your production DB is down you can't have tech support hanging up on you when they find out you're on an "unsupported" distro, right?

    So even though there are no foreseeable Linux problems we couldn't solve on our own, we'll be running fully supported RHEL 5 on our DB servers. Hell, even with the maxicare RHEL package our support costs are about a tenth what they were for $PROPRIETARY_PLATFORM.

    But RHEL will only be on the production DB servers. Everything else will continue to be CentOS.

    --
    This is not my sandwich.
  93. As a user, CentOS makes me more likely to buy RHEL by wikinerd · · Score: 2, Insightful

    My servers run Debian GNU/Linux 4.0 etch amd64. If for any reason I couldn't get Debian and I wanted a RedHat-like distro, then I would examine CentOS. If it suited me, then I would examine the pure RedHat. But if I couldn't get CentOS, then there would be absolutely no chance of even thinking about RedHat.

    To summarise... If I were a CentOS user I would be willing to consider RHEL, but if there were no CentOS I would *never* buy RHEL. I wouldn't get RHEL even if it, its updates, and its support were offered for free.

    Let me explain my reasoning as a user: RHEL is supported by a company. CentOS is supported by a community. Companies may die or bought by a bigger company and leave their users unsupported. Communities, while having no obligation to support the users, tend to live on and almost never die. "Dead" communities are usually just replaced by a new more vibrant one. The reason is that communities are formed because of the needs of developers and users, so for as long as users have the same needs there will always be communities covering these needs. Companies, however, are usually formed for profit, so if you have obscure needs that cannot bring profits to an enterprise then you may be unable to buy a commercial solution to your needs. A company can cease its operations for various reasons. This can't happen with a community. With an active CentOS community around, this means that upgrading to the enterprise support offered by RedHat is safe: Even if RedHat can't support me, I can always just revert back to CentOS and carry on my business as before with no changes. But if CentOS didn't exist, then getting RedHat would mean that you would assume the risk of having business continuity problems if your support provider went out of business etc. With CentOS around acting as a backup, RedHat is a much more safer choice.

    Let's use an actual example: I still have a Commodore 64 home micro from the 1980s with its sexy tape drive, but Commodore is no more and doesn't support this old model anymore. I have to rely to an informal community to get spare parts from auctions, classified ads, etc. The company has stopped supported the C64 users, but the C64 community is still alive and supports its members very well.

    Really, the knowledge that CentOS has good compatibility with RHEL and that I will *never* face the same situation as my did with my C64 makes me a thousand times more willing to buy RHEL if I ever need their enterprise support. Buying RedHat means that if I can't continue running it then I can just revert back to CentOS with little effort.

    In this sense, every commercial distributors should seek to support a compatible community-led parallel distro alongside their commercial offering. Community distros that are compatible with commercial versions achieve synergy benefits for both the community and the commercial vendor. Furthermore, companies should not be afraid of losing customers from the community version, as commercial and community distros are meant for very different kinds of users. In the CentOS/RHEL example, the difference between CentOS and RHEL is that with CentOS you are responsible for keeping your machines operational, while with RHEL you can sign a contract and give portions of your responsibility to RedHat. This usually appeals to middle level managers who get to make a choice between distros and have a higher boss to report to in case somethings gets broken. But CentOS, just like Debian, will appeal to techies and entrepreneurs who either know what they are doing or have no one above them to fear getting fired. So, really, these distros target very different markets and very different psychologies of customers.

  94. Better Centos than RH9 or Fedora by MrJones · · Score: 1

    I just once commited the error of installing Fedora on a server, it was just after RH9 died.
    I was buying RH9 for server but when I saw the 350$ price tag of RHEL, I turned to Centos.

    I still recomends RHEL, but if RH has a 50-100$ server product, I will be still his happy customer. But right, I'm a Centos user.

    --
    Get my e-mail after a captcha test in: http://tinymailt
  95. I don't care. by discogravy · · Score: 1
    The only legit RH options are: pay 1000$/year for RHEL (AS or ES or whatever) OR go with the latest fedora that's going to break in a year or two. I tried to go FreeBSD but mgmnt wanted linux and wanted supported, so we wound up paying for RHEL. It's nice, but their support is worth fuck-all ("oh, you changed the default config by installing a program we don't support?" "yeah, it's a firewall monitoring script. uses SNMP and JRE 1.5...." "yeah, we recommend you reinstall...") and the update/website combo is needlessly complex. Channels? WTF? Can't you keep track of the things on my box and update what needs to be updated to the level I want? apt-get does that, yum does that, fuck, a properly configured FreeBSD will do that, Mac OS X will do that with shiny! -- the only systems that have a more annoying update methodology are Sun's Solaris (and they're gettin better) and MS Windows (yeah, not so much though...although worth pointing out that while it's a pain in the ass, you can still do it if you're running your own AD and update server.)

    So RH needs money, and making a sub-standard free version and an expensive "Enterprise" version are how they decided to do it. That's fine, but it doesn't mean I have to tie myself to them. They screwed themselves out of my custom -- which wouldn't have been a huge contract, but at least one or two yearly support incidents.

    New job and all their linux boxes are various versions of Fedora (except one box which is a debian so old I can't get the ISO to make new disks). Which means I cannot update them since there are no yum repositories for these older versions. I have to make plans to bring up new CentOS boxes and migrate the data so that I can keep them updated.

  96. missing the point by kilgor · · Score: 1

    Seems to me that Jeff Gould is missing the entire point of Linux, RedHat, and GPL in particular. GPL means that the software is FREE for EVERYONE. RedHat sells a service contract to support sites that want to use the free software that RedHat chooses to package and support.

    Another way to look at it is that Red Hat save a boatload of money on parts of the OS that it didn't have to pay to develop.

  97. not alone by mu51c10rd · · Score: 1

    No, you are not the only company doing that. We, too, run our most critical production machines on RHEL, and use CentOS for everything else. That gives us standardization across the entire company, as well as support for our critical boxes. Leaving CentOS alone definitely works to Red Hat's advantage.

  98. Red Hat can't do anything about CentOS by Anonymous Coward · · Score: 0

    CentOS is completely legal because of GPL. There is nothing Red Hat can do to shut it down. People who think that CentOS helps Red Hat are the same people that think illegal p2p music sharing doesn't hurt the recording industry. They don't seem to understand the value of the software itself (nor do they understand the value of a sound recording), which the GPL drives down to $0. Red Hat chose this poison, and they need to live with it.