Slashdot Mirror
MySQL Quietly Drops Support For Debian Linux [UPDATED]
volts writes "MySQL quietly deprecated support for most Linux distributions on October 16, when its 'MySQL Network' support plan was replaced by 'MySQL Enterprise.' MySQL now supports only two Linux distributions — Red Hat Enterprise Linux and SUSE Linux Enterprise Server. We learned of this when MySQL declined to sell us support for some new Debian-based servers. Our sales rep 'found out from engineering that the current Enterprise offering is no longer supported on Debian OS.' We were told that 'Generic Linux' in MySQL's list of supported platforms means 'generic versions of the implementations listed above'; not support for Linux in general." Update: 12/13 20:52 GMT by J : MySQL AB's Director of Architecture (and former Slash programmer) Brian Aker corrects an apparent miscommunication in a blog post: "we are just starting to roll out [Enterprise] binaries... We don't build binaries for Debian in part because the Debian community does a good job themselves... If you call MySQL and you have support we support you if you are running Debian (the same with Suse, RHEL, Fedora, Ubuntu and others)... someone in Sales was left with the wrong information"
MySQL (the database) still works with Debian, but MySQL (the support company) no longer sells support for Debian.
Loudly drop support for MySQL. Here are two excellent alternatives:
PostgreSQL
Firebird
Still, Debian provides good MySQL packages. Use them instead. If you need support, I'm sure you could find someone to provide it for you.
"It ain't a war against drugs.it's a war against personal freedom" --Bill Hicks
MySQL only lets me spoon it.
But Postgre lets me fork it all night long.
I see that a definite split of "Premium Linux" vs. "Unsupported Linux" is coming soon to a vendor near you. That doesn't mean that Linux will die, it's just going to smell funny (possibly like pee).
-"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
I see there's already a few comments that the code should be forked. The thing is, what is forking going to do for it? They are dropping support for Linux distros, but that's not saying it won't run on other distros, just that it's not supported. The only way a fork would do anything is if the forked version had it's own support as well.
> I don't know that you would make any money, but at least you'd be offering something that isn't currently offered.
I doubt it. And more important than my opinion, MySQL doubts it and has the sales figures to show it. Companies don't normally kill off profitable products and services, not even evil/stupid corporations.
Democrat delenda est
...or switch to the excellent Postgres which is more open and a more complete SQL implementation than MySQL anyway.
Expect to see more things like this happening as the IT landscape undergoes it's coming changes.
Mmm fork MySQL? Why? There is nothing wrong with the code. You could try to fork the support and start a company specialized in MySQL support on Debian.....
:-) Anyone in? ;-)
I think there is a market for this. The only thing you need is a couple of good people. You/we(the community) could also create a company GPL style. Create a pool of people willing to devote there time on solving MySQL Debian support problems. Create a ticket like system and assign questions to people in the pool.
This way you can quickly create a non-profit company with little to non investments. The biggest "problem" is that you have to attract people willing to become part of you expert pool.
While writing this, it might even be a good challenge to start this..... I will think some more about this.
Regards,
Johan Louwers.
Regards, Johan Louwers.
I doubt that's the point. I'm sure they just decided that rom a cost/benefit perspective, money spent training their support staff on Debian wasn't worth the amount of business they were getting from Debian customers. Which makes a lot of sense to me - in my experience, people that run Debian servers have a more thorough knowledge of the system and administering it, and consequently have less need/desire for software support (yourself included, it sounds like). And assuming that's true, it's also not much of a stretch to assume that someone that interested in the guts of a system would choose something like Postgres over MySQL anyways if they had a choice, since it's had more advanced features for much longer than MySQL has.
The "who do you sue" line's as old as the hills and, largely speaking, irrelevant because you're never
going to get to first base unless it's a screw-up of epic proportions. Even then, it's more likely to
be a colossal waste of your time and merely an exercise of fattening your lawyer's wallet.
I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
For example, when I was a kid a local pizza delivery chain started delivering breakfast pizzas. They made money hand over fist. But after a few months, the calculated that the additional cost of maintaining a third shift of workers and an expanded breakfast menu would bring in more money if put into opening additiona stores serving the traditional lunch, dinner, late night crowd with the normal pizzaria menu.
Most likely what is happening is that the MySQL corporation finds that if it spends the same number of dollars training a support tech, those dollars bring in more money if the tech is dedicated to Redhat and/or SuSE than if the tech is also trained on Debian. This doesn't mean that there is no market for Debian support. It means only that MySQL has a higher relative profit from supporting just two databases. The calculation may be different for another company that has a different resource pool. For example a company that already supports Debian Linux, may have a very low marginal cost for adding MySQL on Debian support and, consequently, have a far higher ROI for supporting MySQL on Debian.
Only in WoW...
Yes, I know, there goes my Karma.