Last week I had announced in the LXer forums that I would be a contributing author to Linux Advocates. That was followed by a post on the site announcing that I would be joining their team. I was honestly excited about this. I felt that writing for Linux Advocates would add credibility to my stories and bring me back some of the wider audience I had when I wrote for O'Reilly Media. The additional exposure would help me market my consulting business which brings Linux and FOSS solutions to businesses and organizations looking to reduce IT costs and enhance the reliability, stability and security of their IT infrastructure.
Today it became clear that I wouldn't be writing for Linux Advocates after all. I've learned a lot in the past week and I've come to the conclusion that this is for the best.
First, a number of prominent writers and developers in the Linux community tried to get me to reconsider. The big issue for them was what they saw as heavy handed moderation by Dietrich Schmitz, including banning a number of them from the site entirely. I've argued that website owners have the right to moderate and control the content on their sites. I've made clear that such editorial control is most definitely not censorship as some have claimed. The dispute between Mr. Schmitz and those who felt they were unfairly treated, including several former Linux Advocates writers, spilled over into five different threads in the LXer forums and several Google+ pages and included a great deal of rather heated language.
After reading all the comments back and forth I decided to go ahead as planned and I began an article on systemd to be published as my first post for Linux Advocates. Unfortunately little things like earning a living plus one day where I was a bit under the weather got in the way of my finishing the article until today. Following instructions sent to me by Mr. Schmitz I added myself as a contributor to the site. So far, so good.
Only then did I really read and digest everything else Mr. Schmitz wanted me to do, like setup an account in his personal domain so that I could have a Linux Advocates e-mail address. He also wanted me to install a Zemanta plugin for Chrome. I have deliberately chosen not to use Chrome (an article about that soon) and wasn't happy about that at all. I went to install the Zemanta plugin for Firefox instead and was presented with a Microsoft-style End User License Agreement (EULA). As many in the open source community would expect, that set off all sorts of red flags for me.
In the seven years since my identity was stolen and used for criminal purposes I've become increasingly paranoid about data security. I already feel I've left way too much information about myself out on the net. I'm very concerned about what companies like Google, Facebook and Microsoft do when they collect data about me. I'm very concerned about who they might sell or give that data to. Suddenly, I found myself reading a license agreement for a proprietary piece of software that explicitly had terms relating to collecting and retaining data.
I felt deeply uncomfortable and didn't go through with the installation. It's one thing to be forced to use proprietary software to service a client or do work required by an employer. It's quite another for someone who is getting my labor at no cost and benefiting from it to demand I install something on my own system. I first asked if Zemanta was mandatory and then wrote a follow-up e-mail making clear that I wasn't about to install it.
Mr. Schmitz' response was direct and to the point. If I can't accommodate how he chooses to run his site then I should go elsewhere. Once again, he was getting writing from me on a voluntary basis on a website were he is currently begging for money to make ends meet. This is a Linux advocacy site. You'd think he'd be the one to accommodate an aversion to proprietary tools that aren't in any way necessary for him to publish my writing. I guess not.
So.. no, sorry, Mr. Schmitz, I won't be accommodating you. I'll find ways to bring traffic to my blog which don't require sacrificing my security, privacy or principles. I still have other outlets who would like me to write for them as well. I wish Dietrich Schmitz all the best with his website. I just won't be a part of it.
Friday, May 24, 2013
Friday, May 17, 2013
Linux, Standards and the Enterprise: Why Red Hat Enterprise Linux Remains the Best Choice
Dietrich Schmitz, writing for the Linux Advocates website, posted an article yesterday about how Red Hat's adherence to the Linux Standards Base (LSB) guarantees stability and reduces costs in the enterprise. While I agree with Mr. Schmitz wholeheartedly, from my perspective the reasons by Red Hat Enterprise Linux remains both the leader and the best choice in business, government and non-profit spaces goes far beyond the LSB.
I've been a professional UNIX/Linux systems administrator for 18 years now. I've had to implement, maintain and support servers from all of the enterprise distributions and a few distributions not generally used in the enterprise as well for my employers and customers over the years. I'm a big advocate for Red Hat and the various free clones (CentOS, Scientific Linux and Springdale Linux) as the best solution for most organizations. First, it's exceptionally stable as Mr. Schmitz points out. Second, it offers the longest support period at 10 years. Third, they have excellent and professional support.* Fourth, they do the best job at insuring compatibility with both FOSS and commercial apps during the full 10 year release cycle.
My big issue with SUSE Linux Enterprise (SLES/SLED) is that they do push major version changes of the kernel, tool chain and apps in what they euphemistically call Service Packs. The Service Packs are actually major releases recently and have been known to cause major breakage and pain. My experience with their support organization here in the U.S. has been less than satisfactory, particularly the time needed to respond to and resolve issues.
Canonical (Ubuntu) has much shorter support periods than either Red Hat or SUSE. They also don't backport additional hardware support or patches into their kernel, forcing you to either do the SUSE style update gamble even more frequently than with SUSE or else to run without needed support and/or vulnerabilities.
The free clones of Red Hat Enterprise Linux I mentioned earlier are not permitted to name their source, referring merely to "the upstream provider," but pretty much everyone in the Linux community knows precisely what they mean. They represent a real advantage to Red Hat (the distribution if not the business) in that they allow businesses to try before they buy. They provide the opportunity to run a test bed or non-critical system at reduced cost. The clones also allow non-profits and cash strapped small businesses to forgo commercial support, at least for a time, and still use software that is entirely compatible with the leading enterprise Linux distribution. As organizations grow and their needs change converting a server or workstation running a clone to a genuine, supported Red Hat system is a simple process.
Finally, I'm sure fans of Debian and Slackware packaging will disagree with me, but keeping to standards, specifically the LSB, also goes a long way to insure application compatibility. I think it's vital that all enterprise distros follow standards.
*= Disclaimer: I was part of the support team for seven months as a consultant in 2005. I no longer am affiliated with Red Hat in any way, shape or form. [NOTE: This article originally appeared as a comment on LXer.com in abbreviated form.]
I've been a professional UNIX/Linux systems administrator for 18 years now. I've had to implement, maintain and support servers from all of the enterprise distributions and a few distributions not generally used in the enterprise as well for my employers and customers over the years. I'm a big advocate for Red Hat and the various free clones (CentOS, Scientific Linux and Springdale Linux) as the best solution for most organizations. First, it's exceptionally stable as Mr. Schmitz points out. Second, it offers the longest support period at 10 years. Third, they have excellent and professional support.* Fourth, they do the best job at insuring compatibility with both FOSS and commercial apps during the full 10 year release cycle.
My big issue with SUSE Linux Enterprise (SLES/SLED) is that they do push major version changes of the kernel, tool chain and apps in what they euphemistically call Service Packs. The Service Packs are actually major releases recently and have been known to cause major breakage and pain. My experience with their support organization here in the U.S. has been less than satisfactory, particularly the time needed to respond to and resolve issues.
Canonical (Ubuntu) has much shorter support periods than either Red Hat or SUSE. They also don't backport additional hardware support or patches into their kernel, forcing you to either do the SUSE style update gamble even more frequently than with SUSE or else to run without needed support and/or vulnerabilities.
The free clones of Red Hat Enterprise Linux I mentioned earlier are not permitted to name their source, referring merely to "the upstream provider," but pretty much everyone in the Linux community knows precisely what they mean. They represent a real advantage to Red Hat (the distribution if not the business) in that they allow businesses to try before they buy. They provide the opportunity to run a test bed or non-critical system at reduced cost. The clones also allow non-profits and cash strapped small businesses to forgo commercial support, at least for a time, and still use software that is entirely compatible with the leading enterprise Linux distribution. As organizations grow and their needs change converting a server or workstation running a clone to a genuine, supported Red Hat system is a simple process.
Finally, I'm sure fans of Debian and Slackware packaging will disagree with me, but keeping to standards, specifically the LSB, also goes a long way to insure application compatibility. I think it's vital that all enterprise distros follow standards.
*= Disclaimer: I was part of the support team for seven months as a consultant in 2005. I no longer am affiliated with Red Hat in any way, shape or form. [NOTE: This article originally appeared as a comment on LXer.com in abbreviated form.]
Subscribe to:
Posts (Atom)