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.
Actually all I ever do is just sit in kde, pop open konsole and cd to the dir where the packages all are and just do 'upgradepkg *'
Sit back and wait a few minutes. Then log out of kde back to kdm and just do 'ctrl+alt+backspace' to restart X. You now have kde 3.4
Or if you don't start in init 4 then just exit kde back to commandline and then just 'startx' and kde 3.4 will come up.
If you're unsure about doing it while in kde don't worry. All that is happening is yes you are putting in a new kde but heres the cool thing, you can use kde while upgrading its packages because kde is all sitting in RAM. So you can still use konsole and konqueror and some stuff without any problems. Heck once I forgot to restart X after a kde upgrade and used the kde that was in RAM for like 2 or 3 days without even noticing.
Cool. What about the 10.1 vs. 10.0 issue? Ideally, I'd like to install KDE 3.4 right onto 10.0, because I don't think 10.1, minus KDE 3.4, justifies the upgrade (to me, at least). However, if I have to install 10.1, I'd like to know how to do it while preserving all my settings.
Originally posted by apachedude Cool. What about the 10.1 vs. 10.0 issue? Ideally, I'd like to install KDE 3.4 right onto 10.0, because I don't think 10.1, minus KDE 3.4, justifies the upgrade (to me, at least). However, if I have to install 10.1, I'd like to know how to do it while preserving all my settings.
Actually, if the packages for KDE 3.4 were compiled using 10.1 you *might* run into some problems with the different versions of glibc. Not saying you WILL run into problems, but you MIGHT.
Originally posted by Namaseit You mean like all your desktop settings and window preferences etc.? Just save your user directory. Everything Is in there related to specific kde settings.
I meant more on the lines of Slackware 10.1 vs. 10.0. For example, I want to keep the kernel I custom-compiled, the udev rules I wrote, etc. I'm sure I forgot some stuff. I could live if I lost my program files...
Oh, well if you want to keep your kernel there is a couple ways you could do it. Just save the .config file in the kernel source directory as something like 2.6.11.config and then when you extract the sources into your newly installed system just copy the 2.6.11.config back to the kernel source directory as .config and then just 'make && make install' and you now have the same kernel. The other way is to save the sources directory and your bzImage and modules but that is a hassle. Saving one little file is so much more easier. It doesn't take long to compile the kernel anyways.
Originally posted by tw001_tw Seiken - worse comes to worse, install kde again from CD#2. Then you can research
and try again. OR you can use anather WM (XFCE?) in the mean time.
So besides adding /opt/kde/bin to your path, have you tried cd'ing to /opt/kde/bin and
then trying it? and/or verifying its there?
I'm still downloading 3.4.0 at a painful 45K/sec - just about there though.
Yes, I have tried adding to my path and running from /opt/kde/bin, still no go. I ended up removepkg'ing all of the kde packages, and then adding arts, kdelibs, and kdebase, and now I can open konqueror again oh, and k3b too. only thing I miss now is how when I ran "konqueror /home/josh" before, it had all my mounted drives (cd, dvd, etc) listed under Devices in the left window. now Devices is empty.
Thanks for your suggestions. PS: I tried XFCE yesterday too, but so far I'm liking E better.