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 have been experimenting with various Distros for a couple of years and am currently working my way around Debian and Slackware on a couple of spare PCs.
Both are challenging and I really like the way Debian upgrades etc with Apt-get.
Debian is really well documented on forums such as this and elsewhere, so when I get problems I read and search etc.
Slackware i find easier to use and more up to date, but I cannot figure how to apply the latest patches and upgrades such as new librarys etc. How do you keep Slack up to date?
Is the idea that you should upgrade to the latest version every time it comes out? I am on Slack 9.0. Maybe I have not figured out the Slack philosophy yet? I understand how Debian goes about how it upgrades etc and its 'committee' approach. No problems with that.
Thanks to all the experts out there prepared to help.
Well, slack works great out-of-the-box, but don't expect it to "evolve" on your pc: there's no real package manager, not to mention a repository. What you do is reinstall every 6 months a new release. Too bad the don't even use jigdo, so you must download whole iso from scratch.
I used slack 9.0 for a while, then when i needed newer libs for mozilla i simply moved to debian sarge.
I still promote slack for first-timers: it's much faster, smaller and cleaner than mandrake while being easy to install. It's probably useful, provided the get cds, for people with dial-up, too, who won't upgrade so often and are not exposed to high risk.
My advice is: don't try to keep slack updated via rpm: you'll soon end up with a caotic system. Use it while it lasts then move on. And keep your /home on a different filesystem
have you tried swaret? It's on the second CD in the extras/ directory. I don't think the repository is as refined as apt's but it does dependency checking for you. I find it quite handy for keeping up to date.
And, if you set version in the config to current, swaret will detect and upgrade all packages on the Slack mirrors that are newer than what you have now. Doing this can even bring Slackware 9.0 up to 9.1! It's great.
You might also want to check out slapt-get, an apt-like system for Slackware. I've personally stuck with swaret, but slapt-get seems to be updated frequently. The best site to know is linuxpackages.net. They have lots of slack packages and links to other sites. When I built this new box I tried both Libranet 2.7 and a hard-drive install of Knoppix, and I didn't see any particular difference in the upgrade processes if you're using Swaret or slapt-get.
And I love having the latest packages. With 9.1 being 2.6-ready, I'm hoping Slackware comes out with a 2.6 upgrade quickly after that kernel is declared stable. Maybe I can finally install onto my SATA drive.
Slack security updates are kept in the patches directory of the Slackware version on the ftp mirrors.
For example, ftp.slackware.com/pub/slackware/slackware-9.1/patches.
I usually download the changelog.txt and md5sums from there, then find the packages on one of the faster mirrors. I prefer to update my packages manually one at a time, since it does happen that a package can sometimes not work quite as perfect as it should. Also note that Patrick is very fast at releasing security updates, sometimes faster than just about anyone else. He also continues supporting versions of Slackware for a while, even after a newer version has come out. However, eventually, support for older versions gets quietly dropped, without any fanfare or official End of Life date. As a rule of thumb, I find that the latest 2 versions are supported and patched. (currently, 9.0 and 9.1)
Personally, I'm not too fond of swaret......I used it to update my system, which it did without problems. But when doing the dependency checks, I installed all the libs asked for. When it double-checked for dependencies again, swaret was asking for sane and xsane, which I did and then swaret was happy. But these two I didn't install when first installing Slack since I don't have a scanner
But that's not all. After a reboot, I get error messages about not being able to find my sound card drivers when starting up the GUI (KDE). I know how to fix that, by reinstalling alsa by hand, but this is a bit bothersome for me.
So now, I think I'll try slapt-get and see how that fares. Also, I've just installed checkinstall (which I found out about at linuxpackages.net) to keep track of any installs I do from source, so if I want to uninstall something completely (that wasn't installed with the package manager), I can do so.
Originally posted by zaphodiv
No kernel upgrade for 8.1 :-(
Building a kernel is one thing people who admin Linux boxen (and that includes keeping a home system up to date) should learn as early on as they can. It isn't terribly difficult, and updating kernels by binary packages is by comparison, just a really scary thing.
Well, I must say my bias against swaret is a little misplaced......at least about it breaking my sound driver. It seems that the culprit is not swaret, but the updated "alsa-driver" pkg. The same thing happened with slapt-get.
The only workaround I can think of offhand is to exclude the "alsa-driver" pkg from being upgraded until a fix is available. ......and exclude the sane/xsane pkgs that I don't need.
........And building kernels isn't that difficult. I'm a real Linux n00b, but am able to rebuild a kernel without too much problem.....the hardest part is in what to configure. The only advice I can give anyone new to Linux is to browse throught the /usr/src/linux/Documentation directory. You'll find a wealth of information to help you along