summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/source/english/texlive-en/maintenance.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/source/english/texlive-en/maintenance.tex')
-rw-r--r--Master/texmf-doc/source/english/texlive-en/maintenance.tex188
1 files changed, 188 insertions, 0 deletions
diff --git a/Master/texmf-doc/source/english/texlive-en/maintenance.tex b/Master/texmf-doc/source/english/texlive-en/maintenance.tex
new file mode 100644
index 00000000000..6954d852a13
--- /dev/null
+++ b/Master/texmf-doc/source/english/texlive-en/maintenance.tex
@@ -0,0 +1,188 @@
+\section{Post-installation}
+\label{sec:postinstall}
+
+After the main installation is done, for any operating system, the
+remaining steps are to configure the system for your local needs, and
+perform some basic tests.
+
+Another sort of post-installation is to acquire packages, fonts, or
+programs that were not included in \TL{}. The basic idea is to
+install such additions in the \envname{TEXMFLOCAL} tree (if you
+installed to disk), or \envname{TEXMFSYSVAR} (if you are running live).
+See the ``Installation directories'' option on \p.\pageref{text:instdir}.
+
+Unfortunately, the details can and do vary widely, and so we do not attempt to
+address them here. Here are some external links to descriptions:
+\begin{itemize*}
+\item
+\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages}
+\item
+\url{http://www.ctan.org/installationadvice}
+\item
+\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst}
+\item
+\url{http://www.ctan.org/tex-archive/info/Type1fonts} for
+installation information for fonts in particular.
+\end{itemize*}
+
+
+\subsection{The \protect\cmdname{texconfig} program}
+\label{sec:texconfig}
+
+At any time after installation, you can and should use the program
+\cmdname{texconfig} to configure the system to fit your local needs. It
+is installed in the architecture-specific subdirectory
+\texttt{TEXDIR/bin/\var{arch}} along with everything else.
+
+If you run it without arguments, it will enter full-screen mode and
+allow you to view and change options interactively.
+
+You can also run it with various command-line options. Here are some of
+the most common (\TL{} is configured for the A4 paper size by default):
+
+\begin{ttdescription}
+
+\item [texconfig paper letter] Set default paper size for
+various programs and drivers (\cmdname{pdftex}, \cmdname{dvips},
+\cmdname{dvipdfm}, \cmdname{xdvi}) to be \acro{US} letter. The other
+allowable size is \optname{a4}, which is the default.
+
+\item [texconfig rehash] Update all the \TeX{} ``filename databases'',
+after adding or removing files.
+
+\item [texconfig faq] Show the \teTeX{} \acro{FAQ}.
+(See also the main \TeX{} \acro{FAQ} in \OnCD{texmf-doc/doc/english/FAQ-en}.)
+
+\item [texconfig help] Output help information for \cmdname{texconfig}.
+
+\end{ttdescription}
+
+Of course, \cmdname{texconfig} can only support changing a few of the
+many options and configuration parameters in a \TeX{} system. The main
+configuration file for the base \Webc{} programs is named
+\filename{texmf.cnf}. You can find its location by running
+\samp{kpsewhich texmf.cnf}; it contains many comments explaining the
+default settings and useful alternatives.
+
+\cmdname{texconfig} alters files in a user-specific directory, as in
+\dirname{\$HOME/.texlive2007}. If you install \TeX\ just for yourself,
+that is unlikely to make a difference. But if you install \TeX\ on a
+multi-user system, you will want to change the configuration for the
+whole system. In this case, run \cmdname{texconfig-sys} instead of
+\cmdname{texconfig}.
+
+Likewise, the \cmdname{updmap} and \cmdname{fmtutil} scripts were
+changed, to work under \dirname{\$HOME/.texliveYYYY}. To alter system
+directories, use \cmdname{updmap-sys} and \cmdname{fmtutil-sys}.
+
+In particular, for multi-user systems, you will probably want to
+pregenerate the standard formats with \texttt{fmtutil-sys --missing}.
+Otherwise, each user will end up with their own formats.
+
+Also, if you have a personally-modified copy of \filename{fmtutil.cnf}
+or \filename{updmap.cfg}, instead of using the ones generated by
+installation, they must be installed in the tree referenced by the
+variable \envname{TEXMFSYSCONFIG}.
+
+The variables specifying the directories altered by these commands are
+listed in section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}.
+You can see the actual directories by running \texttt{texconfig conf},
+and you can change them by editing \filename{texmf.cnf}.
+
+
+\subsection{Testing the installation}
+\label{sec:test-install}
+
+After installing \TL{} as best you can, you naturally want to test
+it out, so you can start creating beautiful documents and\slash or fonts.
+
+This section gives some basic procedures for testing that the new system
+is functional. We give Unix commands; under \MacOSX{} and Windows,
+you're more likely to run the tests through a graphical interface, but
+the principles are the same.
+
+\begin{enumerate}
+
+\item Make sure that you can run the \cmdname{tex} program in the first
+place:
+
+\begin{alltt}
+> \Ucom{tex -{}-version}
+TeX 3.141592 (Web2C 7.5.5)
+kpathsea version 3.5.5
+...
+\end{alltt}
+If this comes back with `command not found' instead of version and
+copyright information, most likely you don't have the correct
+\dirname{bin} subdirectory in your \envname{PATH}. See
+the environment-setting information on \p.\pageref{text:path}.
+
+\item Process a basic \LaTeX{} file:
+\begin{alltt}
+> \Ucom{latex sample2e.tex}
+This is pdfeTeXk, Version 3.141592...
+...
+Output written on sample2e.dvi (3 pages, 7496 bytes).
+Transcript written on sample2e.log.
+\end{alltt}
+If this fails to find \filename{sample2e.tex} or other files, perhaps
+you have interference from old environment variables or configuration
+files. For a deep analysis, you can always ask \TeX{} to report on
+exactly what it is searching for, and finding; see ``Debugging actions''
+on page~\pageref{Debugging}.
+
+\item Preview the result online:
+\begin{alltt}
+> \Ucom{xdvi sample2e.dvi}
+\end{alltt}
+(Under Windows, the analogous command is \cmdname{dviout}.) You should
+see a new window with a nice document explaining some of the basics of
+\LaTeX{}. (Well worth reading, by the way if you're new to the system.)
+You do have to be running under X for \cmdname{xdvi} to work; if you're
+not, or your \envname{DISPLAY} environment variable is set incorrectly,
+you'll get an error \samp{Can't open display}.
+
+\item Create a \PS{} file for printing or display:
+\begin{alltt}
+> \Ucom{dvips sample2e.dvi -o sample2e.ps}
+\end{alltt}
+
+\item Create a \acro{PDF} file instead of \dvi{}; this processes the
+\filename{.tex} file and writes \acro{PDF} directly:
+\begin{alltt}
+> \Ucom{pdflatex sample2e.tex}
+\end{alltt}
+
+\item Preview the \acro{PDF} file:
+\begin{alltt}
+> \Ucom{gv sample2e.pdf}
+\textrm{or:}
+> \Ucom{xpdf sample2e.pdf}
+\end{alltt}
+Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently
+included in \TL{}, so you must install them separately. See
+\url{http://www.gnu.org/software/gv} and
+\url{http://www.foolabs.com/xpdf}, respectively.
+
+\item Other standard test files you may find useful:
+
+\begin{ttdescription}
+\item [small2e.tex] A simpler document than \filename{sample2e}, to
+reduce the input size if you're having troubles.
+\item [testpage.tex] Test if your printer introduces any offsets.
+\item [nfssfont.tex] For printing font tables and tests.
+\item [testfont.tex] Also for font tables, but using plain \TeX{}.
+\item [story.tex] The most canonical (plain) \TeX{} test file of all.
+You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex
+story.tex}.
+\end{ttdescription}
+You can process these in the same way as we did with
+\filename{sample2e.tex}.
+
+\end{enumerate}
+
+If you are new to \TeX{}, or otherwise need help with actually
+constructing \TeX{} or \LaTeX{} documents, please visit
+\url{http://tug.org/begin.html} for some introductory resources.
+
+