Slashdot Mirror
The Increasing Cost of Red Hat Linux?
An Anonymous Coward asks: "I work at a company with a large number of Linux servers in the data center. We're currently evaluating what distribution we want to use moving forward. Upgrading to Red Hat Enterprise from 7.2 would cost ~$350k just for the systems we already have deployed. Due to the change in Red Hat's release policy, we either have to move to Enterprise, or change distributions. Also, we don't have Oracle on any of these systems, but we will need it in the future. This leaves us with rather limited options. I'm interested hearing what other Slashdot readers are running, and planning?"
How much more would Suse cost? I have worked at facilities before that switch from windows to Suse recently and they said it was a lot less expensive in the long run.
[RIAA] says its concern is artists. That's true, in just the sense that a cattle rancher is concerned about its cattle.
If you're looking for support (which is what I'm assuming your reason for going with Enterprise server is), then either pay for Advance Server or go with a different cheaper distribution and put the money you saved into someone that can search Google and find out how to make "RH only" stuff work on Debian or something.
We run oracle (both 8 and 9) on Debian, as well as most of our internet infrastructure (with the exception of proprietary programs that are stuck on Win2K for the time being). Most of the vendors of Linux based apps that we have worked with are willing to provide support even with Debian being the distro we chose (and then the ones that have complained, I've just called for another technician that was more distro-agnostic and gotten right through).
I was personally involved in porting our company's software to Linux. I chose to support Red Hat, thinking that their big name would mean that they were somehow better as an organization.
I WAS TOTALLY WRONG!
I recently tried phoning Red Hat Sales to try and buy support, and it has been more than 1 week, and I have been unable to get them to respond! My first 3 attempts to contact Sales were ignored, and finally I got someone on the phone. They directed me to someone else, and after an initial e-mail, they have yet to contact me after I sent them 2 follow-up e-mails. It is absolutely ridiculous.
You would in this day-and-age that Red Hat would be salivating over someone who is willing to pay them money for support, but they seem competely disinterested in helping me give them money. I have already complained to my superiors that we should consider supporting a different flavor of Linux, because if this is how responsive Red Hat's Sales unit is, imagine how unresponsive their Support unit it.
I agree, I think Red Hat is really leaving small/medium businesses out in the cold with their new policies.
One example, I set up a server/firewall for a small business as a contract job on the side. It runs all their stuff, web, email, etc. They really don't have a need for more than one server.
Last year when I set it up, I told them it would be good for at least three years. I don't like it that Red Hat made a liar out of me.
At my real job, we have more than a dozen Red Hat servers, and I'm stuck in the same dilemma. We can't afford to destabilize servers by putting essentially beta software on them, that the 12 month EOL requires. I used to let RH releases age about 3 or 4 months to get the major bugs out before I even considered using them in production.
So now I'm faced with either spending tons more time patching the servers by hand (even though we pay for RHN), or spending tons more money, buying RHEL which would cost at least 10 times more than the ~$1000 a year we spend on RHN now.
I really hope something gives on this situation. Red Hat better think twice before they alienate small to medium businesses. I don't need support. I do need updates. I do need more than 12 months before EOL.
I've had enough abrasive sigs. Kittens are cute and fuzzy.
Now, I have 70 Linux servers around the country, and a steady stream of new customers. I've been installing Redhat 8.0 on new deployments because 9.0 doesn't work well with our application. So, we've everything from 7.0 through 8.0 in the field. Over the past few months, Redhat dropped up2date support and patches for Redhat 7 and 7.1. I feel guilty installing 8.0 on new boxes because I know support for it will be dropped at the end of the year.
I don't wish to buy into Redhat AS or ES because I don't understand what I'm paying for. *I'm* the Redhat support. I just need something that will receive patches and support for more than one year. The 5 year lifespan of the ES versions is nice, but I've NEVER called Redhat for support. I don't plan to.
I build the kernels for each of the servers. I use vanilla kernel.org source with XFS. We sell 2, 4 and 8-way servers. Am I missing out on anything from the "optimized" Redhat Advanced Server kernels? What are other people in this situation doing?
I think it's confusing because we initially chose Redhat for the accountability aspect of having a corporation behind the distro. Now, I'm not sure who they're targeting. I would imagine that most firms that select Redhat Advanced server and are willing to pay the price (>$1000/license) would have a staff talented enough to support it. So why the mandatory support costs from Redhat?
Edmund White
http://flickr.com/ewwhite
The catch; using a commercial piece of software in the mix. In our case, a certain database. Being closed-source and totally non-self-servicable in case of serious problems or bugs, it is imperative to have a support contract for the commercial software. Almost all the RDBMS vendors have now altered/clarified their support policy: they will *not* honor a paid support agreement if you are running the free version of Red Hat underneath their software.
Why this policy exists is a question I will let somebody else speculate about...
There is exactly one major RDBMS vendor I could find that will officially support its software running on the free version of Red Hat (as of April 2003, at least), and that vendor is IBM with their DB/2 product.
Unfortunately, we were too time-constrained to port our system to DB/2, so in the end we caved and paid for Red Hat Enterprise so we could get RDBMS support on our existing platform. To this day we have not called Red Hat tech support once and don't expect to do so, ever. The thousands of dollars we paid covered the 3 minutes of effort the sales guy put in over the phone. Not a bad deal for Red Hat. If I were starting from scratch, knowing about the new support policies from the RDBMS vendors, I would have done the project using DB/2. PostgreSQL would have been an even better choice, except our project required real-time database replication, and PostgreSQL is just now getting to the point where that works well enough.