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.
One thing I noted is a strange behavior - time to time - of a mouse. It runs out to an edge of a screen. Also a communication between a mouse and the desktop works not well as sometimes moves of mouse is interpreted as clicks.
This may be some kind of coincidence, but some time ago, when I was still using slackware-12.x with kde 3.5, I had problems with mouse behavior, similar to yours. I simply thought it was broken, so i changed it. Never had those problems again. (The device was a cheap "Manta", first optical mouse I had)
I've been running a Slackware 13.1 64-Bit system with KDE 3.5.10 for about 8 months now, you can make a Slackware 13.1 64-Bit system running on KDE-3.5.10
By Using "menu selection" during the Slackware64 13.1 install and "DO NOT" installing any of the KDE packages, and "DO NOT" installing: QScintilla, attica, automoc4, phonon, qca, qca-cyrus-sasl, qca-gnupg, qca-ossl, qimageblitz, qt4, qtscriptgenerator, and Soprano from the l directory. Then proceed with the rest of the installation as normal.
After rebooting the machine, install the all the KDE 3.5.10 packages from Slam64 12.2 and arts, dbus-qt3, qca, qca-tls, qt3 from the l directory of Slam64 12.2. Reboot the machine, and issue a
select the KDE desktop.
I've been able to compile and run most programs from places like Slackbuild, although sometime I trouble figuring out if I need to use the Slackbuild 13.1 or 12.2 script.
haha , So , lots of website ( for example facebook, youtube ,even the website which to change password in google code) are blocked in my country .So sad It made me ... But linuxquestions.org has escaped .
ennorie , Thanks for your link . Although it's remain 5~6 hours to download the file ...
Don't let it keep you sad, it's not worth it.
It will change in time as the old guard slowly die out, just like it did in Russia.
And as technology becomes even more influential on our daily lives, it'll make it harder to censor communication.
The Internet has already made it possible for you to communicate freely with the rest of the world.
When I was growing up behind the iron curtain in the 70s before I defected, the only (one way only) communication was the Voice of Free Europe which I'd listen to at night on short wave radio pressed to my ear and reception was really bad and breaking up all the time.
So just live you life to its fullest and don't let politics depress you.
Oh yeah, and don't get caught
Is there a place online to download your build scripts? My ISP prohibits file sharing in any manner. I can't use torrents.
3.5.10 needs many patches for gcc 4.x, python 2.6, etc. Do you have those patches available somewhere?
I see the link above for the large tar from rapidshare, but does that download include build scripts and patches?
Regarding do not install QScintilla, attica, automoc4, phonon, qca, qca-cyrus-sasl, qca-gnupg, qca-ossl, qimageblitz, qt4, qtscriptgenerator, and Soprano from the l directory --- does that mean when building too?
There is a script for downloading the source code with all patches included. You can find it in the tar archive. If you want I can send it to you by email. Just send me your email adress by PM.
As for Qscintilla and others - i didn't remove them at all. I just didn't install kde/ series. To be honest - I don't really know if it's a good approach.
Did you use KDE.SlacBuild? Try building every slackbuild manually - I did it that way - just remember to follow package building order found in the KDE.SlackBuild. It's much easier to track errors if you do so. In case of error just paste the error output here - I'll try to help. It's very unlikely that I've forgot to include any patch, but it's possible...
How did you download the source? Did you use my script? Did you have 'kde_source.diff' and 'l_source.diff' in directory which contained 'download_source.sh' file?
And finally there is another possibility. I just thought that there is a bug in my script. If you try running it from a directory different from the one that it actually is in, you will run into problems with patching.
For example: if your files are in /some_path/directory/ and your `pwd` is /some_path/ and you try to run the script by using a command
You'll end up with an error saying:
cat: /some_path/l_source.diff: No such file or directory.
Hmm... I can't seem to find a patch in there anywhere.
while it's obvious, that the file is located in /some_path/directory/l_source.diff