Slackware 10-RC1 Released 346
Chaxid writes "According to the latest Slackware ChangeLog, release candidate one of the next iteration of Slack is upon us. I asked Patrick Volkerding via e-mail if the 2.6 series of the Linux kernel would be included in this version, and this was his response: 'To have support for using the 2.6 kernel in the installer might not be a good idea quite yet, and it would delay the release a lot. I'm planning to wait on that for the next one'. It's worth noting the Slackware 10 RC1 is fully 2.6 compliant however."
As TouchOfRed writes, though, "A test kernel 2.6.6 option is offered via the 'testing' tree. Slackware does not offer ISOs for the RCs (however there are some third party users that compile the RCs or the -Current tree regularly as ISOs), so if you are already running Slackware 9.1, you can use the excellent Swaret to upgrade to the latest packages (make sure you edit your /etc/swaret.conf prior of using swaret to allow for kernel upgrades and other options)." This release includes kernel 2.4.26 , Gnome 2.6.1+, KDE 3.2.3, GCC 3.4, XOrg 6.7 and more.
Obligatory complaint (Score:3, Funny)
Re:Slack (Score:5, Funny)
Memories... (Score:5, Funny)
A giant leap into 2001! (Score:0, Funny)
Re:Slack (Score:1, Funny)
Re:Slack (Score:1, Funny)
Re:Slack (Score:2, Funny)
Re:A question... (Score:0, Funny)
This is not news! (Score:5, Funny)
This is not the release of Slackware 10! This is merely the release of the "release candidate version 1"!
Worst of all, I was looking forward to rsync the update today, and now you've shot that idea to hell, Timothy!
Re:Wow, 10 already? (Score:3, Funny)
Re:Obligatory complaint (Score:3, Funny)
Re:I started with Slackware... (Score:3, Funny)
Have you ever used Slackware? Seriously. I've used about every distro out there, most of the SysV init, and I can honestly say that BSD init is much simpler, more intuitive, and as a result easier to use. In saying that SysV init has a startup script for everything you're neglecting that BSD init does too. Look at rc.samba, rc.httpd, rc.portmap, etc.
Basically SvsV init works by having an absolute ton of symbolic links to each startup script. Init checks each of these links to see if that service should be started in that runlevel or not, and in what order they should be started. Not only does this contribute to long startup time by having to seek all over the drive to find these files, it's hell on the user to track down everything.
Don't want mysql to startup on boot? In SysV init you mave to rename six symbolic links to begin with the leter "K", and possibly reorder them. In BSD init, you just remove the executable permission from rc.mysql.
Want to change the order that your startup scripts run in? In SysV init have to make these changes for numerous sym links in six different directories (one for each runlevel). In BSD init, you just open two text files (one for boot up and one for shutdown) and move the blocks of text to where you want them.
Bottom line, BSD init is much simpler on the sysadmin. The only advantages I've ever seen in SysV init are the ability to:
A) Have each runlevel start things in a different order (also easily manageable in BSD init, if not as straight forward), and:
B) Allow automagical setup tools to make changes in system initialization (something a control freak hates).
Re:Can anyone say why they don't release... (Score:2, Funny)
And what about robots which have been programmed to love? WHAT ABOUT THE ROBOTS, HAS ANYONE THOUGHT ABOUT THE ROBOTS?!?
But the serious answer is, if you are on such a restrictive network, then you shouldn't be downloading an ISO. But you already knew that.
DaC
Re:KDE (Score:1, Funny)
And why do you think so my young grasshopper?
Re:Wow, 10 already? (Score:3, Funny)
Ha! That's nothing!
1, 2, 3, 95, 98, 2000, 2003, ...
Re:The only real linux distribution! (Score:3, Funny)
10 years ago there was no google.
funny guy
Don't use Linux!!! (Score:1, Funny)