Linux Beat Project Monterey to IA-64 by 8 months

One of the things that SCO keeps bringing up is how IBM did nasty things to them on Project Monterey. Thing is that Linux actually ran on one of the target architectures of Project Monterey, Intel’s Itanium (aka Merced, IA-64), 8 months prior to Monterey and the people who did this were not IBM, but HP!

When Monterey first booted on IA-64 in September 1999 HP
had already
had the
Linux kernel running in native 64-bit mode on the platform
according to this
technical report from HP
, (direct link to PDF here).

There is also a paper
(PDF here)
& slides
(PDF here)
that David Mosberger from HP presented at Linux Expo ’99
documenting their work that includes a
very
interesting timeline
that shows that they first got the
kernel to successfully boot and run Hello World on the 20th
January 1999, and they had that with CERNs glibc for IA64
running by the 9th April 1999.

So, if Linux was running on IA-64 8 months *before*
Monterey, could
we claim that they copied from Linux using SCO’s bent
logic ? 😉

SCO Copies Their Own Legal Documents From Groklaw and Tuxrocks – Without Attribution

Here’s an interesting turn up for the books. SCO, who started the lawsuit and who’s lawyers created their side of the documents, apparently have been been ripping off the scans of legal documents from the cases done by Tuxrocks and Groklaw and putting them up on their new “IP” website, without any credit to the original source.

Ironic, isn’t it ?

Frank Sorenson is quoted on Groklaw as writing:


For example, compare SCO’s #156 with the copy from my site. Note (using pdfinfo) that they were both scanned with “AXIS 700 Scan Server” (the scanner/copier at my office), they were both scanned at the same identical time (“Fri May 28 16:51:21 2004”), and that they both have the sme size (85387 bytes). Also note that they both have the same md5sum (3c1064ecedb19073e2194cd88507c349).

Another example is the Declaration of Ira Kistenberg (compare with the copy I obtained, scanned, and posted). In the upper right-hand corner of the page, you can see my handwriting where I noted which particular document this one was (236-G) so that I could remember when I got home from making copies at the courthouse.

RSS Feed Backend Updated to RSS2.0

Hoorah! I’ve just replaced the standard Postnuke RSS 0.91 RSS backend.php with the xBackends 2.6 from LEXeBus to give me an RSS 2.0 feed instead of the older 0.91 version.

The two minor hacks I did was to mimic the behaviour of the old backend.php so I could just drop it in as a replacement by setting the following variables at the top of the script:

$show_content=1;        // Default to showing the content of articles
$feedtype="rss2";       // Default to giving an RSS2 feed

With that done I get a successful validation via FeedValidator, viz:

[Valid RSS]

Gentoo Split Ebuilds for KDE 3.4 and Onwards

Here’s a good thing, those nice Gentoo folks are going to create ebuilds for the various components of KDE, migrating away from the monolithic, all-or-nothing ebuilds for kdebase and kdepim to packages for things like kdebase-kioslaves and kopete. The monolithic ebuilds will be maintained for 3.4, but for KDE 4.0 and later there will only be the split ones.

For the details see the Gentoo KDE Split Ebuilds HOWTO.

Making Postnuke Understand Time Properly

I finally got fed up enough with the dumb way that PostNuke does its time stamping to try and fix it. Basically it uses local time everywhere, then gets you to tell it which timezone its in via its preferences and finally expects users to register and set their timezone so it can re-correct the time for them!

Anyway, this isn’t obvious until you go hunting around for why it doesn’t seem to work if you’re not in the same timezone (or in my case, continent & hemisphere) for where your website is. Googling around for Postnuke “time zone offset” gives some helpful references, especially with respect to a Postnuke Forums posting about fixing it. But before you go off and read that, note that (a) it won’t work on current versions and (b) there’s a simplified variant of the hack. Still kudos to them for working this out!

You’ll need to read on for the guts of the article, as I don’t want to scare the non-techies out there by putting it on the front page directly.. 🙂

Continue reading

Fork-bombing Linux – a Lesson in Poor Defaults

My good friend Alec Muffett has blogged an article from SecurityFocus about the vulnerability of default Linux system installs to, what he neatly call, "The triumphant return of: main(){while(1)fork();}".

It’s sad to see that many Linux distros (Debian being the notable exception) still ship with bad defaults that don’t prevent a non-privileged user fork-bombing a box. Certainly something that needs to be addressed as it’s all part of the “defence in depth” that any system needs.

Referrer Spammers Using Non-Existant Domains

You’ve probably seen this yourself already if you’re running a blog yourself, but the referral spammers are now using referrer URLs that don’t have any DNS records yet, I presume because they think that people can’t check them out first to see if they’re a spammer or not.

Of course, it’s fairly obvious because how on earth do you get a referral from a site that doesn’t exist! They go *plonk* here as soon as I spot them..