Installing programs under linux...

[Ziphnor]

Coming from Windows im having a bit hard to understand how Linux manages installed programs? In Windows programs are usually dependent on a few DLL's and perhaps a registry entry, but most will run by just being copied into some dir. But these linux programs seem to distribute their files all over my harddrive, and i still dont understand the RPM system.
I managed to install WebDownloader for X and a few other programs. but they always give an error( it just displays a file/package name? ), after that some programs work fine, but others dont(Java 1.3). Also, its rather confusing looking around the file structure, i have no idea where anything is, or ought to be, where are systemfiles stored? etc.
Is there somewhere where i can get a quick overview over subjects like this?(Please, no lengthy extremelly technical HOW-TO that starts talking about recompiling the kernel :)

[WeDeliver]

If you are using RPM, just remember a few switches:

-i = install --rebuild = self explanatory.

If a file has an RPM extension but a 'src' in it, and does not load, try the '--rebuild' switch.

Many programs do need to be recompiled. Without explaining, just try this:

Download the program, gunzip it if it ends with a '.gz' extension. Then, if it ends in a '.tar' use the command 'tar -xvf filename'. It will extract in the same directory. Next, try typing './configure'. If it does nothing or gives errors, try using 'make'. After it finishes, it may still not give you an ok, or after the './configure', it may not take to 'make'. In this case, try 'make depend $$ make'.

Also, always look for an "install" file. For instance, "SimCityinstall*". In this case, just typr './SimCityinstall' and let the script do everything for you.

Oh yea, another tip, when trying to make or install a program, look closely at the errors, they will usually tell you why the install didnt work or what you need. If the program doesn't seem to generate errors but fail, try redirecting the errors to a file. You can do that with a '2>' command. Example:
"./SimCityinstall 2> /usr/errors" - that would try to run the install script and place all error messages in a file named 'errors' in the /usr directory. You could then just 'cat /usr/errors | more' to view the error messages.


Hope that helped. :)

[ 28 April 2001: Message edited by: WeDeliver ]

[bdg1983]

Check out Directory Navigation NHF (http://www.linuxnewbie.org/nhf/intel/filesys/directory_nav.html). It explains pretty clearly where all the files go (and not a single word about compiling kernel ;))

[Ziphnor]

That NHF was pretty good, now i dont feel completely clueless.
But maybe i should explain a bit more of my install woes. I tried using the packagemanager that automaticly pops up with RedHat 7.1(kpackage), it is this programs which gives me an error. The only reason i know its an error is because the titlebar says error the text just mentions a file(i think) name, like jdk-1.3.0_02-fcs...
If i try rpm --install it seems to work, but when i go find the java or javac files and try to run them on Java class or source file i get an error on some missing files i think.
The error goes something like this:
./java: /usr/bin/cut: no such file or directory
/usr/java/jdk1.3.0_02/bin/nativethreads/java;
error while loading share libraries: libjvm.so: cannot load shared object file: No such file or directory.

Im currently downloading the second image file of Mandrake 8.0 ill think ill give that a spin instead ofRedHat since many people seems to find it more userfriendly.
No matter how it turns out im convinced enough about linux to keep it on my HD. :)

[irlandes]

Thought, but on Mandrake 7.2. I wanted to install Star Office from the CD, also Acrobat Reader. I tried to sort out the garbage in the manuals, with no luck. Finally, by accident, while I was looking at files in the CD, I clicked ONCE on one that ended with .rpm and kpackage automatically configured itself for that package, and all I had to do to install was click on INSTALL on the kpackage box. Sure wish they could say that in the manuals. Sigh.