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.
The mirror that you have selected in /etc/slackpkg/mirrors probably hasn't synced with the official slackware server yet, so either give it a few days or try picking another mirror. I'm using the mirrors.usc.edu mirror, and it has the latest security patches.
slackware-current is the mirror that contains the newest releases of certain programs, including Mozilla Firefox (6.0.2 is in slackware-current).
You should be very careful doing this, or not do it at all. Many (most?) packages from current will not run on 13.37, and you will easily bork your system this way. I think that Firefox is a repackaged binary, so it _might_ work in this case, but for the most part mixing 13.37 and current is just asking for trouble. 6.02 is available in the /patches directory for 13.37. If you really want the newest releases of programs which are in current but not 13.37 you should either try to build them yourself on your 13.37 system or upgrade the whole system to current with the understanding that current is by its nature unstable.
No. That is poor advice as the OP will then inadvertently upgrade his/her unit to slackware-current (the development branch of slackware). The best advice is to wait until your present mirror syncs with the official slackware mirror or choose a more up to date mirror. I use this mirror for slackware 13.37.
The only things I alter are /etc/slackpkg/slackpkg.conf
And uncomment a mirror in /etc/slackpkg/mirrors. I've never noticed this before, just reading http://lwn.net/Articles/457899/rss made me notice my version of firefox wasn't the same as the patch. When I update I do...
Wrong order... You should instead (moreover when you're on current):
slackpkg install-new # <- this first is recommended
install-new might installs dependencies or tools required for the following upgrade-all
slackpkg clean-system # <- if on current or upgrading from a previous version...
Btw, you can upgrade from versions using slackpkg, but you should first upgrade packages in a specific order which should be explained in the UPGRADE.TXT. And as said, it's not recommended to work with current, although if you don't rush on the last minutes updates and check this forum, you should be able to maximize your chance to have something quite solid .
Last edited by NoStressHQ; 09-08-2011 at 02:40 AM.
And as said, it's not recommended to work with current, although if you don't rush on the last minutes updates and check this forum, you should be able to maximize your chance to have something quite solid .
Agreed. If you're going to run slackware-current you are expected to be able to trouble shoot and solve some problems on your own. It is a very good idea to read the current changelog before you add new updates as there will on occasion be information to help you to avoid pitfalls, gotchas.