Language Selection

English French German Italian Portuguese Spanish

Woohoo! Slackware Linux 11.0 RC1 Released!

Filed under
Slack

The long development process of Slackware Linux 11.0 is about to conclude - that's according to Patrick Volkerding who has declared the "current" tree as RC1: "There are still a few changes yet to happen, but let's call this Slackware 11.0 release candidate 1." Other recent changes include upgrade to stable kernel 2.4.33; upgrade to udev 097, and rebuild of glibc 2.3.6 for both 2.4.33 and 2.6.16.27 kernels. The new release will ship with X.Org 6.9.0 and KDE 3.5.4, and will provide SeaMonkey instead of Mozilla.

For more detailed information please see the Current ChangeLog. As has become customary with Slackware, there are no official ISO images, but interested testers can upgrade to the "current" branch and follow the development; alternatively you can obtain recent unofficial CD/DVD images from download servers.

Full Story.

More in Tux Machines

Whitehurst: Free OSS Red Hat's biggest competition in Asia

Red Hat still faces a major challenge convincing organisations to pay for its services, especially in markets such as China where there is widespread use of free, open source alternatives, says CEO Jim Whitehurst. Read more

Red Hat CEO issues call to arms for open source participation

Broadening the strength and depth of the open source community has always been a goal that has been supported by vendors and businesses alike, but a call to arms for a greater participation was the message that Red Hat wanted to get across at its annual summit. The Red Hat Summit in San Francisco was an opportunity for CEO Jim Whitehurst to talk about the ideology of open source during his keynote presentation, and a message of changing hierarchies underpinned much of what he said. Read more

Avoiding bad practices in open source project management

This whole list has been inspired by many years of open source hacking and free software contributions. Everyone's experiences and feelings might be different, or malpractice may have been seen under different forms. Let me know if there are any other points that you encountered that blocked you from contributing to open source projects! Read more

Today in Techrights