SlackwareThis 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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ok ok I knew I shouldnt have done it, but hey, linux is about learning right? anyways if you havent guessed it by now, I tried to remove my glib packages, I was going to upgrade them. I've never done it before for just important libraries. When I normaly upgrade packages, I remove the old one and put in the new one. You see I wanted to use gimp2.2, but it needed a higher verson of gtk+, after that I needed a newer version of X11, and then that needed new glib packages, haha quite a mess huh?
So how should I go about fixing it? I have the slackware 10.0 cds on my windows harddrive and a 512mb usbdrive. Slackware is and all its packages are fine except for the glib ones(glibc, glib2, glibc-solibs, glibc-zoneinfo) How can I just put those packages back with out having to reinstall?
OH and Merry Chrismas and a happy New Year, I got some cool presents that should keep me happy while I await a reply.
...... i just want to die, why is it that when I do these crazy things, I never read the readme files? oh well. I thought I just update that part. hehe I didnt know about upgradepkg for some strange reason. So any ideas as to help me?
HI.
do you have (can burn from windoze) slackware disk2? if so - boot from it, mount your slackware partition lets say to /mnt/slack then mount the cd1 via loopback device(or copy the needed packages from it somewhere in the first place) and
Thanks for the command! I dont have a cd burnner hehe but maybe now I'll get one. Anyways after fruitless trys to get my usb flashdrive to boot, I used my good old windows98 boot disk to use loadlin. From there I was able to do what I needed to do. But It seems that somethings were also affected buy upgrading glibc and glib2. I'm going to upgrade the sysvinit package, is there any other base packages that I should upgrade?
ok so I downloaded the whole /a stuff from slackware-current but i'm stilll having problems. I get errors about /sbin/agetty and not being able to execute it. and I upgraded that package too. also when I change inittab to not make so many terminals, i'm able to see an error that I couldnt see before. It seems its not able to run rc.S I checked my /etc/rc.d and found some rc.*.new files, changed them to the right names and backed up the old ones. Still no go. Any other ideas?
I'm listing all my steps just in case someone else is in my situation.
After booting up slackware from windows using loadlin (if you have the cd the by all means use that) I was then able to use ROOT=/dev/hda3 upgradepkg *.tgz just so I could upgrade everything to make sure it was uptodate. If you plan on upgrading your glib packages, you will need to upgrade everything in the /a and /l folders from slackware-current. After that use ldconfig -root /path/to/root/drive that was something I forgot to do and took a while before I figured it out, hehe seems ldconfig can fix most about anything. After that just check some config files to make sure everything was in place. I'm not sure what this might do but after updating, in my rc.d folder I had some rc.*.new files, so i replaced the old ones with them. Might not make a difference but diff showed there was a difference between them. *NOTE* since the kernel packages were in the /a folder, they got installed too. This seemed to remove all my modules from the kernel I was using. a simple make modules and modules_install fixed that, but the same thing happened when the alsa packages were upgraded. Just did the same thing. after that everything was running great in text mode so I switched over to X. Since I had to upgrade X too, there was one slight problem. it seems that the xorg.conf file is case sensitive and wouldnt load the keyboard driver since it was "Keyboard" fixing the K to k let X run. Also if you are like me and like to have kdm insted of gdm, you have to edit rc.4. I guess thats it. haha all that just to get gimp-2.2 running. Well I learned some new tricks so I'm happy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.