From 524dce79afdcd7e0cfbc9f7f758639d7dbef760b Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Mon, 25 Jan 2010 10:40:58 +0100 Subject: [PATCH] Update non-translated Spanish chapters --- docs/manuals/es/console/bconsole.tex | 30 +- docs/manuals/es/console/console.tex | 2 +- docs/manuals/es/developers/coverpage.tex | 4 +- docs/manuals/es/developers/gui-interface.tex | 36 +- docs/manuals/es/main/coverpage.tex | 5 +- docs/manuals/es/main/dirdconf.tex | 35 ++ docs/manuals/es/main/fileset.tex | 2 +- docs/manuals/es/main/general.tex | 2 +- docs/manuals/es/main/install.tex | 357 ++++++++----------- docs/manuals/es/main/lesser.tex | 22 +- 10 files changed, 246 insertions(+), 249 deletions(-) diff --git a/docs/manuals/es/console/bconsole.tex b/docs/manuals/es/console/bconsole.tex index 32774003..f090374b 100644 --- a/docs/manuals/es/console/bconsole.tex +++ b/docs/manuals/es/console/bconsole.tex @@ -13,10 +13,10 @@ allows the user or the System Administrator, to interact with the Bacula Director daemon while the daemon is running. The current Bacula Console comes in two versions: a shell interface (TTY -style), and a GNOME GUI interface. Both permit the administrator or authorized -users to interact with Bacula. You can determine the status of a particular -job, examine the contents of the Catalog as well as perform certain tape -manipulations with the Console program. +style), and a QT GUI interface (Bat). Both permit the administrator or +authorized users to interact with Bacula. You can determine the status of a +particular job, examine the contents of the Catalog as well as perform certain +tape manipulations with the Console program. In addition, there is a bwx-console built with wxWidgets that allows a graphic restore of files. As of version 1.34.1 it is in an early stage of development, @@ -39,8 +39,8 @@ indicates that the new tape is mounted. \index[general]{Configuration!Console} When the Console starts, it reads a standard Bacula configuration file -named {\bf bconsole.conf} or {\bf bgnome-console.conf} in the case of the GNOME -Console version from the current directory unless you specify the {\bf {-}c} +named {\bf bconsole.conf} or {\bf bat.conf} in the case of the Bat +QT Console version from the current directory unless you specify the {\bf {-}c} command line option (see below). This file allows default configuration of the Console, and at the current time, the only Resource Record defined is the Director resource, which gives the Console the name and address of @@ -69,13 +69,11 @@ Usage: bconsole [-s] [-c config_file] [-d debug_level] \normalsize -After launching the Console program (bconsole), it will prompt you for the -next command with an asterisk (*). (Note, in the GNOME version, the prompt is -not present; you simply enter the commands you want in the command text box at -the bottom of the screen.) Generally, for all commands, you can simply enter -the command name and the Console program will prompt you for the necessary -arguments. Alternatively, in most cases, you may enter the command followed by -arguments. The general format is: +After launching the Console program (bconsole), it will prompt you for the next +command with an asterisk (*). Generally, for all commands, you can simply +enter the command name and the Console program will prompt you for the +necessary arguments. Alternatively, in most cases, you may enter the command +followed by arguments. The general format is: \footnotesize \begin{verbatim} @@ -311,9 +309,7 @@ The following commands are currently implemented: auto-display of messages on or off respectively. The default for the console program is {\bf off}, which means that you will be notified when there are console messages pending, but they will not automatically be - displayed. The default for the bgnome-console program is {\bf on}, which - means that messages will be displayed when they are received (usually - within five seconds of them being generated). + displayed. When autodisplay is turned off, you must explicitly retrieve the messages with the {\bf messages} command. When autodisplay is turned @@ -1432,7 +1428,7 @@ forwarded to the Director, which may be on another machine, to be executed. However, there is a small list of {\bf at} commands, all beginning with an at character (@), that will not be sent to the Director, but rather interpreted by the Console program directly. Note, these commands are implemented only in -the tty console program and not in the GNOME Console. These commands are: +the tty console program and not in the Bat Console. These commands are: \begin{description} diff --git a/docs/manuals/es/console/console.tex b/docs/manuals/es/console/console.tex index 28850d69..95f9c659 100644 --- a/docs/manuals/es/console/console.tex +++ b/docs/manuals/es/console/console.tex @@ -51,7 +51,7 @@ \date{\vspace{1.0in}\today \\ This manual documents Bacula version \input{version} \\ \vspace{0.2in} - Copyright \copyright 1999-2009, Free Software Foundation Europe + Copyright \copyright 1999-2010, Free Software Foundation Europe e.V. \\ \vspace{0.2in} Permission is granted to copy, distribute and/or modify this document under the terms of the diff --git a/docs/manuals/es/developers/coverpage.tex b/docs/manuals/es/developers/coverpage.tex index c1aaca82..a6b1ecc9 100644 --- a/docs/manuals/es/developers/coverpage.tex +++ b/docs/manuals/es/developers/coverpage.tex @@ -13,9 +13,9 @@ \author{Kern Sibbald} \date{\vspace{1.0in}\today \\ - This manual documents Bacula version \fullversion \\ + This manual documents Bacula version \input{version} \\ \vspace{0.2in} - Copyright {\copyright} 1999-2009, Free Software Foundation Europe + Copyright {\copyright} 1999-2010, Free Software Foundation Europe e.V. \\ Bacula {\textregistered} is a registered trademark of Kern Sibbald.\\ \vspace{0.2in} diff --git a/docs/manuals/es/developers/gui-interface.tex b/docs/manuals/es/developers/gui-interface.tex index 2733cda9..218f5af5 100644 --- a/docs/manuals/es/developers/gui-interface.tex +++ b/docs/manuals/es/developers/gui-interface.tex @@ -24,7 +24,7 @@ exception of dbcheck and bscan). This is because at some point I would like to add user level security and access. If we have code spread everywhere such as in a GUI this will be more difficult. The other advantage is that any code you add to the Director is automatically available to both the tty console program -and the GNOME program. The major disadvantage is it increases the size of the +and the WX program. The major disadvantage is it increases the size of the code -- however, compared to Networker the Bacula Director is really tiny. \subsection{GUI Interface is Difficult} @@ -98,5 +98,35 @@ Then the read\_and\_process\_input routine looks like the following: For a GUI program things will be a bit more complicated. Basically in the very inner loop, you will need to check and see if any output is available on the -UA\_sock. For an example, please take a look at the GNOME GUI interface code -in: \lt{}bacula-source\>/src/gnome-console/console.c +UA\_sock. For an example, please take a look at the WX GUI interface code +in: \lt{bacula-source/src/wx-console} + +\section{Bvfs API} +\label{sec:bvfs} + +To help developers of restore GUI interfaces, we have added new \textsl{dot + commands} that permit browsing the catalog in a very simple way. + +\begin{itemize} +\item \texttt{.bvfs\_update [jobid=x,y,z]} This command is required to update + the Bvfs cache in the catalog. You need to run it before any access to the + Bvfs layer. + +\item \texttt{.bvfs\_lsdirs jobid=x,y,z path=/path | pathid=101} This command + will list all directories in the specified \texttt{path} or + \texttt{pathid}. Using \texttt{pathid} avoids problems with character + encoding of path/filenames. + +\item \texttt{.bvfs\_lsfiles jobid=x,y,z path=/path | pathid=101} This command + will list all files in the specified \texttt{path} or \texttt{pathid}. Using + \texttt{pathid} avoids problems with character encoding. +\end{itemize} + +You can use \texttt{limit=xxx} and \texttt{offset=yyy} to limit the amount of +data that will be displayed. + +\begin{verbatim} +* .bvfs_update jobid=1,2 +* .bvfs_update +* .bvfs_lsdir path=/ jobid=1,2 +\end{verbatim} diff --git a/docs/manuals/es/main/coverpage.tex b/docs/manuals/es/main/coverpage.tex index d6aa6a5c..d9aecf39 100644 --- a/docs/manuals/es/main/coverpage.tex +++ b/docs/manuals/es/main/coverpage.tex @@ -1,3 +1,4 @@ + \newfont{\bighead}{cmr17 at 36pt} \parskip 10pt \parindent 0pt @@ -13,9 +14,9 @@ \author{Kern Sibbald} \date{\vspace{1.0in}\today \\ - This manual documents Bacula version \fullversion \\ + This manual documents Bacula version \input{version} \\ \vspace{0.2in} - Copyright {\copyright} 1999-2009, Free Software Foundation Europe + Copyright {\copyright} 1999-2010, Free Software Foundation Europe e.V. \\ Bacula {\textregistered} is a registered trademark of Kern Sibbald.\\ \vspace{0.2in} diff --git a/docs/manuals/es/main/dirdconf.tex b/docs/manuals/es/main/dirdconf.tex index e262af1a..c1223b9b 100644 --- a/docs/manuals/es/main/dirdconf.tex +++ b/docs/manuals/es/main/dirdconf.tex @@ -2177,6 +2177,7 @@ console run command. This directive is required. \label{FileRetention} \item [File Retention = \lt{}time-period-specification\gt{}] + \label{FileRetention} \index[dir]{File Retention} \index[dir]{Directive!File Retention} The File Retention directive defines the length of time that Bacula will @@ -2200,6 +2201,7 @@ console run command. This directive is required. \label{JobRetention} \item [Job Retention = \lt{}time-period-specification\gt{}] + \label{JobRetention} \index[dir]{Job Retention} \index[dir]{Directive!Job Retention} The Job Retention directive defines the length of time that Bacula will keep @@ -2962,6 +2964,39 @@ Pool { sure that some day, Bacula will recycle a Volume that contains current data. The default is {\bf no}. +\item [File Retention = \lt{}time-period-specification\gt{}] + \index[dir]{File Retention} + \index[dir]{Directive!File Retention} + The File Retention directive defines the length of time that Bacula will + keep File records in the Catalog database after the End time of the + Job corresponding to the File records. + + This directive takes precedence over Client directives of the same name. For + example, you can decide to increase Retention times for Archive or OffSite + Pool. + + Note, this affects only records in the catalog database. It does not affect + your archive backups. + + For more information see Client documentation about + \ilink{FileRetention}{FileRetention} + +\item [Job Retention = \lt{}time-period-specification\gt{}] + \index[dir]{Job Retention} + \index[dir]{Directive!Job Retention} + + The Job Retention directive defines the length of time that Bacula will keep + Job records in the Catalog database after the Job End time. As with the + other retention periods, this affects only records in the catalog and not + data in your archive backup. + + This directive takes precedence over Client directives of the same name. + For example, you can decide to increase Retention times for Archive or + OffSite Pool. + + For more information see Client side documentation + \ilink{JobRetention}{JobRetention} + \item [Cleaning Prefix = \lt{}string\gt{}] \index[dir]{Cleaning Prefix} \index[dir]{Directive!Cleaning Prefix} diff --git a/docs/manuals/es/main/fileset.tex b/docs/manuals/es/main/fileset.tex index 357621d5..536a6cb3 100644 --- a/docs/manuals/es/main/fileset.tex +++ b/docs/manuals/es/main/fileset.tex @@ -607,7 +607,7 @@ Change: 2005-11-06 12:36:48.000000000 +0100 \index[dir]{checkfilechanges} \index[dir]{Directive!checkfilechanges} On versions 2.0.4 or greater, - if enabled, the Client will checks size, age of each file after + if enabled, the Client will check size, age of each file after their backup to see if they have changed during backup. If time or size mismatch, an error will raise. diff --git a/docs/manuals/es/main/general.tex b/docs/manuals/es/main/general.tex index ab0f100b..dc8740bf 100644 --- a/docs/manuals/es/main/general.tex +++ b/docs/manuals/es/main/general.tex @@ -78,7 +78,7 @@ Director, Console, File, Storage, and Monitor services. The Bacula Console service is the program that allows the administrator or user to communicate with the Bacula Director Currently, the Bacula Console is available in three versions: - text-based console interface, GNOME-based interface, and a + text-based console interface, QT-based interface, and a wxWidgets graphical interface. The first and simplest is to run the Console program in a shell window (i.e. TTY interface). Most system administrators will find this diff --git a/docs/manuals/es/main/install.tex b/docs/manuals/es/main/install.tex index 83b62a96..25d9a701 100644 --- a/docs/manuals/es/main/install.tex +++ b/docs/manuals/es/main/install.tex @@ -291,11 +291,9 @@ to time, the current makeup is the following: \hline \multicolumn{1}{|c| }{\bf 3rd Party Package} & \multicolumn{1}{c| }{\bf depkgs} & \multicolumn{1}{c| }{\bf depkgs-qt} \\ - \hline {SQLite } & \multicolumn{1}{c| }{X } & \multicolumn{1}{c| }{ }\\ \hline {SQLite3 } & \multicolumn{1}{c| }{X } & \multicolumn{1}{c| }{ }\\ \hline {mtx } & \multicolumn{1}{c| }{X } & \multicolumn{1}{c| }{ } \\ \hline {qt4 } & \multicolumn{1}{c| }{ } & \multicolumn{1}{c| }{X } \\ - \hline {qwt } & \multicolumn{1}{c| }{ } & \multicolumn{1}{c| }{X } \\ \hline \end{longtable} @@ -415,7 +413,7 @@ continue on. (src/stored), it is probably because you have not loaded the static libraries on your system. I noticed this problem on a Solaris system. To correct it, make sure that you have not added {\bf - {-}{-}enable-static-tools} to the {\bf ./configure} command. + {-} {-}enable-static-tools} to the {\bf ./configure} command. If you skip this step ({\bf make}) and proceed immediately to the {\bf make install} you are making two serious errors: 1. your install will @@ -536,16 +534,16 @@ the {\bf examples} directory. This script contains the statements that you would normally use, and each developer/user may modify them to suit his needs. You should find additional useful examples in this directory as well. -The {\bf \verb:--:enable-conio} or {\bf \verb:--:enable-readline} options are useful because -they provide a command line history and editing capability for the Console -program. If you have included either option in the build, either the {\bf -termcap} or the {\bf ncurses} package will be needed to link. On most -systems, including Red Hat and SuSE, you should include the ncurses package. -If Bacula's configure process finds the ncurses libraries, it will use -those rather than the termcap library. -On some systems, such as SuSE, the termcap library is not in the standard -library directory. As a consequence, the option may be disabled or you may -get an error message such as: +The {\bf \verb:--:enable-conio} or {\bf \verb:--:enable-readline} options are +useful because they provide a command line history, editing capability for the +Console program and tab completion on various option. If you have included +either option in the build, either the {\bf termcap} or the {\bf ncurses} +package will be needed to link. On most systems, including Red Hat and SuSE, +you should include the ncurses package. If Bacula's configure process finds +the ncurses libraries, it will use those rather than the termcap library. On +some systems, such as SuSE, the termcap library is not in the standard library +directory. As a consequence, the option may be disabled or you may get an +error message such as: \footnotesize \begin{verbatim} @@ -564,12 +562,11 @@ export LDFLAGS="-L/usr/lib/termcap" \end{verbatim} \normalsize -The same library requirements apply if you wish to use the readline -subroutines for command line editing and history or -if you are using a MySQL library that requires encryption. If you need encryption, -you can either export the appropriate additional library options as shown -above or, alternatively, you can include them directly on the ./configure line -as in: +The same library requirements apply if you wish to use the readline subroutines +for command line editing, history and tab completion or if you are using a +MySQL library that requires encryption. If you need encryption, you can either +export the appropriate additional library options as shown above or, +alternatively, you can include them directly on the ./configure line as in: \footnotesize \begin{verbatim} @@ -641,10 +638,10 @@ If the ./configure process is unable to find specific libraries (e.g. libintl, you should ensure that the appropriate package is installed on your system. Alternatively, if the package is installed in a non-standard location (as far as Bacula is concerned), then there is generally an -option listed below (or listed with "./configure {-}{-}help" that will +option listed below (or listed with "./configure {-} {-}help" that will permit you to specify the directory that should be searched. In other cases, there are options that will permit you to disable to feature -(e.g. {-}{-}disable-nls). +(e.g. {-} {-}disable-nls). If you want to dive right into it, we recommend you skip to the next chapter, and run the example program. It will teach you a lot about Bacula and as an @@ -661,7 +658,7 @@ The following command line options are available for {\bf configure} to customize your installation. \begin{description} -\item [ {-}prefix=\lt{}patch\gt{}] +\item [ \--prefix=\lt{}patch\gt{}] \index[general]{{-}prefix} This option is meant to allow you to direct where the architecture independent files should be placed. However, we find this a somewhat @@ -670,18 +667,18 @@ customize your installation. you avoid it. We have provided options that allow you to explicitly specify the directories for each of the major categories of installation files. -\item [ {-}{-}sbindir=\lt{}binary-path\gt{}] - \index[general]{{-}{-}sbindir} +\item [ {-}{\-}sbindir=\lt{}binary-path\gt{}] + \index[general]{{-}{\-}sbindir} Defines where the Bacula binary (executable) files will be placed during a {\bf make install} command. -\item [ {-}{-}sysconfdir=\lt{}config-path\gt{}] - \index[general]{{-}{-}sysconfdir} +\item [ {-}{\-}sysconfdir=\lt{}config-path\gt{}] + \index[general]{{-}{\-}sysconfdir} Defines where the Bacula configuration files should be placed during a {\bf make install} command. -\item [ {-}{-}mandir=\lt{}path\gt{}] - \index[general]{{-}{-}mandir} +\item [ {-}{\-}mandir=\lt{}path\gt{}] + \index[general]{{-}{\-}mandir} Note, as of Bacula version 1.39.14, the meaning of any path specified on this option is change from prior versions. It now specifies the top level man directory. @@ -699,18 +696,18 @@ customize your installation. Note, the main HTML and PDF Bacula documents are in a separate tar file that is not part of the source distribution. -\item [ {-}{-}datadir=\lt{}path\gt{} ] - \index[general]{{-}{-}datadir} +\item [ {-}{\-}datadir=\lt{}path\gt{} ] + \index[general]{{-}{\-}datadir} If you translate Bacula or parts of Bacula into a different language you may specify the location of the po files using the {\bf - {-}{-}datadir} option. You must manually install any po files as + {-}{\-}datadir} option. You must manually install any po files as Bacula does not (yet) automatically do so. -\item [ {-}{-}disable-ipv6 ] - \index[general]{{-}{-}disable-ipv6} +\item [ {-}{\-}disable-ipv6 ] + \index[general]{{-}{\-}disable-ipv6} -\item [ {-}{-}enable-smartalloc ] - \index[general]{{-}{-}enable-smartalloc} +\item [ {-}{\-}enable-smartalloc ] + \index[general]{{-}{\-}enable-smartalloc} This enables the inclusion of the Smartalloc orphaned buffer detection code. This option is highly recommended. Because we never build without this option, you may experience problems if it is not enabled. @@ -718,10 +715,10 @@ customize your installation. keeping this option enabled as it helps detect memory leaks. This configuration parameter is used while building Bacula -\item [ {-}{-}enable-bat ] +\item [ {-}{\-}enable-bat ] \label{enablebat} - \index[general]{{-}{-}enable-bat} - If you have Qt4 >= 4.3 installed on your computer including the + \index[general]{{-}{\-}enable-bat} + If you have Qt4 >= 4.3.4 installed on your computer including the libqt4 and libqt4-devel (libqt4-dev on Debian) libraries, and you want to use the Bacula Administration Tool (bat) GUI Console interface to Bacula, you must specify this option. Doing so will build everything in @@ -731,45 +728,14 @@ customize your installation. Qt4 is available on OpenSUSE 10.2, CentOS 5, Fedora, and Debian. If it is not available on your system, you can download the {\bf depkgs-qt} - package from the Bacula Source Forge download area and build it and - the qwt package, both of which are needed to build bat. See the + package from the Bacula Source Forge download area and build it. + See the INSTALL file in that package for more details. In particular to use - the Qt4 built by {\bf depkgs-qt} you {bf must} source the file + the Qt4 built by {\bf depkgs-qt} you {\bf must} source the file {\bf qt4-paths}. -\item [ {-}{-}with-qwt=\lt{}path\gt{} ] - \index[general]{{-}{-}with-qwt} - The qwt package is a graphics library for Qt. If it is included - during the building of bat, you will get one extra graphical function. - At the current time, we recommend not including this option when - building bat. The path specified must be an absolute path and - not relative. - - The qwt package is available for download from - the qwt project on Source Forge. If you wish, you may build and - install it on your system (by default in /usr/lib). - If you have done so, you would specify: - -\begin{verbatim} - --with-qwt=/usr/lib/qwt-5.0.2 -\end{verbatim} - - Alternatively, you can download the Bacula depkgs-qt package (currently - version 28Jul09) and build it, then assuming that you have put it - into a directory named bacula, you would specify: - -\begin{verbatim} - --with-qwt=$HOME/bacula/depkgs-qt/qwt -\end{verbatim} - - Some packages such as Debian do not adhere to the standard of - naming the library libqwt.a or libqwt.so, and you will either need - to manually add a soft link to the name they use or use the - depkgs version, which handles the naming correctly. - - -\item [ {-}{-}enable-batch-insert ] - \index[general]{{-}{-}enable-batch-insert} +\item [ {-}{\-}enable-batch-insert ] + \index[general]{{-}{\-}enable-batch-insert} This option enables batch inserts of the attribute records (default) in the catalog database, which is much faster (10 times or more) than without this option for large numbers of files. However, this option @@ -807,12 +773,6 @@ $ nm /usr/local/lib/libpq.a | grep mutex Bacula always links to the thread safe MySQL libraries. - As a default, Bacula runs SQLite3 with {\bf PRAGMA synchronous=OFF} - because it improves performance by more than 30 times. However, it - increases the possibility of a corrupted database. If you want more - security, please modify src/version.h appropriately (it should be - obvious when you look at the file). - Running with Batch Insert turned on is recommended because it can significantly improve attribute insertion times. However, it does put a significantly larger part of the work on your SQL engine, so @@ -823,24 +783,17 @@ $ nm /usr/local/lib/libpq.a | grep mutex want to increase the memory available to your SQL engine to further improve performance during Batch Inserts. -\item [ {-}{-}enable-gnome ] - \index[general]{{-}{-}enable-gnome} - If you have GNOME installed on your computer including the - GNOME development libraries, and you want to use the - GNOME GUI Console interface to Bacula, you must specify this option. - Doing so will build everything in the {\bf src/gnome2-console} directory. - -\item [ {-}{-}enable-bwx-console ] - \index[general]{{-}{-}enable-bwx-console} +\item [ {-}{\-}enable-bwx-console ] + \index[general]{{-}{\-}enable-bwx-console} If you have wxWidgets installed on your computer and you want to use the wxWidgets GUI Console interface to Bacula, you must specify this option. Doing so will build everything in the {\bf src/wx-console} directory. This could also be useful to users who want a GUI Console and don't want - to install GNOME, as wxWidgets can work with GTK+, Motif or even X11 + to install QT, as wxWidgets can work with GTK+, Motif or even X11 libraries. -\item [ {-}{-}enable-tray-monitor ] - \index[general]{{-}{-}enable-tray-monitor} +\item [ {-}{\-}enable-tray-monitor ] + \index[general]{{-}{\-}enable-tray-monitor} If you have GTK installed on your computer, you run a graphical environment or a window manager compatible with the FreeDesktop system tray standard (like KDE and GNOME) and you want to use a GUI to monitor @@ -851,8 +804,8 @@ $ nm /usr/local/lib/libpq.a | grep mutex calls to the GTK+ API, and unfortunately, the tray icon API necessary was not implemented until GTK version 2.10 or later. -\item [ {-}{-}enable-static-tools] - \index[general]{{-}{-}enable-static-tools} +\item [ {-}{\-}enable-static-tools] + \index[general]{{-}{\-}enable-static-tools} This option causes the linker to link the Storage daemon utility tools ({\bf bls}, {\bf bextract}, and {\bf bscan}) statically. This permits using them without having the shared libraries loaded. If you have @@ -860,8 +813,8 @@ $ nm /usr/local/lib/libpq.a | grep mutex not enabled this option, or explicitly disable static linking by adding {\bf \verb:--:disable-static-tools}. -\item [ {-}{-}enable-static-fd] - \index[general]{{-}{-}enable-static-fd} +\item [ {-}{\-}enable-static-fd] + \index[general]{{-}{\-}enable-static-fd} This option causes the make process to build a {\bf static-bacula-fd} in addition to the standard File daemon. This static version will include statically linked libraries and is required for the Bare Metal recovery. @@ -876,14 +829,14 @@ $ nm /usr/local/lib/libpq.a | grep mutex experience linking errors when this option is used. The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure - you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python} + you do not specify {\bf {-}{\-}openssl} or {\bf {-}{\-}with-python} on your ./configure statement as these options require additional libraries. You may be able to enable those options, but you will need to load additional static libraries. -\item [ {-}{-}enable-static-sd] - \index[general]{{-}{-}enable-static-sd} +\item [ {-}{\-}enable-static-sd] + \index[general]{{-}{\-}enable-static-sd} This option causes the make process to build a {\bf static-bacula-sd} in addition to the standard Storage daemon. This static version will include statically linked libraries and could be useful during a Bare @@ -894,14 +847,14 @@ $ nm /usr/local/lib/libpq.a | grep mutex experience linking errors when this option is used. The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure - you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python} + you do not specify {\bf {-}{\-}openssl} or {\bf {-}{\-}with-python} on your ./configure statement as these options require additional libraries. You may be able to enable those options, but you will need to load additional static libraries. -\item [ {-}{-}enable-static-dir] - \index[general]{{-}{-}enable-static-dir} +\item [ {-}{\-}enable-static-dir] + \index[general]{{-}{\-}enable-static-dir} This option causes the make process to build a {\bf static-bacula-dir} in addition to the standard Director. This static version will include statically linked libraries and could be useful during a Bare Metal @@ -912,32 +865,32 @@ $ nm /usr/local/lib/libpq.a | grep mutex experience linking errors when this option is used. The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure - you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python} + you do not specify {\bf {-}{\-}openssl} or {\bf {-}{\-}with-python} on your ./configure statement as these options require additional libraries. You may be able to enable those options, but you will need to load additional static libraries. -\item [ {-}{-}enable-static-cons] - \index[general]{{-}{-}enable-static-cons} - This option causes the make process to build a {\bf static-console} and - a {\bf static-gnome-console} in addition to the standard console. This - static version will include statically linked libraries and could be - useful during a Bare Metal recovery. +\item [ {-}{\-}enable-static-cons] + \index[general]{{-}{\-}enable-static-cons} + This option causes the make process to build a {\bf static-console} in + addition to the standard console. This static version will include + statically linked libraries and could be useful during a Bare Metal + recovery. When linking a static binary, the linker needs the static versions of all the libraries that are used, so frequently users will experience linking errors when this option is used. The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure - you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python} + you do not specify {\bf {-}{\-}openssl} or {\bf {-}{\-}with-python} on your ./configure statement as these options require additional libraries. You may be able to enable those options, but you will need to load additional static libraries. -\item [ {-}{-}enable-client-only] - \index[general]{{-}{-}enable-client-only} +\item [ {-}{\-}enable-client-only] + \index[general]{{-}{\-}enable-client-only} This option causes the make process to build only the File daemon and the libraries that it needs. None of the other daemons, storage tools, nor the console will be built. Likewise a {\bf make install} will then @@ -950,91 +903,81 @@ $ nm /usr/local/lib/libpq.a | grep mutex experience linking errors when this option is used. The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure - you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python} + you do not specify {\bf {-}{\-}openssl} or {\bf {-}{\-}with-python} on your ./configure statement as these options require additional libraries. You may be able to enable those options, but you will need to load additional static libraries. -\item [ {-}{-}enable-build-dird] - \index[general]{{-}{-}enable-build-dird} +\item [ {-}{\-}enable-build-dird] + \index[general]{{-}{\-}enable-build-dird} This option causes the make process to build the Director and the Director's tools. By default, this option is on, but you may turn - it off by using {\bf {-}{-}disable-build-dird} to prevent the + it off by using {\bf {-}{\-}disable-build-dird} to prevent the Director from being built. -\item [ {-}{-}enable-build-stored] - \index[general]{{-}{-}enable-build-stored} +\item [ {-}{\-}enable-build-stored] + \index[general]{{-}{\-}enable-build-stored} This option causes the make process to build the Storage daemon. By default, this option is on, but you may turn - it off by using {\bf {-}{-}disable-build-stored} to prevent the + it off by using {\bf {-}{\-}disable-build-stored} to prevent the Storage daemon from being built. -\item [ {-}{-}enable-largefile] - \index[general]{{-}{-}enable-largefile} +\item [ {-}{\-}enable-largefile] + \index[general]{{-}{\-}enable-largefile} This option (default) causes Bacula to be built with 64 bit file address support if it is available on your system. This permits Bacula to read and write files greater than 2 GBytes in size. You may disable this feature and revert to 32 bit file addresses by using {\bf \verb:--:disable-largefile}. -\item [ {-}{-}disable-nls] - \index[general]{{-}{-}disable-nls} +\item [ {-}{\-}disable-nls] + \index[general]{{-}{\-}disable-nls} By default, Bacula uses the GNU Native Language Support (NLS) libraries. On some machines, these libraries may not be present or may not function correctly (especially on non-Linux implementations). In such cases, you - may specify {\bf {-}{-}disable-nls} to disable use of those libraries. + may specify {\bf {-}{\-}disable-nls} to disable use of those libraries. In such a case, Bacula will revert to using English. -\item [ {-}{-}disable-ipv6 ] - \index[general]{{-}{-}disable-ipv6} +\item [ {-}{\-}disable-ipv6 ] + \index[general]{{-}{\-}disable-ipv6} By default, Bacula enables IPv6 protocol. On some systems, the files for IPv6 may exist, but the functionality could be turned off in the kernel. In that case, in order to correctly build Bacula, you will explicitly need to use this option so that Bacula does not attempt to reference OS function calls that do not exist. -\item [ {-}{-}with-sqlite=\lt{}sqlite-path\gt{}] - \index[general]{{-}{-}with-sqlite} - This enables use of the SQLite version 2.8.x database. The {\bf - sqlite-path} is not normally specified as Bacula looks for the necessary - components in a standard location ({\bf depkgs/sqlite}). See - \ilink{Installing and Configuring SQLite}{SqlLiteChapter} chapter of - this manual for more details. SQLite is not supported on Solaris. - - See the note below under the {-}{-}with-postgresql item. - -\item [ {-}{-}with-sqlite3=\lt{}sqlite3-path\gt{}] - \index[general]{{-}{-}with-sqlite3} +\item [ {-}{\-}with-sqlite3=\lt{}sqlite3-path\gt{}] + \index[general]{{-}{\-}with-sqlite3} This enables use of the SQLite version 3.x database. The {\bf sqlite3-path} is not normally specified as Bacula looks for the necessary components in a standard location ({\bf depkgs/sqlite3}). See \ilink{Installing and Configuring SQLite}{SqlLiteChapter} chapter of this manual for more details. SQLite3 is not supported on Solaris. -\item [ {-}{-}with-mysql=\lt{}mysql-path\gt{}] - \index[general]{{-}{-}with-mysql} +\item [ {-}{\-}with-mysql=\lt{}mysql-path\gt{}] + \index[general]{{-}{\-}with-mysql} This enables building of the Catalog services for Bacula. It assumes that MySQL is running on your system, and expects it to be installed in the {\bf mysql-path} that you specify. Normally, if MySQL is installed - in a standard system location, you can simply use {\bf {-}{-}with-mysql} + in a standard system location, you can simply use {\bf {-}{\-}with-mysql} with no path specification. If you do use this option, please proceed to installing MySQL in the \ilink{Installing and Configuring MySQL}{MySqlChapter} chapter before proceeding with the configuration. - See the note below under the {-}{-}with-postgresql item. + See the note below under the {-}{\-}with-postgresql item. -\item [ {-}{-}with-postgresql=\lt{}path\gt{}] - \index[general]{{-}{-}with-postgresql} +\item [ {-}{\-}with-postgresql=\lt{}path\gt{}] + \index[general]{{-}{\-}with-postgresql} This provides an explicit path to the PostgreSQL libraries if Bacula cannot find it by default. Normally to build with PostgreSQL, you would - simply use {\bf {-}{-}with-postgresql}. + simply use {\bf {-}{\-}with-postgresql}. Note, for Bacula to be configured properly, you must specify one of the four database options supported. That is: - {-}{-}with-sqlite, {-}{-}with-sqlite3, {-}{-}with-mysql, or - {-}{-}with-postgresql, otherwise the ./configure will fail. + {-}{\-}with-sqlite, {-}{\-}with-sqlite3, {-}{\-}with-mysql, or + {-}{\-}with-postgresql, otherwise the ./configure will fail. -\item [ {-}{-}with-openssl=\lt{}path\gt{}] +\item [ {-}{\-}with-openssl=\lt{}path\gt{}] This configuration option is necessary if you want to enable TLS (ssl), which encrypts the communications within Bacula or if you want to use File Daemon PKI data encryption. @@ -1049,8 +992,8 @@ $ nm /usr/local/lib/libpq.a | grep mutex \ilink{Bacula PKI -- Data Encryption}{DataEncryption} chapter of this manual. -\item [ {-}{-}with-python=\lt{}path\gt{}] - \index[general]{{-}{-}with-python} +\item [ {-}{\-}with-python=\lt{}path\gt{}] + \index[general]{{-}{\-}with-python} This option enables Bacula support for Python. If no path is supplied, configure will search the standard library locations for Python 2.2, 2.3, 2.4, or 2.5. If it cannot find the library, you will need to @@ -1058,36 +1001,36 @@ $ nm /usr/local/lib/libpq.a | grep mutex \ilink{Python chapter}{PythonChapter} for the details of using Python scripting. -\item [ {-}{-}with-libintl-prefix=\lt{}DIR\gt{}] - \index[general]{{-}{-}with-libintl-prefix} +\item [ {-}{\-}with-libintl-prefix=\lt{}DIR\gt{}] + \index[general]{{-}{\-}with-libintl-prefix} This option may be used to tell Bacula to search DIR/include and DIR/lib for the libintl headers and libraries needed for Native Language Support (NLS). -\item [ {-}{-}enable-conio] - \index[general]{{-}{-}enable-conio} +\item [ {-}{\-}enable-conio] + \index[general]{{-}{\-}enable-conio} Tells Bacula to enable building the small, light weight readline replacement routine. It is generally much easier to configure than readline, although, like readline, it needs either the termcap or ncurses library. -\item [ {-}{-}with-readline=\lt{}readline-path\gt{}] - \index[general]{{-}{-}with-readline} +\item [ {-}{\-}with-readline=\lt{}readline-path\gt{}] + \index[general]{{-}{\-}with-readline} Tells Bacula where {\bf readline} is installed. Normally, Bacula will find readline if it is in a standard library. If it is not found and no - {-}{-}with-readline is specified, readline will be disabled. This + {-}{\-}with-readline is specified, readline will be disabled. This option affects the Bacula build. Readline provides the Console program with a command line history and editing capability and is no longer supported, so you are on your own if you have problems. -\item [ {-}{-}enable-readline] - \index[general]{{-}{-}enable-readline} +\item [ {-}{\-}enable-readline] + \index[general]{{-}{\-}enable-readline} Tells Bacula to enable readline support. It is normally disabled due to the large number of configuration problems and the fact that the package seems to change in incompatible ways from version to version. -\item [ {-}{-}with-tcp-wrappers=\lt{}path\gt{}] - \index[general]{{-}{-}with-tcp-wrappers} +\item [ {-}{\-}with-tcp-wrappers=\lt{}path\gt{}] + \index[general]{{-}{\-}with-tcp-wrappers} \index[general]{TCP Wrappers} \index[general]{Wrappers!TCP} \index[general]{libwrappers} @@ -1109,8 +1052,8 @@ $ nm /usr/local/lib/libpq.a | grep mutex contained in the tcpd-devel package. On Red Hat, the package is named tcp\_wrappers. -\item [ {-}{-}with-archivedir=\lt{}path\gt{} ] - \index[general]{{-}{-}with-archivedir} +\item [ {-}{\-}with-archivedir=\lt{}path\gt{} ] + \index[general]{{-}{\-}with-archivedir} The directory used for disk-based backups. Default value is /tmp. This parameter sets the default values in the bacula-dir.conf and bacula-sd.conf configuration files. For example, it sets the Where directive for the @@ -1120,8 +1063,8 @@ $ nm /usr/local/lib/libpq.a | grep mutex This option is designed primarily for use in regression testing. Most users can safely ignore this option. -\item [ {-}{-}with-working-dir=\lt{}working-directory-path\gt{} ] - \index[general]{{-}{-}with-working-dir} +\item [ {-}{\-}with-working-dir=\lt{}working-directory-path\gt{} ] + \index[general]{{-}{\-}with-working-dir} This option is mandatory and specifies a directory into which Bacula may safely place files that will remain between Bacula executions. For example, if the internal database is used, Bacula will keep those files in this @@ -1130,8 +1073,8 @@ $ nm /usr/local/lib/libpq.a | grep mutex The working directory is not automatically created by the install process, so you must ensure that it exists before using Bacula for the first time. -\item [ {-}{-}with-base-port=\lt{}port=number\gt{}] - \index[general]{{-}{-}with-base-port} +\item [ {-}{\-}with-base-port=\lt{}port=number\gt{}] + \index[general]{{-}{\-}with-base-port} In order to run, Bacula needs three TCP/IP ports (one for the Bacula Console, one for the Storage daemon, and one for the File daemon). The {\bf \verb:--:with-baseport} option will automatically assign three ports beginning at @@ -1143,20 +1086,20 @@ $ nm /usr/local/lib/libpq.a | grep mutex IANA. This option is only used to modify the daemon configuration files. You may also accomplish the same thing by directly editing them later. -\item [ {-}{-}with-dump-email=\lt{}email-address\gt{}] - \index[general]{{-}{-}with-dump-email} +\item [ {-}{\-}with-dump-email=\lt{}email-address\gt{}] + \index[general]{{-}{\-}with-dump-email} This option specifies the email address where any core dumps should be set. This option is normally only used by developers. -\item [ {-}{-}with-pid-dir=\lt{}PATH\gt{} ] - \index[general]{{-}{-}with-pid-dir} +\item [ {-}{\-}with-pid-dir=\lt{}PATH\gt{} ] + \index[general]{{-}{\-}with-pid-dir} This specifies where Bacula should place the process id file during execution. The default is: {\bf /var/run}. This directory is not created by the install process, so you must ensure that it exists before using Bacula the first time. -\item [ {-}{-}with-subsys-dir=\lt{}PATH\gt{}] - \index[general]{{-}{-}with-subsys-dir} +\item [ {-}{\-}with-subsys-dir=\lt{}PATH\gt{}] + \index[general]{{-}{\-}with-subsys-dir} This specifies where Bacula should place the subsystem lock file during execution. The default is {\bf /var/run/subsys}. Please make sure that you do not specify the same directory for this directory and for the {\bf sbindir} @@ -1164,26 +1107,26 @@ $ nm /usr/local/lib/libpq.a | grep mutex subsys directory is not created by the Bacula install, so you must be sure to create it before using Bacula. -\item [ {-}{-}with-dir-password=\lt{}Password\gt{}] - \index[general]{{-}{-}with-dir-password} +\item [ {-}{\-}with-dir-password=\lt{}Password\gt{}] + \index[general]{{-}{\-}with-dir-password} This option allows you to specify the password used to access the Director (normally from the Console program). If it is not specified, configure will automatically create a random password. -\item [ {-}{-}with-fd-password=\lt{}Password\gt{} ] - \index[general]{{-}{-}with-fd-password} +\item [ {-}{\-}with-fd-password=\lt{}Password\gt{} ] + \index[general]{{-}{\-}with-fd-password} This option allows you to specify the password used to access the File daemon (normally called from the Director). If it is not specified, configure will automatically create a random password. -\item [ {-}{-}with-sd-password=\lt{}Password\gt{} ] - \index[general]{{-}{-}with-sd-password} +\item [ {-}{\-}with-sd-password=\lt{}Password\gt{} ] + \index[general]{{-}{\-}with-sd-password} This option allows you to specify the password used to access the Storage daemon (normally called from the Director). If it is not specified, configure will automatically create a random password. -\item [ {-}{-}with-dir-user=\lt{}User\gt{} ] - \index[general]{{-}{-}with-dir-user} +\item [ {-}{\-}with-dir-user=\lt{}User\gt{} ] + \index[general]{{-}{\-}with-dir-user} This option allows you to specify the Userid used to run the Director. The Director must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the UserId @@ -1192,8 +1135,8 @@ $ nm /usr/local/lib/libpq.a | grep mutex create the User prior to running {\bf make install}, because the working directory owner will be set to {\bf User}. -\item [ {-}{-}with-dir-group=\lt{}Group\gt{} ] - \index[general]{{-}{-}with-dir-group} +\item [ {-}{\-}with-dir-group=\lt{}Group\gt{} ] + \index[general]{{-}{\-}with-dir-group} This option allows you to specify the GroupId used to run the Director. The Director must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the GroupId specified @@ -1202,8 +1145,8 @@ $ nm /usr/local/lib/libpq.a | grep mutex create the Group prior to running {\bf make install}, because the working directory group will be set to {\bf Group}. -\item [ {-}{-}with-sd-user=\lt{}User\gt{} ] - \index[general]{{-}{-}with-sd-user} +\item [ {-}{\-}with-sd-user=\lt{}User\gt{} ] + \index[general]{{-}{\-}with-sd-user} This option allows you to specify the Userid used to run the Storage daemon. The Storage daemon must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the UserId @@ -1211,53 +1154,53 @@ $ nm /usr/local/lib/libpq.a | grep mutex that the Storage daemon has access to all the devices (tape drives, ...) that it needs. -\item [ {-}{-}with-sd-group=\lt{}Group\gt{} ] - \index[general]{{-}{-}with-sd-group} +\item [ {-}{\-}with-sd-group=\lt{}Group\gt{} ] + \index[general]{{-}{\-}with-sd-group} This option allows you to specify the GroupId used to run the Storage daemon. The Storage daemon must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the GroupId specified on this option. -\item [ {-}{-}with-fd-user=\lt{}User\gt{} ] - \index[general]{{-}{-}with-fd-user} +\item [ {-}{\-}with-fd-user=\lt{}User\gt{} ] + \index[general]{{-}{\-}with-fd-user} This option allows you to specify the Userid used to run the File daemon. The File daemon must be started as root, and in most cases, it needs to run as root, so this option is used only in very special cases, after doing preliminary initializations, it can "drop" to the UserId specified on this option. -\item [ {-}{-}with-fd-group=\lt{}Group\gt{} ] - \index[general]{{-}{-}with-fd-group} +\item [ {-}{\-}with-fd-group=\lt{}Group\gt{} ] + \index[general]{{-}{\-}with-fd-group} This option allows you to specify the GroupId used to run the File daemon. The File daemon must be started as root, and in most cases, it must be run as root, however, after doing preliminary initializations, it can "drop" to the GroupId specified on this option. -\item [ {-}{-}with-mon-dir-password=\lt{}Password\gt{}] - \index[general]{{-}{-}with-mon-dir-password} +\item [ {-}{\-}with-mon-dir-password=\lt{}Password\gt{}] + \index[general]{{-}{\-}with-mon-dir-password} This option allows you to specify the password used to access the Directory from the monitor. If it is not specified, configure will automatically create a random password. -\item [ {-}{-}with-mon-fd-password=\lt{}Password\gt{} ] - \index[general]{{-}{-}with-mon-fd-password} +\item [ {-}{\-}with-mon-fd-password=\lt{}Password\gt{} ] + \index[general]{{-}{\-}with-mon-fd-password} This option allows you to specify the password used to access the File daemon from the Monitor. If it is not specified, configure will automatically create a random password. -\item [ {-}{-}with-mon-sd-password=\lt{}Password\gt{} ] - \index[general]{{-}{-}with-mon-sd-password} +\item [ {-}{\-}with-mon-sd-password=\lt{}Password\gt{} ] + \index[general]{{-}{\-}with-mon-sd-password} This option allows you to specify the password used to access the Storage daemon from the Monitor. If it is not specified, configure will automatically create a random password. -\item [ {-}{-}with-db-name=\lt{}database-name\gt{} ] - \index[general]{{-}{-}with-db-name} +\item [ {-}{\-}with-db-name=\lt{}database-name\gt{} ] + \index[general]{{-}{\-}with-db-name} This option allows you to specify the database name to be used in the conf files. The default is bacula. -\item [ {-}{-}with-db-user=\lt{}database-user\gt{} ] - \index[general]{{-}{-}with-db-user} +\item [ {-}{\-}with-db-user=\lt{}database-user\gt{} ] + \index[general]{{-}{\-}with-db-user} This option allows you to specify the database user name to be used in the conf files. The default is bacula. @@ -1311,7 +1254,6 @@ CFLAGS="-g -Wall" ./configure \ --with-pid-dir=$HOME/bacula/bin/working \ --with-subsys-dir=$HOME/bacula/bin/working \ --enable-bat \ - --with-qwt=$HOME/bacula/depkgs/qwt \ --enable-conio \end{verbatim} \normalsize @@ -1329,7 +1271,6 @@ CFLAGS="-g -Wall" ./configure \ --with-working-dir=$HOME/bacula/working --with-pid-dir=$HOME/bacula/bin/working \ --with-subsys-dir=$HOME/bacula/bin/working - --enable-gnome \ --enable-conio \end{verbatim} \normalsize @@ -1344,7 +1285,6 @@ CFLAGS="-g -Wall" ./configure \ --with-scriptdir=/etc/bacula \ --enable-smartalloc \ --enable-bat \ - --with-qwt=$HOME/bacula/depkgs/qwt \ --with-mysql \ --with-working-dir=/var/bacula \ --with-pid-dir=/var/run \ @@ -1471,9 +1411,7 @@ CFLAGS="-g -Wall" \ --sysconfdir=$HOME/bacula/bin \ --mandir=$HOME/bacula/bin \ --enable-smartalloc \ - --enable-gnome \ --enable-bat \ - --with-qwt=$HOME/bacula/depkgs/qwt \ --enable-bwx-console \ --enable-tray-monitor \ --with-pid-dir=$HOME/bacula/bin/working \ @@ -1647,9 +1585,8 @@ going to run it to backup your system. After doing a {\bf make install} the following files will be installed on your system (more or less). The exact files and location (directory) for each file -depends on your {\bf ./configure} command (e.g. bgnome-console and -bgnome-console.conf are not installed if you do not configure GNOME. Also, if -you are using SQLite instead of MySQL, some of the files will be different). +depends on your {\bf ./configure} command (e.g. if you are using SQLite instead +of MySQL, some of the files will be different). NOTE: it is quite probable that this list is out of date. But it is a starting point. @@ -1678,8 +1615,6 @@ dbcheck delete_catalog_backup drop_bacula_tables drop_mysql_tables -bgnome-console -bgnome-console.conf make_bacula_tables make_catalog_backup make_mysql_tables diff --git a/docs/manuals/es/main/lesser.tex b/docs/manuals/es/main/lesser.tex index 6fcc81ed..5922ba6d 100644 --- a/docs/manuals/es/main/lesser.tex +++ b/docs/manuals/es/main/lesser.tex @@ -7,24 +7,24 @@ \index[general]{License!GNU Lesser General Public } \elink{image of a Philosophical GNU} -{\url{http://www.gnu.org/graphics/philosophicalgnu.html}} [ -\elink{English}{\url{http://www.gnu.org/copyleft/lesser.html}} | -\elink{Japanese}{\url{http://www.gnu.org/copyleft/lesser.ja.html}} ] +{http://www.gnu.org/graphics/philosophicalgnu.html} [ +\elink{English}{http://www.gnu.org/copyleft/lesser.html} | +\elink{Japanese}{http://www.gnu.org/copyleft/lesser.ja.html} ] \begin{itemize} \item \elink{Why you shouldn't use the Lesser GPL for your next - library}{\url{http://www.gnu.org/philosophy/why-not-lgpl.html}} + library}{http://www.gnu.org/philosophy/why-not-lgpl.html} \item \elink{What to do if you see a possible LGPL - violation}{\url{http://www.gnu.org/copyleft/gpl-violation.html}} + violation}{http://www.gnu.org/copyleft/gpl-violation.html} \item \elink{Translations of the LGPL} -{\url{http://www.gnu.org/copyleft/copyleft.html\#translationsLGPL}} +{http://www.gnu.org/copyleft/copyleft.html\#translationsLGPL} \item The GNU Lesser General Public License as a - \elink{text file}{\url{http://www.gnu.org/copyleft/lesser.txt}} + \elink{text file}{http://www.gnu.org/copyleft/lesser.txt} \item The GNU Lesser General Public License as a - \elink{Texinfo}{\url{http://www.gnu.org/copyleft/lesser.texi}} file + \elink{Texinfo}{http://www.gnu.org/copyleft/lesser.texi} file \end{itemize} @@ -32,7 +32,7 @@ This GNU Lesser General Public License counts as the successor of the GNU Library General Public License. For an explanation of why this change was necessary, read the \elink{Why you shouldn't use the Lesser GPL for your next -library}{\url{http://www.gnu.org/philosophy/why-not-lgpl.html}} article. +library}{http://www.gnu.org/philosophy/why-not-lgpl.html} article. \section{Table of Contents} \index[general]{Table of Contents } @@ -554,11 +554,11 @@ Ty Coon, President of Vice That's all there is to it! Return to -\elink{GNU's home page}{\url{http://www.gnu.org/home.html}}. +\elink{GNU's home page}{http://www.gnu.org/home.html}. FSF \& GNU inquiries \& questions to \elink{gnu@gnu.org}{mailto:gnu@gnu.org}. Other -\elink{ways to contact}{\url{http://www.gnu.org/home.html\#ContactInfo}} the FSF. +\elink{ways to contact}{http://www.gnu.org/home.html\#ContactInfo} the FSF. Comments on these web pages to \elink{webmasters@www.gnu.org}{mailto:webmasters@www.gnu.org}, send other -- 2.39.2