August 5, 2009
A few weeks ago I wrote a post about an acquaintance that had been given some very strange legal advice from a Sun sales rep. It generated a lot of interest, from both people inside Sun and those outside. Here’s what I have learned since:
1). Many people think that keeping your sources’ identities private makes the resulting information lies or FUD. They should talk to Woodward and Bernstein.
2). Many people cannot interpret a question mark at the end of a sentence. I was not making an indictment with my previous post, I was asking a question.
3). Most Sun employees do not make mistakes 1 and 2.
The third point is what prompts this post. Thanks to some concerned people inside Sun, the person who received the bad information now has a clear line of communication to get it resolved. I hope they do so.
Also, Sun has asked that anyone that feels that they have been given bad advice by a Sun sales representative contact a sales manager to get the straight dope. You can find a list of worldwide contacts on Sun’s worldwide MySQL sales team page.
Sun employees have also assured me that the sales rep mentioned in my previous post was incorrect, and was giving advice contrary to Sun’s policy. It seems clear that some re-training or better training is in order. I hope Sun takes this opportunity to better educate their sales staff.
August 5, 2009
My name is Kurt, and I’m a SELECTaholic … wait … wrong place. Strike that.
Thanks very much to Dups and Bryan Alsdorf for getting this all sorted.
July 6, 2009
As The Clash reminded us, Know Your Rights!
A good friend whom I trust implicitly recently told me of a disturbing conversation that had taken place between a DBA acquaintance friend of his and a Sun sales engineer. Disturbing enough that it prompts me to remind everyone what your rights and obligations are when you use the community edition of MySQL that is licensed under the GPLv2.
Apparently, this friend of a friend needed some performance tuning done on a MySQL Community Edition installation that spans several servers, and serves up their proprietary, commercial web application. They contacted Sun in order to see about getting some work done on a contractual basis. In other words, they wanted to pay Sun for performance tuning.
They were then contacted by a Sun sales engineer who, upon hearing they have multiple servers running the Community Edition of MySQL serving up a proprietary web app, told them:
1). They were in violation of the license.
2). They would need to release their proprietary app under the GPL, since it uses MySQL client libraries.
3). They could avoid having to GPL their application by paying Sun licensing fees for every server.
Now, I’m not a lawyer. But, in my legally uneducated but GPL-savvy opinion, there is a simple term for this. It’s extortion. “Pay us, or we’ll make sure you have to GPL your proprietary work.” If someone admitted to the bar in any US state wants to correct my opinion that this is extortion, chime in. I may be confusing terms.
However, I am not confused about the rights and obligations granted and ensured by the GPL. Let me cast some light into the darkness created by this Sun salesman.
First, this company uses the Community Edition of MySQL. Therefore, they are bound by the terms of the GPL, and NO other license, be it from Sun or elsewhere. Full stop. Sun can have whatever convoluted license they please for MySQL Enterprise, but if you use the Community Edition you are bound solely by the GPL.
The GPL ensures that anyone that releases code that touches GPL code must also use the GPL. The key word here is “releases.” Let’s give two examples.
First, Linksys recently settled a lawsuit brought against them by the Software Freedom Law Center. They use Linux kernel code in some of their router firmware, and had not released the source code to that firmware. Why did they have to? Because the firmware shipped to end users. They released code to the public in binary form that touches the GPL Linux kernel. Thus, they need to GPL their firmware.
Second, it’s no secret that Google uses MySQL extensively. So why aren’t GMail, Google Reader, Google News, or other such services released to the public under the GPL? It’s simple. They aren’t released at all! These are proprietary applications that are not released in either binary or source form. If your code touches GPL code, but you don’t release your code in binary or source form, you do not have to use the GPL for your code, nor do you run afoul of the GPL itself.
So, let’s go over the three points the Sun sales engineer made above.
1). They were not in violation of the license of the Community Edition MySQL server software they were using. To imply differently is at best misinformed, and at worst FUD.
2). They don’t have to release their code at all! Now, if they do decide to release their code, because it touches the MySQL client libraries they will have to use the GPL. But if they keep it a closed-source, proprietary, commerical app, with no public releases, they are well within their rights. Their application, developed in-house and run as a service on top of the MySQL Community Edition, is not released to the public in any form. Therefore, they do not have to use the GPL with their application or service, nor do they have to acquire commercial licenses from Sun. End of story.
3). They wanted to pay Sun for performance tuning. Sun decided to go for a bigger paycheck. In the end, Sun probably will not get a dime. Smart. Really, really smart. Glad I don’t own stock.
If Sun contacts you or someone you know and begins talking about license violations, read this post again carefully. Know your rights. And if you’re not sure, contact the Software Freedom Law Center. Or contact us at Monty Program; our staff was responsible for putting MySQL under the GPL. We know the terrain better than Sun.
If you have had a similar experience, I’d sure like to know about it. I’m curious as to how widespread this “tactic” is, and how people are responding to it and dealing with it. Let me know via comments.
And while we’re at it, if you need MySQL or MariaDB performance tuning, why contact a company that instead of seeing an opportunity to make a client happy while earning money instead sees an opportunity to extort money from a heretofore satisfied user? Contact the Open Database Alliance. We have people that can get the job done, and that don’t care about your licensing.
May 27, 2009
The OpenBSD hackers are writing their own SMTPD. Anyone that says “what an absolute waste of time” has:
1). Never run Sendmail.
2). Doesn’t care if their SMTPD is not GPL-compatible (Postfix ain’t).
3). Too much free time and not enough experience.
I’m psyched for this. I’d love to see an SMTPD that
1). Has configuration files that need not be treated as binaries.
2). Is resource-friendly.
3). Is sysadmin-friendly.
4). Is secure.
In my experience, the OpenBSD crowd is among the most likely subset of Free Software and open source hackers able and willing to deliver on this wishlist.
Make me happy, guys!
May 13, 2009
Today we at Monty Program Ab and our dear friends at Percona announced the Open Database Alliance. Click the name for the full press release.
If you are a MySQL hacker, user, documentation writer, or just an interested bystander, we’re ensuring the database software you have come to know and love, and with which you (quite rightly) feel a sense of shared ownership, stays Free and open. Not only are we going to keep the same development and participation model with which you are familiar, but we are going to open the project even wider. Got patches? We want them! Got questions, comments, or other issues? We want to hear them, and we will respond in meaningful ways! Got production deployments of MySQL? We will keep you up and running without labyrinthine licensing and high expense! We’re lowering the bar for participation and raising the bar for what a Free and open database can do.
And the point of the Alliance is that we’re not doing it alone. The MySQL ecosystem has a large number of stakeholders, and we want them all to consider the value in being part of a community of like-minded individuals and organizations. The Alliance is here to ensure that your transition to MariaDB is painless, and offers you a more robust and healthy world of code.
We’re just getting started with the Open Database Alliance. If you have built a business or beloved hobby on MySQL, I encourage you to contact us and join the Alliance. We’re here for you if you’re here with us.
Think positively. With the Oracle acquisition of Sun, doors may close. But we have just removed a wall from the side of the house. In Free and open source software, doors are for chumps.
May 9, 2009
The days of asking people to dial a phone number by associating letters in your nifty, branded phone number (I’m looking at you, Key Bank and Compass Bank) to digits on my telephone keypad are over. Why? I have a Blackberry Curve. Here’s my keypad:
My wife has the Blackberry Pearl. Here’s her keyboard:
Asking me to dial 1-800-KEY2YOU or 1-800-COMPASS without giving me the actual digits basically shows your entire marketing team thinks this is the 1950s, and all telephone handsets look and behave exactly alike.
In our home, we only have cell phones. The only POTS phones we own are packed in a box in the garage. I could look up an old-fashioned telephone keypad with a Google image search, but … seriously? And what if I’m in my car? Pull over and find a pay telephone so that I can figure out what number to dial? Ridiculous.
Wake up, suits!
April 19, 2009
Seen the movie? Very funny fiction about the Vermont State Police.
So a week or so ago I was pulled over on I-89 in northern Vermont for speeding. The officer exhibited behavior and judgment so poor and so unprofessional I will not sully the reputation of his peers by discussing it here. I have raised my concerns with his supervisor.
However, that does not negate the fact I was, indeed, traveling at a rate of speed higher than the posted speed limit. So I’ll pay the ticket. And when I went to do so, I noticed that “You can now pay your tickets online at the VT Judiciary Branch website.” Click the URL for some head-scratchin’ fun!
I’m aghast. WTF are they smoking in Vermont?
April 18, 2009
Big events today, and the MySQL User Conference is all abuzz with news, speculation, and even some concern. Oracle has acquired Sun, which again brings the light of Apollo to Mount Parnassus.
Of course, this raises all kinds of questions about the whys and hows. I’m happy to publicly speculate, as I am not in an insider’s position with either Sun or Oracle. Of course, I do work for Monty Program Ab, which makes me somewhat less than a wholly dispassionate bystander. And please, before you read my humble musings on the subject, please read my boss’ thoughts.
Without further ado, here some possible reasons I can see for this move by Oracle:
- Oracle now has a hardware business, something I think they have craved for a very long time.
- Oracle now has their very own trusted server operating system. Not to disparage what must have been some very hard work, but Oracle’s Linux platform has been and will be an also-ran. I predict that Solaris as a commercial product will soon disappear, and that Oracle will concentrate their efforts on OpenSolaris. I think Oracle wants an operating system, but I (perhaps naively) believe they see the folly in closed, commercial OSes in 2009.
- And of course, MySQL. I think it almost certain that we will begin to see MySQL used as a sort of “gateway drug” to Oracle’s flagship DB products.
Of course, this begs the question “Why would Oracle continue to pay attention to and improve a product that is solely used as a carrot to their flagship product?”
I’m not quite sure I know the answer to this. However, I do know that it is nigh impossible to “own” a Free or open source project in the same sense that Oracle “owns” their database. Patrick Galbraith spoke to this point quite eloquently in a recent blog post. I think Monty paraphrased it perfectly when he said “that ‘ownership’ of Free and open source projects has more to do with who provides the best stewardship of the code, rather than who owns a trademark.” Amen, brother.
That having been said, I hope Oracle realizes that they have taken their first big step into the Free and open source software world with their acquisition of Sun. Their track record in this field is non-existent, as they have traditionally been quite opposed to the ideals and values that make Free and open source software viable. They now stand at a crossroads. They can continue to play the closed, proprietary, commercial game they have been playing (quite successfully, mind you) for many years. However, if they do this, they almost guarantee the success of competitors (including Monty Program Ab). I cannot say I’m opposed to this, but it decreases users’ choice, and this is never good.
Alternatively, Oracle could choose to engage and interact with the open source community in ways that Sun never did (e.g. viewing each developer with meaningful patches as a full partner in their success). Should they choose this route, I have every confidence that they will succeed where Sun did not.
When Sun was the principle owner of MySQL, Monty liked to think of Monty Program and the Maria Project as the MySQL Fedora to Sun’s RHEL. Now that Oracle is in charge, I see three possibilities:
1). The Maria Project continues to be the MySQL Fedora to Oracle’s RHEL.
2). Oracle completely fails to understand the open model and Maria becomes the Linux to Oracle’s Windows.
3). Oracle really and truly understands the landscape in which they now live, and the Maria Project becomes the Ubuntu to Oracle’s Debian.
As I said, there is palpable concern amongst the conference attendees. I think there are some easy tasks Oracle could undertake to alleviate these concerns to some degree. I’ll post my ideas in the next few days, once I’ve a a bit more time to process today’s events.
Fasten your seatbelts and return your tray table and seat back to their upright and locked positions.
February 13, 2009
HMS (His Mark Shuttleworth’s-ness) Ubuntu
Ship’s Log: February 2009
At six bells on the evening on February 6, HMS Ubuntu encountered the Monty, a vessel of Finnish registry transporting forked code to Open Source markets.
Per standing orders of Admiral Shuttleworth, the craft was hailed to determine her intentions. Monty‘s captain, an affable Finn named Widenius, satisfied the deck watch through semaphore that she was a craft in the Free Software armada, and was brought alongside.
Captain Widenius expressed interest in Ubuntu’s detachment of Marines, as their performance in both the user and paid support customer theaters is well known; having served with distinction through the recent Dell Campaigns. Widenius asked that Lieutenant von Finck be released from service aboard the Ubuntu to provide ground command services to the Monty, its crew of developers, and its users in port.
Admiral Shuttleworth having been consulted, the Lieutenant was re-assigned, and will begin organizing campaigns once the Monty and her code reaches safe harbor.
Lieutenant von Finck is hereby released from active duty aboard HMS Ubuntu and commended by his superiors to the service of the Monty.
Admiral Shuttleworth has expressed interest in completing the crew exchange expeditiously, as he plans to continue the hunt for the white whale.
So … yeah. I’m leaving Canonical and joining my friend Monty organizing the developer and user communities around the new Maria storage engine. My last day will be February 27.
I’m still in Free Software. I still use Ubuntu. I’m still an Ubuntu member, and plan to keep doing what small part I can to help. I’m not really going too far. Sorry ’bout that.
November 11, 2008
Excuse the long title, but I want to make sure search engines get this one.
So, you bought a swell new Dell Mini 9 with Ubuntu, ran through the first-boot account configurator, and promptly forgot your password? You’re not alone. Resetting it is done the standard way from a recovery mode kernel boot, albeit with a quirk. Here are the steps.
1). You’ll need your username. If you have auto-login enabled, open a Terminal (Applications > Accessories) and type
whoami and that’s your username.
2). Reboot. When the Dell logo appears, begin tapping
[Esc]. Continue tapping until the boot process stops, displaying a
MBR 2FA: prompt.
3). The boot process is now halted. The GRUB bootloader has a 0-second timeout before booting, so sit quietly, prepare yourself, and reach out with your feelings and dominant Jedi hand and …
[Enter] and then
[Esc] as quickly as possible. Note the “and then.” You must press one, then the other, not both at the same time. And you must be fast.
5). If successful, padawan, you will have a GRUB boot menu. Using the arrow keys, choose recovery mode. Press
[Enter] to boot.
6). At the resulting prompt, type
passwd $USERNAME (replace $USERNAME with your actual username). You’ll be asked to type a new password twice, and nothing will be displayed on-screen as you do.
reboot and press
[Enter]. The job is done.
No one endorses this procedure as actual Jedi training, and machines used for such may lose
[Enter] key functionality as a result. Please only use this mind/hand exercise to reset your password.
« Previous Entries Next Entries »