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.
I don't think the mirrors sites have ever had them. Visit #slackware on irc.oftc.net or freenode.org, and we'll provide you with smaller unofficial mirrors, where you can get official 9.1 isos or even -current/10rc1 unoffficial ones.
--- d'oh
man 8 removepkg
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.
Have you tried LinuxISO.org? They have both of the install ISOs for Slack 9.1.
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).
A released release candidate that is released for testing purposes is still a release candidate for release to the big world.
Official Torrent Page
The reason Slackware is release 10 is because they jumped numbers a few years back because they thought they were falling back in the "numbers game."
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.
Yeah, but RPM is a horrible awful thing and its implementation is a plague on the Linux world.
No central repository, no consistent interface, sparse documentation, incompatible versions, etc. Debian's APT, Slackware's pkgtool, and the ports system the BSDs have have all been a much better working and better designed system, for much longer than RPM has been around.
Just IMHO.
Oh yeah, and shutup all you Gentoo Partyliners, you're way late in this game.
do() || do_not();
No, the new version is not out. He's just moved the -current branch along to the point of calling it RC1. New CD's will be available via Torrent when 10.0 is officially released. And, you'll also be able to buy a nice Slackware box, too.
/extra directory of their slackware-current tree. It will contain an uptodate list of -current mirrors.
In the meantime, grab swaret or slakpkg and update yourself all the way to today's version of -current. Then, you will be at RC1. (If you use slackpkg, pull down the current 1.2.2 version from an updated mirror. It's in the
Also, don't be surprised if it takes the mirrors a few days to catch up.
-- Slashdot: When Public Access TV Says "No"
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!
One nice thing about swaret (swaret.sourceforge.net) is that you can set it to check dependencies, or not. I know it's not part of slackware proper, but is a very, very nifty tool. I run it every week or so to keep my slacks up to "current".
"Would it kill you to put down the toilet seat?" -- Maya Angelou
Patrick droped it from the distro because of the behavoir of it's author. Try something like Slapt-get instead.
But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
I've tried a number of other distributions and always come back to Slackware, mostly because other distributions feel the need to make goofy proprietary crap - er, I mean apps that might work, if you happen to know the exact name of the executable and know where it resides... and so long as you don't mind any customizations to be over-written willy-nilly. This is especially true of RedHat, which I'll never touch again. Suse was a bit better. Debian crapped out on the install for no good reason on a normal hardware configuration that worked fine with Slackware. Plus, the monstrous list of apps to install was impossible to work with. I'll never bother with Debian again.
Slackware is simple. You boot it up and run "setup". How hard is that? If you want, you can use RPM's, and other package "utilities", but they tend to blow up after a while. pkgtool is simple and works. Swaret is the cat's pajamas - though not actually a part of Slackware (see swaret.sourceforge.net). Best of all, most Slackware knowledge is useful on other unix-like OS's; you don't go into a panic about not finding your distro's goofy-ass-proprietary app for configing something, you just know where to look. It's great.
"Would it kill you to put down the toilet seat?" -- Maya Angelou
It drops in a working PAM infrastructure, as well as up to date Gnome and other packages.
Our unofficial Slackware mirrors are here. Some of us have been up to date with RC1 as of last night.. I'm sure the rest will be there soon, if not already.
XML is like violence. If it doesn't solve the problem, use more.
No, because it's a dull, lifeless place with no purpose whatsoever.