Fedora Core 5 was released today. I started downloading it this morning, and it should be done this afternoon. I’ll probably start updating the Fedora boxes at work later this week, though for my home system I may wait until RPMForge catches up.

Meanwhile, I’m reading the release notes, and found one item particularly interesting:

There are new experimental drivers that provide support for the widely-used Broadcom 43xx wireless chipsets (http://bcm43xx.berlios.de/).

Continue reading

I just updated a system running Mandriva Linux 2006 and in the release notes I discovered that not only will it upgrade a Mandrake system, but it can now upgrade a Conectiva system. I suppose I shouldn’t be surprised, given that both used RPM as their package format/database, but I really had the impression that Mandriva was primarily Mandrake with some extra stuff from Conectiva. It’s nice to see that there really is a true upgrade path for both distributions.

The Mandrake/Conectiva merger has had a chance to sink in. I’m almost getting used to the name Mandriva. But I’m still trying to figure out last week’s announcement that Mandriva has bought Lycoris—or rather, has “purchase[d] several assets from Lycoris.” The big news is that they’re combining Mandriva Discovery (their entry-level desktop OS) with Lycoris Desktop/LX.

The main thing is, I can’t make out just what Mandriva has and has not bought. I can’t figure out whether there’s anything left of Lycoris, the company. Their CEO is moving to Mandriva to head up the new product. Their software collection and user forums are moving to Mandrake Club. Their flagship product is being merged with one of Mandriva’s. But the wording of the press release implies that they haven’t bought everything. If I were to guess, Lycoris might start focusing on their Tablet PC line.

What does seem to be happening is that Mandrake has begun collecting a number of the smaller commercial players in the Linux arena. Who knows? They may be in a position to challenge Red Hat and Novell soon.

The eternal Mac OS on Intel rumor resurfaced last week, and as always, my reaction was “I’ll believe it when I see it.” Well, I’ve seen it.

After five years of rumors, Apple has not only confirmed Mac OS X can run on Intel processors, but future Macs will run on Intel. No, they won’t be releasing a version of Mac OS that you can install on your PC, they’re “just” replacing the CPUs in future Macs. Apparently Intel has a better road map for future performance. (Hmm, better tell the marketing division, quick. The PowerMac page [archive.org] still touts the PowerPC’s superiority over the Pentium 4.)

It’s a switch on the order of—well, on the order of leaving the Motorola 68K for PowerPC. Back in those days, it was Apple vs. IBM Compatibles, and IBM was a partner in the PowerPC design. These days it’s Apple vs. Wintel, the Windows/Intel combination.

Apple seems to have everything planned out. Secretly running OS X on both PPC and x86 for the past five years, preparing developer tools to produce applications for both architectures, setting up a translation tool to run PPC apps on Intel chips. Microsoft and Adobe are already on board. It’s not a surprise, really—they’ve done it all before. Of course, we all know how well the best laid plans go…

I do have to wonder how this will affect Linux distributions aimed at the PowerPC line. Yellow Dog Linux, for instance, is also advertised as running on IBM’s own PowerPC systems. And depending on the rest of the hardware, standard x86 distros may have to incorporate formerly PPC-only code. Update: It hasn’t shown up on their website yet, but I just got an email from YDL stating that they will remain focused on PowerPC, remain “in good standing with Apple” as a reseller, and “expect [server OS] Y-HPC to gain an even greater userbase with existing Apple Xserve users.”

I also wonder which Intel chip line they plan on using. Everyone seems to be assuming it’s x86-based, and I’d guess it’s 64-bit (why go backwards from the G5?). In theory Apple could go with Itanium, since they don’t need to drag around x86 compatibility, and the extra volume might be enough to bring the price down.

The gpl-violations.org project has scored another victory, this time against Fortinet, whom they accused of not only violating the GPL (by using GPL’ed source code without publicly releasing their changes) but actually trying to hide that usage with encryption.

Edit (I hit “publish” too soon!): They settled out of court, with Fortinet agreeing to make the source code available for their customized Linux kernel and other GPL’ed software they snurched from other projects, and to include the GPL in their licensing terms.

This is the latest in a string of victories for the gpl-violations.org project. Since starting the project in 2004, Welte has negotiated more than 30 out-of-court settlements.

But then, “the GPL has never been tested in court,” right?