Melvin,
The 585 page manual that came with SuSE 7.0 decribes, in chapter 17, the boot and initialization process. Notice section 17.5, which describes /etc/rc.config and /sbin/SuSEConfig. When you run YaST (console) or YaST2 (graphical) to install or remove software, change configurations, or setup hardware, etc., you are actually making changes to rc.config. When you leave YaST(2) it fires SuSEConfig, which reads rc.config and fires a bunch of perl scripts to make the changes you requested while running YaST(2). YaST(2) uses RPM to install and uninstall programs, and to fire scripts which sets environmental variables. If you install a tarred program then you have to run ./configure, make, and make_install yourself, then you have to setup the required links and environmental variables by editing /etc/profile.local or ~/home/.bashrc. (Installing hardware or drivers or modules is done in /etc/init.d/boot.local.

The 200 page "Configuration" manual, on page 74, describes how to use YaST (Yet another Setup Tool). I personally prefer it over YaST2, but In SuSE 7.2 YaST2 has become extremely powerful. I think SuSE will soon drop YaST.

If an error msg gives you the name of a file you can use 'locate ' to locate it.
Jason gave excellent advice on setting up env variables. Supply a few more details about your error message.
JLK




>Hi to all.
>
>Right now I'm having some problems when I install some software, specially through a shell script. The comon error said to me that the script can´t locate the pass to the X libraries, but this libraries works fine in my machine. I'm still using SuSE 7.0 and I don´t know what to do. I think I need to dfine some PATH in some place but I don´t know where. So if anyone can help me I will appreciate the tip.
>
>Regards,
>
>Melvin

Nebraska Dept of Revenue