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.
I believe SUSE has its own packaging system so I'm not sure how it would work for that. For Slackware, I have had some luck with rpm2tgz and it's worth a try (it's just not 100% effective). It might take some time to redownload everything, but most applications do provide source code and it's not that difficult to install that way once you get used to the process. In fact, that's one of the things I like best about Slackware. I install almost everything from source which gives me control and shows me exactly what's being done, and then use checkinstall instead of make install so that it is installed as a package that can easily be viewed and removed.
tools like rpm2tgz and alien are great as last-ditch alternatives. The situation I have used them in is where someone provides a binary RPM, and no source code. In any other case, there is always a better alternative.
In other words, converting all your old RPMs to TGZs and trying to use them in slack is going to be a mess. Truthfully, even taking them into a distro like Red Hat or SuSE which natively uses RPMs would be messy too.
Chances are good that you will find slack packages if what you need, especially at linuxpackages.net. If not, in almost all cases you can find source. Its really not as hard as you might think to compile from source, and truth be told, you'll need to learn eventually. They usually come with instructions. I reccomend using the tool "checkinstall" which i believe is in slackware /testing or /extra when compiling from source, as it makes for a cleaner system...which means its easier for you to remove things later
Had a look at all the rpms/stuff I downloaded. A lot of it (~75%) is source code and of the rest I seem to remember that the source is available.
Any other tips, like on installation/cofiguration?
I have, at one time, had both Mandrake and Slackware installed, on different partitions, and seem to remember that I couldn't get the sound, samba or LAN to work properly. Also, It apparently didn't see the DVD drive.
Originally posted by OhMyAchingGut I reccomend using the tool "checkinstall" which i believe is in slackware /testing or /extra when compiling from source, as it makes for a cleaner system...which means its easier for you to remove things later
Tell me, would I have to recompile the kernel to use "checkinstall"?
I'd recommend using the checkinstall from a slackware mirror, the other one will work, but I've found at least in my exp. it seems to sometimes screw up the symlinks created during install, also the one from the slackware mirror has been modified to only make slackware packages:
Originally posted by __J I'd recommend using the checkinstall from a slackware mirror, the other one will work, but I've found at least in my exp. it seems to sometimes screw up the symlinks created during install, also the one from the slackware mirror has been modified to only make slackware packages: