Slashdot Mirror
Slackware 11.0 Almost Done
linuxbeta writes "DistroWatch reports that the development process for Slackware Linux 11.0 is almost over. OSDir has some sweet shots of Slackware 11.0 RC1 in the Slackware 11.0 RC1 Screenshot Tour." From the article: "'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."
1999 called, they want their kernel back...
Slackware's always been designed with maximum stability and reliability in mind. Patrick thinks that 2.4 is still the safer bet, so he's gone with it as a default. The option to install with a new 2.6 kernel is also available, for those who'd prefer something a touch more modern.
I was using Slackware for few years before I switched to Arch Linux.
I don't understand why it still uses xorg 6.9. Maybe the reason is that nobody has the time to make so many packages for xorg7? IIRC that was the reason why there is no full GNOME in Slackware.
Kernel 2.4 - OK, as long as it is 2.6 ready (and it is).
But guys... what's the point to use so old software? If you don't want to put new desktop stuff, then just remove all desktop packages from distro.
Granted, I don't use Slackware. But when I saw a link stating "Slackware Screen Shot Tour", I fully expected to see a bunch of shell prompts :-P I wasn't entirely wrong!
Am I missing something here?
Well, besides that its KDE, I dont think so.
2.4 is old but by no means 'dated'. 2.4 is significantly leaner than 2.6, runs on old hardware and has a lot of backports from 2.6 http://kernel.org/pub/linux/kernel/v2.4/ChangeLog- 2.4.33
Even DSL uses 2.4. I still use 2.4 on my old PIIs and newer hardware myself.
Slack aims to run on as many types of hardware as possible. Besides, you can always compile your own 2.6 kernel into your slack system.
... the Church Of the SubGenius!
"Powers. I have them."
Because it's considered more stable, and supports things that haven't been up-ported to the 2.6 kernels.
Patrick aims at the most stable distro...not the latest, flashiest distro. That is why it is used on a large variety of servers...in fact, it has the probably more server installs than any other Distro still built by one person, and his wife. Debian is probably closest, but it is now a large team that works on it.
Slackware just works...and works...and works...it's sort of the Energizer Bunny of Distros!
ttyl
Farrell
CAN-CON 2019 - Ottawa's only book oriented Science Fiction Convention! October 18-20, Sheraton Hotel, Ottawa, Canada h
SeaMonkey, the code name to the Mozilla Application Suite, an internet suite maintained by the Seamonkey Council. It is no longer maintained by the Mozilla Foundation.
source: http://en.wikipedia.org/wiki/Seamonkey
To Patrick Volkerding, his wife and Volkerding 2.0!
This is the oldest existing Linux Distro! Possibly one of the most stable as well. It retains the Unix philosophy that it does a few things really, really well, and gives you the tools to add on to it. It's tanj simple to maintain and update, no "RPM Hell". And it's one person's vision, which gives it a consistancy that is lacking in other "art by committee" Distros.
And I am biased...I moved to Slackware from Soft Landing Systems (SLS) Linux, and although I have tried many different Distros over the years, I keep on comming back to Slackware...and not just for religious reasons, either!
Thanx you Patrick and Co for keeping the vision!
ttyl
Farrell
CAN-CON 2019 - Ottawa's only book oriented Science Fiction Convention! October 18-20, Sheraton Hotel, Ottawa, Canada h
... for its venerability as well as its stability. It was my first, and still favourite distribution. It's not on the bleeding edge, but it has other virtues. One is that it can be scaled easily to install as much or as little of it as you need, and run on machines with very different CPU and memory resources and amounts of disk space. Great for turning a bunch of old mismatched PCs into a Beowulf Cluster.
Semi-automatic package management has taken awhile to evolve, but for some time now it has been very good indeed. There are several good PM clients; I think slapt-get has the edge right now. And if you can't find what you need in the distro, there are several sites (such as http://www.linuxpackages.net/) that offer lots of additional packages and goodies.
If it weren't for deadlines, nothing would be late.
Being a dedicated Slack user for the better part of a decade, I've rarely questioned any of Patrick's decisions in the maintenance of HIS distro. (Most people who piss & moan about Slackware being dated don't realize that it's one of the few distros that is still maintained, for the most part, by a single individual).
However, with great trepidation, I must say that perhaps some changes are in order.
Slackware has had a dedicated following for a long time because the distribution filled an industry need. The need for a truly rock solid stable distro that was a fairly easy transition for those coming from a pure Unix world. It seems now that those days are, for the most part, gone. The majority of the engineers out there now days have been brought up on other Linux distros, and many have never touched an actual Unix system. (No need to start any "What is Unix really?" flame wars).
While I do still prefer the structure and stability of Slackware, I do think it's time to make certain changes. I'm not saying it's time to jump on the "Latest and Greatest Everything" bandwagon. I think it's time for the distro to be re-focused. Possibly into a pure Server OS, with a strong focus on commercial grade clustering & virtualization. All of the other distros that have done this (i.e. RedHat, SUSE, etc.), did not have the right base for it. They were based on bleeding edge, sometimes alpha code, and everything had to be stabilized (which hasn't seemed to work out very well). Slackware does have the right, truly stable base for a dedicated server OS. If Patrick were to shift things to this direction, build in the right set of truly enterprise-class server features, I think he may very well see a new found following.
The other area that I believe a re-focused version of slack could be very successful is the embedded systems market. Slack is known for is lean, fast, optimized code. I think it would fit well into this segment.
I think either of these markets are perfect for Slack. Neither is looking for the latest, most newfangled, gui-based, anything. They want lean, fast, stable code, & steady release cycles. Just my $.02.
I choose my linux distro (read: flavor of the month) based upon screenshots, and the pure number of fanboys. That is why I am Ubuntu until I die (or until the lemmings march themselves into the water), and I have to choose a new distro, 'til I die.
YOU'RE WINNER !
Another lame blog
and their boot loader
Supplies!
Don't you mean 2001? Anyhow, what difference does it make what kernel they ship with (within reason)? If the hardware and software does not require a newer kernel, wouldn't it be more prudent in an environment where reliability is important to have the most reliable kernel out there?
I make a reasonable middle-class wage by going to work and not spamming blogs with scams.