From MySQL Quietly Drops Support For Debian Linux:

MySQL now supports only two Linux distributions -- Red Hat Enterprise Linux and SUSE Linux Enterprise Server.

Read between lines: MySQL had given up on vanilla Linux kernel and all its pesky VM bugs.

Well, at least that was my experience of MySQL on vanilla kernel: trying to rebuild index for table of size several times bigger than RAM brings system completely down. Though miraculously it did worked ok when booted into RH shipped kernel. Go figure.

Edit1. Well Okay they clarified the issue. There is no problems of supporting MySQL on other Linux system. Mea culpa for not waiting for official news.

Interesting C|Net piece How GPL fits in with the future of antitrust regulation about case which wanted to challenge GPL on anti-trust grounds. Quotes:

The plaintiff in the case, Daniel Wallace, has wanted to compete with Linux by offering a derivative work or by writing an operating system from the ground up. He argued that he has been barred from doing so, while Linux and its derivatives can be obtained at no charge. He asserted that IBM, Red Hat and Novell have conspired to eliminate competition in the operating-system market by making Linux available at an "unbeatable" price: free.

The court found Wallace's theory to be "faulty substantively." The decision pointed out that "the goal of antitrust law is to use rivalry to keep prices low for consumers' benefit." Here, the court concluded that Wallace sought to employ "antitrust law to drive prices up," which would "turn (antitrust law) on its head."

Common sense prevailed.

OpenDocument Fellowship has done some interoperability testing. Sadly, no ODF suit/application has as of yet received "5 out of 5 stars" conformance/interoperability mark.

KOffice and OO.o are noted as having problems with each other documents - specifically images. Or to put it bluntly, goal of interoperability is more than just far away. But at moment it is clear that price is major driving force behind the office suits so interoperability apparently had been lowered to second priority.

I wonder how would OASIS.org handle interoperability of ODF suits in future. Apparently interoperability with M$Office is still higher in list of OO.o priorities - compared to fellow ODF suits / standalone applications.

P.S.

Slashdot is powered by your submissions, so send in your scoop

No scoops, just botherdom of real world.

I recently tried to make simple QuickRef document for GNU/Arch. QuickRef in theory is simple document which encompass list of often used commands of specific tool. I wanted to create such one in ODT using OpenOffice.org 2.0 under (sorry) Windows.

It's all started Okay. But after typing few lines, I got tired of OO.o2 bug: one-two minute freezE when opening fonts dialog (It happens sometime when you have several documents open in OO.o for long period of time.)

I bravely decided that KOffice 1.5 would do better job, so I fired up VMware Player (we are not allowed to have Linux in office - free VMware is Ok) with Debian. First problem appeared - fonts. Windows and Linux do not have same fonts. Document with Times New Roman and Courier New looked ugly, until I replaced M$Windows fonts with native Linux ones - Bitstream Serif/Sans/Mono.

Then second problem surfaced: KOffice 1.5 apparently doesn't support character styles, but only paragraph styles. I used such style in comments intermixed in meta-code I were adding to QuickRef.

Okay. KOffice is really more pleasant to work with, compared to OO.o1/2. And bit later job was done. Now I was going to enjoy the results. "Print" > "Print to PDF" ... Oops. That looks ugly. Apparently GhostScript didn't like fonts I have used and all labels in PDFed QuickRef were misrendered: readable, but ugly. Nevermind - let's try another fonts. No luck: the same ugly result.

Okay. Nevermind. Let's bring my QuickRef back to Windows and OO.o2 - if it's inconvenient to edit document, printing/exporting framework of OO.o is definitely more stable compared to KOffice one.

FTP, copy document, fire up OO.o2 ... Holy crap. Fonts - OO.o seems used some randomization algorithm picking font substitution. Font sizes - some paragraphs or parts of them displayed with font size two times (or so) smaller than standard (and no apparent problem is visible in paragraph style dialog - all sizes globally set to 11pt, reapplying style didn't help). Italic I have used for comments got partially removed... Needless to say that next-to-perfect PDF export function of OO.o have produced exact replica of the ugly mess I have had on screen.

No matter how raw and unstable KOffice 1.x, OO.o2 dumbly breaks on document created in alternative application. The only way I have come up to fix the observed in OO.o weirdnesses - reimport thru plain text file (select all, copy to notepad, reselect in notepad and then back from notepad into OO.o) what is bogus. Does anybody ever tested OO.o with ODF generated by other tools, me wonders.

I wonder if I am only one who is trying interoperability of ODF suits. Have anybody else tryed to move ODF documents around between ODF capable suits (OO.o and KOffice are the only I know and have) with positive results? Moving documents from Windows to Linux and back?

Recently bought Nintendo DS Lite - just for fun and distraction from my usual heavy duty Unix programming. Two games we purchased: Tetris DS and Mario Carts DS.

I spent about 0.00 hours installing/updating Windows. I spent less than 0.00 hours installing fresh nVidia drivers. DS doesn't support (nor requires for proper functioning) apt-get, what was bit disappointing. ;)

And guess what? Regardless device is working great: plug cartridge, press 'A' key and here you go. I wish someday PeeCee software would reach that level of usability.

Games are fun. Tetris is real official Tetris (since that [bad guy] Pajitnov sold the Tetris game invented by his colleague to Nintendo) and well made. Carts are fun too: all tracks are made so that most of the races are about 3 minutes long - precisely time I need to make a break hacking sockets and pipes.

Overall, I'm impressed. It was hard to imagine that the appliance (which sadly doesn't run Linux) could be that well made and provide only good experience.

I think Nintendo might have sold much more of them, be they priced here in Europe more sanely. 140€ for DS Lite and 20-40€ per game is bit too much for something targeted at kids. Many games are rated "3+" - but I wonder how much parents would even think about spending that much for toy for their 3+ kids.

Acceptance without proof is the fundamental characteristic of Western religion, rejection without proof is the fundamental characteristic of Western science.

-- Gary Zukav

P.S.

Reporter: What do you think of western civilization?
Mahatma Gandhi: I think it would be a good idea.

Solution to a problem I was bugged for more than two weeks since I have updated myself to Debian/testsing/unstable and got VIM7.

It's of course shame that such a good editor starts brining in such useless features. I do not try to oppose bells'n'whistles per se. But enabling such feature in editor designed for professionals is I think very stupid.

That particular feature does distract my eyes forcing them to move needlessly all the time I work on source code of my programs. What make the situation worse, is that the feature is plug-in - in other words you have very very very narrow chances of finding documentation for it. Especially since you do not know the name of that feature nor plug-in implementing it.

I can only hope that the single feature doesn't indicate a trend in VIM's development - trend in bringing useless distracting bells'n'whistles which made Emacs unusable and unconfigurable. Unusable, because reaction of Emacs on users actions is pretty random and unpredictable. Unconfigurable, since nobody really knows names of all Emacs options, nor the module they are provided by. And nobody knows the level of nesting of its pluggable modes.

Started blog trying to document parts of my vimrc - vimrc-dissection

The move was spured by another crashed hard drive and need to rebuild vimrc from scratch. Finding all clues in vim's help takes too much time. Backing up config is for whinnies. Heroes aren't looking for easy ways.

P.S. Actually, that's test of journal.