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've heard a few times, that this is a bad idea, and shouldn't be used as an easy way to upgrade many packages at once. Is this true, or can I safely use it?
I especially worry about it trying to upgrade the kernel packages...
I have tried it before and basically broke everything and had to reinstall, but I didn't exactly know what I was doing or how to go about it, and I think I used a -current mirror instead of the correct version. So I'm wondering if there is still a way to do it, without annihilating the install.
Thanks in advance for any info!
(By the way, I'm using 12.2, and will use a 12.2 mirror to do this.)
Last edited by ryan858; 08-31-2009 at 02:16 PM.
Reason: including some info...
I use slackpkg on quite a lot of Slackware machines, and always run "slackpkg update ; slackpkg install-new ; slackpkg upgrade-all".
But, I like to do the kernel updates myself, so I add kernel, kernel-generic, kernel-huge and kernel-modules to the blacklist file /etc/slackpkg/blacklist. That way, slackpkg will only upgrade kernel-sources and kernel-headers (which is the desired way).
By the way, I never use "upgradepkg" for my kernels. I always use "installpkg" to install a new kernel package (plus the modules package) and add this new kernel to /etc/lilo.conf (and then run the "lilo" command). That way, if the new kernel turns out to be broken I can still boot into my old kernel. When the new kernel tests fine, I "removepkg" the old kernel and it's modules, remove this old kernel from lilo.conf and re-run lilo.
Another thing to pay attention to before upgrading from version 12.2: it is to read the UPGRADE.TXT and CHANGES_AND_HINTS.TXT files available in the root directory of the DVD (or first installation CD).
They contain valuable information about changes and points of attention that may cause havoc is not properly managed (ex: due to KDE4, move your old $HOME/.kde directory).
Otherwise, I also never had any issue upgrading using slackpkg tool. The tool is rock solid.