Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
04-23-2007, 10:04 AM
|
#1
|
|
Member
Registered: Apr 2007
Location: México
Distribution: Slackware, Fedora
Posts: 61
Rep:
|
Slackware Update
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.
If someone can give me a tip or sometime, Thanks.
|
|
|
|
04-23-2007, 10:27 AM
|
#2
|
|
Member
Registered: Mar 2005
Location: UK
Distribution: Slackware
Posts: 794
Rep:
|
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.
upgradepkg NAMEOFPACKAGE.tgz
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.
http://ftp.osuosl.org/pub/slackware/slackware-10.2/
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.
Last edited by simcox1; 04-23-2007 at 10:29 AM.
|
|
|
|
04-23-2007, 11:45 AM
|
#3
|
|
Member
Registered: Aug 2006
Distribution: Slackware
Posts: 767
Rep:
|
KSlackCheck
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.
|
|
|
|
04-23-2007, 02:15 PM
|
#4
|
|
Senior Member
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,513
Rep: 
|
KSlackCheck is very good, indeed.
A command line alternative is slackpkg. It's in /extra on one of the Slackware CDs.
To apply security fixes and important patches, just type (as root):
# slackpkg update
# slackpkg upgrade patches
That's all there is to keeping "official" packages up-to-date. If you have 3rd party packages installed, it's up to you how to keep them up-to-date.
gargamel
|
|
|
|
04-23-2007, 03:33 PM
|
#5
|
|
Member
Registered: Nov 2006
Location: Slovenia
Distribution: Slackware 13.37
Posts: 511
Rep:
|
i use slapt-get for this
|
|
|
|
04-23-2007, 03:52 PM
|
#6
|
|
Member
Registered: Apr 2007
Location: México
Distribution: Slackware, Fedora
Posts: 61
Original Poster
Rep:
|
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
|
|
|
|
04-23-2007, 04:11 PM
|
#7
|
|
Member
Registered: Mar 2005
Location: UK
Distribution: Slackware
Posts: 794
Rep:
|
Which package were you upgrading when it crashed?
|
|
|
|
04-23-2007, 04:55 PM
|
#8
|
|
Member
Registered: Apr 2007
Location: México
Distribution: Slackware, Fedora
Posts: 61
Original Poster
Rep:
|
I was upgrading these packages:
glibc-profile-2.3.5-i486-6_slack10.2.tgz
glibc-i18n-2.3.5-noarch-6_slack10.2.tgz
glibc-solibs-2.3.5-i486-6_slack10.2.tgz
After these pachages, the console did not recognize any of the commands, neither reboot.
|
|
|
|
04-23-2007, 05:08 PM
|
#9
|
|
Guru
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,818
|
Upgrading the glibc packages is not something to be taken lightly, as it has significant effect on the rest of the operating system.
Did you follow the notes in the UPGRADE.TXT and CHANGES_AND_HINTS.TXT files as you were instructed to earlier?
|
|
|
|
04-24-2007, 02:38 AM
|
#10
|
|
Member
Registered: Mar 2005
Location: UK
Distribution: Slackware
Posts: 794
Rep:
|
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
Linux single
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.
upgradepkg --reinstall NAMEOFPACKAGE.tgz
And then reboot. Control-Alt-Delete.
|
|
|
|
04-25-2007, 01:40 PM
|
#11
|
|
Member
Registered: Mar 2005
Location: UK
Distribution: Slackware
Posts: 794
Rep:
|
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.
|
|
|
|
04-25-2007, 02:13 PM
|
#12
|
|
Member
Registered: Apr 2007
Location: México
Distribution: Slackware, Fedora
Posts: 61
Original Poster
Rep:
|
Thanks, I reinstall the packages and I upgrade them with Slackpkg.
Thanks you all =)
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 11:42 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|