SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I will shortly install slackware current and was wondering if there is a way to follow the updates to current easily.. i.e. can I just install updated packages over old ones, or is something more intricate required?
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
If you don't have experience with Linux (I have no idea if you do or not),
I would suggest you stay one release behind. The slackware-current is
bleeding edge, unstable, development type of stuff. It'll probably crash,
things won't work the way you expect. If you have experience with
Linux and you want to tinker, then by all means use slackware-current.
In order to keep up with the changes Patrick makes, I would suggest you
become a good friend of pkgtool and upgradepkg, download the new
packages into a directory, maybe /var/spool/packages, then use pkgtool
or upgradepkg to install the new SW.
I didn't see an rsync server on the get-slack page, so it may be a little
bit of work to keep up with the changes being made. . .
Slackware-current is actually fairly stable, as Peter doesn't usually include packages that aren't considered to be stable by the developers. I am currently running slackware-current on my home machine and the only package that isn't a full release version is aalib-1.4-rc5. Now if you go for packages in extra you might find some instability.
Thanks for the help. I am experienced with linux (since 1997), but have mainly used debian up until now. I have been using slackware for 6 months and far prefer it.
Just one more question about updating slackware-current: is there a list somewhere that anounces when updates are made. slackware-announce doesn't seen to carry these...
Also note that it seems that some mirros are lacking behind a lot with the slackware-current. Atleast ftp.slackware.at seems to be fairly well up to date. (ftp.slackware.com is usually very slow so you probably want to use mirrors)