Slashdot Mirror
Slackware 10-RC1 Released
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.
Slackware 9.1 was fully 2.6 compliant, too.
I swaret my way to the newest versions. (swaret.org)
It's nice to have an up-to-date installation-CD though.
If you mod this up, your slashdot background will turn into a beautiful sunset!
And I am still using it today. Why?
All in all, thanks Patrick ! Another great version of a great distribution !
The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
If you want PAM, you can roll your own and make packages of it, or you can use the PAM packages from Dropline GNOME. I still don't recommend it! =)
Because their current form of distribution is superior to ISO download. By using an rsync mirror, you can not only easily download an entire distro, but update that distro with any changes as they occur...without downloading the entire ISO again. For instance, when RC2 comes out, by using rsync you'll be able to easily download just the changes from RC1 to RC2. (I don't use swaret as i've got some custom scripts built to use some rsync mirrors I know of, but I'm sure it works on this concept and uses rsync).
Also: this distro method allows you to pick only those packages you want to download. Don't like GNOME? don't download it. Don't want any gui at all? skip gnome, kde, and X.
Once you've downloaded your distro, just do an NFS export on the distro dir on the host machine. Then build yourself a boot CD or boot floppy (as you prefer). Once you've booted on the target machine, you can install straight off the NFS share to the target. Works great, I do it all the time...I did my first ever Slackware install this way, even though the host machine was a Windows box.
Honestly, ISO downloads of distros kinda sucks, once you start doing things this way.
DaC
ftp://inferno.bioinformatics.vt.edu/linux-distros/ slackware/slackware-current-iso/
I don't even know what you're talking about-- slackware has had easy removal of packages nearly forever! Incredibly, it's called 'removepkg', but like any tool, you can shoot yourself in the foot if you're not careful. =) With the addition of Swaret to the mix, managing packages on slackware is too easy.
the others have answered your question, and I'll even add this, it even comes with RPM, should you feel the need to scream out loud.
IIRC, no official FTP sites ever had the ISOs. Patrick did this for a reason, which he explained in great depth when 9.1 came out. I can't remember why, but I'm sure you can find it on the mailing list archives. He chose to release the ISOs using bitTorrent to save all the mirrors' bandwidth. Download yourself a bitTorrent client and point your browser to Slackware's official bitTorrent page. You can get the ISOs that way, like everyone else.
For allegedly having a "disdain" for GUIs, it's ironic that it was because of fitting both Gnome and KDE (and sources) that they had to jump to two cds, instead of one. Not to mention the fact it's one of the first to distribute (in the RC, at least) X.org as part of its' distribution (afaik, mandrake doesn't do that yes, and neither does redhat).
Well, not really, Slackware did a version jump from 4 to 7 because people did not realise the difference between the Slackware version and the component packages version. See: Why the jump from 4 to 7? from the Slackware FAQ.
No trees were harmed in the posting of this message. However, a great number of electrons were terribly inconvenienced.
(1) edit /etc/swaret.conf so that VERSION=current
(2) issue the command: swaret --update; swaret --upgrade -a
and you'll basically have installed Slackware 10 RC1. Damn, I love Slack, and swaret just makes it easier to keep 'current'.
CB
free ipod and free gmail!