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.
Heres what happened. I had the bright idea of changing the slapt-get config to point to the current ftp rather than 10.0. after a few hours of donwlaoding it upgradedmy system with all the new packages. my problem now is that kde wont start. it looks like it starts correctly but then in the top left corner i get a white box that says could not start kdeinit. chck your installation. then i click ok and it goes back to console where i get many errors about eror while loading shared libraries: libidn.so.11 any help would be great since i really dont want to have to format and reinstall.
I'm not sure when you did all this, but "-current" is on the verge of becoming 10.1. As such, PV has added updates to aaa-elflibs:
a/aaa_elflibs-10.1.0-i486-1.tgz: Updated initial library collection.
Please remember that (as the package description notes) this package is
only intended to be installed at an initial installation, and attempting
to "upgrade" it later may copy over newer libraries and cause damage to
your system. Some broken upgrade tools haven't learned this fact...
This update WILL completely hose your system.
This is why one MUST read the changelogs if you are running current. If this is the case, a complete re-install is likely in order as all of your libs have been overwritten.
Hopefully this is not the case and my previouse post will solve your problems.
oo thank you muchly i know it seems like a really newbish thing to ask and im not al that linux affluent but i tend to install msot of my programs from source rather than packages and this is like the first time ive used slap-get sorry for the annoyingness of the question.
Originally posted by zwyrbla oo thank you muchly i know it seems like a really newbish thing to ask and im not al that linux affluent but i tend to install msot of my programs from source rather than packages and this is like the first time ive used slap-get sorry for the annoyingness of the question.
No apology needed. Many people know how apt-get works in Debian systems and they "assume" slapt-get/swaret solve all the upgrade/install/dependency problems the same way. They make the update process a little easier, but you still need to read the changelogs to get a real picture of what is being added/subtracted/updated. Slackware is a "thinking" person's distro and is very simple to administer so long as you don't chuck the "thinking" part when you choose to use these 3rd party package management systems.
Reading the changelog on a regular basis if you are running -current is a MUST - period.
The fact that you compile most of your programs from source shows you have picked the right distro. Slack makes that easy. Easiest distro for compiling a kernel as well (IMHO).
I'm assuming from your following post that you got things running OK.
Can't help you much with alsa I'm afraid - but knowing your sound card may help me/others to help you....
Distribution: slamd64 2.6.12 Slackware 2.4.32 Windows XP x64 pro
There was and addition of a lib and a driver name change that will not be resolved by swaret or slaptget.
Sorry man swaret does get the lib, slapt-get doesn't, so thats why I use swaret. Also if you updated kde you need to del /tmp/kde-username/sycoca otherwise you get a whole bunch of errors on the console screen and in the logs.
Originally posted by tormented_one Sorry man swaret does get the lib, slapt-get doesn't, so thats why I use swaret. Also if you updated kde you need to del /tmp/kde-username/sycoca otherwise you get a whole bunch of errors on the console screen and in the logs.
I stand corrected
I don't use either (swaret for a while), but rsync -current to my server and use upgradepkg.