Slackware 10.1 Released

wikinerd writes "Slackware 10.1 was released and it contains the Linux kernel 2.4.29/2.6.10, X.org X11R6.8.1, KDE 3.3.2, Mozilla 1.7.5, Xfce 4.2.0 and several other updated software, as you can see in the official changelog. You can download it right now via BitTorrent."

Dropline Gnome

[Xpilot]

For Slackware users who love Gnome (like me), they can still use Dropline's Gnome [dropline.net] distribution. It should work out of the box for Slackware 10.1 too.

Torrent Mirror

[hashinclude]

In case someone manages to /. the torrents themselves, here [tripod.com] is an alternate location.

Mirror

[Anonymous Coward]

For those not already in the know about MirrorDot, the non-slashdotted version is here [mirrordot.com].

Posting as AC so not karma whoring.

Re:Real package management?

[Anonymous Coward]

Swaret works nicely for Slackware. [swaret.org]

Re:Dropline Gnome

[WarehouseCU]

The Dropline GNOME version is 2.8 vs. the 2.6 included with Slackware. I'd say that an entire release is more than a few tweaks.

Re: kernel

[adamjaskie]

Slackware 8 came with 2.2.something and 2.4.5, your choice which to install, but defaulting to the more stable 2.2.x kernel. This is no different, really. I used 2.4.5, because I wanted to use ReiserFS :)

CHANGELOG

[Anonymous Coward]

Here's a copy of the CHANGELOG, as the original seems to have been taken down:

http://mirror.linuxquestions.org/pub/distributions /slackware/slackware-current/ChangeLog.txt [linuxquestions.org]

--jeremy [linuxquestions.org]

Re:Ok, self-confessed Debian lover, but ...

[sordid_mammal]

from the changelog:

And about my status... I didn't want to have to bring this up again, but since a lot of people are under the impression that I've recovered and I'm just fine (and are beginning to make the usual demands of my time ;-), I'd better clarify what's going on. Especially since I'm not exactly fine.

Back on Thu Nov 25, I posted in the ChangeLog that I thought I had infective endocarditis (and was promptly flamed for self-diagnosing again). After so much beating around the bush without getting a referral to a cardiologist, I finally called one myself and waited the two weeks it takes to get in. He is a top-notch doctor and heart surgeon (I was very lucky to be able get in to see him), and with no planting of any suggestion from me whatsoever came to the conclusion that it seemed to be infective endocarditis. I'm still waiting for more test results, but it looks like I finally have someone working on my side. So, lets hope that they get some conclusive diagnostics (I get another echo on Wednesday), that I make it until they do, and that it's not too late for this to be treated without a need for valve (or heart) replacement. I've had a rough couple of weeks (well, months really, but especially the last two weeks), and I have to say that while it's good to have a near-death experience every couple of years to keep your head clear and your focus on the important things in life, having one every morning is too often. With that frequency, they start to become a distraction. ;-)

So, this verson is going to be wrapped up pretty quickly. I hope people will support the release, because I'm sure I'll have a lot more bills before all of this is through, and I'm blowing through what little money I've managed to save. Again, I'm not asking for donations, but I hope that when Slackware 10.1 comes out that people wanting to help out will order it. Also, in case of emergency I've left instructions with some very trusted people, so nobody should have to worry that if something happens to me that their Slackware systems will be orphaned and unsupported. It may be a long road back for me, but there will be people taking care of security issues as they crop up (like the folks at GUS-BR and SlackSec), and if I should make an unplanned departure there is a basic plan of succession in place.

Thanks again to all the kind folks I've known over the years, and I hope to know you for many more. :-)

Your Humble Slackware Maintainer,

Pat

Re:SATA?

[jprior2001]

There is a SATA boot floppy http://slackware.at/data/slackware-current/bootdis ks/

And there is a SATA kernel selection.

Re:Torrent Mirror

[Wordsmith]

Another copy of the same torrent file mirrored elsewhere will still point you to the same network of seeds and peers. It's the tracker that matters, not the host for the torrent file.

Re:I suggest you buy it

[Skater]

I'm on the automatic subscription plan. Very convenient, and it supports my distro of choice. Slightly slower than downloading it, but I'll probably have the discs later this week or sometime next week, so it's really not bad at all.

Re:Dropline Gnome

[zdzichu]

Sorry, but Dropline is against Slackware ideas. Dropline forces you to install PAM, which is not well seen in slackland. Dropline tend to replace half of the system, including X11. That's wrong! Last time I've checked there was some abstract requirement on external libiconv, despite iconv beeing part of standard glibc.

Re:No GNOME?

[0racle]

what kind of modern linux distribution doesn't include GNOME?
One that has recognized the quality that has come out of another project that provides the same desktop. Pat decided that Dropline was so nice, and there were so many people using Dropline Gnome that it wasn't worth his time anymore to package a vanilla Gnome.

Pat on GNOME

[antizeus]

Here's a copy of something Pat said about GNOME:

Anyway, suffice to say the jury is still out. Since GNOME 1.4 I've felt that GNOME is going in a direction that doesn't fit well with Slackware's goals, and for at least as long I've considered removing it completely and taking whatever flames I get for that decision. Right now, I think removing it would be the best thing for Slackware as it's become a maintainance nightmare (unlike nearly every other ./configure'ed source, GNOME doesn't build into packages easily with DESTDIR).

Not what you wanted to hear, I'm sure, but I do believe it would be best to let Dropline produce Slackware's GNOME and quit wasting my own time with it. Probably 1/3 of developement time here is used maintaining GNOME, and *most* of the bug reports I get have something to do with GNOME (and aren't bugs I caused, or can fix). KDE, on the other hand, tends to build using the existing build scripts with no changes at all. I can start the build and come back to finished packages in a few hours. A GNOME update usually takes at least a week of manual labor, and another week of cleaning up broken things. It's been a long time (like I said, around GNOME 1.4), since I've felt the effort was worth the return.

Sincerely,

Pat

Personally, I don't care. I use FVWM.

Re:Pat on GNOME

[m50d]

1. He's semi-endorsing the dropline people, who have always done a good job of packaging it. He doesn't want to lose control by turning over part of the actual distro to other people

2. Yes. He's asked them repeatedly, but they don't seem to care. If they could just get make install DESTDIR=/tmp/root work like it works for everything else then he could keep it in no problem.

3. Because Pat maintains Slackware *by himself*. Most distros can just devote a few people to managing the Gnome build, Slackware can't.