Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
In general, not just in Linux, if you find something that does 1 thing, it will usually do it well; the flip side; if you find something that does too many things, it usually doesn't do any 1 of them very well.
This does seem to be the case (for the most part) with konqueror. It does SO many things, but in very limited capacities, with very little tweak-ability (easily) and not very resourcefully.
However, this does not mean it will not work, it simply means you may be better off (you'll soon find out) with finding that application that does 1 thing, and does it very well.
To set your kde wide mp3 and ogg options just click on over to the Audio CD section of the Sound and Multimedia section of the kde control center.
I know you like konqueror, and I appologize that I shoot it down rather from my inability than it's lack of features. After all, due to a post from you long ago I can easily create my picture albums to host on my apache server (CTRL I)
Thanks Aussie. I looked at the settings in Audio CDs and didn't see anything that looked like it needed to be checked in order to make a virtual directory of mp3's appear when I type audiocd:/ in the location bar.
I've been scouring the KDE Control Center and help files and ran into this in the Help tab in Audio CDs :
Note that MP3 and Ogg Vorbis encoding are only available if KDE was built with a recent version of the LAME or Ogg Vorbis libraries.
I know my KDE was not build with any version of LAME because my sytem (Slack 9) didn't come with it and I just downloaded it (LAME) a couple of days ago.
Now that I have LAME, what kind of task is it to rebuild KDE? Not really knowing anything about how to do it, it seems enormous, KDE has so many little applications. Is this something that an intermediate-newbie could undertake?
I build kde from source, it takes a bit of time to build everything but you should be fine building kdelibs, kdebase and kdemiltimedia only, but since there has been a kde update since slack 9 came out you might as well build it all.
I would recomend downloading a copy of the slack build scripts, you can find them in the source directories on any full slackware mirror, you can change a few options before you run them, I set my flags for athlon-tbird instead of i686 when I use them.
I think I'm going to just build kdelibs, kdebase, and kdemultimedia so I stay with the old version of KDE (3.1) so when I have questions in the future I'll still have the same version as most (some?) of the rest of the Slack 9 community. I can just see having a problem in 3.1.1 and everyone answering "works fine for me in 3.1".
What preparation do I need to do on my current machine as far as the current kdelibs, kdebase, and kdemultimedia packages go? Uninstallpkg on them? (originally installed via main Slackware 9 install) Will this break things that the new compiling from source won't fix?
I took a look at the build scripts on the Slackware mirror and it looks like they rely on the directory structure that exists on the Slackware mirror. Do you edit all the scripts, or recreate the directory structure on your harddrive and then place the source files from KDE in the proper directory?
To followup for anyone who may follow this thread in the future, here's what I did to get the mp3 ripping on the fly working in kde.
Previously I had downloaded and installed lame-3.93.1 from linuxpackages.net.
I used pkgtool to uninstall all kde packages.
My strategy was to recompile version 3.1 kdelibs, kdebase, and kdemultimedia, just to see if the thing worked (upgrade to 3.1.1a will wait until I have a bigger chunk of time). The Slackware mirror has some build scripts that help automate the compilation and installation of kde. KDE.SlackBuild is the master script that calls individual scripts for each package, e.g. kdelibs.SlackBuild, kdebase.SlackBuild, etc. Comment out the packages you don't want to compile and install. Also make sure to download the KDE-VERSION file if you're going to use the scripts as they refer to this file to determine the version number used in the names of the .tar.bz2 source files.
I recreated the mirror's directory structure for those three packages, including all subdirectories and downloaded all files for each directory. It's important to get all the files, not just the .tar.bz2's, because the scripts have a few patch/configuration routines embedded in them, for which you'll need those extra files.
I ran into an error during the configure of kdebase: xmkmf couldn't be found. I had it on my system, but it wasn't in root's PATH. After I edited the PATH, I reran the KDE.SlackBuild script and everything seemed to go through without a hitch. It did take the script a little over 2 hours to compile and install these three packages on a P4 1.5GHz machine.