Linux Administration: Installing Software - Installing the Package and Testing the Software (Page 6 of 10 )
As with the compile stage, the installation stage typically goes smoothly. In most cases, once the compile is done, all you need to run is
[root@ford hello-1.3]# make install
This will start the installation script (which is usually embedded in the makefile). Because make displays each command as it is executing it, you will see a lot of text fly by. Don’t worry about it--it’s perfectly normal. Unless you see an error message, the package is installed.
If you do see an error message, it is most likely because of permissions problems. Look at the last file it was trying to install before failure, and then go check on all the permissions required to place a file there. You may need to use the chmod, chown, and chgrp commands for this step; see Module 6 for additional details.
Testing the Software
A common mistake administrators make is to go through all of the process of configuring and compiling and then when they install they don’t test out the software. Testing the software also needs be done as a regular user, if the software is to be used by non-root users. In our example, you run the hello command to verify the permissions are correct and users won’t have problems running the program. You will quickly change users to make sure the software is usable by everyone. We’ll cover the su command in Module 6.
[root@ford /]# su - sgraham
[sgraham@ford ]-> /usr/local/bin/hello
Hello, world!
[sgraham@ford ]-> exit
[root@ford /]#
 This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.
Buy this book now. |
Next: Common Software Problems >>
More Administration Articles
More By McGraw-Hill/Osborne
/ 29 
