The groklaw review of the issues is rather good (IMHO) and is as balanced as I think you will get on this issue.
Lest we forget there are a number of forks, special patch sets and even a Monty specific version out there for people to use (http://lwn.net/Articles/329626/). I use or have used Oracle, BerkeleyDB (formerly sleepycat), MySQL and PostgreSQL not to mention being forced to use MS SQL/Jet/Horror in some cases. The only threat I have seen/heard with MySQL getting acquired (by Sun no less) was that the documentation is not fully GPL'd. As far as I know either that rumor was false or has been addressed by Sun in which case everything is forked. Ironically, keeping the dual licensing means more vendors who bundle MySQL have the opportunity to use it with less license hassle. - Brian On Dec 14, 2009, at 1:25 PM, Ragi Y. Burhum wrote: > Oops, wrong link below: > > On Mon, Dec 14, 2009 at 12:55 PM, Ragi Y. Burhum <r...@burhum.com> wrote: > Monty's call for help: > http://monty-says.blogspot.com/2009/12/help-saving-mysql.html > > > A different take - one I agree more with (with a few exceptions) > > Replace this: > http://bit.ly/3nrfH9 > > > Withis this: > > http://www.groklaw.net/article.php?story=20091021164738392 > > Honestly, I am biased since I am strong PostgreSQL proponent. > > What do you guys think? > > > :) > _______________________________________________ > LinuxUsers mailing list > LinuxUsers@socallinux.org > http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
_______________________________________________ LinuxUsers mailing list LinuxUsers@socallinux.org http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
