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.
I'll try to answer my questions to the best of my ability so here we go:
When you './configure\make\make install' the stuff you just compiled and installed is probably going to end up somewhere in /usr/local/. Most likely you will have everything you need to run the program because ./configure usually spits out error messages if you're missing something vital.
Yes you can remove those source subdirectories. You might want to hold onto the tarballs however, because if you need to uninstall the program, you untar the tarball and run make uninstall in that directory. A better way to go about all this though is to use checkinstall. checkinstall takes a compiled program and makes a slackpack out of it and installs it. This way the program can be uninstalled with 'removepkg /var/log/packages/package-name' and you don't need to keep the source, the slackpack, or the original tarball around. So after you install checkinstall your series would go './configure\make\checkinstall'. Answer the questions and you're golden.
The permissions thing probably has to do with the permissions of device /dev/rmt0. You'll need to set the permissions of that to the correct settings. At least that's what I think, but I don't do anything with tape drives so it could be something else.
> When you do a , ".configure", "make" or "make install" how do you know where the files are copied to ?
don't do "make install", rather run checkinstall. it will create tgz package for you and install it. then you can easily see the content of the installed package (via /var/log/packages) or eventually remove the package. other than this you can still find out by reading Makefile (but i wouldn't recommend this to a confused linux newbie..)
> Are they in the right libraries etc. ? How do I determine if they are ?
configure and make can assure you.. they are
> Can I now "rm" my subdirectory containing the untar files ?
well, why not. but if you didn't create the package using checkinstall you will lose the option to cleanly uninstall the program (while having the tarballs you can still run make uninstall - and hope it will work..).
> Also, about permission - a user (km) gets "permission denied" running "mt -f /dv/rmt0 rewind" although the "/bin/mt-st" has a+rwx permission.
Originally posted by kgm
Do you always do "./configure","make", and "make install" on every tarball
you install or does this sequence changes depending on the file ?
Sometimes the sequence is different; for example programs done in python usually are built with 'python ./setup.py build' and installed with 'python ./setup.py install'. I've also had experiences with perl programs compiling with different commands. Look at the ReadMe and INSTALL files that should come with the program for instructions.
How do I get "checkinstall" ?
With SWareT: 'swaret --install checkinstall'
With slapt-get: I'm not really sure but there probably is a way.
You can also download it here.