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.
ISO's of RCs? Is it to help the guys selling ISO CDs? Seems to me they would want to make it easier to get and test.
Don't be a looter...and yes, I know that it's spelled with an "A" instead of an "E".
Cousin to Gentoo I guess you would call it. Glad to see it's still chuggin along. I may just have to install it again one day.
Ubuntu- Linux for human beings.
This release includes kernel 2.4.26 , Gnome 2.6.1+, KDE 3.2.3, GCC 3.4, XOrg 6.7 and more.
Not much interested in those. Half the reason I run Slackware is because it's not bleeding edge and bloated. Good to see they don't force 2.6 on the users.
Slackware 9.1 was fully 2.6 compliant, too.
It fills my heart with glee that a fellow dutchy is making (among other people of course) one of the more popular linux distros.
Congrats to him (and the team)
This is the sig that says NI (again)
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 just installed 9.1... *grumble*
Surely you can't release an RC? You can issue an RC, but once it's released it's a release, not a release candidate.
Until Slackware has a solid PAM implementation, it will be delegated to my smaller, simpler tasks. And yes, I've read Patrick's rants about his dislike of PAM.
And 2.6 is quite stable, not to mention a hell of a lot faster than 2.4... so why are we still stuck in the stone age? If you want to be really elitist about it, stick with 2.2...
Slackware was the first distro I ever used, way back in 1995. I had read about Linux in a small InfoWorld article, back when InfoWorld was tabloid size instead of regular magazine size. The article said you could run an entire operating system on a single floppy disk. Of course, I had to try this on my 386SX with 4M RAM. I downloaded Slack over a 14.4 modem and then copying it all to a set of floppy disks. I wish I could remember the name of that tool. Anyway, I ended up installing Slackware using UMSDOS so I could keep my DOS/Windows data.
:)
I remember I had to completely reinstall Slackware any time I wanted to add a new piece of software because I didn't know how it all worked. The very first question I asked on a Linux newsgroup was, "What's darkstar?" It, of course, was the default hostname for a new Slackware install. Heh. Starting X would dump you into fvwm with only an xterm and a pager; not much has changed there.
Ultimately I used that Slackware machine to learn about Unix and make the move from client-focused to enterprise-focused. Those were fun times.
I can still remember my grandpa telling me stories about this distro.
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)
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.
Okay, i am a linux user of several years. Mostly Red Hat, but i've had Suse, Mandrake and Gentoo at various times, but never Slack or Debian.
:(
i'm told it doesn't get more stable than Debian Stable, but i normally hear people say Slack is hard to install or hard to work with. Why is that? And can someone please clear that up for me? i'm not trolling, i just don't know enough about Slack to see why people would want to run it. Is it small and fast and just less "junk" to worry about for security reasons? Help me out!
heh, i've also heard Slack mentioned amidst some rather colorful expletives (i know the feeling though
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
Slackware is not so much a cousin to Gentoo, as it is Gentoo's *mentor*. That said, any further comparison strains credulity.
Such silly, half-thought, cookie-cutter comparisons of the two distros only serve to further obscure the true nature and intent of Slackware.
Trolly, trolly, troll-troll
There's a Starman, waiting in the sky / He'd like to come and meet us, but he hasn't got the time.
man 8 removepkg
Don't speak until you've used it. I've used nearly every distro including slack, debian, and fedora. Fedora is the only one that "just works" and works really well. It doesn't hide things from the user but its simple enough for newbies. I like slack, but Debian and Fedora IMHO are slightly better. Fedora has been my distro of choice since its first release. I can just give it to friends and they can use it, I can use it as a secure server, or anything I pretty much want. Debian does have some advantages, which is why I run it on most servers. And slack has its place, as does every distro, but the only thing that I see slack has that the others don't is the history. It is a great distro, but hardly the best, or the only one worth using. Oh, and the best community support I've seen has come from the Fedora community, ask a question in a debian or slack irc channel and you'll get nothing but trolled and told how stupid you are, even for fairly advanced questions(at least thats been the majority of my experiences), where as fedora always has someone willing to help.
Regards,
Steve
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.
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!
There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
If you only use prebuilt binaries then I can see why this might be a problem. However, Slackware is designed with simplicity in mind for the user who is prepared to get his hands dirty compiling his own stuff (even if only from time to time). This almost by definition makes any package management system a la Debian or SillyHat redundant, since your database is out of date the first time you do this.
If you want to stay current with Slackware and stay with pre-built binaries, there's always swaret (and it really is current). However, you'll never appreciate the simplicity of Slackware if you never try playing with it.
I do. I'm only a newcommer to the loving arms of slackware(9.1) for about 4 months now. The non-bloatness. With slackware I am in total control of my system. so what slack is manaul configuring and it doesn't have the greatest auto hardware detection. In my eyes thats a good thing. it makes you learn, and with slackware you learn fast.
Official Torrent Page
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"
You make such a fine point, I could hardly agree more. Slackware has contributed more to my general knowledge of *nix-like systems than any other single entity. Slackware *does* force you to learn, but allows one to do it at their own speed. After almost six years using Slackware, I can sit down at virtually any Linux distro (or for that matter, *BSD) and soon have the task at hand complete.
I don't want to perpetuate the old myth that 'if you know Slack, you know BSD', but Slack does more to stomp out the learned helplessness that cripples most user's *nix experiences, especially those unfortunate enough to have grown up in Walt Microsoft World.
I never thought that computing could ever again be as fun and rewarding as the days when I pounded out terrible BASIC on my C-64. Slackware has brought all of this joy back, in droves. I am forever grateful to Patrick for all his years of hard work. As an aside: visualize a distro maintainer that actually listens to user comments and wishes, and seems, by all accounts, to be a nice, regular person.
There's a Starman, waiting in the sky / He'd like to come and meet us, but he hasn't got the time.
(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
Ours might not be the most common circumstance, since most internet users aren't bound by HIPAA and other regulations to tightly control what leaves their networks. How many web programmers do you know that have (or should have) the official government Health Insurance Portability and Accountability Act home page bookmarked, for assistance in deciding what can and can not be displayed under what security circumstances? Probably not that many, but, for those of us who do, it means that certain popular distribution methods are not kosher at this point in time.
Jigdo is compliant, since it uses established protocols, and is inbound-only. Bittorrent may or may not be compliant, and I'm not in the mood to be the one who tries to get it approved.
If someone HAS the ISOs, they can make and post the .jigdo and .template files required. And the load on the servers now hosting the ISOs would be lowered significantly, since any mirror that has the basic files for the distribution can be a "jigdo ISO mirror", using either FTP or HTTP.
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
I like slackware because it has captured the flavor of BSD very well. It has a cohesiveness that is the result of Pat's immense knowledge and steady hand.
However, given that Slackware seems to be one of the prefered distros for BSD-o-philes, why not move its old-school BSD init style to be more in line with the other BSDs? The NetBSD rc scripts are not a huge leap for people familiar with Slackware's. That's because the new style is a logical evolution from the old. FreeBSD made the jump too. The new rc script style feels more "BSD" than the old feels to me now...
-Peter
. Penguins Surely Ca
they are not at all mutually exclusive really, as far as applications go. If i have gnome libs installed and kde libs installed, I can run a gnome based app right alongside a kde based app.
hell, i have kde installed in slackware and never actually use kde as a desktop environment. there are a few apps that are built for kde that I use.
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.
I think that distros try to keep up with each other so that newbies don't go: "Oh, Slackware only has Linux 9, Mandrake is already at Linux 10!"
In fact, I think it was one of the reasons Patrick himself mentioned for skipping a few version numbers with Slack.
I love slack, btw! Keep up the good work, Patrick!
Treehugger? Treehugger... Treehugger!
lol!
10 years ago there was no google.
funny guy