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.
Hi, I'm a new Slackware user, but I have used another distributions like Fedora. I recently installed Slackware 10.2, and I don't know what to do know.
In fedora, after the installation was accomplissed, I download the latest packages and dependencies that were available at the moment, with the command "yum update", and it was really easy.
Now I don't know if it is similar in Slackware, I haven't found yet how can I do the updates to my packages, kernel and dependencies.
The best way to keep slackware up to date, is to simply go to any mirror, and download the packages in the patches/ directory. Make a folder in your home directory, and download all the packages to there. Then upgrade each package with the following command.
Read the changelog to see of there are any special instructions. For example, if there is a new package, or something has changed its name, you can use 'upgradepkg --install-new'. Here is a slackware mirror.
Click on patches/ , and then read the ChangeLog.txt. Then click on packages/ where you will find all the updates. There are automated tools, but they can get you into trouble, and it's always best to read the changelog.
You could use something like KSlackCheck. It will check what you have installed and give you a list of packages to upgrade. It won't install anything, so you don't have to worry too much about hosing your system. If you are going from 10.2 to 11 or current, you REALLY, REALLY, REALLY need to read UPGRADE.TXT or the CHANGES_AND_HINTS.TXT in current.
I have already downloaded those packages in the mirror you gave me, and I was upgrading them, until the OS crashes, first, it didn't recognize any command at the console, and I restart the computer, and it doesn't allow me to enter to Slackware.
It show's me this error:
INIT: cannot execute "/sbin/agetty" (Several times)
INIT: no more processes left in this runlevel
Try booting in single user mode and reinstalling the updates. Install all the glibc packages first, and then the other updates. To boot in single user mode, append the word 'single' at the lilo boot prompt. When you get the lilo boot screen, hit the <tab> key and then type whatever your lilo entry is called, followed by 'single'. So if your menu entry is called Linux, you would type
That will hopefully boot you into single user mode. Then cd to where your updates are. Start with the glibc packages, and use this command.
Did you get it sorted in the end SlacUser? I hope you haven't been put off using Slackware. I'm not sure why you had problems with the updates. Updating glibc shouldn't have been a problem as it was a patch and not a version change. So I'm not sure what went wrong there.