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.
According to http://www.computerhope.com/unix/usetenv.htm, setenv is used in the C shell. If you're using the Bash shell, setting an environment variable is done with export. Can you post the info from the TeX docs and someone here should be able to tell you what needs to be done.
7) final configuration steps
- set up PATH
- check environment
- configure teTeX using texconfig
- generate fonts with a batch job
- set up area for automatic font generation
Set up PATH:
Set up your PATH to include the directory containing the just installed
binaries (e.g. /usr/local/teTeX/bin/i686-pc-linux-gnu); similarly, MANPATH
and INFOPATH to include the relevant newly installed subdirectories,
i.e. $prefix/man resp. $prefix/info. To avoid conflicts with a
possible different TeX installation, make sure to put the new directories
first. E.g. for setting PATH, use something like the following, but
replace i686-pc-linux-gnu by your actual platform directory:
PATH=/usr/local/teTeX/bin/i686-pc-linux-gnu:$PATH; export PATH
setenv PATH /usr/local/teTeX/bin/i686-pc-linux-gnu:$PATH
As an alternative to adjust PATH, you could as well create symbolic
links in a standard location such as /usr/local/bin:
Example using GNU-ls (which supports the "force" option):
ln -sf /usr/local/teTeX/bin/i686-pc-linux-gnu/* /usr/local/bin
Example using standard ln:
(cd /usr/local/teTeX/bin/i686-pc-linux-gnu; echo *) \
| (cd /usr/local/bin; xargs rm -f)
ln -s /usr/local/teTeX/bin/i686-pc-linux-gnu/* /usr/local/bin
This is the segment of the doc of TeTeX that I dont understand...
Well, theres a problem : when I do the PATH=, it works in the terminal ONLY IF I DONT CLOSE IT!!!, but if I open back rxvt, the PATH= is not in set...
And the MANPATH= is the same thing...
I would like rxvt to ALWAYS know where is the MAN pages of TeX...
I assume you're using Bash as your shell... If so, do you want the change made just for yourself? Add the following to the file .bash_profile in your home directory. You'll have to do the same for MANPATH and INFOPATH:
If this is for all users, check that there is a section in /etc/profile that says:
for profile_script in /etc/profile.d/*.sh ; do
if [ -x $profile_script ]; then
If there is, you can create a file called /etc/profile.d/tex.sh and add the same lines to it instead (from memory, the file needs to be executable). If the profile.d stuff is not there, add the lines to /etc/profile. Either way, the next time you login those variables should already be set for you.