Hello everybody!
It is my first post here!
I used to use slackware when it was slackware 7.1 or so, with 2.2 kernels.
At those times it was not completely safe to just upgrade to slackware current, it was sometime buggy.
Now it seems this has become a common habit among slackware users. I have just installed slackware 10.1 and I'm not sure if sync to current or just do security upgrades. What do you advice?
Thanks in advance and please forgive my funny english!

It really depends on whether you are willing to take the risk. Current is usually stable but sometimes some packages can have minor problems.

I personally don't run current until Pat gives it a number. But I will selectively grab a few packages when Pat makes something I want, such as firefox.

It should be alright. I don't upgrade to -current for my desktop, but that's because I'm behind a firewall, I have server-side antivirus for my proxy and mail, and because I subscribe to the "if it ain't broke, don't fix it" philosophy.

On my sever, however, I subscribe to the mailing lists for Sendmail and all of the other server software running, and I usually have them updated within a day or two.

Where do you look for packages made by pat? linuxpackages.net (used to be linuxmafia.org for me or slackware.com?

I made my original question because I read the very good guide in this forum which mentioned swaret.
To me slackware lacks a real good package method, especially as far as concerned dependences. I don't like RPM neither, for this reason I usually build my software from tarball sources...

Slack's package tool is specifically written to ignore dependancies. That allows for a leaner package, and a faster install. A Slack package is basically a tarball (.tar.gz), and if you were to extract it at the root, you'd get basically the same effect as instaling the package.

If you want a package tool with support for dependancies, but don't like RPM, use Debian's apt-get. It's really good.

I think, however, that he meant that he waits for official releases of Slackware. IOW, he's currently running 10.1, without upgrading anything (except probably his Firefox/Thunderbird installation). When Pat releases the next version, probably Slack 11, he'll upgrade. Until then, he'll stick with what he's got.

10.1 works. I'd keep it ;-)

i get my packages from slackware.com. i use slackpkg to keep my distro current, and have only had one minor problem, which was actually my fault for not reading the changelogs before i installed something. once slackpkg is installed, you have a long list of mirrors to choose from, but they only offer packages that ship normally with slackware, or are added by pat after the fact. linuxpackages.net is where i find packages i need, if i'm not compiling them from source.