LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

lots of little updates, added info about new apps, deleted tracers

This commit is contained in:
tille 2005-03-01 21:54:42 +00:00
parent f44fc012e4
commit 1f851de37c
11 changed files with 58 additions and 440 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
LDP/guide/docbook/Intro-Linux/abook.xml
View File

@ -35,12 +35,13 @@
</affiliation>
</author>
</authorgroup>
<edition>Version 1.16 20041206</edition>
<edition>Version 1.17 20050301</edition>
<pubdate>First published December 2002</pubdate>
<copyright>
<year>2002</year>
<year>2003</year>
<year>2004</year>
<year>2005</year>
<holder>Machtelt Garrels</holder>
</copyright>
<isbn>ISBN 90-808529-1-0</isbn>
@ -140,6 +141,12 @@
<title>Revision History</title>
<para>
<revhistory>
<revision>
<revnumber>1.17</revnumber>
<date>2005-03-01</date>
<authorinitials>MG</authorinitials>
<revremark>Lots of little details that were outdated, added several notes, removed tracer image, added info about new apps.</revremark>
</revision>
<revision>
<revnumber>1.16</revnumber>
<date>2004-12-06</date>

74
LDP/guide/docbook/Intro-Linux/chap1.xml
View File

@ -183,13 +183,6 @@ wristwatches. This makes Linux the only operating system in the world covering
such a wide range of hardware.</para>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_01_02">
@ -254,22 +247,16 @@ examples; these sites have a lot of screenshots that will give you a glimpse of
what Linux on the desktop can be like:
</para>
<itemizedlist>
<listitem><para><ulink url="http://ximian.com/products/desktop/screenshots.html" />
<listitem><para><ulink url="http://www.gnome.org" />
</para></listitem>
<listitem><para><ulink url="http://kde.org/screenshots/" />
</para></listitem>
<listitem><para><ulink url="http://www.codeweavers.com/products/office/" />
<listitem><para><ulink url="http://www.openoffice.org" />
</para></listitem>
<listitem><para><ulink url="http://www.mozilla.org" /></para></listitem>
</itemizedlist>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_01_03"><title>Does Linux have a future?</title>
@ -359,13 +346,6 @@ home:
</figure>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_01_04"><title>Properties of Linux</title>
@ -433,11 +413,11 @@ just recycling your old 486, Linux will do that as well.
</para>
</listitem>
<listitem>
<para>The Linux OS and Linux applications have very short debug-times:
<para>The Linux OS and quite some Linux applications have very short debug-times:
</para>
<para>Because Linux has been developed and tested by thousands of people, both
errors and people to fix them are found very quickly. It often happens that
there are only a couple of hours between discovery and fixing of a bug.
errors and people to fix them are usually found rather quickly. It sometimes happens that
there are only a couple of hours between discovery and fixing of a bug.
</para>
</listitem>
</itemizedlist>
@ -462,10 +442,10 @@ making, for example, TurboLinux more suitable for the small and medium
enterprise, RedHat for servers and SuSE for workstations. However, the
differences are likely to be very superficial. The best strategy is to test a
couple of distributions; unfortunately not everybody has the time for this.
Luckily, there is plenty of advice on the subject of choosing your Linux. One
place is <ulink url="http://www.linuxjournal.com/bg/advice/distributions.php">
LinuxJournal</ulink>, which discusses hardware and support, among many other
subjects. The <ulink url="http://www.tldp.org/HOWTO/Installation-HOWTO/">
Luckily, there is plenty of advice on the subject of choosing your Linux.
A quick search on <ulink url="http://www.google.com/linux">Google</ulink>, using the keywords <quote>choosing your distribution</quote> brings up tens of
links to good advise.
The <ulink url="http://www.tldp.org/HOWTO/Installation-HOWTO/">
Installation HOWTO</ulink> also discusses choosing your distribution.
</para>
</listitem>
@ -473,6 +453,7 @@ Installation HOWTO</ulink> also discusses choosing your distribution.
<para>Linux is not very user friendly and confusing for beginners:
</para>
<para>
It must be said that Linux, at least the core system, is less userfriendly to use than MS Windows and certainly more difficult than MacOS, but...
In light of its popularity, considerable effort has been made to make Linux
even easier to use, especially for new users. More information is being released
daily, such as this guide, to help fill the gap for documentation available to
@ -497,13 +478,6 @@ project that continues to strive for perfection.
</itemizedlist>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_01_05"><title>Linux Flavors</title>
@ -524,7 +498,7 @@ interfaces are built, remain the same. The Linux system is based on GNU tools
(Gnu's Not UNIX), which provide a set of standard ways to handle and use the
system. All GNU tools are open source, so they can be installed on any system.
Most distributions offer pre-compiled packages of most common tools, such as RPM
packages on RedHat and dpkg packages on Debian, so you needn't be a programmer
packages on RedHat and Debian packages (also called deb or dpkg) on Debian, so you needn't be a programmer
to install a package on your system. However, if you are and like doing things
yourself, you will enjoy Linux all the better, since most distributions come
with a complete set of development tools, allowing installation of new software
@ -539,6 +513,7 @@ it does not exist in a pre-packaged form suitable for your system.
</para></listitem>
<listitem><para>GDB: The GNU Debugger
</para></listitem>
<listitem><para>coreutils: a set of basic UNIX-style utilities, such as <command>ls</command>, <command>cat</command> and <command>chmod</command></para></listitem>
<listitem><para>Findutils: to search and find files
</para></listitem>
<listitem><para>Fontutils: to convert fonts from one format to another or make
@ -637,7 +612,7 @@ mainstream distribution, supporting all common hardware and applications by
default. The following are very good choices for novices:
</para>
<itemizedlist>
<listitem><para><ulink url="http://fedora.redhat.com">Fedora Linux</ulink>
<listitem><para><ulink url="http://fedora.redhat.com">Fedora Core</ulink>
</para></listitem>
<listitem><para><ulink url="http://www.suse.de">SuSE Linux</ulink>
</para></listitem>
@ -651,13 +626,6 @@ operating system that runs from your CD-ROM, you don't need to install anything.
</para>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_01_06"><title>Summary</title>
@ -676,13 +644,6 @@ for handling the operating system.
</para></listitem>
</itemizedlist>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_01_07"><title>Exercises</title>
@ -762,12 +723,5 @@ http://www.ibiblio.org/mdw/HOWTO/Installation-HOWTO/index.html</ulink>.
successful.
</para>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
</chapter>

46
LDP/guide/docbook/Intro-Linux/chap10.xml
View File

@ -283,13 +283,6 @@ Turner Broadcasting (CNN-DOM)
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_10_02"><title>Internet/Intranet applications</title>
<para>The Linux system is a great platform for offering networking services. In this section, we will try to give an overview of most common network servers and applications.</para>
@ -455,6 +448,7 @@ bookmarks get lookup mkdir quit show
<listitem><para><command>Konversation</command>, <command>KVIrc</command> and many other K-tools from the KDE suite.</para></listitem>
<listitem><para><command>gnomemeeting</command>: videoconferencing program for UNIX.</para></listitem>
<listitem><para><command>jabber</command>: Open Source Instant Messenging platform, compatible with ICQ, AIM, Yahoo, MSN, IRC, SMTP and much more.</para></listitem>
<listitem><para><command>psi</command>: jabber client, see <ulink url="http://psi.affinix.com/">the PSI Jabber Client Homepage</ulink>.</para></listitem>
</itemizedlist>
@ -532,13 +526,6 @@ On the negative side, if you want to use LDAP, you will need LDAP-enabled applic
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_10_03"><title>Remote execution of applications</title>
<sect2 id="sect_10_03_01"><title>Introduction</title>
@ -704,6 +691,9 @@ Fetching /var/tmp/Schedule.sdc.gz to Schedule.sdc.gz
<prompt>lenny /var/tmp&gt;</prompt>
</screen>
<note><title>Secure copy or FTP GUIs</title>
<para>Don't feel comfortable with the command line yet? Try <application>Konqueror</application>'s capabilities for secure remote copy, or install <application>Putty</application>.</para>
</note>
</sect3>
<sect3 id="sect_10_03_04_05"><title>Authentication keys</title>
<para>The <command>ssh-keygen</command> command generates, manages and converts authentication keys for <command>ssh</command>. It can create RSA keys for use by SSH protocol version 1 and RSA or DSA keys for use by SSH protocol version 2.</para>
@ -729,13 +719,6 @@ Fetching /var/tmp/Schedule.sdc.gz to Schedule.sdc.gz
<para>Surprise your friends (or management) with the fullscreen mode, multiple types of keyboard layouts and single application mode, just like the real thing. The <command>man <parameter>rdesktop</parameter></command> manual provides more information. The project's homepage is at <ulink url="http://www.rdesktop.org/" />.</para>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_10_05"><title>Security</title>
<sect2 id="sect_10_05_01"><title>Introduction</title>
@ -867,13 +850,6 @@ tcp 0 0 ::1:x11-ssh-offset *:* LISTEN
</itemizedlist>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_10_06"><title>Summary</title>
<para>Linux and networking go hand in hand. The Linux kernel has support for all common and most uncommon network protocols. The standard UNIX networking tools are provided in each distribution. Next to those, most distributions offer tools for easy network installation and management.</para>
@ -881,13 +857,6 @@ tcp 0 0 ::1:x11-ssh-offset *:* LISTEN
<para>We briefly touched the subject of security. Linux is an ideal firewall system, light and cheap, but can be used in several other network functions such as routers and proxy servers.</para>
<para>Increasing network security is mainly done by applying frequent updates and common sense.</para>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_10_07"><title>Exercises</title>
@ -922,12 +891,5 @@ tcp 0 0 ::1:x11-ssh-offset *:* LISTEN
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
</chapter>

41
LDP/guide/docbook/Intro-Linux/chap2.xml
View File

@ -36,7 +36,7 @@ user name and password. You always need to authenticate to the system. As we
already mentioned in the exercise from <xref linkend="chap_01" />, most PC-based
Linux systems have two basic modes for a system to run in: either quick and
sober in text console mode, which looks like DOS with mouse, multitasking and
multi-user features, or in graphical console mode, which looks better but eats
multi-user features, or in graphical mode, which looks better but eats
more system resources.
</para>
</sect2>
@ -98,13 +98,6 @@ blast login: _
<para>Now that we know how to connect to and disconnect from the system, we're ready for our first commands.</para>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_02_02"><title>Absolute basics</title>
@ -227,13 +220,6 @@ lsb_release lsof lspnp lsusb
</screen>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_02_03"><title>Getting help</title>
<sect2 id="sect_02_03_01"><title>Be warned</title>
@ -275,7 +261,7 @@ OPTIONS
-C config_file
lines 1-27
</screen>
<para>Browse to the next page using the space bar. You can go back to the previous page using the b-key. When you reach the end, <command>man</command> will quit and you get the prompt back, or type <keycap>q</keycap> if you want to leave the man page before reaching the end.</para>
<para>Browse to the next page using the space bar. You can go back to the previous page using the b-key. When you reach the end, <command>man</command> will usually quit and you get the prompt back. Type <keycap>q</keycap> if you want to leave the man page before reaching the end, or if the viewer does not quit automatically at the end of the page.</para>
<para>Each man page usually contains a couple of standard sections, as we can see from the <command>man <option>man</option></command> example:</para>
<itemizedlist>
<listitem><para>The first line contains the name of the command you are reading about, and the id of the section in which this man page is located. The man pages are ordered in chapters. Commands are likely to have multiple man pages, for example the man page from the user section, the man page from the system admin section, and the man page from the programmer section.</para></listitem>
@ -351,7 +337,7 @@ viewres (1x) - graphical class browser for Xt
<para>After pressing <keycap>Enter</keycap> you will see that a lot of browser related stuff is on your machine: not only web browsers, but also file and FTP browsers, and browsers for documentation. If you have development packages installed, you may also have the accompanying man pages dealing with writing programs having to do with browsers. Generally, a command with a man page in section one, so one marked with <quote>(1)</quote>, is suitable for trying out as a user. The user who issued the above <command>apropos</command> might consequently try to start the commands <command>galeon</command>, <command>lynx</command> or <command>opera</command>, since these clearly have to do with browsing the world wide web.</para>
</sect3>
<sect3 id="sect_02_03_03_03"><title>The --help option</title>
<para>Most GNU commands support the <option>--help</option>, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <command>cat</command>:</para>
<para>Most GNU commands support the <option>--help</option>, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <command>cat</command> command:</para>
<screen>
<prompt>userprompt@host:</prompt> <command>cat --help</command>
Usage: cat [OPTION] [FILE]...
@ -402,25 +388,11 @@ Report bugs to &lt;bug-textutils@gnu.org&gt;.
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_02_04"><title>Summary</title>
<para>Linux traditionally operates in text mode or in graphical mode. Since CPU power and RAM are not the cost anymore these days, every Linux user can afford to work in graphical mode and will usually do so. This does not mean that you don't have to know about text mode: we will work in the text environment throughout this course, using a terminal window.</para>
<para>Linux encourages its users to acquire knowledge and to become independent. Inevitably, you will have to read a lot of documentation to achieve that goal; that is why, as you will notice, we refer to extra documentation for almost every command, tool and problem listed in this book. The more docs you read, the easier it will become and the faster you will leaf through manuals. Make reading documentation a habit as soon as possible. When you don't know the answer to a problem, refering to the documentation should become a second nature.</para>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_02_05"><title>Exercises</title>
<para>Most of what we learn is by making mistakes and by seeing how things can go wrong. These exercises are made to get you to read some error messages. The order in which you do these exercises is important.</para>
@ -529,12 +501,5 @@ Report bugs to &lt;bug-textutils@gnu.org&gt;.
</itemizedlist>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
</chapter>

111
LDP/guide/docbook/Intro-Linux/chap3.xml
View File

@ -279,13 +279,6 @@ Filesystem Size Used Avail Use% Mounted on
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_03_02"><title>Orientation in the file system</title>
<sect2 id="sect_03_02_01"><title>The path</title>
@ -367,8 +360,8 @@ oriental/ pop/ sixties/
<sect3 id="sect_03_02_03_02"><title>The shell</title>
<sect4><title>What is a shell?</title>
<para>When I was looking for an appropriate explanation on the concept of a <emphasis>shell</emphasis>, it gave me more trouble than I expected. All kinds of definitions are available, ranging from the simple comparison that <quote>the shell is the steering wheel of the car</quote>, to the vague definition in the Bash manual which says that <quote>bash is an sh-compatible command language interpreter,</quote> or an even more obscure expression, <quote>a shell manages the interaction between the system and its users</quote>. A shell is much more than that.</para>
<para>A shell can best be compared with a way of talking to the computer, a language. Most users do know that other language, the click-and-point language of the desktop. But in that language the user is treated as a baby, asked to pick from what is presented to him.</para>
<para>The shell, on the other hand, is an advanced way of communicating with the system, because it allows for conversation and taking initiative. Both partners in the communication are equal, so new ideas can be tested. The shell allows the user to handle a system in a flexible way, and is also a means of stress reduction. Who does not appreciate being treated like an adult?</para>
<para>A shell can best be compared with a way of talking to the computer, a language. Most users do know that other language, the click-and-point language of the desktop. But in that language the computer is leading the conversation, while the user has the passive role of picking tasks from the ones presented. It is very difficult for a programmer to include all options and possible uses of a command in the GUI-format. Thus, GUIs are almost always less capable than the command or commands that form the backend.</para>
<para>The shell, on the other hand, is an advanced way of communicating with the system, because it allows for two-way conversation and taking initiative. Both partners in the communication are equal, so new ideas can be tested. The shell allows the user to handle a system in a very flexible way. An additional asset is that the shell allows for task automation.</para>
</sect4>
<sect4><title>Shell types</title>
<para>Just like people know different languages and dialects, the computer knows different shell types:</para>
@ -420,6 +413,9 @@ mia:L2NOfqdlPrHwE:504:504:Mia Maya:/home/mia:/bin/bash
Diskquotas for user pierre (uid 501): none
</screen>
<para>In case quotas have been set, you get a list of the limited partitions and their specific limitations. Exceeding the limits may be tolerated during a grace period with fewer or no restrictions at all. Detailed information can be found using the <command>info <parameter>quota</parameter></command> or <command>man <parameter>quota</parameter></command> commands.</para>
<note><title>No Quota?</title>
<para>If your system can not find the <command>quota</command>, then no limitation of file system usage is being applied.</para>
</note>
<para>Your home directory is indicated by a tilde (~), shorthand for <filename>/path_to_home/user_name</filename>. This same path is stored in the <varname>HOME</varname> variable, so you don't have to do anything to activate it. A simple application: switch from <filename>/var/music/albums/arno/2001</filename> to <filename>images</filename> in your home directory using one elegant command:</para>
<screen>
<prompt>rom:/var/music/albums/arno/2001&gt;</prompt> <command>cd ~/images</command>
@ -433,7 +429,7 @@ Diskquotas for user pierre (uid 501): none
<sect2 id="sect_03_02_04"><title>The most important configuration files</title>
<para>As we mentioned before, most configuration files are stored in the <filename>/etc</filename> directory. Content can be viewed using the <command>cat</command> command, which sends text files to the standard output (usually your monitor). The syntax is straight forward:</para>
<cmdsynopsis><command>cat <filename>file1</filename> <filename>file2</filename> ... <filename>fileN</filename></command></cmdsynopsis>
<para>In this section we try to give an overview of the most common configuration files. This is certainly not a complete list. Adding extra packages may also add extra configuration files in <filename>/etc</filename>. When reading the configuration files, you will find that they are usually quite well commented and self-explanatory. Some files also have man pages which contain extra documentation, such as <command>man <parameter>aliases</parameter></command>.</para>
<para>In this section we try to give an overview of the most common configuration files. This is certainly not a complete list. Adding extra packages may also add extra configuration files in <filename>/etc</filename>. When reading the configuration files, you will find that they are usually quite well commented and self-explanatory. Some files also have man pages which contain extra documentation, such as <command>man <parameter>group</parameter></command>.</para>
<table frame="all">
<title>Most common configuration files</title>
@ -448,9 +444,14 @@ Diskquotas for user pierre (uid 501): none
<row>
<entry><filename>aliases</filename>
</entry>
<entry>Mail aliases file for use with the Sendmail mail server. Running a mail server on each and every system has long been common use in the UNIX world, and almost every Linux distribution still comes with a Sendmail package. In this file local user names are matched with real names as they occur in E-mail addresses, or with other local addresses.
<entry>Mail aliases file for use with the Sendmail and Postfix mail server. Running a mail server on each and every system has long been common use in the UNIX world, and almost every Linux distribution still comes with a Sendmail package. In this file local user names are matched with real names as they occur in E-mail addresses, or with other local addresses.
</entry>
</row>
<row><entry>
<filename>apache</filename>
</entry><entry>Config files for the Apache web server.
</entry>
</row>
<row><entry>
<filename>bashrc</filename>
</entry><entry>The system-wide configuration file for the Bourne Again SHell. Defines functions and aliases for all users. Other shells may have their own system-wide config files, like <filename>cshrc</filename>.
@ -493,24 +494,12 @@ Diskquotas for user pierre (uid 501): none
</entry>
</row>
<row><entry>
<filename>grub.conf</filename>
</entry><entry>Boot information.
</entry>
</row>
<row><entry>
<filename>hosts</filename>
</entry><entry>A list of machines that can be contacted using the network, but without the need for a domain name service. This has nothing to do with the system's network configuration, which is done in <filename>/etc/sysconfig</filename>.
</entry>
</row>
<row><entry>
<filename>httpd</filename>
</entry><entry>Config files for the Apache web server.
</entry>
</row>
<row><entry>
<filename>inittab</filename>
</entry><entry>Information for booting: mode, number of text consoles etc.
@ -531,7 +520,7 @@ Diskquotas for user pierre (uid 501): none
<row><entry>
<filename>lilo.conf</filename>, <filename>silo.conf</filename>, <filename>aboot.conf</filename> etc.
</entry><entry>Boot information for the LInux LOader, the system for booting that was in use before Lilo changed to GRUB.
</entry><entry>Boot information for the LInux LOader, the system for booting that is now gradually being replaced with GRUB.
</entry>
</row>
@ -620,7 +609,7 @@ Diskquotas for user pierre (uid 501): none
</row>
<row><entry>
<filename>sndconfig</filename> and <filename>sound</filename>
<filename>sndconfig</filename> or <filename>sound</filename>
</entry><entry>Configuration of the sound card and sound events.
</entry>
</row>
@ -644,7 +633,7 @@ Diskquotas for user pierre (uid 501): none
</row>
<row><entry>
<filename>xinetd.*</filename>
<filename>xinetd.*</filename> or <filename>inetd.conf</filename>
</entry>
<entry>Configuration files for Internet services that are run from the system's (extended) Internet services daemon (servers that don't run an independent daemon).</entry>
</row>
@ -671,7 +660,7 @@ Diskquotas for user pierre (uid 501): none
<row><entry><filename>console</filename></entry><entry>Special entry for the currently used console.</entry></row>
<row><entry><filename>cua*</filename></entry><entry>Serial ports</entry></row>
<row><entry><filename>dsp*</filename></entry><entry>Devices for sampling and recording</entry></row>
<row><entry><filename>fd*</filename></entry><entry>Entries for most kinds of floppy drives, the default is <filename>/dev/fd0H1440</filename>, a floppy drive for 1.44 MB floppies.</entry></row>
<row><entry><filename>fd*</filename></entry><entry>Entries for most kinds of floppy drives, the default is <filename>/dev/fd0</filename>, a floppy drive for 1.44 MB floppies.</entry></row>
<row><entry><filename>hd[a-t][1-16]</filename></entry><entry>Standard support for IDE drives with maximum amount of partitions each.</entry></row>
<row><entry><filename>ir*</filename></entry><entry>Infrared devices</entry></row>
<row><entry><filename>isdn*</filename></entry><entry>Management of ISDN connections</entry></row>
@ -681,7 +670,7 @@ Diskquotas for user pierre (uid 501): none
<row><entry><filename>midi*</filename></entry><entry>midi player</entry></row>
<row><entry><filename>mixer*</filename> and <filename>music</filename></entry><entry>Idealized model of a mixer (combines or adds signals)</entry></row>
<row><entry><filename>modem</filename></entry><entry>Modem</entry></row>
<row><entry><filename>mouse</filename> (also msmouse, logimouse, psmouse</entry><entry>All kinds of mouses</entry></row>
<row><entry><filename>mouse</filename> (also msmouse, logimouse, psmouse, input/mice, psaux)</entry><entry>All kinds of mouses</entry></row>
<row><entry><filename>null</filename></entry><entry>Bottomless garbage can</entry></row>
<row><entry><filename>par*</filename></entry><entry>Entries for parallel port support</entry></row>
<row><entry><filename>pty*</filename></entry><entry>Pseudo terminals</entry></row>
@ -713,13 +702,6 @@ Diskquotas for user pierre (uid 501): none
<para>The <filename>/var/lib/rpm</filename> directory is specific to RPM-based (RedHat Package Manager) distributions; it is where RPM package information is stored.</para>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_03_03"><title>Manipulating files</title>
@ -992,15 +974,7 @@ rm: remove directory `archive'? <command>y</command>
<prompt>gerrit:~&gt;</prompt> <command>which -a ls</command>
ls is aliased to `ls -F --color=auto'
ls is /bin/ls
<prompt>gerrit:~&gt;</prompt> <command>which -a which</command>
which is aliased to `type'
which is /usr/bin/which
<prompt>gerrit:~&gt;</prompt> <command>which type</command>
type is a shell builtin
</screen>
<para>This actually means that <command>which</command> is built-in in the shell, but that there is also a <command>which</command> <quote>stand alone version</quote>. The shell built-in version precedes the <command>which</command> in <filename>/usr/bin</filename>, which is still there for compatibility with UNIX.</para>
</sect3>
<sect3 id="sect_03_03_03_03"><title>Find and locate</title>
<para>These are the real tools, used when searching other paths beside those listed in the search path. The <command>find</command> tool, known from UNIX, is very powerful, which may be the cause of a somewhat more difficult syntax. GNU <command>find</command>, however, deals with the syntax problems. This command not only allows you to search file names, it can also accept file size, date of last change and other file properties as criteria for a search. The most common use is for finding file names:</para>
@ -1021,7 +995,7 @@ psychotic_chaos.mp3
<para>This command will call on <command>rm</command> as many times as a file answering the requirements is found. In the worst case, this might be thousands or millions of times. This is quite a load on your system.</para>
<para>A more realistic way of working would be the use of a pipe (|) and the <command>xargs</command> tool with <command>rm</command> as an argument. This way, the <command>rm</command> command is only called when the command line is full, instead of for every file. See <xref linkend="chap_05" /> for more on using I/O redirection to ease everyday tasks.</para>
</tip>
<para>Later on (in 1999 according to the man pages, after 20 years of <command>find</command>), <command>locate</command> was developed. This program is easier to use, but more restricted than <command>find</command>, since its output is based on a file index database that is updated only once every day. On the other hand, a search in the <command>locate</command> database is less time- and CPU-consuming than a search with <command>find</command>.</para>
<para>Later on (in 1999 according to the man pages, after 20 years of <command>find</command>), <command>locate</command> was developed. This program is easier to use, but more restricted than <command>find</command>, since its output is based on a file index database that is updated only once every day. On the other hand, a search in the <command>locate</command> database uses less resources than <command>find</command> and therefor shows the results nearly instantly.</para>
<para>Most Linux distributions use <command>slocate</command> these days, security enhanced locate, the modern version of <command>locate</command> that prevents users from getting output they have no right to read. The files in <emphasis>root</emphasis>'s home directory are such an example, these are not normally accessible to the public. A user who wants to find someone who knows about the C-shell may issue the command <command>locate <filename>.cshrc</filename></command>, to display all users who have a customized configuration file for the C shell. Supposing the users <emphasis>root</emphasis> and <emphasis>jenny</emphasis> are running C shell, then only the file <filename>/home/jenny/.cshrc</filename> will be displayed, and not the one in <emphasis>root</emphasis>'s home directory. On most systems, <command>locate</command> is a symbolic link to the <command>slocate</command> program:</para>
<screen>
<prompt>billy:~&gt;</prompt> <command>ls -l /usr/bin/locate</command>
@ -1095,11 +1069,11 @@ sent-mail: On Mon, 24 Dec 2001, Arno.Hintjens@celeb.com wrote:
<para><command>find</command> and <command>locate</command> are often used in combination with <command>grep</command> to define some serious queries. For more information, see <xref linkend="chap_05" /> on I/O redirection.</para>
</sect4>
<sect4 id="sect_03_03_03_04_02"><title>Special characters</title>
<para>Characters that have a special meaning to the shell have to be <emphasis>escaped</emphasis>. The escape character in Bash is backslash, as in most shells; this takes away the special meaning of the following character. The shell knows about quite some special characters, among the most common /, ., ? and *. A full list can be found in the Info pages and documentation for your shell. For instance, say that you want to display the lines containing <quote>searchstring*</quote> (where * matches the asterisk character) instead of any lines containing the string <quote>searchstring</quote>* (where * matches any amount of any character), you issue the command</para>
<cmdsynopsis><command>grep <parameter>"searchstring\*"</parameter> <filename>file(s)</filename></command></cmdsynopsis>
<para>Finding the string <quote>e.g.</quote> in a file will report all lines containing any character in the second and forth position of the search string. If you escape the dots, you will find the occurrences of the string representing the abbreviation for <quote>example given</quote>:</para>
<cmdsynopsis><command>grep <parameter>"e\.g\."</parameter> <filename>file</filename></command></cmdsynopsis>
<para>More in the <command>grep</command> Info pages.</para>
<para>Characters that have a special meaning to the shell have to be <emphasis>escaped</emphasis>. The escape character in Bash is backslash, as in most shells; this takes away the special meaning of the following character. The shell knows about quite some special characters, among the most common /, ., ? and *. A full list can be found in the Info pages and documentation for your shell.</para>
<para>For instance, say that you want to display the file <quote>*</quote> instead of all the files in a directory, you would have to use </para>
<cmdsynopsis><command>less <filename>\*</filename></command></cmdsynopsis>
<para>The same goes for filenames containing a space:</para>
<cmdsynopsis><command>cat <filename>This\ File</filename></command></cmdsynopsis>
</sect4>
</sect3>
@ -1107,7 +1081,7 @@ sent-mail: On Mon, 24 Dec 2001, Arno.Hintjens@celeb.com wrote:
<sect2 id="sect_03_03_04"><title>More ways to view file content</title>
<sect3 id="sect_03_03_04_01"><title>General</title>
<para>Apart from <command>cat</command>, which really doesn't do much more than sending files to the standard output, there are other tools to view file content.</para>
<para>The easiest way of course would be to use graphical tools instead of command line tools. In the introduction we already saw a glimpse of an office application, OpenOffice. Other examples are the GIMP (start up with <command>gimp</command> from the command line), the GNU Image Manipulation Program; <command>xpdf</command> to view Portable Document Format files (PDF); GhostView (<command>gv</command>) for viewing PostScript files; the Mozilla Project, <command>links</command> (a text mode browser), Konqueror, Opera and many others for web content; XMMS, CDplay and others for multi-media file content; AbiWord, Gnumeric, KOffice etc. for all kinds of office applications and so on. There are thousands of Linux applications; to list them all would take days.</para>
<para>The easiest way of course would be to use graphical tools instead of command line tools. In the introduction we already saw a glimpse of an office application, OpenOffice. Other examples are the GIMP (start up with <command>gimp</command> from the command line), the GNU Image Manipulation Program; <command>xpdf</command> to view Portable Document Format files (PDF); GhostView (<command>gv</command>) for viewing PostScript files; Mozilla/FireFox, <command>links</command> (a text mode browser), Konqueror, Opera and many others for web content; XMMS, CDplay and others for multimedia file content; AbiWord, Gnumeric, KOffice etc. for all kinds of office applications and so on. There are thousands of Linux applications; to list them all would take days.</para>
<para>Instead we keep concentrating on shell- or text-mode applications, which form the basics for all other applications. These commands work best in a text environment on files containing text. When in doubt, check first using the <command>file</command> command.</para>
<para>So let's see what text tools we have that are useful to look inside files.</para>
<note><title>Font problems</title>
@ -1171,7 +1145,7 @@ frm
</mediaobject>
</figure>
<para>Note that removing the target file for a symbolic link makes the link useless.</para>
<para>Each regular file is principally a hardlink. Hardlinks can not span across partitions, since they refer to inodes, and inode numbers are only unique within a given partition.</para>
<para>Each regular file is in principal a hardlink. Hardlinks can not span across partitions, since they refer to inodes, and inode numbers are only unique within a given partition.</para>
<para>It may be argued that there is a third kind of link, the <emphasis>user-space</emphasis> link, which is similar to a shortcut in MS Windows. These are files containing meta-data which can only be interpreted by the graphical file manager. To the kernel and the shell these are just normal files. They may end in a <emphasis>.desktop</emphasis> or <emphasis>.lnk</emphasis> suffix; an example can be found in <filename>~/.gnome-desktop</filename>:</para>
<screen>
<prompt>[dupont@boulot .gnome-desktop]$</prompt> <command>cat La\ Maison\ Dupont</command>
@ -1212,17 +1186,10 @@ lrwxrwxrwx 1 freddy freddy 17 Jan 22 11:07 Queen -&gt; /opt/mp3/Queen
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_03_04"><title>File security</title>
<sect2 id="sect_03_04_01"><title>Access rights: Linux's first line of defense</title>
<para>The Linux security model is based on the one used on UNIX systems, and is as rigid, and in some cases even more, as the UNIX security model, which is already quite robust. On a Linux system, every file is owned by a user and a group user. There is also a third category of users, those that are not the user owner and don't belong to the group owning the file. For each category of users, read, write and execute permissions can be granted or denied.</para>
<para>The Linux security model is based on the one used on UNIX systems, and is as rigid as the UNIX security model (and sometimes even more), which is already quite robust. On a Linux system, every file is owned by a user and a group user. There is also a third category of users, those that are not the user owner and don't belong to the group owning the file. For each category of users, read, write and execute permissions can be granted or denied.</para>
<para>We already used the <emphasis>long</emphasis> option to list files using the <command>ls <option>-l</option></command> command, though for other reasons. This command also displays file permissions for these three user categories; they are indicated by the nine characters that follow the first character, which is the file type indicator at the beginning of the file properties line. As seen in the examples below, the first three characters in this series of nine display access rights for the actual user that owns the file. The next three are for the group owner of the file, the last three for other users. The permissions are always in the same order: read, write, execute for the user, the group and the others. Some examples:</para>
<screen>
<prompt>marise:~&gt;</prompt> <command>ls -l To_Do</command>
@ -1342,7 +1309,7 @@ Hello, World
<entry><command>chmod <parameter>644</parameter> <filename>file</filename></command></entry><entry>A publicly readable file that can only be changed by the issuing user.</entry>
</row>
<row>
<entry><command>chmod <parameter>660</parameter> <filename>file</filename></command></entry><entry>Users belonging to your group can change this files, others don't have any access to it at all.</entry>
<entry><command>chmod <parameter>660</parameter> <filename>file</filename></command></entry><entry>Users belonging to your group can change this file, others don't have any access to it at all.</entry>
</row>
<row>
<entry><command>chmod <parameter>700</parameter> <filename>file</filename></command></entry><entry>Protects a file against any access from other users, while the issuing user still has full access.</entry>
@ -1465,7 +1432,7 @@ uid=1304(jacky) gid=(1304) groups=1304(jacky),2034(pproject)
<sect3 id="sect_03_04_02_05"><title>Special modes</title>
<para>For the system admin to not be bothered solving permission problems all the time, special access rights can be given to entire directories, or to separate programs. There are three special modes:</para>
<itemizedlist>
<listitem><para>Sticky bit mode: After execution of a job, the command is kept in the system memory. Originally this was a feature used a lot to save memory, but these days memory is inexpensive, so it is not used anymore for its optimizing capabilities on single files. When applied to an entire directory, however, the sticky bit has a different meaning. In that case, a user can only change files in this directory when she is the user owner of the file or when the file has appropriate permissions. This feature is used on directories like <filename>/var/tmp</filename>, that have to be accessible for everyone, but where it is not appropriate for users to change or delete each other's data. The sticky bit is indicated by a <emphasis>t</emphasis> at the end of the file permission field:</para>
<listitem><para>Sticky bit mode: After execution of a job, the command is kept in the system memory. Originally this was a feature used a lot to save memory: big jobs are loaded into memory only once. But these days memory is inexpensive and there are better techniques to manage it, so it is not used anymore for its optimizing capabilities on single files. When applied to an entire directory, however, the sticky bit has a different meaning. In that case, a user can only change files in this directory when she is the user owner of the file or when the file has appropriate permissions. This feature is used on directories like <filename>/var/tmp</filename>, that have to be accessible for everyone, but where it is not appropriate for users to change or delete each other's data. The sticky bit is indicated by a <emphasis>t</emphasis> at the end of the file permission field:</para>
<screen>
<prompt>mark:~&gt;</prompt> <command>ls -ld /var/tmp</command>
drwxrwxrwt 19 root root 8192 Jan 16 10:37 /var/tmp/
@ -1491,13 +1458,6 @@ drwxrws--- 4 root users 4096 Jul 25 2001 docs/
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_03_05"><title>Summary</title>
<para>On UNIX, as on Linux, all entities are in some way or another presented to the system as files with the appropriate file properties. Use of (predefined) paths allows the users and the system admin to find, read and manipulate files.</para>
@ -1609,13 +1569,6 @@ drwxrws--- 4 root users 4096 Jul 25 2001 docs/
</table>
<para>We also stressed the fact that you should READ THE MAN PAGES. This documentation is your first-aid kit and contains the answers to many questions. The above list contains the basic commands that you will use on a daily basis, but they can do much more than the tasks we've discussed here. Reading the documentation will give you the control you need.</para>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_03_06"><title>Exercises</title>
@ -1647,6 +1600,7 @@ drwxrws--- 4 root users 4096 Jul 25 2001 docs/
<listitem><para>How much swap space do you have?</para></listitem>
<listitem><para>What drivers are loaded?</para></listitem>
<listitem><para>How many hours has the system been running?</para></listitem>
<listitem><para>Which filesystems are known by your system?</para></listitem>
<listitem><para>Change to <filename>/etc/rc.d</filename> and choose the directory appropriate for your run level.</para></listitem>
<listitem><para>What services should be running in this level?</para></listitem>
<listitem><para>Which services run in graphical mode that don't run in text mode?</para></listitem>
@ -1691,13 +1645,6 @@ drwxrws--- 4 root users 4096 Jul 25 2001 docs/
</itemizedlist>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
</chapter>

42
LDP/guide/docbook/Intro-Linux/chap4.xml
View File

@ -342,13 +342,6 @@ EOF
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_04_02"><title>Boot process, Init and shutdown</title>
<sect2 id="sect_04_02_01"><title>Introduction</title>
@ -454,13 +447,6 @@ All of these utilities must be run as root. The system administrator may also m
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_04_03"><title>Managing processes</title>
<sect2 id="sect_04_03_01"><title>Work for the system admin</title>
@ -642,13 +628,6 @@ joe 2634 32273 0 18:09 pts/4 00:00:00 grep 25915
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_04_04"><title>Scheduling processes</title>
<sect2 id="sect_04_04_01"><title>Use that idle time!</title>
@ -760,13 +739,6 @@ crontab: installing new crontab
</note>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_04_05"><title>Summary</title>
<para>Linux is a multi-user, multi-tasking operating system that has a UNIX-like way of handling processes. Execution speed of commands can depend on a thousand tiny things. Among others, we learned a lot of new commands to visualize and handle processes. Here's a list:</para>
@ -861,13 +833,6 @@ crontab: installing new crontab
</table>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_04_06"><title>Exercises</title>
<para>These are some exercises that will help you get the feel for processes running on your system.</para>
@ -909,12 +874,5 @@ crontab: installing new crontab
</itemizedlist>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
</chapter>

21
LDP/guide/docbook/Intro-Linux/chap5.xml
View File

@ -223,25 +223,11 @@ My boss
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_05_02"><title>Summary</title>
<para>In this chapter we learned how commands can be linked to each other, and how input from one command can be used as output for another command.</para>
<para>Input/output redirection is a common task on UNIX and Linux machines. This powerful mechanism allows flexible use of the building blocks UNIX is made of.</para>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_05_03"><title>Exercises</title>
<para>These exercises give more examples on how to combine commands. The main goal is to try and use the <keycap>Enter</keycap> key as little as possible.</para>
@ -267,13 +253,6 @@ system: root
</listitem>
</itemizedlist>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>

35
LDP/guide/docbook/Intro-Linux/chap6.xml
View File

@ -44,13 +44,6 @@
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_06_02"><title>Using the Vim editor</title>
@ -108,13 +101,6 @@ Commands that switch the editor to insert mode</title>
<para>In UNIX and MS Windows, if Vim has been properly installed, you can start this program from the shell or command line, entering the <command>vimtutor</command> command. This will make a copy of the tutor file, so that you can edit it without the risk of damaging the original. There are a few translated versions of the tutor. To find out if yours is available, use the two-letter language code. For French this would be <command>vimtutor <parameter>fr</parameter></command> (if installed on the system).</para>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_06_03"><title>Linux in the office</title>
<sect2 id="sect_06_03_01"><title>History</title>
@ -149,38 +135,17 @@ Commands that switch the editor to insert mode</title>
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_06_04"><title>Summary</title>
<para>In this chapter we learned to use an editor. While it depends on your own individual preference which one you use, it is necessary to at least know how to use one editor.</para>
<para>The <command>vi</command> editor is available on every UNIX system.</para>
<para>Most Linux distributions include an office suite and a graphical text editor.</para>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_06_05"><title>Exercises</title>
<para>This chapter has only one exercise: start the Vim tutor by entering <command>vimtutor</command> in a terminal session, and get started.</para>
<para>You may alternatively start <command>emacs</command> and type <keycap>Ctrl</keycap>+<keycap>H</keycap> and then <keycap>T</keycap> to invoke the self-paced Emacs tutorial.</para>
<para>Practice is the only way!</para>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
</chapter>

56
LDP/guide/docbook/Intro-Linux/chap7.xml
View File

@ -108,13 +108,6 @@ virtual memory (kbytes) unlimited
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_07_02"><title>Your text environment</title>
<sect2 id="sect_07_02_1"><title>Environment variables</title>
@ -480,13 +473,6 @@ This script is a fine example of using functions, which make the script easier t
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_7_03"><title>The graphical environment</title>
<sect2 id="sect_7_03_01"><title>Introduction</title>
@ -557,13 +543,6 @@ This script is a fine example of using functions, which make the script easier t
<para>Should you need to change graphical server settings, however, you can run the configuration tools or edit the configuration files that set up the infrastructure to use the XFree86 server. See the man pages for more information; your distribution might have its own tools. Since misconfiguration may result in unreadable garbage in graphical mode, you may want to make a backup copy of the <filename>XF86Config</filename> file before attempting to change it, just to be on the safe side.</para>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_07_04"><title>Sound and video</title>
<sect2 id="sect_07_04_01"><title>Sound card configuration</title>
@ -669,13 +648,6 @@ If your soundcard is not supported by default, you will need to apply other tech
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_07_05"><title>Region specific settings</title>
<sect2 id="sect_07_05_01"><title>Keyboard setup</title>
@ -736,13 +708,6 @@ LANG=en_US.UTF-8
<para>The <ulink url="http://www.tldp.org/HOWTO/HOWTO-INDEX/howtos.html">list of HOWTOs</ulink> contains references to Bangla, Belarusian, Chinese, Esperanto, Finnish, Hebrew, Hellenic, Latvian, Polish, Portugese, Serbian, Slovak, Slovenian, Spanish, Thai and Turkish localization instructions.</para>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_07_06"><title>Installing new software</title>
<sect2 id="sect_07_06_01"><title>General</title>
@ -910,13 +875,6 @@ title old-kernel
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_07_07"><title>Summary</title>
<para>When everything has its place, that means already half the work is done.</para>
@ -924,13 +882,6 @@ title old-kernel
<para>Regional settings such as keyboard setup, installing appropriate fonts and language support are best done at installation time.</para>
<para>Software is managed either automatically or manually using a package system.</para>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_07_08"><title>Exercises</title>
<sect2 id="sect_07_08_01"><title>Shell environment</title>
@ -964,12 +915,5 @@ title old-kernel
</itemizedlist>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
</chapter>

35
LDP/guide/docbook/Intro-Linux/chap8.xml
View File

@ -78,13 +78,6 @@ Printer: lp@blob
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_08_02"><title>The server side</title>
<sect2 id="sect_08_02_01"><title>General</title>
@ -108,13 +101,6 @@ More information can be found at <ulink url="http://www.cups.org">the CUPS homep
<para>Your best choice would be a printer with native PostScript support in the firmware, since nearly all UNIX or Linux software producing printable output, produces it in PostScript, the publishing industry's printer control language of choice. PostScript printers are usually a bit more expensive, but it is a device-independent, open programming language.</para>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_08_03"><title>Print problems</title>
<para>In this section, we will discuss what you can do as a user when something goes wrong. We won't discuss any problems that have to do with the daemon-part of the printing service, as that is a task for system administrators.</para>
@ -158,13 +144,6 @@ Printer: lp@blob
<para>The <ulink url="http://www.linuxprinting.org">GNU/Linux Printing site</ulink> contains more tips and tricks.</para>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_08_05"><title>Summary</title>
<para>The Linux print service comes with a set of printing tools based on the standard UNIX LPD tools. Below is a list of print-related commands.</para>
@ -210,13 +189,6 @@ Printer: lp@blob
</tgroup>
</table>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_08_06"><title>Exercises</title>
<para>Configuring and testing printers involves being in the possession of one, and having access to the <emphasis>root</emphasis> account. If so, you may try:</para>
@ -238,12 +210,5 @@ Printer: lp@blob
<listitem><para>Use <command>a2ps</command> to print the <filename>/etc/profile</filename> file to an output file. Test again with <command>gv</command>. What happens if you don't specify an output file?</para></listitem>
</itemizedlist>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
</chapter>

28
LDP/guide/docbook/Intro-Linux/chap9.xml
View File

@ -173,13 +173,6 @@ Data, including tarballs, can be compressed using zip tools. The <command>gzip<
</sect3>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_09_02">
<title>Moving your data to a backup device</title>
@ -313,13 +306,6 @@ Track 01: Total bytes read/written: 341540864/341540864
</itemizedlist>
</sect2>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_09_03"><title>Summary</title>
<para>Here's a list of the commands involving file backup:</para>
@ -345,13 +331,6 @@ Track 01: Total bytes read/written: 341540864/341540864
</tgroup>
</table>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
<sect1 id="sect_09_04"><title>Exercises</title>
<itemizedlist>
@ -361,12 +340,5 @@ Track 01: Total bytes read/written: 341540864/341540864
<listitem><para>What happens to an unformatted floppy when you want to mount it into the file system?</para></listitem>
</itemizedlist>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="http://tille.xalasys.com/images/blank.png" format="PNG" />
</imageobject>
</mediaobject>
</informalfigure>
</sect1>
</chapter>