mirror of https://github.com/tLDP/LDP
minor corrections from reader contributions.
This commit is contained in:
tille
parent
c67e719e31
commit
72c010ac8e
|
|
@ -16,7 +16,6 @@
|
|||
<!ENTITY app1 SYSTEM "app1.xml">
|
||||
<!ENTITY app2 SYSTEM "app2.xml">
|
||||
<!ENTITY app3 SYSTEM "app3.xml">
|
||||
<!ENTITY app4 SYSTEM "app4.xml">
|
||||
<!ENTITY gloss SYSTEM "gloss.xml">
|
||||
]>
|
||||
<book>
|
||||
|
|
@ -36,7 +35,7 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
<edition>1.25</edition>
|
||||
<pubdate>20070511</pubdate>
|
||||
<pubdate>20070919</pubdate>
|
||||
<copyright>
|
||||
<year>2002</year>
|
||||
<year>2003</year>
|
||||
|
|
@ -123,6 +122,12 @@
|
|||
<para>
|
||||
<revhistory>
|
||||
<revision>
|
||||
<revnumber>1.26</revnumber>
|
||||
<date>20070919</date>
|
||||
<authorinitials>MG</authorinitials>
|
||||
<revremark>Comments from readers, license.</revremark>
|
||||
</revision>
|
||||
<revision>
|
||||
<revnumber>1.25</revnumber>
|
||||
<date>20070511</date>
|
||||
<authorinitials>MG</authorinitials>
|
||||
|
|
@ -349,16 +354,32 @@
|
|||
</section>
|
||||
<section id="intro_07">
|
||||
<title>Copyright information</title>
|
||||
<para>© 2002-2007 Machtelt Garrels.</para>
|
||||
<para> Permission is granted to copy, distribute and/or modify this document under the
|
||||
terms of the GNU Free Documentation License, Version 1.2 or any later version
|
||||
published by the Free Software Foundation, with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in
|
||||
<xref linkend="app4"/> entitled <quote>GNU Free Documentation License</quote>.</para>
|
||||
<para>The author and publisher have made every effort in the preparation of this book to
|
||||
ensure the accuracy of the information. However, the information contained in this
|
||||
book is offered without warranty, either express or implied. Neither the author nor
|
||||
the publisher nor any dealer or distributor will be held liable for any damages
|
||||
caused or alleged to be caused either directly or indirectly by this book.</para>
|
||||
<screen>
|
||||
* Copyright (c) 2002-2007, Machtelt Garrels
|
||||
* All rights reserved.
|
||||
* Redistribution and use in source and binary forms, with or without
|
||||
* modification, are permitted provided that the following conditions are met:
|
||||
*
|
||||
* * Redistributions of source code must retain the above copyright
|
||||
* notice, this list of conditions and the following disclaimer.
|
||||
* * Redistributions in binary form must reproduce the above copyright
|
||||
* notice, this list of conditions and the following disclaimer in the
|
||||
* documentation and/or other materials provided with the distribution.
|
||||
* * Neither the name of the author, Machtelt Garrels, nor the
|
||||
* names of its contributors may be used to endorse or promote products
|
||||
* derived from this software without specific prior written permission.
|
||||
*
|
||||
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY
|
||||
* EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
|
||||
* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
|
||||
* DISCLAIMED. IN NO EVENT SHALL THE AUTHOR AND CONTRIBUTORS BE LIABLE FOR ANY
|
||||
* DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
|
||||
* (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
|
||||
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
|
||||
* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
||||
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
|
||||
* SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
</screen>
|
||||
<para>The logos, trademarks and symbols used in this book are the properties of their
|
||||
respective owners.</para>
|
||||
|
||||
|
|
@ -620,15 +641,11 @@
|
|||
outcome. Also a good argument when your boss insists that YOU should use HIS
|
||||
favorite shell.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<xref linkend="app4"/>: What you can do with this guide, from the legal perspective.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</section>
|
||||
</preface>
|
||||
<toc/> &chap1; &chap2; &chap3; &chap4; &chap5; &chap6; &chap7;
|
||||
&chap8; &chap9; &chap10; &chap11; &app1; &app2; &app3; &app4; &gloss;
|
||||
&chap8; &chap9; &chap10; &chap11; &app1; &app2; &app3; &gloss;
|
||||
<index/>
|
||||
</book>
|
||||
|
|
|
|||
|
|
@ -165,7 +165,7 @@ processors, spreadsheets, presentations and the like.
|
|||
</para>
|
||||
<para>On the server side, Linux is well-known as a stable and reliable platform,
|
||||
providing database and trading services for companies like Amazon, the
|
||||
well-known online bookshop, US Post Office, the German army and such.
|
||||
well-known online bookshop, US Post Office, the German army and many others.
|
||||
Especially Internet providers and Internet service providers have grown fond of
|
||||
Linux as firewall, proxy- and web server, and you will find a Linux box within
|
||||
reach of every UNIX system administrator who appreciates a comfortable
|
||||
|
|
@ -413,7 +413,7 @@ just recycling your old 486, Linux will do that as well.
|
|||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>The Linux OS and quite some Linux applications have very short debug-times:
|
||||
<para>The Linux OS and most Linux applications have very short debug-times:
|
||||
</para>
|
||||
<para>Because Linux<indexterm><primary>Linux</primary><secondary>bugs</secondary></indexterm> has been developed and tested by thousands of people, both
|
||||
errors and people to fix them are usually found rather quickly. It sometimes happens that
|
||||
|
|
|
|||
|
|
@ -426,7 +426,7 @@ localhost.localdomain: anonymous/bob@his.server.com: IDLE
|
|||
</sect3>
|
||||
<sect3 id="sect_10_04_02_03"><title>Mail user-agents</title>
|
||||
<para>There are plenty of both text and graphical E-mail<indexterm><primary>mail</primary><secondary>client applications</secondary></indexterm> clients, we'll just name a few of the common ones. Pick your favorite.</para>
|
||||
<para>The UNIX <command>mail</command> command has been around for years, even before networking existed. It is a simple interface to send messages and small files to other users, who can then save the message, redirect it, reply to it and such.</para>
|
||||
<para>The UNIX <command>mail</command> command has been around for years, even before networking existed. It is a simple interface to send messages and small files to other users, who can then save the message, redirect it, reply to it etcetera.</para>
|
||||
<para>While it is not commonly used as a client anymore, the <command>mail</command> program is still useful, for example to mail the output of a command to somebody:</para>
|
||||
<cmdsynopsis><command>mail <email>future.employer@whereIwant2work.com</email> < <filename>cv.txt</filename></command></cmdsynopsis>
|
||||
<para>The <command>elm</command> mail reader is a much needed improvement to <command>mail</command>, and so is <command>pine</command> (Pine Is Not ELM). The <command>mutt</command> mail reader is even more recent and offers features like threading.</para>
|
||||
|
|
|
|||
|
|
@ -924,7 +924,7 @@ Restaurants-Michelin/
|
|||
-rw-rw-r-- 1 richard richard 2534 Jan 15 12:39 done
|
||||
</screen>
|
||||
<para>It is clear that only the name of the file changes. All other properties remain the same.</para>
|
||||
<para>Detailed information about the syntax and features of the <command>mv</command> command can be found in the man or Info pages. The use of this documentation should always be your first reflex when confronted with a problem. The answer to your problem is likely to be in the system documentation. Even experienced users read man pages every day, so beginning users should read them all the time. After a while, you will get to know the most common options to the common commands, but you will still need the documentation as a primary source of information. Note that the information contained in the HOWTOs, FAQs, man pages and such is slowly being merged into the Info pages, which are today the most up-to-date source of online (as in readily available on the system) documentation.</para>
|
||||
<para>Detailed information about the syntax and features of the <command>mv</command> command can be found in the man or Info pages. The use of this documentation should always be your first reflex when confronted with a problem. The answer to your problem is likely to be in the system documentation. Even experienced users read man pages every day, so beginning users should read them all the time. After a while, you will get to know the most common options to the common commands, but you will still need the documentation as a primary source of information. Note that the information contained in the HOWTOs, FAQs, man pages and other sources is slowly being merged into the Info pages, which are today the most up-to-date source of online (as in readily available on the system) documentation.</para>
|
||||
</sect4>
|
||||
<sect4><title>Copying files</title>
|
||||
<para>Copying<indexterm><primary>files</primary><secondary>copying</secondary></indexterm> files and directories is done with the <command>cp<indexterm><primary>cp</primary></indexterm></command> command. A useful option is recursive copy (copy all underlying files and subdirectories), using the <option>-R</option> option to <command>cp</command>. The general syntax is</para>
|
||||
|
|
|
|||
|
|
@ -464,7 +464,7 @@ All of these utilities must be run as root. The system administrator may also m
|
|||
<sect1 id="sect_04_03"><title>Managing processes</title>
|
||||
<sect2 id="sect_04_03_01"><title>Work for the system admin</title>
|
||||
<para>While managing system resources<indexterm><primary>processes</primary><secondary>managing</secondary></indexterm>, including processes, is a task for the local system administrator, it doesn't hurt a common user to know something about it, especially where his or her own processes and their optimal execution are concerned.</para>
|
||||
<para>We will explain a little bit on a theoretical level about system performance, though not as far as hardware optimization and such. Instead, we will study the daily problems a common user is confronted with, and actions such a user can take to optimally use the resources available. As we learn in the next section, this is mainly a matter of thinking before acting.</para>
|
||||
<para>We will explain a little bit on a theoretical level about system performance, though not as far as hardware optimization and other advanced procedures. Instead, we will study the daily problems a common user is confronted with, and actions such a user can take to optimally use the resources available. As we learn in the next section, this is mainly a matter of thinking before acting.</para>
|
||||
<figure><title>Can't you go faster?</title>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
|
|
@ -526,11 +526,11 @@ Command exited with non-zero status 2
|
|||
<para>Keep in mind that different systems will behave different with the same load average. For example, a system with a graphics card supporting hardware acceleration will have no problem rendering 3D images, while the same system with a cheap VGA card will slow down tremendously while rendering. My old P133 will become quite uncomfortable when I start the X server, but on a modern system you hardly notice the difference in the system load.</para>
|
||||
</sect2>
|
||||
<sect2 id="sect_04_03_05"><title>Can I do anything as a user?</title>
|
||||
<para>A big environment can slow you down. If you have lots of environment variables set (instead of shell variables), long search paths that are not optimized (errors in setting the path environment variable) and such, the system will need more time to search and read data.</para>
|
||||
<para>A big environment can slow you down. If you have lots of environment variables set (instead of shell variables), long search paths that are not optimized (errors in setting the path environment variable) and more of those settings that are usually made <quote>on the fly</quote>, the system will need more time to search and read data.</para>
|
||||
<para>In X, window managers and desktop environments can be real CPU-eaters. A really fancy desktop comes with a price, even when you can download it for free, since most desktops provide add-ons ad infinitum. Modesty is a virtue if you don't buy a new computer every year.</para>
|
||||
<sect3 id="sect_04_03_05_01"><title>Priority</title>
|
||||
<para>The priority<indexterm><primary>processes</primary><secondary>priority</secondary></indexterm> or importance of a job is defined by it's <emphasis>nice</emphasis> number<indexterm><primary>nice number</primary></indexterm>. A program with a high nice number is friendly to other programs, other users and the system; it is not an important job. The lower the nice number, the more important a job is and the more resources it will take without sharing them.</para>
|
||||
<para>Making a job nicer by increasing its nice number is only useful for processes that use a lot of CPU time (compilers, math applications and such). Processes that always use a lot of I/O time are automatically rewarded by the system and given a higher priority (a lower nice number), for example keyboard input always gets highest priority on a system.</para>
|
||||
<para>Making a job nicer by increasing its nice number is only useful for processes that use a lot of CPU time (compilers, math applications and the like). Processes that always use a lot of I/O time are automatically rewarded by the system and given a higher priority (a lower nice number), for example keyboard input always gets highest priority on a system.</para>
|
||||
<para>Defining the priority of a program is done with the <command>nice<indexterm><primary>nice</primary></indexterm></command> command.</para>
|
||||
<para>Most systems also provide the BSD <command>renice<indexterm><primary>renice</primary></indexterm></command> command, which allows you to change the <emphasis>niceness</emphasis> of a running command. Again, read the man page for your system-specific information.</para>
|
||||
<caution><title>Interactive programs</title>
|
||||
|
|
|
|||
|
|
@ -24,10 +24,12 @@
|
|||
<sect2 id="sect_06_01_02"><title>Which editor should I use?</title>
|
||||
<para>Our focus is on text editors<indexterm><primary>editors</primary><secondary>text editor overview</secondary></indexterm>, which can also be used on systems without a graphical environment and in terminal windows. The additional advantage of mastering a text editor is in using it on remote machines. Since you don't need to transfer the entire graphical environment over the network, working with text editors tremendously improves network speed.</para>
|
||||
<para>There are, as usual, multiple ways to handle the problem. Let's see what editors are commonly available:</para>
|
||||
<!--
|
||||
<sect3 id="sect_06_01_02_01"><title>Ed</title>
|
||||
<para>The <command>ed<indexterm><primary>ed</primary></indexterm></command> editor is line-oriented and used to create, display, modify and otherwise manipulate text files, both interactively and by use in shell scripts.</para>
|
||||
<para><command>ed</command> is the original text editor on UNIX machines, and thus widely available. For most purposes, however, it is superceded by full-screen editors such as <command>emacs</command> and <command>vi</command>, see below.</para>
|
||||
</sect3>
|
||||
-->
|
||||
<sect3 id="sect_06_01_02_02"><title>GNU Emacs</title>
|
||||
<para><application>Emacs<indexterm><primary>editors</primary><secondary>emacs</secondary></indexterm></application> is the extensible, customizable, self-documenting, real-time display editor, known on many UNIX and other systems. The text being<indexterm><primary>emacs</primary></indexterm> edited is visible on the screen and is updated automatically as you type your commands. It is a real-time editor because the display is updated very frequently, usually after each character or pair of characters you type. This minimizes the amount of information you must keep in your head as you edit. <application>Emacs</application> is called advanced because it provides facilities that go beyond simple insertion and deletion: controlling subprocesses; automatic indentation of programs; viewing two or more files at once; editing formatted text; and dealing in terms of characters, words, lines, sentences, paragraphs, and pages, as well as expressions and comments in several different programming languages.</para>
|
||||
<para><emphasis>Self-documenting</emphasis> means that at any time you can type a special character, <keycap>Ctrl</keycap>+<keycap>H</keycap>, to find out what your options are. You can also use it to find out what any command does, or to find all the commands that pertain to a topic. <emphasis>Customizable</emphasis> means that you can change the definitions of <application>Emacs</application> commands in little ways. For example, if you use a programming language in which comments start with <quote><**</quote> and end with <quote>**></quote>, you can tell the <application>Emacs</application> comment manipulation commands to use those strings. Another sort of customization is rearrangement of the command set. For example, if you prefer the four basic cursor motion commands (up, down, left and right) on keys in a diamond pattern on the keyboard, you can rebind the keys that way.</para>
|
||||
|
|
|
|||
|
|
@ -105,7 +105,7 @@ virtual memory (kbytes) unlimited
|
|||
</sect3>
|
||||
<sect3 id="sect_07_01_02_06"><title>Compressed files</title>
|
||||
<para>Compressed files are useful because they take less space on your hard disk. Another advantage is that it takes less bandwidth to send a compressed file over your network. A lot of files, such as the man pages, are stored in a compressed format on your system. Yet unpacking these to get a little bit of information and then having to compress them again is rather time-consuming. You don't want to unpack a man page, for instance, read about an option to a command and then compress the man page again. Most people will probably forget to clean up after they found the information they needed.</para>
|
||||
<para>So we have tools that work on compressed files, by uncompressing them only in memory. The actual compressed file stays on your disk as it is. Most systems support <command>zgrep</command>, <command>zcat</command>, <command>bzless</command> and such to prevent unnecessary decompressing/compressing actions. See your system's binary directory and the Info pages.</para>
|
||||
<para>So we have tools that work on compressed files, by uncompressing them only in memory. The actual compressed file stays on your disk as it is. Most systems support <command>zgrep</command>, <command>zcat</command>, <command>bzless</command> and other members of the z-family to prevent unnecessary decompressing/compressing actions. See your system's binary directory and the Info pages.</para>
|
||||
<para>See <xref linkend="chap_09" /> for more on the actual compressing of files and examples on making archives.</para>
|
||||
|
||||
</sect3>
|
||||
|
|
@ -619,7 +619,7 @@ LANG=en_US.UTF-8
|
|||
</sect1>
|
||||
<sect1 id="sect_07_06"><title>Installing new software</title>
|
||||
<sect2 id="sect_07_06_01"><title>General</title>
|
||||
<para>Most people are surprised to see that they have a running, usable computer after installing Linux; most distributions contain ample support for video and network cards, monitors and other external devices, so there is usually no need to install extra drivers. Also common tools such as office suites, web browsers, E-mail clients and such are included in the main distributions. Even so, an initial installation might not meet your requirements.</para>
|
||||
<para>Most people are surprised to see that they have a running, usable computer after installing Linux; most distributions contain ample support for video and network cards, monitors and other external devices, so there is usually no need to install extra drivers. Also common tools such as office suites, web browsers, E-mail and other network client programs are included in the main distributions. Even so, an initial installation might not meet your requirements.</para>
|
||||
<para>If you just can't find<indexterm><primary>software</primary><secondary>installing</secondary></indexterm> what you need, maybe it is not installed on your system. It may also be that you have the required software, but it does not do what it is supposed to do. Remember that Linux moves fast, and software improves on a daily basis. Don't waste your time troubleshooting problems that might already be resolved.</para>
|
||||
<para>You can update your system or add packages to it at any time you want. Most software comes in packages. Extra software may be found on your installation CDs or on the Internet. The website of your Linux distribution is a good place to start looking for additional software and contains instructions about how to install it on your type of Linux, see <xref linkend="app1" />. Always read the documentation that comes with new software, and any installation guidelines the package might contain. All software comes with a <filename>README<indexterm><primary>README</primary></indexterm></filename> file, which you are very strongly advised to read.</para>
|
||||
</sect2>
|
||||
|
|
|
|||
|
|
@ -280,7 +280,7 @@ Track 01: Total bytes read/written: 341540864/341540864
|
|||
</screen>
|
||||
<para>There are some graphical tools available to make it easier on you. One of the popular ones is <command>xcdroast<indexterm><primary>CD burning</primary><secondary>graphical tools</secondary></indexterm></command>, which is freely available from <ulink url="http://www.xcdroast.org/">the X-CD-Roast web site<indexterm><primary>xcdroast</primary></indexterm></ulink> and is included on most systems and in the GNU directory. Both the KDE and Gnome desktop managers have facilities to make your own CDs.</para>
|
||||
</sect2>
|
||||
<sect2 id="sect_09_02_03"><title>Backups on/from jazz drives, USB devices and such</title>
|
||||
<sect2 id="sect_09_02_03"><title>Backups on/from jazz drives, USB devices and other removables</title>
|
||||
<para>These devices are usually mounted into the file system. After the mount procedure, they are accessed as normal directories, so you can use the standard commands for manipulating files.</para>
|
||||
<para>In the example below, images are copied from a USB<indexterm><primary>archiving</primary><secondary>USB devices</secondary></indexterm> camera to the hard disk:</para>
|
||||
<screen>
|
||||
|
|
@ -327,7 +327,7 @@ Track 01: Total bytes read/written: 341540864/341540864
|
|||
<prompt>root@theserver# </prompt><command>mount <option>-t vfat</option> <filename>/dev/sda1 /mnt/usbstore</filename></command>
|
||||
</screen>
|
||||
<note><title>Userfriendly</title>
|
||||
<para>More and more distributions give access to removable devices for non-prilileged users and mount USB devices, CD-ROMs and such automatically.</para>
|
||||
<para>More and more distributions give access to removable devices for non-prilileged users and mount USB devices, CD-ROMs and other removable devices automatically.</para>
|
||||
</note>
|
||||
<para>Note that this guideline requires USB support to be installed on your system. See <ulink url="http://www.linux-usb.org/USB-guide/">the USB Guide</ulink> for help if this does not work. Check with <command>dmesg</command> that <filename>/dev/sda1</filename> is indeed the device to mount.</para>
|
||||
<para>Then you can start the actual backup, for instance of the <filename>/home/karl</filename> directory:</para>
|
||||
|
|
|
|||
Loading…
Reference in New Issue