Skip to main content

Some good damage control from MySQL AB re SCOX

Pamela Jones interviews Marten Mickos from MySQL AB. The summary:

  • no money went to SCO from MySQL, so MySQL is not supporting SCO financially [hoorah!]
  • it was SCO seeking out the partnership, not the other way around [big surprise there, not]
  • MySQL had stopped supporting SCO in 2004 [see comment below]
  • MySQL did not put out the press release about the partnership. [good, but again no surprise] Mickos did provide a quotation for the press release however. [something you could hardly avoid]

This comment by Mike Kruckenberg in April 2004 (referenced in the GrokLaw article) is interesting:

SCO Unixware support is being stopped.

If anyone knows:

  • What about OpenServer?
  • What is the practical difference between “support” for SCOX OSes and “partnership”?

Call me inconsistent if you will, but stopping support for UnixWare (unless MySQL was running out of UW customers) is inconsistent with embracing a partnership with SCOX.

SCOX certainly haven’t changed, except that a few of their stupider claims have bounced off the Courts, crashing and burning before even coming to trial. And why stop support for UW but not OpenServer? Now OS uses what amounts to a UW kernel, so I suppose that the remaining differences are hardly radical, but if MySQL stopped support on moral grounds, why resume it again while the moral issue remains in full force? This confuses me.

Marten said:

I can tell you that the deal produces revenue to us.

And what do we do with revenue? We hire developers who produce GPL code.

Good. But the money is tainted. It’s almost akin to taking drug money to support a school. Likewise:

As a company, we do not have a position on other companies’ strategies.

Taken as a general comment devoid of context, fine, but Marten’s talking about a company he’s ”partnered” with. Quite a different kettle of fish. The “partnership” makes SCOX’s strategies MySQL AB’s problem. Pilate washing his hands? I think considerably more distancing is required than we’ve so far seen.

In summary, MySQL have scored some good points with me and I think improved their conceptual position, but there’s still some major stuff in there not making sense. We await further revelations with the usual ’bated breath.

Comments

Popular posts from this blog

new life for an old (FTX) PSU, improved life for one human

the LEDs on this 5m strip happen to emit light centred on a red that does unexpectedly helpful things to (and surprisingly deeply within) a human routinely exposed to it. it has been soldered to a Molex connector, plugged into a TFX power supply from a (retired: the MoBo is cactus) Small Form Factor PC, the assorted PSU connectors (and loose end from the strip) have been taped over. the LED strip cost $10.24 including postage, the rest cost $0, the PSU is running at 12½% of capacity, consumes less power than a laptop plug-pack despite running a fan. trial runs begin today.

every-application-is-part-of-a-toolkit at work

I have a LibreOffice Impress slideshow that I wish to turn into a narrated video. 1. export the slideshow as PNG images (if that is partially broken — as at now — at higher resolutions, Export Directly as PDF then use ‘pdftoppm’ (from the poppler-utils package) to do the same). 2. write a small C program (63 lines including comments) to display those images one at a time, writing a config file entry for Imagination (default transition: ‘cross fade’) based on when the image-viewer application (‘display,’ from the GraphicsMagick suite) is closed on each one; run that, read each image aloud, then close each image in turn. 3. run ‘Imagination’ over the config file to produce a silent MP4 video with the correct timings. 4. run ‘Audacity’ to record speech while using ‘SMPlayer’ to display the silent video, then export that recording as a WAV file. 4a. optionally, use ‘TiMIDIty’ to convert a non-copyright-encumbered MIDI tune to WAV, then import that and blend it with the speech (as a quiet b...

boundaries

pushing the actual boundaries of the physical (not extremes, the boundaries themselves) can often remove barriers not otherwise perceived. one can then often resolve an issue itself, rather than merely stonewalling at the physical consequences of the issue.