I personnaly use current and stay up to date using slapt-get I it is rock stable.

I run a server on current and up to now never had any issue.

I think Slack is one of the best if not the best linux distro for the one who wants to learn linux inside out!

I've learned more in one year with slack than in three years using fedora/mandrake. But again every distro has it's own public. That is what is so great about linux, there is so many flavors that everyone is able to find a suting one.

Cheer!

My 2 Euro Cents:

Just follow the links on http://www.slackware.com to the GUS-BR server.

In fact there haven't been that many patches for Slackware 10.0 from Patrick Volkerding, but he has authorised the patches provided by some folks in Brazil (GUS-BR group). So you can keep your system up-to-date as far as security is considered.

On a production server use Slackware 10.0, don't use current.

When 10.1 is published you will be able to upgrade. The upgrade scripts for Slackware really work. Slackware is the only distribution I know that has never required a fresh install (though you might have good reasons to do one, anyway). With all other distributions I know of it was unpredictable and dependent on the machine if an upgrade to a newer version would succeed or fail. More than once I had to start over and install from scratch after a failed update.

So you won't have to wait for 10.1 if you'd like to start now, as it won't be a problem to upgrade once 10.1 materialises.

On a machine where an occasional crash of a bleeding edge software package version won't hurt you might go for current. I used current for two or three months a while ago, and I had *no* crash. So even current is usually very stable, which shows
(1) the incredible talent and capability of Patrick Volkerding who manages to offer a bleeding-edge, yet stable and mature distribution
(2) how good Slackware stable releases actually are, as only a very stable snapshot of current will be the basis of a stable release.

Nevertheless, current is for testing. Particular stable snapshots of current are taken as the basis for the next release.

Many thanks to Patrick Volkerding for doing such a great job and all the best for your health!

gargamel

I am as up to date as I can be from both update sites. The temporary one is no longer going to be posting new updates. I'm just going to wait for the next one and quit worrying about it. I'm not even running a server, so what's the difference.

I have been checking for rootkits more frequently now, though.

Is GUS-BR really no longer providing updates?
Then you are doing the right thing, checking for root kits.

For anyone operating a server this is no good news, however...

Could it be that there are just no things to be fixed, currently?

gargamel

As far as i know gargamel the GUS-BR group have stopped providing updates for slackware.
i was also wondering why there haven't been any new security updates for slackware 10.thought like the rest of you that maybe there just wasn't anything to update.Although a new mozilla was just released not to long ago,and one of the reasons for the new mozilla version was a security issue.So shouldn't it have been updated in slack 10?

Mozilla in 10.0 is 1.7.3, should be 1.7.5, security problem
Samba in 10.0 is 3.0.5, should be 3.0.10, lots of security problems

It's been worrying me a bit too, maybe it's time to switch to FreeBSD.

I know a lot of Slack fans swear by Pat, but the events over the last few months have shown that a distro mainly maintained by one individual can run into problems if anything happens to the maintainer. It's made me seriously reconsider using Slack as my default distro coz as much as I empathise with the situation that Pat found himself in, I need a Linux distro that I know will be provide me with security updates etc on time. Obviously Pat has a massive back log of work he needs to catch up with, but if there were other contributors, this back log could have been severely reduced.

I'm going to stick with Slackware, it's the best of both Linux and Unix IMO. I'm just wondering if I should start using some files in current, since stable isn't being worked on, apparently.

Hopefully, this situation will show Pat that it's time to get more people who he can trust and rely on. I know it's hard to let go, but it may be time for him to get some disciples to take over the work while he oversees.

I played with FreeBSD for a couple of weeks. It's good too, but their latest stable-5.3 wouldn't load or install on my computer.

Yeah, me too. I imagine Patrick's work priority now is to get 10.1 out the door. After that, we'll probably see things returning to normal.

Patrick did say he'd learned a lot of lessons during his illness, and, since he's obviously a pretty astute fellow, he'll probably come up with a good way to tap into available resources so that Slackware can weather this sort of crisis well.

While a lot of people are talking about how vulnerable Slackware is since it depends on one person, it occurs to me that an awful lot of corporations with huge payrolls and assets seem to vanish like the morning mist. I don't feel any less secure by depending on Patrick and the enormous -- and enormously talented -- Slackware community.

i recommend that you consider moving to slackware-current entirely while pat gets squared-away, as slackware-current is currently way much smoother than 10.0 will ever be... one of the easiest and most effective ways to move to slackware-current is to install using slackware-current CDs... you can get weekly ISOs of slackware-current here:

ftp://ftp.slackware.no/pub/linux/ISO...ent-ISO-build/