Slashdot Mirror
Slackware Linux 10.2 Released
excelblue writes "Slackware Linux 10.2 has finally been released. This release comes with Linux 2.4.31, with 2.6.13 available in the testing packages and glibc 2.3.5. This time, they've decided to get up with times and switch to Firefox, Thunderbird, and subversion instead of using the Mozilla suite and cvs from the previous distros. Here are Torrents of ISO images."
well, if i understood this submission correctly, it implies that mozilla & cvs now are missing - that's not true.
:)
it contains mozilla-1.7.11 and cvs-1.11.20
at least in latest-current that should be identical to 10.2
Rich
slamd64 has been released with many quite similar changes. What a coincidence, 'eh? Grab it now if your CPU is of the x86-64 persuation.
Rob
Re: up with the times... Slackware has never tried to be up with the times. They're just now allowing 2.6 kernel (from the installer). Firefox is still a 1.0.x release so its not as stable as the mozilla suite has been (though its pretty good). I think Pat just lets everyone else work out the bugs before he incorporates it into his release. Stability and Ease of Use.
Slackware has 28 distros based on it (29 if you include the new PocketLinux), some of which are trying to be "Enterprise Level."
Thanks. I assume you mean this?
:-)
From the changelog, and for anyone else interested:
gnome/*: Removed from -current, and turned over to community support and distribution. I'm not going to rehash all the reasons behind this, but it's been under consideration for more than four years. There are already good projects in place to provide Slackware GNOME for those who want it, and these are more complete than what Slackware has shipped in the past. So, if you're looking for GNOME for Slackware -current, I would recommend looking at these two projects for well-built packages that follow a policy of minimal interference with the base Slackware system:
http://gsb.sf.net/ http://gware.sf.net/
There is also Dropline, of course, which is quite popular. However, due to their policy of adding PAM and replacing large system packages (like the entire X11 system) with their own versions, I can't give quite the same sort of nod to Dropline. Nevertheless, it remains another choice, and it's _your_ system, so I will also mention their project:
http://www.dropline.net/gnome/
Please do not incorrectly interpret any of this as a slight against GNOME itself, which (although it does usually need to be fixed and polished beyond the way it ships from upstream more so than, say, KDE or XFce) is a decent desktop choice. So are a lot of others, but Slackware does not need to ship every choice. GNOME is and always has been a moving target (even the "stable" releases usually aren't quite ready yet) that really does demand a team to keep up on all the changes (many of which are not always well documented). I fully expect that this move will improve the quality of both Slackware itself, and the quality (and quantity) of the GNOME options available for it.
Folks, this is how open source is supposed to work. Enjoy.
I'll look into the alternatives, though it's still sad I won't be able to depend on their stability as I would the base system.
He had Actinomycosis.r e_PAT/
Brave guy to keep working as sick as he was.
You can rad about it here-
http://linuxreviews.org/news/2004/11/17_0_slackwa
Too bad there isn't a "completr lack of package management". pkgtool is a package management tool, it scares me to think you admin 120 boxes, and you aren't familiar with the pkgtools suite of tools.
YOU'RE WINNER !
Another lame blog
There isn't a complete lack of package mangement, it is the pkgtool suite (upgradepkg, installpkg, removepkg, etc.). That is one thing I like about Slackware, you should look to see what the dependencies are. The problem I've been having administrating Red Hat machines is the endless levels of dependencies that are compile against any random package. It is like a slippery slope installing a package on Red Hat, when it would be easier just to compile stuff from source, or not link it against so many things.
Such that to install package a, you need to install package b, which requires packages c and d, which also require additional packages. Compiling from source can be less time intensive if you ask me.
YOU'RE WINNER !
Another lame blog
Checkinstall is your friend. You'll never have to type "make install" again. Instead, run checkinstall at the "make install" stage, and it builds a package for your distro (it handles .rpm, .deb, and .tgz based distros) and installs it. You can then just use your distro's package management tool, in Slack's case pkgtool, to remove it at a later time.
I think it's in the extras directory on the second Slack CD, if memory serves correctly.
"Proudly Posting Without Reading The Article"
MISCONCEPTIONS FALSE: Slackware uses a very simple package management system that accomplishes two things. 1. it allows you to track files installed. 2. allows you to upgrade to newer versions (yes there is versioning). And as a bonus, your not bogged down with dependancies.... oh wait you want cyclical dependancies??? FALSE: Why? because it still uses 2.4 kernel? Please! stability is the issue here. Purchase a RedHat Advanced server and you'll find it STILL uses 2.4. You cant please everyone all the time, but you can still produce a quality product with proven technology. AD-HOMINIM: This argument is too often used against Slackware in general. For what it is, an "everything is a file" operating system, you must expect to have to get to the command line eventually. If your using it as a server in place of another Unix OS, its not any harder to manage. If your using it to replace RedHat or SuSe, still, its not any harder, and with the added bonus that you dont have as much bloat (did i mention cyclical dependancies?). TRUE: So is Linus Torvolds, and as far as direction, every company, ceo, lead developer must make thier own decisions and you just cant please everyone all the time.
Before the mods make me -1 troll, let me just say Slackware is not perfect, but nothing is. I dont like the fact that PAM will probably never be added
I use it as a desktop and a server. My servers are usually stripped down and single serve boxes, and slackware is a perfect fit. By trade, I work with Solaris, AIX, and RedHat. The only reason I dont push Slack at work is that my company wants to spend the money to have a finger to point at (specifically a large company to point at) when a problem arises.
But in the 5 years i've been using slackware, I've never encountered a show stopper.
Just use swaret to upgrade your box to either 10.2 or current. Shouldn't take more than a few minutes.
"Proudly Posting Without Reading The Article"