mirror of https://github.com/tLDP/LDP
Merge pull request #64 from jasonleschnik/master
Fixed up repeated words and Typos
This commit is contained in:
commit
d8e3f44db9
|
@ -9,7 +9,7 @@
|
||||||
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
||||||
and therefore generates MULTIPLE HTML FILES as output. -->
|
and therefore generates MULTIPLE HTML FILES as output. -->
|
||||||
|
|
||||||
<!-- Note the the *order* of the import statements below is important and
|
<!-- Note the *order* of the import statements below is important and
|
||||||
should not be changed. -->
|
should not be changed. -->
|
||||||
|
|
||||||
<!-- Change this to the path to where you have installed Norman
|
<!-- Change this to the path to where you have installed Norman
|
||||||
|
|
|
@ -9,7 +9,7 @@
|
||||||
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
||||||
and therefore generates a SINGLE HTML FILE as output. -->
|
and therefore generates a SINGLE HTML FILE as output. -->
|
||||||
|
|
||||||
<!-- Note the the *order* of the import statements below is important and
|
<!-- Note the *order* of the import statements below is important and
|
||||||
should not be changed. -->
|
should not be changed. -->
|
||||||
|
|
||||||
<!-- Change this to the path to where you have installed Norman
|
<!-- Change this to the path to where you have installed Norman
|
||||||
|
|
|
@ -854,7 +854,7 @@ mt -f /dev/nqft0 rewind
|
||||||
</verb></tscreen>
|
</verb></tscreen>
|
||||||
would result in a backup of all files under <it>/bin</it> and <it>/etc</it>. When
|
would result in a backup of all files under <it>/bin</it> and <it>/etc</it>. When
|
||||||
the first <it/tar/ finishes, the kernel driver will take care of writing
|
the first <it/tar/ finishes, the kernel driver will take care of writing
|
||||||
a file mark to the tape at the the current tape position, and when the
|
a file mark to the tape at the current tape position, and when the
|
||||||
second <it/tar/ process has finished, another file mark is written to the
|
second <it/tar/ process has finished, another file mark is written to the
|
||||||
tape cartridge at that position.
|
tape cartridge at that position.
|
||||||
|
|
||||||
|
@ -1416,7 +1416,7 @@ with the single line
|
||||||
<tscreen><verb>
|
<tscreen><verb>
|
||||||
unsubscribe linux-tape MY@EMAIL.ADDRESS
|
unsubscribe linux-tape MY@EMAIL.ADDRESS
|
||||||
</verb></tscreen>
|
</verb></tscreen>
|
||||||
where <tt/MY@EMAIL.ADDRESS/ has to be replaced by the the email
|
where <tt/MY@EMAIL.ADDRESS/ has to be replaced by the email
|
||||||
address that you used when subscribing to the list. Note that you must
|
address that you used when subscribing to the list. Note that you must
|
||||||
have received an email with instructions how to unsubscribe from the
|
have received an email with instructions how to unsubscribe from the
|
||||||
mailing list at the time you subscribed to it.
|
mailing list at the time you subscribed to it.
|
||||||
|
|
|
@ -57,7 +57,7 @@ satisfy this requirement, the LVM plug-in will not allow the object to be added
|
||||||
<sect2><title>Removing objects from LVM containers</title>
|
<sect2><title>Removing objects from LVM containers</title>
|
||||||
<para>You can remove a consumed object from its container as long as no regions
|
<para>You can remove a consumed object from its container as long as no regions
|
||||||
are mapped to that object. The LVM plug-in does not allow objects that are in use to
|
are mapped to that object. The LVM plug-in does not allow objects that are in use to
|
||||||
be removed their their container. If an object must be removed, you can delete or
|
be removed from their container. If an object must be removed, you can delete or
|
||||||
shrink regions, or move extents, in order to free the object from use.</para>
|
shrink regions, or move extents, in order to free the object from use.</para>
|
||||||
<para>No options are available for removing objects from LVM containers.</para>
|
<para>No options are available for removing objects from LVM containers.</para>
|
||||||
|
|
||||||
|
|
|
@ -1710,7 +1710,7 @@ sectors to the end of the segment, moving the end of the data segment
|
||||||
up into the freespace that immediately follows the data segment. However,
|
up into the freespace that immediately follows the data segment. However,
|
||||||
what if there is no freespace following the data segment? A segment or
|
what if there is no freespace following the data segment? A segment or
|
||||||
segments could
|
segments could
|
||||||
be be moved around to put freespace after the segment that is to be
|
be moved around to put freespace after the segment that is to be
|
||||||
expanded. For example:
|
expanded. For example:
|
||||||
</p><div class="itemizedlist"><ul type="disc"><li><p>The segment following the segment to be expanded can be moved
|
</p><div class="itemizedlist"><ul type="disc"><li><p>The segment following the segment to be expanded can be moved
|
||||||
elsewhere on the disk, thus freeing up space after the segment that
|
elsewhere on the disk, thus freeing up space after the segment that
|
||||||
|
@ -2082,7 +2082,7 @@ must be large enough to hold five physical extents. If an object is not large e
|
||||||
satisfy this requirement, the LVM plug-in will not allow the object to be added to the container.
|
satisfy this requirement, the LVM plug-in will not allow the object to be added to the container.
|
||||||
</p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="id2887424"></a>C.2.3. Removing objects from LVM containers</h3></div></div><p>You can remove a consumed object from its container as long as no regions
|
</p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="id2887424"></a>C.2.3. Removing objects from LVM containers</h3></div></div><p>You can remove a consumed object from its container as long as no regions
|
||||||
are mapped to that object. The LVM plug-in does not allow objects that are in use to
|
are mapped to that object. The LVM plug-in does not allow objects that are in use to
|
||||||
be removed their their container. If an object must be removed, you can delete or
|
be removed from their container. If an object must be removed, you can delete or
|
||||||
shrink regions, or move extents, in order to free the object from use.</p><p>No options are available for removing objects from LVM containers.</p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="id2888540"></a>C.2.4. Deleting LVM containers</h3></div></div><p>You can delete a container as long as the container does not have any produced
|
shrink regions, or move extents, in order to free the object from use.</p><p>No options are available for removing objects from LVM containers.</p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="id2888540"></a>C.2.4. Deleting LVM containers</h3></div></div><p>You can delete a container as long as the container does not have any produced
|
||||||
regions. The LVM plug-in does not allow containers to be deleted if they have any
|
regions. The LVM plug-in does not allow containers to be deleted if they have any
|
||||||
regions. No options are available for deleting LVM containers.</p></div></div><div class="sect1"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888557"></a>C.3. Region operations</h2></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="id2888563"></a>C.3.1. Creating LVM regions</h3></div></div><p>You create LVM regions from the freespace in LVM containers. If there is at least
|
regions. No options are available for deleting LVM containers.</p></div></div><div class="sect1"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888557"></a>C.3. Region operations</h2></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="id2888563"></a>C.3.1. Creating LVM regions</h3></div></div><p>You create LVM regions from the freespace in LVM containers. If there is at least
|
||||||
|
|
|
@ -3,7 +3,7 @@
|
||||||
<para>In order for user-space programs to access EVMS
|
<para>In order for user-space programs to access EVMS
|
||||||
volumes, device files are created in the <filename>/dev/evms
|
volumes, device files are created in the <filename>/dev/evms
|
||||||
</filename> directory for each volume that is exported by EVMS. Device files are created every time
|
</filename> directory for each volume that is exported by EVMS. Device files are created every time
|
||||||
the Engine is opened and saves changes, so you can always see the the current state of the volume configuration
|
the Engine is opened and saves changes, so you can always see the current state of the volume configuration
|
||||||
in the <filename>/dev/evms</filename> directory.</para>
|
in the <filename>/dev/evms</filename> directory.</para>
|
||||||
|
|
||||||
<para>A variety of namespaces exist within the <filename>/dev/evms</filename> directory. Each plug-in defines
|
<para>A variety of namespaces exist within the <filename>/dev/evms</filename> directory. Each plug-in defines
|
||||||
|
|
|
@ -21,7 +21,7 @@ sectors to the end of the segment, moving the end of the data segment
|
||||||
up into the freespace that immediately follows the data segment. However,
|
up into the freespace that immediately follows the data segment. However,
|
||||||
what if there is no freespace following the data segment? A segment or
|
what if there is no freespace following the data segment? A segment or
|
||||||
segments could
|
segments could
|
||||||
be be moved around to put freespace after the segment that is to be
|
be moved around to put freespace after the segment that is to be
|
||||||
expanded. For example:
|
expanded. For example:
|
||||||
</para>
|
</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
|
|
@ -21,7 +21,7 @@ sectors to the end of the segment, moving the end of the data segment
|
||||||
up into the freespace that immediately follows the data segment. However,
|
up into the freespace that immediately follows the data segment. However,
|
||||||
what if there is no freespace following the data segment? A segment or
|
what if there is no freespace following the data segment? A segment or
|
||||||
segments could
|
segments could
|
||||||
be be moved around to put freespace after the segment that is to be
|
be moved around to put freespace after the segment that is to be
|
||||||
expanded. For example:
|
expanded. For example:
|
||||||
</para>
|
</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
|
|
@ -258,7 +258,7 @@ If you wish to make contributions it is recommended (if possible) to read the Ly
|
||||||
<chapter id="Legal"><title>Legal</title><para>The legal <indexterm><primary>legal</primary></indexterm>chapter provides information <indexterm><primary>information</primary></indexterm>about the disclaimer <indexterm><primary>disclaimer</primary></indexterm>that applies to the entire document and the licensing <indexterm><primary>licensing</primary></indexterm>information.</para><sect1 id="disclaimer"><title>Disclaimer</title><para>No liability <indexterm><primary>liability</primary></indexterm>for the contents <indexterm><primary>contents</primary></indexterm>of this document <indexterm><primary>documents</primary></indexterm>can be accepted. Use the concepts,<indexterm><primary>concepts</primary></indexterm> examples <indexterm><primary>examples</primary></indexterm>and other content <indexterm><primary>content</primary></indexterm>at your own risk.<indexterm><primary>risk</primary></indexterm> There may be errors <indexterm><primary>errors</primary></indexterm>and inaccuracies,<indexterm><primary>inaccuracies</primary></indexterm> that may of course be damaging to your system. Although this is highly <indexterm><primary>highly</primary></indexterm>unlikely, you should proceed <indexterm><primary>proceed</primary></indexterm>with caution.<indexterm><primary>caution</primary></indexterm> The author <indexterm><primary>author</primary></indexterm>does not accept any responsibility <indexterm><primary>responsibility</primary></indexterm>for any damage <indexterm><primary>damage</primary></indexterm>incurred.</para><para>All copyrights <indexterm><primary>copyrights</primary></indexterm>are held by their respective owners<indexterm><primary>respective owners</primary></indexterm>, unless specifically<indexterm><primary>specifically</primary></indexterm> noted otherwise. Use of a term <indexterm><primary>term</primary></indexterm>in this document should not be regarded <indexterm><primary>regarded</primary></indexterm>as affecting the validity <indexterm><primary>validity</primary></indexterm>of any trademark <indexterm><primary>trademark</primary></indexterm>or service mark<indexterm><primary>service mark</primary></indexterm>.</para><para>Naming <indexterm><primary>Naming</primary></indexterm>of particular products <indexterm><primary>products</primary></indexterm>or brands <indexterm><primary>brands</primary></indexterm>should not be seen as endorsements.<indexterm><primary>endorsements</primary></indexterm></para><para>UNIX <indexterm><primary>UNIX</primary></indexterm>is a registered trademark <indexterm><primary>trademark</primary></indexterm>of The Open Group<indexterm><primary>The Open Group</primary></indexterm>.</para></sect1>
|
<chapter id="Legal"><title>Legal</title><para>The legal <indexterm><primary>legal</primary></indexterm>chapter provides information <indexterm><primary>information</primary></indexterm>about the disclaimer <indexterm><primary>disclaimer</primary></indexterm>that applies to the entire document and the licensing <indexterm><primary>licensing</primary></indexterm>information.</para><sect1 id="disclaimer"><title>Disclaimer</title><para>No liability <indexterm><primary>liability</primary></indexterm>for the contents <indexterm><primary>contents</primary></indexterm>of this document <indexterm><primary>documents</primary></indexterm>can be accepted. Use the concepts,<indexterm><primary>concepts</primary></indexterm> examples <indexterm><primary>examples</primary></indexterm>and other content <indexterm><primary>content</primary></indexterm>at your own risk.<indexterm><primary>risk</primary></indexterm> There may be errors <indexterm><primary>errors</primary></indexterm>and inaccuracies,<indexterm><primary>inaccuracies</primary></indexterm> that may of course be damaging to your system. Although this is highly <indexterm><primary>highly</primary></indexterm>unlikely, you should proceed <indexterm><primary>proceed</primary></indexterm>with caution.<indexterm><primary>caution</primary></indexterm> The author <indexterm><primary>author</primary></indexterm>does not accept any responsibility <indexterm><primary>responsibility</primary></indexterm>for any damage <indexterm><primary>damage</primary></indexterm>incurred.</para><para>All copyrights <indexterm><primary>copyrights</primary></indexterm>are held by their respective owners<indexterm><primary>respective owners</primary></indexterm>, unless specifically<indexterm><primary>specifically</primary></indexterm> noted otherwise. Use of a term <indexterm><primary>term</primary></indexterm>in this document should not be regarded <indexterm><primary>regarded</primary></indexterm>as affecting the validity <indexterm><primary>validity</primary></indexterm>of any trademark <indexterm><primary>trademark</primary></indexterm>or service mark<indexterm><primary>service mark</primary></indexterm>.</para><para>Naming <indexterm><primary>Naming</primary></indexterm>of particular products <indexterm><primary>products</primary></indexterm>or brands <indexterm><primary>brands</primary></indexterm>should not be seen as endorsements.<indexterm><primary>endorsements</primary></indexterm></para><para>UNIX <indexterm><primary>UNIX</primary></indexterm>is a registered trademark <indexterm><primary>trademark</primary></indexterm>of The Open Group<indexterm><primary>The Open Group</primary></indexterm>.</para></sect1>
|
||||||
<sect1 id="license"><title>License</title><para>Copyright <indexterm><primary>Copyright</primary></indexterm>© 2003 - 2006 Gareth Anderson.<indexterm><primary>Gareth Anderson</primary></indexterm> Permission <indexterm><primary>Permission</primary></indexterm>is granted <indexterm><primary>granted</primary></indexterm>to copy,<indexterm><primary>copy</primary></indexterm> distribute <indexterm><primary>distribute</primary></indexterm>and/or modify <indexterm><primary>modify</primary></indexterm>this document under the terms <indexterm><primary>terms</primary></indexterm>of the <acronym>GNU</acronym> <indexterm><primary>GNU</primary></indexterm>Free Documentation License,<indexterm><primary>GNU Free Documentation License</primary></indexterm><indexterm><primary>GFDL</primary></indexterm> Version <indexterm><primary>Version</primary></indexterm>1.1 or any later version <indexterm><primary>version</primary></indexterm>published by the Free Software Foundation;<indexterm><primary>FSF</primary></indexterm><indexterm><primary>Free Software Foundation</primary></indexterm> with no Invariant <indexterm><primary>Invariant</primary></indexterm>Sections,<indexterm><primary>Sections</primary></indexterm> with no Front-Cover <indexterm><primary>Front-Cover</primary></indexterm>Texts, and with no Back-Cover <indexterm><primary>Back-Cover</primary></indexterm>Texts.<indexterm><primary>Texts</primary></indexterm> A copy of the license <indexterm><primary>license</primary></indexterm>can be found in the section called the <acronym>GNU</acronym> Free Documentation License or at the <ulink url="http://www.gnu.org/licenses/licenses.html">GNU Documentation License Site</ulink>.<indexterm><primary>GNU Documentation License Site</primary></indexterm></para></sect1>
|
<sect1 id="license"><title>License</title><para>Copyright <indexterm><primary>Copyright</primary></indexterm>© 2003 - 2006 Gareth Anderson.<indexterm><primary>Gareth Anderson</primary></indexterm> Permission <indexterm><primary>Permission</primary></indexterm>is granted <indexterm><primary>granted</primary></indexterm>to copy,<indexterm><primary>copy</primary></indexterm> distribute <indexterm><primary>distribute</primary></indexterm>and/or modify <indexterm><primary>modify</primary></indexterm>this document under the terms <indexterm><primary>terms</primary></indexterm>of the <acronym>GNU</acronym> <indexterm><primary>GNU</primary></indexterm>Free Documentation License,<indexterm><primary>GNU Free Documentation License</primary></indexterm><indexterm><primary>GFDL</primary></indexterm> Version <indexterm><primary>Version</primary></indexterm>1.1 or any later version <indexterm><primary>version</primary></indexterm>published by the Free Software Foundation;<indexterm><primary>FSF</primary></indexterm><indexterm><primary>Free Software Foundation</primary></indexterm> with no Invariant <indexterm><primary>Invariant</primary></indexterm>Sections,<indexterm><primary>Sections</primary></indexterm> with no Front-Cover <indexterm><primary>Front-Cover</primary></indexterm>Texts, and with no Back-Cover <indexterm><primary>Back-Cover</primary></indexterm>Texts.<indexterm><primary>Texts</primary></indexterm> A copy of the license <indexterm><primary>license</primary></indexterm>can be found in the section called the <acronym>GNU</acronym> Free Documentation License or at the <ulink url="http://www.gnu.org/licenses/licenses.html">GNU Documentation License Site</ulink>.<indexterm><primary>GNU Documentation License Site</primary></indexterm></para></sect1>
|
||||||
</chapter>
|
</chapter>
|
||||||
<chapter id="The-UNIX-Tools-Philosophy"><title>The Unix Tools Philosophy</title><para>A tool is a simple program,<indexterm><primary>program</primary></indexterm> usually designed for a specific purpose, it is sometimes referred <indexterm><primary>referred</primary></indexterm>to (at least throughout this document) as a command.</para><para>The “ Unix tools philosophy”<indexterm><primary>Unix Tools Philosophy</primary></indexterm> emerged <indexterm><primary>emerged</primary></indexterm>during the creation of the <productname>UNIX</productname> <indexterm><primary>UNIX</primary></indexterm>operating system, after the breakthrough invention <indexterm><primary>invention</primary></indexterm>of the pipe <indexterm><primary>pipe</primary></indexterm>'|' (refer to <xref linkend="Directing-input-ouput"> for information on using the pipe).</para><para>The pipe <indexterm><primary>pipe</primary></indexterm>allowed the output <indexterm><primary>output</primary></indexterm>of one program to be sent to the input <indexterm><primary>input</primary></indexterm>of another. The tools philosophy was to have small programs to accomplish a particular task instead of trying to develop large monolithic programs to do a large number of tasks. To accomplish more complex <indexterm><primary>complex</primary></indexterm>tasks,<indexterm><primary>tasks</primary></indexterm> tools would simply be connected <indexterm><primary>connected</primary></indexterm>together, using pipes.<indexterm><primary>pipes</primary></indexterm></para><para>All the core <indexterm><primary>core</primary></indexterm>UNIX system <indexterm><primary>UNIX system</primary></indexterm>tools were designed <indexterm><primary>designed</primary></indexterm>so that they could operate<indexterm><primary>operate</primary></indexterm> together. The original text-based <indexterm><primary>text-based</primary></indexterm>editors (and even <application>TeX</application> <indexterm><primary>TeX</primary></indexterm>and LaTeX<indexterm><primary>LaTeX</primary></indexterm>) use <acronym>ASCII</acronym> <indexterm><primary>ASCII</primary></indexterm>(the American text encoding standard;<indexterm><primary>American text encoding standard</primary></indexterm> an open standard) and you can use tools such as; <emphasis>sed</emphasis>, <emphasis>awk</emphasis>, <emphasis>vi</emphasis>, <emphasis>grep</emphasis>, <emphasis>cat</emphasis>, <emphasis>more</emphasis>, <emphasis>tr</emphasis> and various other text-based <indexterm><primary>text-based</primary></indexterm>tools in conjunction <indexterm><primary>conjunction</primary></indexterm>with these editors.<indexterm><primary>editors</primary></indexterm> </para><para>Using this philosophy <indexterm><primary>philosophy</primary></indexterm>programmers <indexterm><primary>programmers</primary></indexterm>avoided writing <indexterm><primary>writing</primary></indexterm>a program (within their larger program) that had already been written by someone else (this could be considered a form of code <indexterm><primary>code</primary></indexterm>recycling). For example, command-line<indexterm><primary>command-line</primary></indexterm> spell <indexterm><primary>spell</primary></indexterm>checkers are used by a number of different applications instead of having each application <indexterm><primary>application</primary></indexterm>create its own own spell checker.<indexterm><primary>checker</primary></indexterm></para><para>This philosophy <indexterm><primary>philosophy</primary></indexterm>lives on today <indexterm><primary>today</primary></indexterm>in GNU/Linux and various other <productname>UNIX</productname> system-based operating systems (FreeBSD,<indexterm><primary>FreeBSD</primary></indexterm> NetBSD,<indexterm><primary>NetBSD</primary></indexterm> OpenBSD,<indexterm><primary>OpenBSD</primary></indexterm> etc.).</para><para>For further information (articles) on the <productname>UNIX</productname> tools philosophy <indexterm><primary>UNIX tools philosophy</primary></indexterm>please see the further reading <indexterm><primary>further reading</primary></indexterm>section, here: <xref linkend="unix-tools-further-reading"></para><para></para></chapter>
|
<chapter id="The-UNIX-Tools-Philosophy"><title>The Unix Tools Philosophy</title><para>A tool is a simple program,<indexterm><primary>program</primary></indexterm> usually designed for a specific purpose, it is sometimes referred <indexterm><primary>referred</primary></indexterm>to (at least throughout this document) as a command.</para><para>The “ Unix tools philosophy”<indexterm><primary>Unix Tools Philosophy</primary></indexterm> emerged <indexterm><primary>emerged</primary></indexterm>during the creation of the <productname>UNIX</productname> <indexterm><primary>UNIX</primary></indexterm>operating system, after the breakthrough invention <indexterm><primary>invention</primary></indexterm>of the pipe <indexterm><primary>pipe</primary></indexterm>'|' (refer to <xref linkend="Directing-input-ouput"> for information on using the pipe).</para><para>The pipe <indexterm><primary>pipe</primary></indexterm>allowed the output <indexterm><primary>output</primary></indexterm>of one program to be sent to the input <indexterm><primary>input</primary></indexterm>of another. The tools philosophy was to have small programs to accomplish a particular task instead of trying to develop large monolithic programs to do a large number of tasks. To accomplish more complex <indexterm><primary>complex</primary></indexterm>tasks,<indexterm><primary>tasks</primary></indexterm> tools would simply be connected <indexterm><primary>connected</primary></indexterm>together, using pipes.<indexterm><primary>pipes</primary></indexterm></para><para>All the core <indexterm><primary>core</primary></indexterm>UNIX system <indexterm><primary>UNIX system</primary></indexterm>tools were designed <indexterm><primary>designed</primary></indexterm>so that they could operate<indexterm><primary>operate</primary></indexterm> together. The original text-based <indexterm><primary>text-based</primary></indexterm>editors (and even <application>TeX</application> <indexterm><primary>TeX</primary></indexterm>and LaTeX<indexterm><primary>LaTeX</primary></indexterm>) use <acronym>ASCII</acronym> <indexterm><primary>ASCII</primary></indexterm>(the American text encoding standard;<indexterm><primary>American text encoding standard</primary></indexterm> an open standard) and you can use tools such as; <emphasis>sed</emphasis>, <emphasis>awk</emphasis>, <emphasis>vi</emphasis>, <emphasis>grep</emphasis>, <emphasis>cat</emphasis>, <emphasis>more</emphasis>, <emphasis>tr</emphasis> and various other text-based <indexterm><primary>text-based</primary></indexterm>tools in conjunction <indexterm><primary>conjunction</primary></indexterm>with these editors.<indexterm><primary>editors</primary></indexterm> </para><para>Using this philosophy <indexterm><primary>philosophy</primary></indexterm>programmers <indexterm><primary>programmers</primary></indexterm>avoided writing <indexterm><primary>writing</primary></indexterm>a program (within their larger program) that had already been written by someone else (this could be considered a form of code <indexterm><primary>code</primary></indexterm>recycling). For example, command-line<indexterm><primary>command-line</primary></indexterm> spell <indexterm><primary>spell</primary></indexterm>checkers are used by a number of different applications instead of having each application <indexterm><primary>application</primary></indexterm>create its own spell checker.<indexterm><primary>checker</primary></indexterm></para><para>This philosophy <indexterm><primary>philosophy</primary></indexterm>lives on today <indexterm><primary>today</primary></indexterm>in GNU/Linux and various other <productname>UNIX</productname> system-based operating systems (FreeBSD,<indexterm><primary>FreeBSD</primary></indexterm> NetBSD,<indexterm><primary>NetBSD</primary></indexterm> OpenBSD,<indexterm><primary>OpenBSD</primary></indexterm> etc.).</para><para>For further information (articles) on the <productname>UNIX</productname> tools philosophy <indexterm><primary>UNIX tools philosophy</primary></indexterm>please see the further reading <indexterm><primary>further reading</primary></indexterm>section, here: <xref linkend="unix-tools-further-reading"></para><para></para></chapter>
|
||||||
<chapter id="Shell-Tips"><title>Shell Tips</title><para>The shell <indexterm><primary>shell</primary></indexterm>tips chapter provides handy tricks that you may wish to use when you are using a GNU/Linux shell (the command-line<indexterm><primary>command-line</primary></indexterm> interface). This information includes handy <indexterm><primary>handy</primary></indexterm>shortcut <indexterm><primary>shortcut</primary></indexterm>key combinations,<indexterm><primary>key combinations</primary></indexterm> the shell's command history<indexterm><primary>command history</primary></indexterm> and information on virtual terminals.<indexterm><primary>virtual terminals</primary></indexterm></para><tip>
|
<chapter id="Shell-Tips"><title>Shell Tips</title><para>The shell <indexterm><primary>shell</primary></indexterm>tips chapter provides handy tricks that you may wish to use when you are using a GNU/Linux shell (the command-line<indexterm><primary>command-line</primary></indexterm> interface). This information includes handy <indexterm><primary>handy</primary></indexterm>shortcut <indexterm><primary>shortcut</primary></indexterm>key combinations,<indexterm><primary>key combinations</primary></indexterm> the shell's command history<indexterm><primary>command history</primary></indexterm> and information on virtual terminals.<indexterm><primary>virtual terminals</primary></indexterm></para><tip>
|
||||||
<title>If you can't boot into your system</title>
|
<title>If you can't boot into your system</title>
|
||||||
<para>If your having problems booting into your system you may like to use a shell so you can boot into your system and attempt to fix things up again.</para>
|
<para>If your having problems booting into your system you may like to use a shell so you can boot into your system and attempt to fix things up again.</para>
|
||||||
|
@ -380,7 +380,7 @@ Using <emphasis>echo</emphasis> allows you to expand the wildcards to understand
|
||||||
<sect1 id="the-command-line-history"><title>The command-line history</title><variablelist><varlistentry><term>Using the command history
|
<sect1 id="the-command-line-history"><title>The command-line history</title><variablelist><varlistentry><term>Using the command history
|
||||||
</term><listitem><para><indexterm><primary>command history</primary></indexterm>Use the up and down key's to scroll <indexterm><primary>scroll</primary></indexterm>through previously typed commands. Press [Enter] to execute <indexterm><primary>execute</primary></indexterm>them or use the left and right arrow <indexterm><primary>arrow</primary></indexterm>keys to edit<indexterm><primary>edit</primary></indexterm> the command first. Also see <emphasis>history</emphasis> (below).</para></listitem></varlistentry><varlistentry><term>The history command
|
</term><listitem><para><indexterm><primary>command history</primary></indexterm>Use the up and down key's to scroll <indexterm><primary>scroll</primary></indexterm>through previously typed commands. Press [Enter] to execute <indexterm><primary>execute</primary></indexterm>them or use the left and right arrow <indexterm><primary>arrow</primary></indexterm>keys to edit<indexterm><primary>edit</primary></indexterm> the command first. Also see <emphasis>history</emphasis> (below).</para></listitem></varlistentry><varlistentry><term>The history command
|
||||||
</term><listitem><para>The<emphasis> history <indexterm><primary>history</primary></indexterm></emphasis> command can be used to list Bash's log <indexterm><primary>log</primary></indexterm>of the commands you have typed:</para><para>This log <indexterm><primary>log</primary></indexterm>is called the “history”. To access <indexterm><primary>access</primary></indexterm>it type:</para><screen><![CDATA[history n
|
</term><listitem><para>The<emphasis> history <indexterm><primary>history</primary></indexterm></emphasis> command can be used to list Bash's log <indexterm><primary>log</primary></indexterm>of the commands you have typed:</para><para>This log <indexterm><primary>log</primary></indexterm>is called the “history”. To access <indexterm><primary>access</primary></indexterm>it type:</para><screen><![CDATA[history n
|
||||||
]]></screen><para>This will only list the last <indexterm><primary>last</primary></indexterm><emphasis>n</emphasis> commands. Type “history” (without options) to see the the entire history <indexterm><primary>history</primary></indexterm>list.<indexterm><primary>list</primary></indexterm></para><para>You can also type <emphasis>!n</emphasis><indexterm><primary>!n</primary></indexterm> to execute command number<indexterm><primary>command number</primary></indexterm> n. Use <emphasis>!!<indexterm><primary>!!</primary></indexterm></emphasis> to execute the last command you typed.</para><para><emphasis>!-n<indexterm><primary>!-n</primary></indexterm> </emphasis>will execute the command n times <indexterm><primary>times</primary></indexterm>before (in other words <emphasis>!-1</emphasis> is equivalent <indexterm><primary>equivalent</primary></indexterm>to <emphasis>!!</emphasis>). </para><para><emphasis>!string<indexterm><primary>!string</primary></indexterm> </emphasis>will execute the last command starting <indexterm><primary>starting</primary></indexterm>with that “string” and <emphasis>!?string?</emphasis> will execute the last command containing the word “string”. For example:</para><screen><![CDATA[!cd
|
]]></screen><para>This will only list the last <indexterm><primary>last</primary></indexterm><emphasis>n</emphasis> commands. Type “history” (without options) to see the entire history <indexterm><primary>history</primary></indexterm>list.<indexterm><primary>list</primary></indexterm></para><para>You can also type <emphasis>!n</emphasis><indexterm><primary>!n</primary></indexterm> to execute command number<indexterm><primary>command number</primary></indexterm> n. Use <emphasis>!!<indexterm><primary>!!</primary></indexterm></emphasis> to execute the last command you typed.</para><para><emphasis>!-n<indexterm><primary>!-n</primary></indexterm> </emphasis>will execute the command n times <indexterm><primary>times</primary></indexterm>before (in other words <emphasis>!-1</emphasis> is equivalent <indexterm><primary>equivalent</primary></indexterm>to <emphasis>!!</emphasis>). </para><para><emphasis>!string<indexterm><primary>!string</primary></indexterm> </emphasis>will execute the last command starting <indexterm><primary>starting</primary></indexterm>with that “string” and <emphasis>!?string?</emphasis> will execute the last command containing the word “string”. For example:</para><screen><![CDATA[!cd
|
||||||
]]></screen><para>Will re-run the command that you last typed starting with “cd”.</para><para></para><para><emphasis>“ commandName <indexterm><primary>commandName</primary></indexterm>!*”</emphasis> will execute the “commandName” with any arguments <indexterm><primary>arguments</primary></indexterm>you used on your last command. This maybe useful if you make a spelling <indexterm><primary>spelling</primary></indexterm>mistake, for example. If you typed:</para><screen><![CDATA[emasc /home/fred/mywork.java /tmp/testme.java
|
]]></screen><para>Will re-run the command that you last typed starting with “cd”.</para><para></para><para><emphasis>“ commandName <indexterm><primary>commandName</primary></indexterm>!*”</emphasis> will execute the “commandName” with any arguments <indexterm><primary>arguments</primary></indexterm>you used on your last command. This maybe useful if you make a spelling <indexterm><primary>spelling</primary></indexterm>mistake, for example. If you typed:</para><screen><![CDATA[emasc /home/fred/mywork.java /tmp/testme.java
|
||||||
]]></screen><para>In an attempt <indexterm><primary>attempt</primary></indexterm>to execute emacs <indexterm><primary>emacs</primary></indexterm>on the above two files this will obviously fail.<indexterm><primary>fail</primary></indexterm> So what you can do is type:</para><screen><![CDATA[emacs !*
|
]]></screen><para>In an attempt <indexterm><primary>attempt</primary></indexterm>to execute emacs <indexterm><primary>emacs</primary></indexterm>on the above two files this will obviously fail.<indexterm><primary>fail</primary></indexterm> So what you can do is type:</para><screen><![CDATA[emacs !*
|
||||||
]]></screen><para>This will execute emacs <indexterm><primary>emacs</primary></indexterm>with the arguments <indexterm><primary>arguments</primary></indexterm>that you last typed on the command-line.<indexterm><primary>command-line</primary></indexterm> In other words this is equivalent <indexterm><primary>equivalent</primary></indexterm>to typing:</para><screen><![CDATA[emacs /home/fred/mywork.java /tmp/testme.java
|
]]></screen><para>This will execute emacs <indexterm><primary>emacs</primary></indexterm>with the arguments <indexterm><primary>arguments</primary></indexterm>that you last typed on the command-line.<indexterm><primary>command-line</primary></indexterm> In other words this is equivalent <indexterm><primary>equivalent</primary></indexterm>to typing:</para><screen><![CDATA[emacs /home/fred/mywork.java /tmp/testme.java
|
||||||
|
@ -1237,7 +1237,7 @@ You could also change the command it runs for example if you changed the <emphas
|
||||||
</term><listitem><para>Displays text, one page full at a time,<indexterm><primary>time</primary></indexterm> more limited than <emphasis>less</emphasis>. In this case <emphasis>less</emphasis> is better than <emphasis>more</emphasis>.</para><screen><![CDATA[more filename.txt
|
</term><listitem><para>Displays text, one page full at a time,<indexterm><primary>time</primary></indexterm> more limited than <emphasis>less</emphasis>. In this case <emphasis>less</emphasis> is better than <emphasis>more</emphasis>.</para><screen><![CDATA[more filename.txt
|
||||||
]]></screen><para>Or using a tool (is this example cat):</para><screen><![CDATA[cat file.txt | more
|
]]></screen><para>Or using a tool (is this example cat):</para><screen><![CDATA[cat file.txt | more
|
||||||
]]></screen></listitem></varlistentry><varlistentry><term>cat<anchor id="cat">
|
]]></screen></listitem></varlistentry><varlistentry><term>cat<anchor id="cat">
|
||||||
</term><listitem><para>Combines <indexterm><primary>Combines</primary></indexterm>(concatenates) multiple <indexterm><primary>multiple</primary></indexterm>documents <indexterm><primary>documents</primary></indexterm>into one document.<indexterm><primary>document</primary></indexterm> Can be used on individual <indexterm><primary>individual</primary></indexterm>files as well.</para><para>Some useful options:<indexterm><primary>options</primary></indexterm></para><itemizedlist><listitem><para><emphasis>-b</emphasis><indexterm><primary>-b</primary></indexterm> --- number <indexterm><primary>number</primary></indexterm>all non-blank <indexterm><primary>non-blank</primary></indexterm>lines</para></listitem><listitem><para><emphasis>-n<indexterm><primary>-n</primary></indexterm></emphasis> --- number all lines. </para></listitem></itemizedlist><para>Also try using <emphasis>nl</emphasis> to number lines (it can do more complex <indexterm><primary>complex</primary></indexterm>numbering), you will find it under under this section,<indexterm><primary>section</primary></indexterm> <xref linkend="text-manipulation-tools"></para><para>Example:</para><screen><![CDATA[cat filepart1 filepart2 filepart3 > wholefile.txt
|
</term><listitem><para>Combines <indexterm><primary>Combines</primary></indexterm>(concatenates) multiple <indexterm><primary>multiple</primary></indexterm>documents <indexterm><primary>documents</primary></indexterm>into one document.<indexterm><primary>document</primary></indexterm> Can be used on individual <indexterm><primary>individual</primary></indexterm>files as well.</para><para>Some useful options:<indexterm><primary>options</primary></indexterm></para><itemizedlist><listitem><para><emphasis>-b</emphasis><indexterm><primary>-b</primary></indexterm> --- number <indexterm><primary>number</primary></indexterm>all non-blank <indexterm><primary>non-blank</primary></indexterm>lines</para></listitem><listitem><para><emphasis>-n<indexterm><primary>-n</primary></indexterm></emphasis> --- number all lines. </para></listitem></itemizedlist><para>Also try using <emphasis>nl</emphasis> to number lines (it can do more complex <indexterm><primary>complex</primary></indexterm>numbering), you will find it under this section,<indexterm><primary>section</primary></indexterm> <xref linkend="text-manipulation-tools"></para><para>Example:</para><screen><![CDATA[cat filepart1 filepart2 filepart3 > wholefile.txt
|
||||||
]]></screen><para>This will combine <indexterm><primary>combine</primary></indexterm>(concatenate) filepart1,<indexterm><primary>filepart1</primary></indexterm> filepart2 <indexterm><primary>filepart2</primary></indexterm>and filepart3 <indexterm><primary>filepart3</primary></indexterm>into the single file “wholefile.txt”.</para></listitem></varlistentry><varlistentry><term>tac
|
]]></screen><para>This will combine <indexterm><primary>combine</primary></indexterm>(concatenate) filepart1,<indexterm><primary>filepart1</primary></indexterm> filepart2 <indexterm><primary>filepart2</primary></indexterm>and filepart3 <indexterm><primary>filepart3</primary></indexterm>into the single file “wholefile.txt”.</para></listitem></varlistentry><varlistentry><term>tac
|
||||||
</term><listitem><para><indexterm><primary>tac</primary></indexterm>Combines (concatenates) multiple <indexterm><primary>multiple</primary></indexterm>documents <indexterm><primary>documents</primary></indexterm>into one document <indexterm><primary>document</primary></indexterm>and outputs<indexterm><primary>outputs</primary></indexterm> them in reverse order.<indexterm><primary>reverse</primary></indexterm> Can also be used on individual <indexterm><primary>individual</primary></indexterm>files. Notice that <emphasis>tac</emphasis> is <emphasis>cat</emphasis> written backwards. </para><para>Example:</para><screen><![CDATA[tac filepart1 filepart2 filepart3 > wholefile.txt
|
</term><listitem><para><indexterm><primary>tac</primary></indexterm>Combines (concatenates) multiple <indexterm><primary>multiple</primary></indexterm>documents <indexterm><primary>documents</primary></indexterm>into one document <indexterm><primary>document</primary></indexterm>and outputs<indexterm><primary>outputs</primary></indexterm> them in reverse order.<indexterm><primary>reverse</primary></indexterm> Can also be used on individual <indexterm><primary>individual</primary></indexterm>files. Notice that <emphasis>tac</emphasis> is <emphasis>cat</emphasis> written backwards. </para><para>Example:</para><screen><![CDATA[tac filepart1 filepart2 filepart3 > wholefile.txt
|
||||||
]]></screen><para>This will combine <indexterm><primary>combine</primary></indexterm>(concatenate) filepart1,<indexterm><primary>filepart1</primary></indexterm> filepart2 <indexterm><primary>filepart2</primary></indexterm>and filepart3 <indexterm><primary>filepart3</primary></indexterm>into the single file but have each of the files written in reverse.<indexterm><primary>reverse</primary></indexterm></para></listitem></varlistentry><varlistentry><term>z* commands
|
]]></screen><para>This will combine <indexterm><primary>combine</primary></indexterm>(concatenate) filepart1,<indexterm><primary>filepart1</primary></indexterm> filepart2 <indexterm><primary>filepart2</primary></indexterm>and filepart3 <indexterm><primary>filepart3</primary></indexterm>into the single file but have each of the files written in reverse.<indexterm><primary>reverse</primary></indexterm></para></listitem></varlistentry><varlistentry><term>z* commands
|
||||||
|
@ -1283,8 +1283,8 @@ You could also change the command it runs for example if you changed the <emphas
|
||||||
]]></screen><para>This will run <emphasis>aspell</emphasis> on a particular file called “FILE.txt”, <emphasis>aspell</emphasis> will run interactively and prompt <indexterm><primary>prompt</primary></indexterm>for user input.</para><para><emphasis>ispell</emphasis> example:</para><screen><![CDATA[ispell FILE.txt
|
]]></screen><para>This will run <emphasis>aspell</emphasis> on a particular file called “FILE.txt”, <emphasis>aspell</emphasis> will run interactively and prompt <indexterm><primary>prompt</primary></indexterm>for user input.</para><para><emphasis>ispell</emphasis> example:</para><screen><![CDATA[ispell FILE.txt
|
||||||
]]></screen><para>This will run <emphasis>ispell</emphasis> on a particular file called “FILE.txt” <emphasis>ispell</emphasis> will run interactively and prompt <indexterm><primary>prompt</primary></indexterm>for user input.</para></listitem></varlistentry><varlistentry><term>chcase
|
]]></screen><para>This will run <emphasis>ispell</emphasis> on a particular file called “FILE.txt” <emphasis>ispell</emphasis> will run interactively and prompt <indexterm><primary>prompt</primary></indexterm>for user input.</para></listitem></varlistentry><varlistentry><term>chcase
|
||||||
</term><listitem><para><indexterm><primary>chcase</primary></indexterm>Is used to change the uppercase <indexterm><primary>uppercase</primary></indexterm>letters in a file name to lowercase<indexterm><primary>lowercase</primary></indexterm> (or vice versa).</para><para>You could also use <emphasis>tr<indexterm><primary>tr</primary></indexterm></emphasis> to do the same thing... </para><screen><![CDATA[cat fileName.txt | tr '[A-Z]' '[a-z]' > newFileName.txt
|
</term><listitem><para><indexterm><primary>chcase</primary></indexterm>Is used to change the uppercase <indexterm><primary>uppercase</primary></indexterm>letters in a file name to lowercase<indexterm><primary>lowercase</primary></indexterm> (or vice versa).</para><para>You could also use <emphasis>tr<indexterm><primary>tr</primary></indexterm></emphasis> to do the same thing... </para><screen><![CDATA[cat fileName.txt | tr '[A-Z]' '[a-z]' > newFileName.txt
|
||||||
]]></screen><para>The above would convert <indexterm><primary>convert</primary></indexterm>uppercase to lowercase using the the file “fileName.txt” as input <indexterm><primary>input</primary></indexterm>and outputting the results <indexterm><primary>results</primary></indexterm>to “newFileName.txt”.</para><screen><![CDATA[cat fileName.txt | tr '[a-z]' '[A-Z]' > newFileName.txt
|
]]></screen><para>The above would convert <indexterm><primary>convert</primary></indexterm>uppercase to lowercase using the file “fileName.txt” as input <indexterm><primary>input</primary></indexterm>and outputting the results <indexterm><primary>results</primary></indexterm>to “newFileName.txt”.</para><screen><![CDATA[cat fileName.txt | tr '[a-z]' '[A-Z]' > newFileName.txt
|
||||||
]]></screen><para>The above would convert lowercase to uppercase using the the file “fileName.txt” as input <indexterm><primary>input</primary></indexterm>and outputting the results <indexterm><primary>results</primary></indexterm>to “newFileName.txt”.</para><para><emphasis>chcase</emphasis> (a perl <indexterm><primary>perl</primary></indexterm>script) can be found <indexterm><primary>found</primary></indexterm>at the <ulink url="http://www.blemished.net/chcase.html">chcase homepage.</ulink><indexterm><primary>chcase homepage</primary></indexterm></para><para></para></listitem></varlistentry><varlistentry><term>fmt
|
]]></screen><para>The above would convert lowercase to uppercase using the file “fileName.txt” as input <indexterm><primary>input</primary></indexterm>and outputting the results <indexterm><primary>results</primary></indexterm>to “newFileName.txt”.</para><para><emphasis>chcase</emphasis> (a perl <indexterm><primary>perl</primary></indexterm>script) can be found <indexterm><primary>found</primary></indexterm>at the <ulink url="http://www.blemished.net/chcase.html">chcase homepage.</ulink><indexterm><primary>chcase homepage</primary></indexterm></para><para></para></listitem></varlistentry><varlistentry><term>fmt
|
||||||
</term><listitem><para><indexterm><primary>fmt</primary></indexterm>(format) a simple text formatter. Use<emphasis> fmt <indexterm><primary>fmt</primary></indexterm></emphasis>with the <emphasis>-u<indexterm><primary>-u</primary></indexterm></emphasis> option to output text with "uniform spacing", where the space <indexterm><primary>space</primary></indexterm>between words is reduced to one space character <indexterm><primary>character</primary></indexterm>and the space between sentences <indexterm><primary>sentences</primary></indexterm>is reduced to two space characters. </para><para>Example:</para><screen><![CDATA[fmt -u myessay.txt
|
</term><listitem><para><indexterm><primary>fmt</primary></indexterm>(format) a simple text formatter. Use<emphasis> fmt <indexterm><primary>fmt</primary></indexterm></emphasis>with the <emphasis>-u<indexterm><primary>-u</primary></indexterm></emphasis> option to output text with "uniform spacing", where the space <indexterm><primary>space</primary></indexterm>between words is reduced to one space character <indexterm><primary>character</primary></indexterm>and the space between sentences <indexterm><primary>sentences</primary></indexterm>is reduced to two space characters. </para><para>Example:</para><screen><![CDATA[fmt -u myessay.txt
|
||||||
]]></screen><para>Will make sure the amount <indexterm><primary>amount</primary></indexterm>of space between sentences <indexterm><primary>sentences</primary></indexterm>is two spaces and the amount <indexterm><primary>amount</primary></indexterm>of space between words is one space.</para></listitem></varlistentry><varlistentry><term>paste
|
]]></screen><para>Will make sure the amount <indexterm><primary>amount</primary></indexterm>of space between sentences <indexterm><primary>sentences</primary></indexterm>is two spaces and the amount <indexterm><primary>amount</primary></indexterm>of space between words is one space.</para></listitem></varlistentry><varlistentry><term>paste
|
||||||
</term><listitem><para><indexterm><primary>paste</primary></indexterm>Puts lines from two files together, either lines of each file side by side (normally separated <indexterm><primary>separated</primary></indexterm>by a tab-stop <indexterm><primary>tab-stop</primary></indexterm>but you can have any symbols(s) you like...) or it can have words from each file (the first file then the second file) side by side.</para><para>To obtain a list <indexterm><primary>list</primary></indexterm>of lines side by side, the first lines from the first file on the left side separated <indexterm><primary>separated</primary></indexterm>by a tab-stop <indexterm><primary>tab-stop</primary></indexterm>then the first lines from the second file. You would type:</para><screen><![CDATA[paste file1.txt file2.txt
|
</term><listitem><para><indexterm><primary>paste</primary></indexterm>Puts lines from two files together, either lines of each file side by side (normally separated <indexterm><primary>separated</primary></indexterm>by a tab-stop <indexterm><primary>tab-stop</primary></indexterm>but you can have any symbols(s) you like...) or it can have words from each file (the first file then the second file) side by side.</para><para>To obtain a list <indexterm><primary>list</primary></indexterm>of lines side by side, the first lines from the first file on the left side separated <indexterm><primary>separated</primary></indexterm>by a tab-stop <indexterm><primary>tab-stop</primary></indexterm>then the first lines from the second file. You would type:</para><screen><![CDATA[paste file1.txt file2.txt
|
||||||
|
@ -1721,7 +1721,7 @@ Note that with mtools commands you can use the slashes on the a: part either way
|
||||||
]]></screen><para>This would run the echo <indexterm><primary>echo</primary></indexterm>command with the string <indexterm><primary>string</primary></indexterm>shown at 4:05 every Sunday.</para></listitem></varlistentry></variablelist><para></para></chapter>
|
]]></screen><para>This would run the echo <indexterm><primary>echo</primary></indexterm>command with the string <indexterm><primary>string</primary></indexterm>shown at 4:05 every Sunday.</para></listitem></varlistentry></variablelist><para></para></chapter>
|
||||||
<chapter id="Miscellaneous"><title>Miscellaneous</title><para>The miscellaneous <indexterm><primary>miscellaneous</primary></indexterm>chapter contains commands that don't really fit into the other sections <indexterm><primary>sections</primary></indexterm>of this guide.</para><variablelist><varlistentry><term>renaming extensions
|
<chapter id="Miscellaneous"><title>Miscellaneous</title><para>The miscellaneous <indexterm><primary>miscellaneous</primary></indexterm>chapter contains commands that don't really fit into the other sections <indexterm><primary>sections</primary></indexterm>of this guide.</para><variablelist><varlistentry><term>renaming extensions
|
||||||
</term><listitem><para><indexterm><primary>renaming extensions</primary></indexterm>To rename <indexterm><primary>rename</primary></indexterm>all of the files in the current <indexterm><primary>current</primary></indexterm>directory<indexterm><primary>directory</primary></indexterm> with a '.htm' extension <indexterm><primary>extension</primary></indexterm>to '.html', type:</para><screen><![CDATA[$ chcase -x 's/htm/html/' '*.htm']]><indexterm><primary>-x</primary></indexterm><![CDATA[
|
</term><listitem><para><indexterm><primary>renaming extensions</primary></indexterm>To rename <indexterm><primary>rename</primary></indexterm>all of the files in the current <indexterm><primary>current</primary></indexterm>directory<indexterm><primary>directory</primary></indexterm> with a '.htm' extension <indexterm><primary>extension</primary></indexterm>to '.html', type:</para><screen><![CDATA[$ chcase -x 's/htm/html/' '*.htm']]><indexterm><primary>-x</primary></indexterm><![CDATA[
|
||||||
]]></screen><para>You can get a copy <indexterm><primary>copy</primary></indexterm>of <emphasis>the chcase <indexterm><primary>chcase</primary></indexterm></emphasis> perl <indexterm><primary>perl</primary></indexterm>script<emphasis> <ulink url="http://www.blemished.net/chcase.html">here.</ulink></emphasis></para><para>For more <indexterm><primary>more</primary></indexterm>complex <indexterm><primary>complex</primary></indexterm>renaming <indexterm><primary>renaming</primary></indexterm>you should read <xref linkend="mass-rename"></para></listitem></varlistentry><varlistentry><term>rel<footnote><para>This information information comes from the <productname>Linux</productname> Cookbook (without editing). See [3] in the <xref linkend="references"> for further information.</para></footnote>
|
]]></screen><para>You can get a copy <indexterm><primary>copy</primary></indexterm>of <emphasis>the chcase <indexterm><primary>chcase</primary></indexterm></emphasis> perl <indexterm><primary>perl</primary></indexterm>script<emphasis> <ulink url="http://www.blemished.net/chcase.html">here.</ulink></emphasis></para><para>For more <indexterm><primary>more</primary></indexterm>complex <indexterm><primary>complex</primary></indexterm>renaming <indexterm><primary>renaming</primary></indexterm>you should read <xref linkend="mass-rename"></para></listitem></varlistentry><varlistentry><term>rel<footnote><para>This information comes from the <productname>Linux</productname> Cookbook (without editing). See [3] in the <xref linkend="references"> for further information.</para></footnote>
|
||||||
</term><listitem><para>Use rel <indexterm><primary>rel</primary></indexterm>to analyze <indexterm><primary>analyze</primary></indexterm>text files for relevance <indexterm><primary>relevance</primary></indexterm>to a given set of keywords.<indexterm><primary>keywords</primary></indexterm> It outputs <indexterm><primary>outputs</primary></indexterm>the names of those files that are relevant <indexterm><primary>relevant</primary></indexterm>to the given keywords, ranked <indexterm><primary>ranked</primary></indexterm>in order <indexterm><primary>order</primary></indexterm>of relevance;<indexterm><primary>relevance</primary></indexterm> if a file does not meet the criteria,<indexterm><primary>criteria</primary></indexterm> it is not outputted in the relevance <indexterm><primary>relevance</primary></indexterm>listing.</para></listitem></varlistentry><varlistentry><term>units man page
|
</term><listitem><para>Use rel <indexterm><primary>rel</primary></indexterm>to analyze <indexterm><primary>analyze</primary></indexterm>text files for relevance <indexterm><primary>relevance</primary></indexterm>to a given set of keywords.<indexterm><primary>keywords</primary></indexterm> It outputs <indexterm><primary>outputs</primary></indexterm>the names of those files that are relevant <indexterm><primary>relevant</primary></indexterm>to the given keywords, ranked <indexterm><primary>ranked</primary></indexterm>in order <indexterm><primary>order</primary></indexterm>of relevance;<indexterm><primary>relevance</primary></indexterm> if a file does not meet the criteria,<indexterm><primary>criteria</primary></indexterm> it is not outputted in the relevance <indexterm><primary>relevance</primary></indexterm>listing.</para></listitem></varlistentry><varlistentry><term>units man page
|
||||||
</term><listitem><para><indexterm><primary>units man page</primary></indexterm>There is a man page, part of the <productname>Linux</productname> Programmers <indexterm><primary>Programmers</primary></indexterm>Manual called “units”. It displays various information <indexterm><primary>information</primary></indexterm>on the various scientific <indexterm><primary>scientific</primary></indexterm>measurements<indexterm><primary>measurements</primary></indexterm> (such as mega,<indexterm><primary>mega</primary></indexterm> giga <indexterm><primary>giga</primary></indexterm>et cetera). This manual <indexterm><primary>manual</primary></indexterm>page <indexterm><primary>page</primary></indexterm>also has a short discussion about the argument <indexterm><primary>argument</primary></indexterm>over which<indexterm><primary>which</primary></indexterm> standard <indexterm><primary>standard</primary></indexterm>should be used to measure <indexterm><primary>measure</primary></indexterm>data (ie. the kibibyte <indexterm><primary>kibibyte</primary></indexterm>vs kilobyte). </para><para>To access <indexterm><primary>access</primary></indexterm>this man page type:</para><screen><![CDATA[man 7 units
|
</term><listitem><para><indexterm><primary>units man page</primary></indexterm>There is a man page, part of the <productname>Linux</productname> Programmers <indexterm><primary>Programmers</primary></indexterm>Manual called “units”. It displays various information <indexterm><primary>information</primary></indexterm>on the various scientific <indexterm><primary>scientific</primary></indexterm>measurements<indexterm><primary>measurements</primary></indexterm> (such as mega,<indexterm><primary>mega</primary></indexterm> giga <indexterm><primary>giga</primary></indexterm>et cetera). This manual <indexterm><primary>manual</primary></indexterm>page <indexterm><primary>page</primary></indexterm>also has a short discussion about the argument <indexterm><primary>argument</primary></indexterm>over which<indexterm><primary>which</primary></indexterm> standard <indexterm><primary>standard</primary></indexterm>should be used to measure <indexterm><primary>measure</primary></indexterm>data (ie. the kibibyte <indexterm><primary>kibibyte</primary></indexterm>vs kilobyte). </para><para>To access <indexterm><primary>access</primary></indexterm>this man page type:</para><screen><![CDATA[man 7 units
|
||||||
]]></screen></listitem></varlistentry><varlistentry><term>fortune
|
]]></screen></listitem></varlistentry><varlistentry><term>fortune
|
||||||
|
|
|
@ -848,7 +848,7 @@ access control (access)
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Access control refers to controlling access by a user to a computer system, or data on that system. In formal terms, a "subject" (e.g. a user) attempts to access the "object" (e.g. system or data). An access control system will evaluate the security levels of the subject and object in order to see if access is permitted. Example: A simple example is the case where you enter a username and password in order to log onto the computer. Contrast: mandatory access control The system gives users "clearance levels", and assigns sensitivity levels to information. Therefore, if you only have "secret" clearance level, you cannot access "top-secret" information, but you can access "secret" or "confidential" information. See: Bell-LaPadula Model for more information. discretionary access control This system assigns subjects (users) to one or more groups. An object (system or file) contains a DACL (discretionary access control list) enumeration which users and groups may access the object. See: Access Control List for more information. Key point: There are different kinds of access. Read access means that somebody can read information, whereas write access implies that that somebody can change the data. For example, you can get a copy of your credit report and read it, but you can't necessarily change the data. From Hacking-Lexicon
|
Access control refers to controlling access by a user to a computer system, or data on that system. In formal terms, a "subject" (e.g. a user) attempts to access the "object" (e.g. system or data). An access control system will evaluate the security levels of the subject and object in order to see if access is permitted. Example: A simple example is the case where you enter a username and password in order to log onto the computer. Contrast: mandatory access control The system gives users "clearance levels", and assigns sensitivity levels to information. Therefore, if you only have "secret" clearance level, you cannot access "top-secret" information, but you can access "secret" or "confidential" information. See: Bell-LaPadula Model for more information. discretionary access control This system assigns subjects (users) to one or more groups. An object (system or file) contains a DACL (discretionary access control list) enumeration which users and groups may access the object. See: Access Control List for more information. Key point: There are different kinds of access. Read access means that somebody can read information, whereas write access implies that somebody can change the data. For example, you can get a copy of your credit report and read it, but you can't necessarily change the data. From Hacking-Lexicon
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -12908,7 +12908,7 @@ avra
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Assembler for Atmel AVR microcontrollers Avra is an assembler for the Atmel's family of AVR 8-bit RISC microcontrollers. It is is mostly compatible with Atmel's own assembler, but adds new features such as better macro support and additional preprocessor directives. From Debian 3.0r0 APT
|
Assembler for Atmel AVR microcontrollers Avra is an assembler for the Atmel's family of AVR 8-bit RISC microcontrollers. It is mostly compatible with Atmel's own assembler, but adds new features such as better macro support and additional preprocessor directives. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -704,7 +704,7 @@ bash
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
The default command interpreter, or shell, for Red Hat Linux. bash features several enhancements to sh, such as built-in file management commands and support for completion of commands and paths using the the [Tab] key. From Redhat-9-Glossary
|
The default command interpreter, or shell, for Red Hat Linux. bash features several enhancements to sh, such as built-in file management commands and support for completion of commands and paths using the [Tab] key. From Redhat-9-Glossary
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -1208,7 +1208,7 @@ BBS (Bulletin Board System)
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Electronic BBSs formed much of the the core "cyberspace" in the 1980s. Telecommunication costs were high, so rather than interconnected via "always-on" connections, such systems transfered files and messages as irregular intervals over dial-up lines. Mail was transported through BBS via protocols like FidoNet and UUCP. Files would move themselves from system to system as users would download from one BBS and upload to others. Many of today's older hackers were active in the BBS community of the 1980s. From Hacking-Lexicon
|
Electronic BBSs formed much of the core "cyberspace" in the 1980s. Telecommunication costs were high, so rather than interconnected via "always-on" connections, such systems transfered files and messages as irregular intervals over dial-up lines. Mail was transported through BBS via protocols like FidoNet and UUCP. Files would move themselves from system to system as users would download from one BBS and upload to others. Many of today's older hackers were active in the BBS community of the 1980s. From Hacking-Lexicon
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -6980,7 +6980,7 @@ bugsquish
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Bugs are trying to suck blood out of your arm! "Bug Squish" is an action game not unlike light gun arcade games, but played with a mouse. It's loosely based on a MacOS game whose name I can't recall. Bugs are trying to suck blood out of your arm! Squish them with with your fly swatter before you run out of blood. From Debian 3.0r0 APT
|
Bugs are trying to suck blood out of your arm! "Bug Squish" is an action game not unlike light gun arcade games, but played with a mouse. It's loosely based on a MacOS game whose name I can't recall. Bugs are trying to suck blood out of your arm! Squish them with your fly swatter before you run out of blood. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -5132,7 +5132,7 @@ chbg
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
A tool for changing the desktop background image in X11 A GTK+ based program that lets you periodically change your X desktop. It has several random effects, a slideshow, and and may act as a xscreensaver hack or as a standalone screensaver. From Debian 3.0r0 APT
|
A tool for changing the desktop background image in X11 A GTK+ based program that lets you periodically change your X desktop. It has several random effects, a slideshow and may act as a xscreensaver hack or as a standalone screensaver. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -6632,7 +6632,7 @@ ClarkConnect
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
ClarkConnect is a Red Hat based distribution which can can transform standard PC hardware into a dedicated broadband gateway and easy-to-use server. The software is a great solution for small businesses, home offices, and networked homes. ClarkConnect version 1.1 was released July 31, 2002. From LWN Distribution List
|
ClarkConnect is a Red Hat based distribution which can transform standard PC hardware into a dedicated broadband gateway and easy-to-use server. The software is a great solution for small businesses, home offices, and networked homes. ClarkConnect version 1.1 was released July 31, 2002. From LWN Distribution List
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -3872,7 +3872,7 @@ Debian-Med
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Debian-Med is an internal Debian project to support tasks of people in medical care. The goal of Debian-Med is to build a a complete system for all tasks in medical care, using only free software. A 'special purpose/mini' distribution. From LWN Distribution List
|
Debian-Med is an internal Debian project to support tasks of people in medical care. The goal of Debian-Med is to build a complete system for all tasks in medical care, using only free software. A 'special purpose/mini' distribution. From LWN Distribution List
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -6860,7 +6860,7 @@ Diffie-Hellman (DH)
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
The original public-key algorithm. Modern cryptography starts in 1976 when Diffie and Hellman published their groundbreaking paper "New Directions in Cryptography". Contrast: Whereas RSA is based upon the mathematical problem of factoring large numbers, DH is based upon the discrete logarithm problem. Whereas RSA can be used to encrypt messages, DH can only be used for key-exchange. However, RSA is essentially only used for key-exchange in the first place. The disadvantages of DH vs. RSA are: message expansion DH encrypted messages are larger (though this isn't really an issue for key-exchange). key size Current standards (e.g. DSS) specify smaller key sizes than those supported by RSA-based standards. CPU DH based standards take processing time than RSA based equivalents (and a lot more than than elliptical curve techniques). Advantages of DH over RSA are: patents This is no longer an important issue now that RSA patents have expired, but the reason DH became popular was because it was essentially patent-free. key generation It takes a long time to generate RSA keys, so DH is a better option if keys must be generated often. key size For keys of the same size, DH is more secure. In other words, it takes longer keys for RSA to be as secure as DH. security DH is conjectured to be less likely to be broken by new developements in mathematical theory. Contrast: The most common use of Diffie-Hellman is ElGamal, a public-key encryption variant of Diffie-Hellman. The U.S. government standard DSS is based upon ElGamal. See also: RSA, public-key crypto. From Hacking-Lexicon
|
The original public-key algorithm. Modern cryptography starts in 1976 when Diffie and Hellman published their groundbreaking paper "New Directions in Cryptography". Contrast: Whereas RSA is based upon the mathematical problem of factoring large numbers, DH is based upon the discrete logarithm problem. Whereas RSA can be used to encrypt messages, DH can only be used for key-exchange. However, RSA is essentially only used for key-exchange in the first place. The disadvantages of DH vs. RSA are: message expansion DH encrypted messages are larger (though this isn't really an issue for key-exchange). key size Current standards (e.g. DSS) specify smaller key sizes than those supported by RSA-based standards. CPU DH based standards take processing time than RSA based equivalents (and a lot more than elliptical curve techniques). Advantages of DH over RSA are: patents This is no longer an important issue now that RSA patents have expired, but the reason DH became popular was because it was essentially patent-free. key generation It takes a long time to generate RSA keys, so DH is a better option if keys must be generated often. key size For keys of the same size, DH is more secure. In other words, it takes longer keys for RSA to be as secure as DH. security DH is conjectured to be less likely to be broken by new developements in mathematical theory. Contrast: The most common use of Diffie-Hellman is ElGamal, a public-key encryption variant of Diffie-Hellman. The U.S. government standard DSS is based upon ElGamal. See also: RSA, public-key crypto. From Hacking-Lexicon
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -10868,7 +10868,7 @@ dpkg-iasearch
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
An interface to find relevant packages in Debian. This package adds some tools to find relevant packages in Debian using simple queries, both in natural language and by keywords. It makes uses of the document-vectoring program arrow, adding scripts to make use of it to index the Packages database, and to make queries on to it. Its functionality is similar to dlocate but uses a different (more useful?) approach to make the binary database. This package is a proof-of-concept package, any kind of improvements are are welcomed, although this idea should be part of a dpkg frontend {T,G}UI. From Debian 3.0r0 APT
|
An interface to find relevant packages in Debian. This package adds some tools to find relevant packages in Debian using simple queries, both in natural language and by keywords. It makes uses of the document-vectoring program arrow, adding scripts to make use of it to index the Packages database, and to make queries on to it. Its functionality is similar to dlocate but uses a different (more useful?) approach to make the binary database. This package is a proof-of-concept package, any kind of improvements are welcomed, although this idea should be part of a dpkg frontend {T,G}UI. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -11348,7 +11348,7 @@ dput
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Debian package upload tool This script will allow you to put one or more Debian packages into the archive. It includes some tests to verify that the package is policy-compliant. It offers the possibility to run lintian before the upload. It can also run dinstall in dry-run-mode, when having used an appropriate upload method. This is very useful to see if the the upload will pass dinstall sanity checks in the next run. It's intended for Debian maintainers only. From Debian 3.0r0 APT
|
Debian package upload tool This script will allow you to put one or more Debian packages into the archive. It includes some tests to verify that the package is policy-compliant. It offers the possibility to run lintian before the upload. It can also run dinstall in dry-run-mode, when having used an appropriate upload method. This is very useful to see if the upload will pass dinstall sanity checks in the next run. It's intended for Debian maintainers only. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -6692,7 +6692,7 @@ Eurielec Linux
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
This was a project started by a a club of students at ETSIT (UPM), according to the Spanish web site. Distribution development is not all that active. From LWN Distribution List
|
This was a project started by a club of students at ETSIT (UPM), according to the Spanish web site. Distribution development is not all that active. From LWN Distribution List
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -3500,7 +3500,7 @@ Firewall
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
A security procedure that places a specially progammed computer system between an organisation's Local Area Network (LAN) and the Internet. The firewall computer precents acrackes from accessing the internal network. Unfortunately, it also prevents the organisation's copmuter uses form gaining direct access to the Internet. The access the the firewall provides is indirect and mediated by programs called proxy servers. From QUECID
|
A security procedure that places a specially progammed computer system between an organisation's Local Area Network (LAN) and the Internet. The firewall computer precents acrackes from accessing the internal network. Unfortunately, it also prevents the organisation's copmuter uses form gaining direct access to the Internet. The access the firewall provides is indirect and mediated by programs called proxy servers. From QUECID
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -7640,7 +7640,7 @@ fuzzy hashing
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
a hashing scheme which can handle range based lookups and multiple keys. It was born from debugging problems arising from from the removal of the old AVL tree mechanism for finding the virtual memory area (vma) associated with a page fault. From Linux Guide @FirstLinux
|
a hashing scheme which can handle range based lookups and multiple keys. It was born from debugging problems arising from the removal of the old AVL tree mechanism for finding the virtual memory area (vma) associated with a page fault. From Linux Guide @FirstLinux
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -3488,7 +3488,7 @@ glimmer
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Programmer's editor with multiple windows and syntax highlighting Glimmer is a simple code editor for use with just about any programming language, which makes use of of the Gtk+ widget set and the GNOME libraries, which includes drag and drop support. It includes syntax and bracket highlighting, the ability to build from within the editor, and support for saving sessions of many different code files open at once. Most settings can be customised from within the editor. Glimmer includes support for the following languages: Ada, bash/sh, C, C++, FORTRAN, HTML, Java, Javascript, Latex, GNU Make, Perl, PHP, Python, Lisp (guile, scheme, etc), SGML, SQL, Tcl/Tk, XML, XHTML, and Z80 Assembly, to name a few. Glimmer is also very extensible in the languages it supports for its syntax highlighting. If support for your language of choice is not included, you can write it very easily. In addition to this, Glimmer is completely scriptable with python. See http://glimmer.sourceforge.net for more information. From Debian 3.0r0 APT
|
Programmer's editor with multiple windows and syntax highlighting Glimmer is a simple code editor for use with just about any programming language, which makes use of the Gtk+ widget set and the GNOME libraries, which includes drag and drop support. It includes syntax and bracket highlighting, the ability to build from within the editor, and support for saving sessions of many different code files open at once. Most settings can be customised from within the editor. Glimmer includes support for the following languages: Ada, bash/sh, C, C++, FORTRAN, HTML, Java, Javascript, Latex, GNU Make, Perl, PHP, Python, Lisp (guile, scheme, etc), SGML, SQL, Tcl/Tk, XML, XHTML, and Z80 Assembly, to name a few. Glimmer is also very extensible in the languages it supports for its syntax highlighting. If support for your language of choice is not included, you can write it very easily. In addition to this, Glimmer is completely scriptable with python. See http://glimmer.sourceforge.net for more information. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -5144,7 +5144,7 @@ gnome-sudo
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
GUI frontend to sudo gnome-sudo will popup a dialog requesting the password for the user to run as (if necessary, sudo has caching), and copies ~/.Xauthority so that that user can reach it. This is to provide a way for GUI programs (such as package managers) to run in an easy, point-and-drool fashion. From Debian 3.0r0 APT
|
GUI frontend to sudo gnome-sudo will popup a dialog requesting the password for the user to run as (if necessary, sudo has caching), and copies ~/.Xauthority so that the user can reach it. This is to provide a way for GUI programs (such as package managers) to run in an easy, point-and-drool fashion. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -5936,7 +5936,7 @@ gnupg
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
GNU privacy guard - a free PGP replacement. GnuPG is GNU's tool for secure communication and data storage. It can be used to encrypt data and to create digital signatures. It includes an advanced key management facility and is compliant with the proposed OpenPGP Internet standard as described in RFC2440. GnuPG does not use use any patented algorithms so it cannot be compatible with PGP2 because it uses IDEA (which is patented worldwide) and RSA. RSA's patent expired on the 20th September 2000, and it is now included in GnuPG. From Debian 3.0r0 APT
|
GNU privacy guard - a free PGP replacement. GnuPG is GNU's tool for secure communication and data storage. It can be used to encrypt data and to create digital signatures. It includes an advanced key management facility and is compliant with the proposed OpenPGP Internet standard as described in RFC2440. GnuPG does not use any patented algorithms so it cannot be compatible with PGP2 because it uses IDEA (which is patented worldwide) and RSA. RSA's patent expired on the 20th September 2000, and it is now included in GnuPG. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -2024,7 +2024,7 @@ hindent
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Reformats HTML code This utility reformats HTML code to be properly indented/nested for improved readability. You can indent the existing lines as-is, or totally reformat the code to have one tag per line. Hindent is useful in deciphering software-generated HTML code when it's all just one huge line, or help you find find that last missing end-tag, or deal with code victimized by creeping featurism. Written in Perl for Unix. Understands all HTML 3.2 nestable tags. From Debian 3.0r0 APT
|
Reformats HTML code This utility reformats HTML code to be properly indented/nested for improved readability. You can indent the existing lines as-is, or totally reformat the code to have one tag per line. Hindent is useful in deciphering software-generated HTML code when it's all just one huge line, or help you find that last missing end-tag, or deal with code victimized by creeping featurism. Written in Perl for Unix. Understands all HTML 3.2 nestable tags. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -2252,7 +2252,7 @@ IDEA (International Data Encryption Algorithm)
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
IDEA is a symmetric block cipher algorithm. It is popular because it is used in PGP, but due to commercial licensing issues, it is not popular elsewhere. Controversy: IDEA is one of the few (widely-used) ciphers protected by patents; it requires a license for commercial use. PGP is no longer using IDEA as its default cipher because of this. Notes: It was developed by Xuejia Lai and James L. Massey. It uses 128-bit keys. There is no known way to break it other than brute-force. It was published in 1990. Its patents are held by the Swiss company "Ascom-Tech AG". Misconception: The name implies that IDEA is some sort of official standard -- it isn't. However, it is is widely used, and is an option on many standards. Applications: PGP From Hacking-Lexicon
|
IDEA is a symmetric block cipher algorithm. It is popular because it is used in PGP, but due to commercial licensing issues, it is not popular elsewhere. Controversy: IDEA is one of the few (widely-used) ciphers protected by patents; it requires a license for commercial use. PGP is no longer using IDEA as its default cipher because of this. Notes: It was developed by Xuejia Lai and James L. Massey. It uses 128-bit keys. There is no known way to break it other than brute-force. It was published in 1990. Its patents are held by the Swiss company "Ascom-Tech AG". Misconception: The name implies that IDEA is some sort of official standard -- it isn't. However, it is widely used, and is an option on many standards. Applications: PGP From Hacking-Lexicon
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -3080,7 +3080,7 @@ iesperanto
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
The Esperanto dictionary for ispell. This is the the Esperanto dictionary, to be used with the ispell program, version 3.1.04 and following. The dictionary is based on the words from Plena Ilustrita Vortaro, with additional country/language names. It accepts Latin-3, `cx' and `^c' forms. From Debian 3.0r0 APT
|
The Esperanto dictionary for ispell. This is the Esperanto dictionary, to be used with the ispell program, version 3.1.04 and following. The dictionary is based on the words from Plena Ilustrita Vortaro, with additional country/language names. It accepts Latin-3, `cx' and `^c' forms. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -3728,7 +3728,7 @@ kpsewhich
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
standalone path lookup and and expansion for kpathsea From whatis
|
standalone path lookup and expansion for kpathsea From whatis
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -740,7 +740,7 @@ latex2html
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
LaTeX to HTML translator. LaTeX2HTML is a conversion tool that that converts documents written in LaTeX to HTML format. In addition, it offers an easy migration path towards authoring complex hypermedia documents using familiar word-processing concepts. LaTeX2HTML replicates the basic structure of a LaTeX document as a set of interconnected HTML files which can be explored using automatically generated navigation panels. The cross-references, citations, footnotes, the table of contents and the lists of figures and tables, are also translated into hypertext links. Formatting information which has equivalent ``tags'' in HTML (lists, quotes, paragraph breaks, type styles, etc.) is also converted appropriately. The remaining heavily formatted items such as mathematical equations, pictures or tables are converted to images which are placed automatically at the correct positions in the final HTML document. LaTeX2HTML extends LaTeX by supporting arbitrary hypertext links and symbolic cross-references between evolving remote documents. It also allows the specification of conditional text and the inclusion of raw HTML commands. These hypermedia extensions to LaTeX are available as new commands and environments from within a LaTeX document. Pstoimg, the part of latex2html that produces bitmap images from the LaTeX source, can support both GIF and PNG format. Because of certain legal limitations on the use of the GIF image format, GIF support is disabled in this package. From Debian 3.0r0 APT
|
LaTeX to HTML translator. LaTeX2HTML is a conversion tool that converts documents written in LaTeX to HTML format. In addition, it offers an easy migration path towards authoring complex hypermedia documents using familiar word-processing concepts. LaTeX2HTML replicates the basic structure of a LaTeX document as a set of interconnected HTML files which can be explored using automatically generated navigation panels. The cross-references, citations, footnotes, the table of contents and the lists of figures and tables, are also translated into hypertext links. Formatting information which has equivalent ``tags'' in HTML (lists, quotes, paragraph breaks, type styles, etc.) is also converted appropriately. The remaining heavily formatted items such as mathematical equations, pictures or tables are converted to images which are placed automatically at the correct positions in the final HTML document. LaTeX2HTML extends LaTeX by supporting arbitrary hypertext links and symbolic cross-references between evolving remote documents. It also allows the specification of conditional text and the inclusion of raw HTML commands. These hypermedia extensions to LaTeX are available as new commands and environments from within a LaTeX document. Pstoimg, the part of latex2html that produces bitmap images from the LaTeX source, can support both GIF and PNG format. Because of certain legal limitations on the use of the GIF image format, GIF support is disabled in this package. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -1472,7 +1472,7 @@ ldap2dns
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
LDAP based DNS management system. ldap2dns is a program to create DNS (Domain Name Service) records directly from a LDAP directory. It can and should be be used to replace the secondary name-server by a second primary one. ldap2dns reduces all kind of administration overhead: No more flat file editing, no more zone file editing. After having installed ldap2dns, the administrator only has to access the LDAP directory. ldap2dns is designed to write ASCII data files used by tinydns from the djbdns package, but also may be used to write .db-files used by named as found in the BIND package. From Debian 3.0r0 APT
|
LDAP based DNS management system. ldap2dns is a program to create DNS (Domain Name Service) records directly from a LDAP directory. It can and should be used to replace the secondary name-server by a second primary one. ldap2dns reduces all kind of administration overhead: No more flat file editing, no more zone file editing. After having installed ldap2dns, the administrator only has to access the LDAP directory. ldap2dns is designed to write ASCII data files used by tinydns from the djbdns package, but also may be used to write .db-files used by named as found in the BIND package. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -5228,7 +5228,7 @@ Linux
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
/lee'nuhks/ or /li'nuks/, not /li:'nuhks/ n. The free Unix workalike created by Linus Torvalds and friends starting about 1991. The pronunciation /lee'nuhks/ is preferred because the name `Linus' has an /ee/ sound in Swedish (Linus's family is part of Finland's 6% ethnic-Swedish minority). This may be the most remarkable hacker project in history -- an entire clone of Unix for 386, 486 and Pentium micros, distributed for free with sources over the net (ports to Alpha and Sparc and many other machines are also in use). Linux is what GNU aimed to be, and it relies on the GNU toolset. But the Free Software Foundation didn't produce the kernel to go with that toolset until 1999, which was too late. Other, similar efforts like FreeBSD and NetBSD have been technically successful but never caught fire the way Linux has; as this is written in 2000, Linux is seriously challenging Microsoft's OS dominance. It has already captured 31% of the Internet-server market and 25% of general business servers. An earlier version of this entry opined "The secret of Linux's success seems to be that Linus worked much harder early on to keep the development process open and recruit other hackers, creating a snowball effect." Truer than we knew. See bazaar. (Some people object that the name `Linux' should be used to refer only to the kernel, not the entire operating system. This claim is a proxy for an underlying territorial dispute; people who insist on the term `GNU/Linux' want the the FSF to get most of the credit for Linux because RMS and friends wrote many of its user-level tools. Neither this theory nor the term `GNU/Linux' has gained more than minority acceptance). From Jargon Dictionary
|
/lee'nuhks/ or /li'nuks/, not /li:'nuhks/ n. The free Unix workalike created by Linus Torvalds and friends starting about 1991. The pronunciation /lee'nuhks/ is preferred because the name `Linus' has an /ee/ sound in Swedish (Linus's family is part of Finland's 6% ethnic-Swedish minority). This may be the most remarkable hacker project in history -- an entire clone of Unix for 386, 486 and Pentium micros, distributed for free with sources over the net (ports to Alpha and Sparc and many other machines are also in use). Linux is what GNU aimed to be, and it relies on the GNU toolset. But the Free Software Foundation didn't produce the kernel to go with that toolset until 1999, which was too late. Other, similar efforts like FreeBSD and NetBSD have been technically successful but never caught fire the way Linux has; as this is written in 2000, Linux is seriously challenging Microsoft's OS dominance. It has already captured 31% of the Internet-server market and 25% of general business servers. An earlier version of this entry opined "The secret of Linux's success seems to be that Linus worked much harder early on to keep the development process open and recruit other hackers, creating a snowball effect." Truer than we knew. See bazaar. (Some people object that the name `Linux' should be used to refer only to the kernel, not the entire operating system. This claim is a proxy for an underlying territorial dispute; people who insist on the term `GNU/Linux' want the FSF to get most of the credit for Linux because RMS and friends wrote many of its user-level tools. Neither this theory nor the term `GNU/Linux' has gained more than minority acceptance). From Jargon Dictionary
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -5012,7 +5012,7 @@ pgi
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Progeny graphical installer creation system This package contains PGI, a multi-architecture graphical installer creation system for Debian GNU/Linux originally developed by Progeny Linux Systems, Inc., for their Debian-based "Progeny Debian" operating system. This package enables the user to create ISO images containing a bootable installer (PGI) which guides the user through the steps of installation. The installer supports text and graphical installation modes. PGI runs debootstrap to install a minimal Debian system to the target filesystem(s), sets up a boot loader (if the installing user requests), and uses the pivot_root() system call to "boot" into the installed system. ISO images may be generated with complete or partial Debian package archives, or with the the installer only (useful for network-only installs, which PGI supports.) PGI is extensible and customizable. Two example extensions are provided with this package; one uses the base-config package, while the other configures the installed system using the X-based Configlet system. Two manuals are provided as part of this package. "Creating Debian Installers with PGI" documents the setup and configuration of a PGI-based installer ISO in detail. "Using the PGI Debian Installer" is an example of a PGI user's manual. Those creating custom installers with PGI will want to update the user's manual for their target audience. From Debian 3.0r0 APT
|
Progeny graphical installer creation system This package contains PGI, a multi-architecture graphical installer creation system for Debian GNU/Linux originally developed by Progeny Linux Systems, Inc., for their Debian-based "Progeny Debian" operating system. This package enables the user to create ISO images containing a bootable installer (PGI) which guides the user through the steps of installation. The installer supports text and graphical installation modes. PGI runs debootstrap to install a minimal Debian system to the target filesystem(s), sets up a boot loader (if the installing user requests), and uses the pivot_root() system call to "boot" into the installed system. ISO images may be generated with complete or partial Debian package archives, or with the installer only (useful for network-only installs, which PGI supports.) PGI is extensible and customizable. Two example extensions are provided with this package; one uses the base-config package, while the other configures the installed system using the X-based Configlet system. Two manuals are provided as part of this package. "Creating Debian Installers with PGI" documents the setup and configuration of a PGI-based installer ISO in detail. "Using the PGI Debian Installer" is an example of a PGI user's manual. Those creating custom installers with PGI will want to update the user's manual for their target audience. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -5672,7 +5672,7 @@ picasm
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Assembler for the Microchip PIC-family Microcontrollers An assembler for the the Microchip PIC family of microcontrollers. Supports the majority of the Microchip PIC family. Uses Microchip (not Parallax) syntax. From Debian 3.0r0 APT
|
Assembler for the Microchip PIC-family Microcontrollers An assembler for the Microchip PIC family of microcontrollers. Supports the majority of the Microchip PIC family. Uses Microchip (not Parallax) syntax. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -12668,7 +12668,7 @@ FORTRAN source code From Whatis-Extensions
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
On UNIX, a user can place an e-mail address in his ".forward" file. This will cause all e-mail sent to his account to be forwarded to that e-mail address. This file a is prime target of attackers. If they can overwrite this file, they can subtly start capturing the user's e-mail. This is especially dangerous if the the account in question is the root account. Note that the user doesn't have to know any about this file or have one on his system. The mere creation of this file by the intruder will activate this feature. Furthermore, since this file starts with a 'dot', it is normally hidden from the user, so they won't even be ware that this feature exists. From Hacking-Lexicon
|
On UNIX, a user can place an e-mail address in his ".forward" file. This will cause all e-mail sent to his account to be forwarded to that e-mail address. This file a is prime target of attackers. If they can overwrite this file, they can subtly start capturing the user's e-mail. This is especially dangerous if the account in question is the root account. Note that the user doesn't have to know any about this file or have one on his system. The mere creation of this file by the intruder will activate this feature. Furthermore, since this file starts with a 'dot', it is normally hidden from the user, so they won't even be ware that this feature exists. From Hacking-Lexicon
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -440,7 +440,7 @@ qm
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Quality Management Tools Quality Management Tools, the former 'Software Carpentry Project'. QMTest is the first tool released as a result of the Software Carpentry project. (Hopefully) forthcoming tools are: - a platform investigation and project reconfiguration tool to supersede autoconf. - a dependency management and program reconstruction tool to to supersede make. - an issue tracking system to supersede gnats and bugzilla. From Debian 3.0r0 APT
|
Quality Management Tools Quality Management Tools, the former 'Software Carpentry Project'. QMTest is the first tool released as a result of the Software Carpentry project. (Hopefully) forthcoming tools are: - a platform investigation and project reconfiguration tool to supersede autoconf. - a dependency management and program reconstruction tool to supersede make. - an issue tracking system to supersede gnats and bugzilla. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -3224,7 +3224,7 @@ redhat-switch-printer-gnome
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
The redhat-switch-printer-gnome package contains a GNOME interface for the The Printing System Switcher. From Redhat 8.0 RPM
|
The redhat-switch-printer-gnome package contains a GNOME interface for the Printing System Switcher. From Redhat 8.0 RPM
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -2516,7 +2516,7 @@ scite
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Lightweight GTK-based Programming Editor GTK-based Programming with with syntax highlighting support for many languages. Also supports folding sections, exporting highlighted text into colored HTML and RTF. From Debian 3.0r0 APT
|
Lightweight GTK-based Programming Editor GTK-based Programming with syntax highlighting support for many languages. Also supports folding sections, exporting highlighted text into colored HTML and RTF. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -5900,7 +5900,7 @@ setcd
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Control the behaviour of your cdrom device This program allows you to control the behaviour of your Linux cdrom player. You'll need a cdrom device that complies to the new interface defined in linux/Documentation/cdrom/cdrom-standard.tex. For kernel 2.0 this is only the cm206 drive, for kernel 2.1 this includes IDE and SCSI drives. You can control: auto close, auto eject, medium type checking and tray locking. You can get information on the volume name of cdroms and other data, and you can set the speed of your drive and choose a disc from a jukebox. In order to fully exploit the possibilities, you'll need libc6 and a recent version of the the linux kernel, but you will get decent error behaviour in return. Expect a message "No medium found" if you attempt to mount an empty drive or "Wrong medium type" if you try to mount an audio disc, instead of a whole load of kernel error messages. The source of this package may be an example for cdrom player program developers that wish to exploit the features of the new cdrom interface. From Debian 3.0r0 APT
|
Control the behaviour of your cdrom device This program allows you to control the behaviour of your Linux cdrom player. You'll need a cdrom device that complies to the new interface defined in linux/Documentation/cdrom/cdrom-standard.tex. For kernel 2.0 this is only the cm206 drive, for kernel 2.1 this includes IDE and SCSI drives. You can control: auto close, auto eject, medium type checking and tray locking. You can get information on the volume name of cdroms and other data, and you can set the speed of your drive and choose a disc from a jukebox. In order to fully exploit the possibilities, you'll need libc6 and a recent version of the linux kernel, but you will get decent error behaviour in return. Expect a message "No medium found" if you attempt to mount an empty drive or "Wrong medium type" if you try to mount an audio disc, instead of a whole load of kernel error messages. The source of this package may be an example for cdrom player program developers that wish to exploit the features of the new cdrom interface. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -13328,7 +13328,7 @@ Sorcerer
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
This distribution was created by the original Sorcerer GNU/Linux author, Kyle Sallee. Sources are downloaded directly from software authors' homepages and mirrors. Then, they are compiled with the architecture and optimizations that the system administrator specifies. Finally, it is installed, tracked, and archived for easy removal and upgrades. Sorcerer has both both command line and menu driven package mangement programs. A public beta, not backward compatible with previous releases of SGL, was made available April 14, 2002. From LWN Distribution List
|
This distribution was created by the original Sorcerer GNU/Linux author, Kyle Sallee. Sources are downloaded directly from software authors' homepages and mirrors. Then, they are compiled with the architecture and optimizations that the system administrator specifies. Finally, it is installed, tracked, and archived for easy removal and upgrades. Sorcerer has both command line and menu driven package mangement programs. A public beta, not backward compatible with previous releases of SGL, was made available April 14, 2002. From LWN Distribution List
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -13592,7 +13592,7 @@ source route
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
In network network protocols, source routing is the capability whereby the sender can specify the route a packet should take. Analogy: Somebody asks you how to get to the freeway. You can give them two responses: You tell them to drive a little further on, and there will be signs pointing to the freeway. You tell them just to follow the signs. This is normal routing: you simply hand the packet off to the routers, and let them worry about which direction the packet takes. You tell them to drive up 3 blocks, turn left, then go 2 blocks, then turn right, then go one more block and bear left onto the onramp. This is source routing: you tell the packet every hop it should take through the network. Key point: The hacker can give the packets routes that go around firewalls. From Hacking-Lexicon
|
In network protocols, source routing is the capability whereby the sender can specify the route a packet should take. Analogy: Somebody asks you how to get to the freeway. You can give them two responses: You tell them to drive a little further on, and there will be signs pointing to the freeway. You tell them just to follow the signs. This is normal routing: you simply hand the packet off to the routers, and let them worry about which direction the packet takes. You tell them to drive up 3 blocks, turn left, then go 2 blocks, then turn right, then go one more block and bear left onto the onramp. This is source routing: you tell the packet every hop it should take through the network. Key point: The hacker can give the packets routes that go around firewalls. From Hacking-Lexicon
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -13892,7 +13892,7 @@ spam
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Most spam comes through open SMTP relays. Spam is generally sent through the SMTP mail transfer protocol, though spammers are increasingly making use of web-based e-mail. A big source of spam comes from people who spider websites looking for web-pages that contain e-mail addresses. Since a lot of a web-sites will archive mailing lists and USENET groups, posting to a "private" list will often still expose your e-mail address. The SirCam worm of 2001 spidered the HTML files on the local web-browser cache to forward e-mail, creating a hugely effective manner for discovering new e-mail addresses. Spammers will usually spoof their e-mail address -- you can virtually never reply to the "sender" e-mail address. Netiquette: Use Bcc to send to multiple recipients rather than Cc: or To: fields in order to avoid exposing friends e-mail addresses to potential spammers. Firewalls don't block spam. The @Home cable modem ISP now regularly scans its customers for open USENET relays that spammers often hijack in order to forward spam on newsgroups. Some people are so emotionally against spam that they will will completely shun all access from networks known to be sources of spam. Websites will sometimes scan clients with SNMP or NetBIOS in order to discover their login name. Likewise, some websites sift HTTP fields for usernames (though virtually all web-browsers have disabled this feature). A Rumpelstiltskin attack is where a spammer sends e-mail to all possible names (a@example.com, b@example.com, c@example.com, ...) at a domain. This is similar to a brute-force attack. From Hacking-Lexicon
|
Most spam comes through open SMTP relays. Spam is generally sent through the SMTP mail transfer protocol, though spammers are increasingly making use of web-based e-mail. A big source of spam comes from people who spider websites looking for web-pages that contain e-mail addresses. Since a lot of a web-sites will archive mailing lists and USENET groups, posting to a "private" list will often still expose your e-mail address. The SirCam worm of 2001 spidered the HTML files on the local web-browser cache to forward e-mail, creating a hugely effective manner for discovering new e-mail addresses. Spammers will usually spoof their e-mail address -- you can virtually never reply to the "sender" e-mail address. Netiquette: Use Bcc to send to multiple recipients rather than Cc: or To: fields in order to avoid exposing friends e-mail addresses to potential spammers. Firewalls don't block spam. The @Home cable modem ISP now regularly scans its customers for open USENET relays that spammers often hijack in order to forward spam on newsgroups. Some people are so emotionally against spam that they will completely shun all access from networks known to be sources of spam. Websites will sometimes scan clients with SNMP or NetBIOS in order to discover their login name. Likewise, some websites sift HTTP fields for usernames (though virtually all web-browsers have disabled this feature). A Rumpelstiltskin attack is where a spammer sends e-mail to all possible names (a@example.com, b@example.com, c@example.com, ...) at a domain. This is similar to a brute-force attack. From Hacking-Lexicon
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -17060,7 +17060,7 @@ stalin
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
An extremely aggressive Scheme compiler. stalin is an aggressive self-hosting Scheme compiler, designed to generate resource efficient stand-alone executables with very high computational performance. It is a batch mode compiler like gcc, not an interpreter, and is designed to be used only after your code has stabilized. It places a few limitations on the content of the source code. For example, you may not not LOAD or EVAL new expressions or procedure definitions at runtime, but in exchange, it is able to perform various global analyses which may allow it to transparently map Scheme types to C types and to use native C arithmetic operations on a per-expression basis, whenever such operations are proven safe. Further stalin can often reduce or eliminate run-time type checking and dispatching, and omit garbage collection for data of limited scope or accessability, while omitting unreachable data altogether. stalin also has a foreign procedure interface to both Xlib and OpenGL. From Debian 3.0r0 APT
|
An extremely aggressive Scheme compiler. stalin is an aggressive self-hosting Scheme compiler, designed to generate resource efficient stand-alone executables with very high computational performance. It is a batch mode compiler like gcc, not an interpreter, and is designed to be used only after your code has stabilized. It places a few limitations on the content of the source code. For example, you may not LOAD or EVAL new expressions or procedure definitions at runtime, but in exchange, it is able to perform various global analyses which may allow it to transparently map Scheme types to C types and to use native C arithmetic operations on a per-expression basis, whenever such operations are proven safe. Further stalin can often reduce or eliminate run-time type checking and dispatching, and omit garbage collection for data of limited scope or accessability, while omitting unreachable data altogether. stalin also has a foreign procedure interface to both Xlib and OpenGL. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -20108,7 +20108,7 @@ symlink (symbolic link)
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
On UNIX, a symbolic link is where a file in one directory acts as a pointer to a file in another directory. For example, you could create a link so that all accesses to the file /tmp/foo really act upon the file /etc/passwd. This feature can often be exploited. While a non-root user does not have permission to write to administrative files like /etc/passwd, they can certainly create links to them in the /tmp directory or their local directory. SUID can then be exploited whereby they believe they are acting upon a user file, which which are instead acting upon the original administrative file. This is the leading way that local users can escalate their privileges on a system. Example: finger A user could link their .plan file to any other file on the system. A finger daemon running with root privileges would then follow the link to that file and read it upon execution of a finger lookup. From Hacking-Lexicon
|
On UNIX, a symbolic link is where a file in one directory acts as a pointer to a file in another directory. For example, you could create a link so that all accesses to the file /tmp/foo really act upon the file /etc/passwd. This feature can often be exploited. While a non-root user does not have permission to write to administrative files like /etc/passwd, they can certainly create links to them in the /tmp directory or their local directory. SUID can then be exploited whereby they believe they are acting upon a user file, which are instead acting upon the original administrative file. This is the leading way that local users can escalate their privileges on a system. Example: finger A user could link their .plan file to any other file on the system. A finger daemon running with root privileges would then follow the link to that file and read it upon execution of a finger lookup. From Hacking-Lexicon
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -20180,7 +20180,7 @@ sympa
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Modern mailing list manager Sympa is a scalable and highly customizable modern mailing list manager which can cope with big lists (200,000 subscribers). It can can handle a lots of useful features : - Moderation - Digest mode - Authentication (for subscription process) - Archive management - Multi-language support (us, fr, de, as, it, fi and Chinese locales) - Expiration process - Virtual domains (virtual robots) - Accesses to LDAP directories - Using a RDBMS for storing subscriber information (it supports both MySQL and PostgreSQL). - S/MIME encryption and HTTPS authentication Sympa provides a scripting language for extending the behaviour of commands, and a complete (user and admin) Web interface called WWSympa. SYMPA means 'Systhme de Multi-Postage Automatique' (French) or 'Automatic Mailing System' (English). It is written in Perl and uses some modules (mailtools, md5, msgcat, db). WWSympa is provided in a separate package named `wwsympa'. From Debian 3.0r0 APT
|
Modern mailing list manager Sympa is a scalable and highly customizable modern mailing list manager which can cope with big lists (200,000 subscribers). It can handle a lots of useful features : - Moderation - Digest mode - Authentication (for subscription process) - Archive management - Multi-language support (us, fr, de, as, it, fi and Chinese locales) - Expiration process - Virtual domains (virtual robots) - Accesses to LDAP directories - Using a RDBMS for storing subscriber information (it supports both MySQL and PostgreSQL). - S/MIME encryption and HTTPS authentication Sympa provides a scripting language for extending the behaviour of commands, and a complete (user and admin) Web interface called WWSympa. SYMPA means 'Systhme de Multi-Postage Automatique' (French) or 'Automatic Mailing System' (English). It is written in Perl and uses some modules (mailtools, md5, msgcat, db). WWSympa is provided in a separate package named `wwsympa'. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -1508,7 +1508,7 @@ umsdos
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
This is the distribution of the UMSDOS file system utilities. With the kernel configured accordingly these utilities allow the usage of of Unix filesystem feature on top of the MSDOS filesystem. It is even possible to run Linux completely on an MSDOS formatted disk without repartitioning or reformatting. From Debian 3.0r0 APT
|
This is the distribution of the UMSDOS file system utilities. With the kernel configured accordingly these utilities allow the usage of Unix filesystem feature on top of the MSDOS filesystem. It is even possible to run Linux completely on an MSDOS formatted disk without repartitioning or reformatting. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -3512,7 +3512,7 @@ userland
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
n. Anywhere outside the kernel. "That code belongs in userland." This term has been in common use among Linux kernel hackers since at least 1997, and may have have originated in that community (a sighting has been reported from the 1995 archives of a NetBSD mailing list, however). From Jargon Dictionary
|
n. Anywhere outside the kernel. "That code belongs in userland." This term has been in common use among Linux kernel hackers since at least 1997, and may have had originated in that community (a sighting has been reported from the 1995 archives of a NetBSD mailing list, however). From Jargon Dictionary
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -1064,7 +1064,7 @@ vdr-rcu
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Video Disk Recorder for DVB-S cards with RCU control Video Disk Recorder (VDR) is a digital sat-receiver program using Linux and DVB-S technologies. It allows one to record MPEG2 streams, as well as output the stream to TV. It is also possible to watch DVDs with some comfort and hardware acceleration. This package contains the vdr-kbd program which is controlled via the the "Remote Control Unit". There are also vdr-kbd and vdr-lirc packages which contain another VDR versions using PC keyboard or infrared remote control. From Debian 3.0r0 APT
|
Video Disk Recorder for DVB-S cards with RCU control Video Disk Recorder (VDR) is a digital sat-receiver program using Linux and DVB-S technologies. It allows one to record MPEG2 streams, as well as output the stream to TV. It is also possible to watch DVDs with some comfort and hardware acceleration. This package contains the vdr-kbd program which is controlled via the "Remote Control Unit". There are also vdr-kbd and vdr-lirc packages which contain another VDR versions using PC keyboard or infrared remote control. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -1280,7 +1280,7 @@ webcam
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
capture and upload images webcam captures images from a video4linux device like bttv, annotates them and and uploads them to a webserver using ftp in a endless loop. From Debian 3.0r0 APT
|
capture and upload images webcam captures images from a video4linux device like bttv, annotates them and uploads them to a webserver using ftp in a endless loop. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -1328,7 +1328,7 @@ weblint
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
a syntax and minimal style checker for HTML This is perl script which picks fluff off html pages, much in the same way traditional lint picks fluff off C programs. The script is pretty much a a wrapper around the Weblint module. It currently supports HTML 4.0 (and only HTML 4.0). It allows the various syntax and stylistic checks to be enabled or disabled by the user or in a system-wide configuration file. NOTE: This is a beta release of Weblint 2.0 that provides a subset of of the final functionality. There are one or two features from 1.020 that aren't currently available. But this implements just about all the warnings from 1.020 and uses current HTML standards. From Debian 3.0r0 APT
|
a syntax and minimal style checker for HTML This is perl script which picks fluff off html pages, much in the same way traditional lint picks fluff off C programs. The script is pretty much a wrapper around the Weblint module. It currently supports HTML 4.0 (and only HTML 4.0). It allows the various syntax and stylistic checks to be enabled or disabled by the user or in a system-wide configuration file. NOTE: This is a beta release of Weblint 2.0 that provides a subset of the final functionality. There are one or two features from 1.020 that aren't currently available. But this implements just about all the warnings from 1.020 and uses current HTML standards. From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -3512,7 +3512,7 @@ wmtime
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
Displays time and date WMTime displays the time and date and gives you some nice additional features too. It is intended for docking in WindowMaker. WMTime currently provides: * Time and date; * Realtime morphing UI (analog <> digital mode); * Autoscaling and anti aliased hands; * Locale, can display DAY and DATE in various languages; * Can launch 3 user definable commands through ~/.wmtimerc; * Can be run multiple times; * Commandline options for help (-h), version (-v), digital clock mode (-digital) and and display (-d) From Debian 3.0r0 APT
|
Displays time and date WMTime displays the time and date and gives you some nice additional features too. It is intended for docking in WindowMaker. WMTime currently provides: * Time and date; * Realtime morphing UI (analog <> digital mode); * Autoscaling and anti aliased hands; * Locale, can display DAY and DATE in various languages; * Can launch 3 user definable commands through ~/.wmtimerc; * Can be run multiple times; * Commandline options for help (-h), version (-v), digital clock mode (-digital) and display (-d) From Debian 3.0r0 APT
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
@ -4952,7 +4952,7 @@ WYSIWYG
|
||||||
</glossterm>
|
</glossterm>
|
||||||
<glossdef>
|
<glossdef>
|
||||||
<para>
|
<para>
|
||||||
/wiz'ee-wig/ adj. [Traced to Flip Wilson's "Geraldine" character c.1970] Describes a user interface under which "What You See Is What You Get", as opposed to one that uses more-or-less obscure commands that do not result in immediate visual feedback. True WYSIWYG in environments supporting multiple fonts or graphics is a a rarely-attained ideal; there are variants of this term to express real-world manifestations including WYSIAWYG (What You See Is Almost What You Get) and WYSIMOLWYG (What You See Is More or Less What You Get). All these can be mildly derogatory, as they are often used to refer to dumbed-down user-friendly interfaces targeted at non-programmers; a hacker has no fear of obscure commands (compare WYSIAYG). On the other hand, EMACS was one of the very first WYSIWYG editors, replacing (actually, at first overlaying) the extremely obscure, command-based TECO. See also WIMP environment. [Oddly enough, WYSIWYG has already made it into the OED, in lower case yet. --ESR] From Jargon Dictionary
|
/wiz'ee-wig/ adj. [Traced to Flip Wilson's "Geraldine" character c.1970] Describes a user interface under which "What You See Is What You Get", as opposed to one that uses more-or-less obscure commands that do not result in immediate visual feedback. True WYSIWYG in environments supporting multiple fonts or graphics is a rarely-attained ideal; there are variants of this term to express real-world manifestations including WYSIAWYG (What You See Is Almost What You Get) and WYSIMOLWYG (What You See Is More or Less What You Get). All these can be mildly derogatory, as they are often used to refer to dumbed-down user-friendly interfaces targeted at non-programmers; a hacker has no fear of obscure commands (compare WYSIAYG). On the other hand, EMACS was one of the very first WYSIWYG editors, replacing (actually, at first overlaying) the extremely obscure, command-based TECO. See also WIMP environment. [Oddly enough, WYSIWYG has already made it into the OED, in lower case yet. --ESR] From Jargon Dictionary
|
||||||
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
<ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
|
|
|
@ -6689,7 +6689,7 @@ let "b = $a + 1.3" # Error.
|
||||||
echo "b = $b" # b=1</programlisting>
|
echo "b = $b" # b=1</programlisting>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>Use <link linkend="bcref">bc</link> in scripts that that need floating
|
<para>Use <link linkend="bcref">bc</link> in scripts that need floating
|
||||||
point calculations or math library functions.</para></caution>
|
point calculations or math library functions.</para></caution>
|
||||||
|
|
||||||
|
|
||||||
|
@ -8802,7 +8802,7 @@ possibly_hanging_job & {
|
||||||
|
|
||||||
# -------------------------------------------------------------- #
|
# -------------------------------------------------------------- #
|
||||||
|
|
||||||
# However, this may not not work as specified if another process
|
# However, this may not work as specified if another process
|
||||||
#+ begins to run after the "hanging_job" . . .
|
#+ begins to run after the "hanging_job" . . .
|
||||||
# In such a case, the wrong job may be killed.
|
# In such a case, the wrong job may be killed.
|
||||||
# Ariel Meragelman suggests the following fix.
|
# Ariel Meragelman suggests the following fix.
|
||||||
|
@ -26974,7 +26974,7 @@ COMMAND7</programlisting>
|
||||||
then
|
then
|
||||||
echo "Variable is set."
|
echo "Variable is set."
|
||||||
fi # Variable has been set in current script,
|
fi # Variable has been set in current script,
|
||||||
#+ or is an an internal Bash variable,
|
#+ or is an internal Bash variable,
|
||||||
#+ or is present in environment (has been exported).
|
#+ or is present in environment (has been exported).
|
||||||
|
|
||||||
# Could also be written [[ ${variable-x} != x || ${variable-y} != y ]]
|
# Could also be written [[ ${variable-x} != x || ${variable-y} != y ]]
|
||||||
|
@ -33638,7 +33638,7 @@ bad_command arg1 arg2
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Bash now supports the the
|
<para>Bash now supports the
|
||||||
<replaceable>\u</replaceable>
|
<replaceable>\u</replaceable>
|
||||||
and <replaceable>\U</replaceable>
|
and <replaceable>\U</replaceable>
|
||||||
<firstterm>Unicode</firstterm> escape.</para>
|
<firstterm>Unicode</firstterm> escape.</para>
|
||||||
|
|
|
@ -25,7 +25,7 @@
|
||||||
#+ you'll have to do some other choices for readability.
|
#+ you'll have to do some other choices for readability.
|
||||||
#
|
#
|
||||||
# This bashrc file is a bit overcrowded.
|
# This bashrc file is a bit overcrowded.
|
||||||
# Remember, it is just just an example.
|
# Remember, it is just an example.
|
||||||
# Tailor it to your needs.
|
# Tailor it to your needs.
|
||||||
#
|
#
|
||||||
# =============================================================== #
|
# =============================================================== #
|
||||||
|
|
|
@ -244,7 +244,7 @@ cd_getrc ()
|
||||||
cd_flchar=${cd_flchar}-5
|
cd_flchar=${cd_flchar}-5
|
||||||
else
|
else
|
||||||
cd_flchar=${FLCHAR:=75}
|
cd_flchar=${FLCHAR:=75}
|
||||||
# cd_flchar is used for for the @s & @h history
|
# cd_flchar is used for the @s & @h history
|
||||||
cd_lchar=${LCHAR:=35}
|
cd_lchar=${LCHAR:=35}
|
||||||
cd_rchar=${RCHAR:=35}
|
cd_rchar=${RCHAR:=35}
|
||||||
fi
|
fi
|
||||||
|
@ -466,7 +466,7 @@ export CDFile=${CDFILE:=cdfile} # for the -u and -f commands #
|
||||||
#
|
#
|
||||||
typeset -i cd_lchar cd_rchar cd_flchar
|
typeset -i cd_lchar cd_rchar cd_flchar
|
||||||
# This is the number of chars to allow for the #
|
# This is the number of chars to allow for the #
|
||||||
cd_flchar=${FLCHAR:=75} #+ cd_flchar is used for for the @s & @h history#
|
cd_flchar=${FLCHAR:=75} #+ cd_flchar is used for the @s & @h history#
|
||||||
|
|
||||||
typeset -ax CD CDS
|
typeset -ax CD CDS
|
||||||
#
|
#
|
||||||
|
|
|
@ -20,7 +20,7 @@ echo
|
||||||
#+ a block of working code for debugging purposes.
|
#+ a block of working code for debugging purposes.
|
||||||
# This saves having to put a "#" at the beginning of each line,
|
# This saves having to put a "#" at the beginning of each line,
|
||||||
#+ then having to go back and delete each "#" later.
|
#+ then having to go back and delete each "#" later.
|
||||||
# Note that the use of of colon, above, is optional.
|
# Note that the use of colon, above, is optional.
|
||||||
|
|
||||||
echo "Just before commented-out code block."
|
echo "Just before commented-out code block."
|
||||||
# The lines of code between the double-dashed lines will not execute.
|
# The lines of code between the double-dashed lines will not execute.
|
||||||
|
|
|
@ -24,7 +24,7 @@ updatedb /usr & # Must be run as root.
|
||||||
|
|
||||||
wait
|
wait
|
||||||
# Don't run the rest of the script until 'updatedb' finished.
|
# Don't run the rest of the script until 'updatedb' finished.
|
||||||
# You want the the database updated before looking up the file name.
|
# You want the database updated before looking up the file name.
|
||||||
|
|
||||||
locate $1
|
locate $1
|
||||||
|
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
#!/bin/bash
|
#!/bin/bash
|
||||||
|
|
||||||
# 'echo' is fine for printing single line messages,
|
# 'echo' is fine for printing single line messages,
|
||||||
#+ but somewhat problematic for for message blocks.
|
#+ but somewhat problematic for message blocks.
|
||||||
# A 'cat' here document overcomes this limitation.
|
# A 'cat' here document overcomes this limitation.
|
||||||
|
|
||||||
cat <<End-of-message
|
cat <<End-of-message
|
||||||
|
|
|
@ -368,7 +368,7 @@ exit 0 # CEOF:EOF
|
||||||
|
|
||||||
|
|
||||||
# The grid in this script has a "boundary problem."
|
# The grid in this script has a "boundary problem."
|
||||||
# The the top, bottom, and sides border on a void of dead cells.
|
# The top, bottom, and sides border on a void of dead cells.
|
||||||
# Exercise: Change the script to have the grid wrap around,
|
# Exercise: Change the script to have the grid wrap around,
|
||||||
# + so that the left and right sides will "touch,"
|
# + so that the left and right sides will "touch,"
|
||||||
# + as will the top and bottom.
|
# + as will the top and bottom.
|
||||||
|
|
|
@ -26,5 +26,5 @@ exit $?
|
||||||
# bozo$ ./rand-string.sh my-password
|
# bozo$ ./rand-string.sh my-password
|
||||||
# 1bdd88c4
|
# 1bdd88c4
|
||||||
|
|
||||||
# No, this is is not recommended
|
# No, this is not recommended
|
||||||
#+ as a method of generating hack-proof passwords.
|
#+ as a method of generating hack-proof passwords.
|
||||||
|
|
|
@ -150,7 +150,7 @@ maximum=${max}
|
||||||
|
|
||||||
|
|
||||||
# We need to generate only positive array subscripts,
|
# We need to generate only positive array subscripts,
|
||||||
#+ so we need a displacement that that will guarantee
|
#+ so we need a displacement that will guarantee
|
||||||
#+ positive results.
|
#+ positive results.
|
||||||
|
|
||||||
disp=$((0-minimum))
|
disp=$((0-minimum))
|
||||||
|
|
|
@ -1787,7 +1787,7 @@ else
|
||||||
local routing table.
|
local routing table.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
If the the machine has several IP addresses on one Ethernet interface,
|
If the machine has several IP addresses on one Ethernet interface,
|
||||||
there will be a route to each locally hosted IP in the local routing
|
there will be a route to each locally hosted IP in the local routing
|
||||||
table. This is a normal
|
table. This is a normal
|
||||||
<link linkend="list-basic-ifconfig-side-effects-up">side effect</link>
|
<link linkend="list-basic-ifconfig-side-effects-up">side effect</link>
|
||||||
|
|
|
@ -1589,7 +1589,7 @@ local 127.0.0.1 from 127.0.0.1 dev lo
|
||||||
<command>ip route</command> to populate routing tables.
|
<command>ip route</command> to populate routing tables.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
A simple rule selects a packet on the the packet's characteristics.
|
A simple rule selects a packet on the packet's characteristics.
|
||||||
Some characteristics available as selection criteria are the
|
Some characteristics available as selection criteria are the
|
||||||
source address, the destination, the type of service (ToS), the
|
source address, the destination, the type of service (ToS), the
|
||||||
interface on which the packet arrived, and an fwmark.
|
interface on which the packet arrived, and an fwmark.
|
||||||
|
|
|
@ -9,7 +9,7 @@
|
||||||
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
||||||
and therefore generates MULTIPLE HTML FILES as output. -->
|
and therefore generates MULTIPLE HTML FILES as output. -->
|
||||||
|
|
||||||
<!-- Note the the *order* of the import statements below is important and
|
<!-- Note that the *order* of the import statements below is important and
|
||||||
should not be changed. -->
|
should not be changed. -->
|
||||||
|
|
||||||
<!-- Change this to the path to where you have installed Norman
|
<!-- Change this to the path to where you have installed Norman
|
||||||
|
|
|
@ -9,7 +9,7 @@
|
||||||
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
||||||
and therefore generates MULTIPLE HTML FILES as output. -->
|
and therefore generates MULTIPLE HTML FILES as output. -->
|
||||||
|
|
||||||
<!-- Note the the *order* of the import statements below is important and
|
<!-- Note that the *order* of the import statements below is important and
|
||||||
should not be changed. -->
|
should not be changed. -->
|
||||||
|
|
||||||
<!-- Change this to the path to where you have installed Norman
|
<!-- Change this to the path to where you have installed Norman
|
||||||
|
|
|
@ -9,7 +9,7 @@
|
||||||
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
||||||
and therefore generates a SINGLE HTML FILE as output. -->
|
and therefore generates a SINGLE HTML FILE as output. -->
|
||||||
|
|
||||||
<!-- Note the the *order* of the import statements below is important and
|
<!-- Note that the *order* of the import statements below is important and
|
||||||
should not be changed. -->
|
should not be changed. -->
|
||||||
|
|
||||||
<!-- Change this to the path to where you have installed Norman
|
<!-- Change this to the path to where you have installed Norman
|
||||||
|
|
|
@ -9,7 +9,7 @@
|
||||||
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
||||||
and therefore generates MULTIPLE HTML FILES as output. -->
|
and therefore generates MULTIPLE HTML FILES as output. -->
|
||||||
|
|
||||||
<!-- Note the the *order* of the import statements below is important and
|
<!-- Note that the *order* of the import statements below is important and
|
||||||
should not be changed. -->
|
should not be changed. -->
|
||||||
|
|
||||||
<!-- Change this to the path to where you have installed Norman
|
<!-- Change this to the path to where you have installed Norman
|
||||||
|
|
|
@ -9,7 +9,7 @@
|
||||||
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
|
||||||
and therefore generates a SINGLE HTML FILE as output. -->
|
and therefore generates a SINGLE HTML FILE as output. -->
|
||||||
|
|
||||||
<!-- Note the the *order* of the import statements below is important and
|
<!-- Note that the *order* of the import statements below is important and
|
||||||
should not be changed. -->
|
should not be changed. -->
|
||||||
|
|
||||||
<!-- Change this to the path to where you have installed Norman
|
<!-- Change this to the path to where you have installed Norman
|
||||||
|
|
|
@ -125,7 +125,7 @@ MODULE_LICENSE("GPL");
|
||||||
will cause loading the module to fail, since insmod won't find those functions in the kernel.</para></listitem>
|
will cause loading the module to fail, since insmod won't find those functions in the kernel.</para></listitem>
|
||||||
|
|
||||||
<listitem><para><option>-W -Wall</option>:
|
<listitem><para><option>-W -Wall</option>:
|
||||||
A programming mistake can take take your system down. You should always turn on compiler warnings, and this applies to
|
A programming mistake can take your system down. You should always turn on compiler warnings, and this applies to
|
||||||
all your compiling endeavors, not just module compilation.</para></listitem>
|
all your compiling endeavors, not just module compilation.</para></listitem>
|
||||||
|
|
||||||
<listitem><para><option>-isystem /lib/modules/`uname -r`/build/include</option>:
|
<listitem><para><option>-isystem /lib/modules/`uname -r`/build/include</option>:
|
||||||
|
|
|
@ -138,7 +138,7 @@
|
||||||
number will be. There are a couple of ways to do this. First, the driver itself can print the newly assigned number and
|
number will be. There are a couple of ways to do this. First, the driver itself can print the newly assigned number and
|
||||||
we can make the device file by hand. Second, the newly registered device will have an entry in
|
we can make the device file by hand. Second, the newly registered device will have an entry in
|
||||||
<filename>/proc/devices</filename>, and we can either make the device file by hand or write a shell script to read the
|
<filename>/proc/devices</filename>, and we can either make the device file by hand or write a shell script to read the
|
||||||
file in and make the device file. The third method is we can have our driver make the the device file using the
|
file in and make the device file. The third method is we can have our driver make the device file using the
|
||||||
<function>mknod</function> system call after a successful registration and rm during the call to
|
<function>mknod</function> system call after a successful registration and rm during the call to
|
||||||
<function>cleanup_module</function>.</para>
|
<function>cleanup_module</function>.</para>
|
||||||
|
|
||||||
|
@ -303,7 +303,7 @@ static int device_release(struct inode *inode, struct file *file)
|
||||||
Device_Open --; /* We're now ready for our next caller */
|
Device_Open --; /* We're now ready for our next caller */
|
||||||
|
|
||||||
/* Decrement the usage count, or else once you opened the file, you'll
|
/* Decrement the usage count, or else once you opened the file, you'll
|
||||||
never get get rid of the module. */
|
never get rid of the module. */
|
||||||
MOD_DEC_USE_COUNT;
|
MOD_DEC_USE_COUNT;
|
||||||
|
|
||||||
return 0;
|
return 0;
|
||||||
|
|
|
@ -36,7 +36,7 @@
|
||||||
|
|
||||||
<para>When a process is done with the file, it closes it, and <function>module_close</function> is called. That function
|
<para>When a process is done with the file, it closes it, and <function>module_close</function> is called. That function
|
||||||
wakes up all the processes in the queue (there's no mechanism to only wake up one of them). It then returns and the
|
wakes up all the processes in the queue (there's no mechanism to only wake up one of them). It then returns and the
|
||||||
process which just closed the file can continue to run. In time, the scheduler decides that that process has had enough
|
process which just closed the file can continue to run. In time, the scheduler decides that the process has had enough
|
||||||
and gives control of the CPU to another process. Eventually, one of the processes which was in the queue will be given
|
and gives control of the CPU to another process. Eventually, one of the processes which was in the queue will be given
|
||||||
control of the CPU by the scheduler. It starts at the point right after the call to
|
control of the CPU by the scheduler. It starts at the point right after the call to
|
||||||
<function>module_interruptible_sleep_on</function><footnote><para>This means that the process is still in kernel mode --
|
<function>module_interruptible_sleep_on</function><footnote><para>This means that the process is still in kernel mode --
|
||||||
|
|
|
@ -150,7 +150,7 @@ int register_chrdev(unsigned int major, const char *name, struct file_operations
|
||||||
number will be. There are a couple of ways to do this. First, the driver itself can print the newly assigned number and
|
number will be. There are a couple of ways to do this. First, the driver itself can print the newly assigned number and
|
||||||
we can make the device file by hand. Second, the newly registered device will have an entry in
|
we can make the device file by hand. Second, the newly registered device will have an entry in
|
||||||
<filename>/proc/devices</filename>, and we can either make the device file by hand or write a shell script to read the
|
<filename>/proc/devices</filename>, and we can either make the device file by hand or write a shell script to read the
|
||||||
file in and make the device file. The third method is we can have our driver make the the device file using the
|
file in and make the device file. The third method is we can have our driver make the device file using the
|
||||||
<function>mknod</function> system call after a successful registration and rm during the call to
|
<function>mknod</function> system call after a successful registration and rm during the call to
|
||||||
<function>cleanup_module</function>.</para>
|
<function>cleanup_module</function>.</para>
|
||||||
|
|
||||||
|
|
|
@ -32,7 +32,7 @@
|
||||||
|
|
||||||
<para>When a process is done with the file, it closes it, and <function>module_close</function> is called. That function
|
<para>When a process is done with the file, it closes it, and <function>module_close</function> is called. That function
|
||||||
wakes up all the processes in the queue (there's no mechanism to only wake up one of them). It then returns and the
|
wakes up all the processes in the queue (there's no mechanism to only wake up one of them). It then returns and the
|
||||||
process which just closed the file can continue to run. In time, the scheduler decides that that process has had enough
|
process which just closed the file can continue to run. In time, the scheduler decides that the process has had enough
|
||||||
and gives control of the CPU to another process. Eventually, one of the processes which was in the queue will be given
|
and gives control of the CPU to another process. Eventually, one of the processes which was in the queue will be given
|
||||||
control of the CPU by the scheduler. It starts at the point right after the call to
|
control of the CPU by the scheduler. It starts at the point right after the call to
|
||||||
<function>module_interruptible_sleep_on</function><footnote><para>This means that the process is still in kernel mode --
|
<function>module_interruptible_sleep_on</function><footnote><para>This means that the process is still in kernel mode --
|
||||||
|
|
|
@ -106,7 +106,7 @@ static int device_release(struct inode *inode, struct file *file)
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Decrement the usage count, or else once you opened the file, you'll
|
* Decrement the usage count, or else once you opened the file, you'll
|
||||||
* never get get rid of the module.
|
* never get rid of the module.
|
||||||
*/
|
*/
|
||||||
module_put(THIS_MODULE);
|
module_put(THIS_MODULE);
|
||||||
|
|
||||||
|
|
|
@ -1914,7 +1914,7 @@ further firewall processing occurs. The datagram is accepted.
|
||||||
<para>
|
<para>
|
||||||
Finally, let's look at what happens when we reach the end of a
|
Finally, let's look at what happens when we reach the end of a
|
||||||
user-defined chain. To see this, we'll map the flow for a TCP datagram
|
user-defined chain. To see this, we'll map the flow for a TCP datagram
|
||||||
destined for a port other than than the two we are handling
|
destined for a port other than the two we are handling
|
||||||
specifically, as shown in <xref linkend="X-087-2-firewall.ipchains.tcp.other">.
|
specifically, as shown in <xref linkend="X-087-2-firewall.ipchains.tcp.other">.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
@ -3114,7 +3114,7 @@ accepted
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Note the arguments had to be supplied and the way they've been used to
|
Note the arguments had to be supplied and the way they've been used to
|
||||||
describe a datagram. The output of the command indicates that that the
|
describe a datagram. The output of the command indicates that the
|
||||||
datagram was accepted for forwarding, which is what we hoped for.
|
datagram was accepted for forwarding, which is what we hoped for.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
|
|
@ -496,7 +496,7 @@ articles. If we post 5 articles, they will be numbered 1 through
|
||||||
numbered article, and <replaceable>lowmark</replaceable> will equal 1,
|
numbered article, and <replaceable>lowmark</replaceable> will equal 1,
|
||||||
the lowest active article. If article 5 is cancelled there will be no
|
the lowest active article. If article 5 is cancelled there will be no
|
||||||
change; <replaceable>himark</replaceable> will remain at 5 to ensure
|
change; <replaceable>himark</replaceable> will remain at 5 to ensure
|
||||||
that that article number is not reallocated and
|
that the article number is not reallocated and
|
||||||
<replaceable>lowmark</replaceable> will remain at 1, the lowest active
|
<replaceable>lowmark</replaceable> will remain at 1, the lowest active
|
||||||
article. If we now cancel article 1, <replaceable>himark</replaceable>
|
article. If we now cancel article 1, <replaceable>himark</replaceable>
|
||||||
will remain unchanged, but <replaceable>lowmark</replaceable> will now
|
will remain unchanged, but <replaceable>lowmark</replaceable> will now
|
||||||
|
|
|
@ -73,7 +73,7 @@ Swap: 1044216k av, 161672k used, 882544k free 199388k cached
|
||||||
by CPU utilization.</para>
|
by CPU utilization.</para>
|
||||||
|
|
||||||
<para>You can modify the output of <command>top</command> while
|
<para>You can modify the output of <command>top</command> while
|
||||||
is is running. If you hit an <option>i</option>, top will no longer
|
it is running. If you hit an <option>i</option>, top will no longer
|
||||||
display idle processes. Hit <option>i</option> again to see them
|
display idle processes. Hit <option>i</option> again to see them
|
||||||
again. Hitting <option>M</option> will sort by memory usage,
|
again. Hitting <option>M</option> will sort by memory usage,
|
||||||
<option>S</option> will sort by how long they processes have been
|
<option>S</option> will sort by how long they processes have been
|
||||||
|
|
|
@ -495,7 +495,7 @@ tapes</entry></row>
|
||||||
<para> Backups take a lot of space, which can cost quite
|
<para> Backups take a lot of space, which can cost quite
|
||||||
a lot of money. To reduce the space needed, the backups
|
a lot of money. To reduce the space needed, the backups
|
||||||
can be compressed. There are several ways of doing this.
|
can be compressed. There are several ways of doing this.
|
||||||
Some programs have support for for compression built in; for
|
Some programs have support for compression built in; for
|
||||||
example, the <option>--gzip</option> (<option>-z</option>)
|
example, the <option>--gzip</option> (<option>-z</option>)
|
||||||
option for GNU <command>tar</command> pipes the whole backup
|
option for GNU <command>tar</command> pipes the whole backup
|
||||||
through the <command>gzip</command> compression program, before
|
through the <command>gzip</command> compression program, before
|
||||||
|
|
|
@ -176,7 +176,7 @@
|
||||||
|
|
||||||
<para>Beware of the <command>time</command> command. This is not
|
<para>Beware of the <command>time</command> command. This is not
|
||||||
used to get the system time. Instead it's used to time how long
|
used to get the system time. Instead it's used to time how long
|
||||||
something takes. Refer the the time man page.</para>
|
something takes. Refer to the time man page.</para>
|
||||||
|
|
||||||
<para> <command>date</command> only shows or sets the software
|
<para> <command>date</command> only shows or sets the software
|
||||||
clock. The <command>clock</command> commands synchronizes
|
clock. The <command>clock</command> commands synchronizes
|
||||||
|
@ -351,7 +351,7 @@ restrict 127.0.0.1
|
||||||
<para>Many people get the idea that instead of running the NTP
|
<para>Many people get the idea that instead of running the NTP
|
||||||
daemon, they should just setup a <command>cron</command> job
|
daemon, they should just setup a <command>cron</command> job
|
||||||
job to periodically run the <command>ntpdate</command> command.
|
job to periodically run the <command>ntpdate</command> command.
|
||||||
There are 2 main disadvantages of using using this method.</para>
|
There are 2 main disadvantages of using this method.</para>
|
||||||
|
|
||||||
<para>The first is that <command>ntpdate</command> does a "brute force"
|
<para>The first is that <command>ntpdate</command> does a "brute force"
|
||||||
method of changing the time. So if your computer's time is off my 5
|
method of changing the time. So if your computer's time is off my 5
|
||||||
|
|
|
@ -33409,7 +33409,7 @@ BRU Homepage: <link linkend="prtinxfp26">http://www.bru.com/</link>
|
||||||
</partintro>
|
</partintro>
|
||||||
<appendix label="A"><?dbhtml filename="appendixa.html"?>
|
<appendix label="A"><?dbhtml filename="appendixa.html"?>
|
||||||
<title>Resources</title>
|
<title>Resources</title>
|
||||||
<para><emphasis>Surprised!</emphasis>, Don't be, what we have attempted is to duplicate a server-side redirect here. The idea is, supposingly you are viewing this book online from a website, this will give give enough time to
|
<para><emphasis>Surprised!</emphasis>, Don't be, what we have attempted is to duplicate a server-side redirect here. The idea is, supposingly you are viewing this book online from a website, this will give enough time to
|
||||||
think about leaving this environement which is what would have happened if you had clicked on any link, or save this page and go back to the page you were browsing. this will leave with the option of checking out the
|
think about leaving this environement which is what would have happened if you had clicked on any link, or save this page and go back to the page you were browsing. this will leave with the option of checking out the
|
||||||
later at your convenience. To us when and if, <wordasword>a misnomer</wordasword> the link needs to be updated or changed or edited etc. we have to tinker with this page rather than hunt and peck at the links by searching them from different pages
|
later at your convenience. To us when and if, <wordasword>a misnomer</wordasword> the link needs to be updated or changed or edited etc. we have to tinker with this page rather than hunt and peck at the links by searching them from different pages
|
||||||
</para>
|
</para>
|
||||||
|
|
|
@ -3653,7 +3653,7 @@ determines why it was awakened, and how it should
|
||||||
respond. The following cases are handled:
|
respond. The following cases are handled:
|
||||||
|
|
||||||
<itemize>
|
<itemize>
|
||||||
<item> If the the semaphore set has been removed, then
|
<item> If the semaphore set has been removed, then
|
||||||
the system call fails with EIDRM.
|
the system call fails with EIDRM.
|
||||||
|
|
||||||
<item> If the <tt>status</tt> element of the
|
<item> If the <tt>status</tt> element of the
|
||||||
|
@ -4208,7 +4208,7 @@ the temporary buffer are copied out to user space by
|
||||||
The user data is copied in via
|
The user data is copied in via
|
||||||
<ref id="copy_msqid_to_user" name="copy_msqid_to_user()">. The global
|
<ref id="copy_msqid_to_user" name="copy_msqid_to_user()">. The global
|
||||||
message queue semaphore and spinlock are obtained and released
|
message queue semaphore and spinlock are obtained and released
|
||||||
at the end. After the the message queue ID and the current
|
at the end. After the message queue ID and the current
|
||||||
process access permissions are validated, the message queue
|
process access permissions are validated, the message queue
|
||||||
information is updated with the user provided data. Later,
|
information is updated with the user provided data. Later,
|
||||||
<ref id="expunge_all" name="expunge_all()"> and
|
<ref id="expunge_all" name="expunge_all()"> and
|
||||||
|
@ -4754,7 +4754,7 @@ flag equals IPC_64, then copy_to_user() is invoked to copy from
|
||||||
the kernel buffer to the user buffer directly. Otherwise a
|
the kernel buffer to the user buffer directly. Otherwise a
|
||||||
temporary buffer of type struct msqid_ds is initialized, and the
|
temporary buffer of type struct msqid_ds is initialized, and the
|
||||||
kernel data is translated to this temporary buffer. Later
|
kernel data is translated to this temporary buffer. Later
|
||||||
copy_to_user() is called to copy the contents of the the temporary
|
copy_to_user() is called to copy the contents of the temporary
|
||||||
buffer to the user buffer.
|
buffer to the user buffer.
|
||||||
</sect3>
|
</sect3>
|
||||||
|
|
||||||
|
@ -5163,7 +5163,7 @@ spinlock for the given IPC type locked.
|
||||||
</sect3>
|
</sect3>
|
||||||
|
|
||||||
<sect3>ipc_rmid()<label id="func_ipc_rmid"><p>
|
<sect3>ipc_rmid()<label id="func_ipc_rmid"><p>
|
||||||
ipc_rmid() removes the IPC descriptor from the the global
|
ipc_rmid() removes the IPC descriptor from the global
|
||||||
descriptor array of the IPC type, updates the count of IDs which
|
descriptor array of the IPC type, updates the count of IDs which
|
||||||
are in use, and adjusts the maximum ID in the corresponding
|
are in use, and adjusts the maximum ID in the corresponding
|
||||||
descriptor array if necessary. A pointer to the IPC
|
descriptor array if necessary. A pointer to the IPC
|
||||||
|
|
|
@ -1014,7 +1014,7 @@
|
||||||
|
|
||||||
<step performance="required">
|
<step performance="required">
|
||||||
<para>
|
<para>
|
||||||
Download the latest source from from <ulink
|
Download the latest source from <ulink
|
||||||
url="http://www.open1x.org/">http://www.open1x.org/</ulink>
|
url="http://www.open1x.org/">http://www.open1x.org/</ulink>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
|
|
@ -328,7 +328,7 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Mark all packets that are going to a multi-player game server as 0x02. This will give gamers low latency but
|
<para>Mark all packets that are going to a multi-player game server as 0x02. This will give gamers low latency but
|
||||||
will keep them from swamping out the the system applications that require low latency.</para>
|
will keep them from swamping out the system applications that require low latency.</para>
|
||||||
<para>Mark any "small" packets as 0x02. Outbound ACK packets from inbound downloads should be sent promptly
|
<para>Mark any "small" packets as 0x02. Outbound ACK packets from inbound downloads should be sent promptly
|
||||||
to assure efficient downloads. This is possible using the iptables length module.</para>
|
to assure efficient downloads. This is possible using the iptables length module.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
|
@ -4629,7 +4629,7 @@ appropriate rules to the <Literal>/etc/ax25/ax25d.conf</Literal>
|
||||||
file. In my configuration I wanted users to have a choice of either
|
file. In my configuration I wanted users to have a choice of either
|
||||||
connecting to the <Emphasis>node</Emphasis> or connecting to other
|
connecting to the <Emphasis>node</Emphasis> or connecting to other
|
||||||
services. <Emphasis>ax25d</Emphasis> allows you to do this by cleverly
|
services. <Emphasis>ax25d</Emphasis> allows you to do this by cleverly
|
||||||
creating creating port aliases. For example, given the
|
creating port aliases. For example, given the
|
||||||
<Emphasis>ax25d</Emphasis> configuration presented above, I want to
|
<Emphasis>ax25d</Emphasis> configuration presented above, I want to
|
||||||
configure <Emphasis>node</Emphasis> so that all users who connect to
|
configure <Emphasis>node</Emphasis> so that all users who connect to
|
||||||
<Literal>VK2KTJ-1</Literal> are given the node. To do this I add the
|
<Literal>VK2KTJ-1</Literal> are given the node. To do this I add the
|
||||||
|
@ -5213,7 +5213,7 @@ I don't think much explanation will be necessary.
|
||||||
<ListItem>
|
<ListItem>
|
||||||
<Para>
|
<Para>
|
||||||
contains the list of Address Resolution Protocol
|
contains the list of Address Resolution Protocol
|
||||||
mappings of IP addresses to MAC layer protocol addresses. These can can AX.25,
|
mappings of IP addresses to MAC layer protocol addresses. These can be AX.25,
|
||||||
ethernet or some other MAC layer protocol.
|
ethernet or some other MAC layer protocol.
|
||||||
</Para>
|
</Para>
|
||||||
</ListItem>
|
</ListItem>
|
||||||
|
@ -5921,7 +5921,7 @@ call axip vk5xxx
|
||||||
The "<Literal>route</Literal>" command is where you specify where you want your AX.25
|
The "<Literal>route</Literal>" command is where you specify where you want your AX.25
|
||||||
packets encapsulated and sent to. When the <Emphasis>ax25ipd</Emphasis> daemon receives
|
packets encapsulated and sent to. When the <Emphasis>ax25ipd</Emphasis> daemon receives
|
||||||
a packet from its interface, it compares the destination callsign with each
|
a packet from its interface, it compares the destination callsign with each
|
||||||
of the callsigns in its routing table. If if finds a match then the ax.25
|
of the callsigns in its routing table. If it finds a match then the ax.25
|
||||||
packet is encapsulated in an IP datagram and then transmitted to the host
|
packet is encapsulated in an IP datagram and then transmitted to the host
|
||||||
at the specified IP address.
|
at the specified IP address.
|
||||||
</Para>
|
</Para>
|
||||||
|
@ -6322,7 +6322,7 @@ This section summarizes all of the commands that are specific to AX.25.
|
||||||
<row>
|
<row>
|
||||||
<entry>ax25mond</entry>
|
<entry>ax25mond</entry>
|
||||||
<entry>ax25-apps</entry>
|
<entry>ax25-apps</entry>
|
||||||
<entry>Dump the AX.25 network traffic and and provide sockets where the received data will be retransmitted</entry>
|
<entry>Dump the AX.25 network traffic and provide sockets where the received data will be retransmitted</entry>
|
||||||
</row>
|
</row>
|
||||||
|
|
||||||
<row>
|
<row>
|
||||||
|
|
|
@ -1811,7 +1811,7 @@ only reschedule, delay or drop it.
|
||||||
<Para>
|
<Para>
|
||||||
These can be used to shape traffic for an entire interface, without any
|
These can be used to shape traffic for an entire interface, without any
|
||||||
subdivisions. It is vital that you understand this part of queueing before
|
subdivisions. It is vital that you understand this part of queueing before
|
||||||
we go on the the classful qdisc-containing-qdiscs!
|
we go onto the classful qdisc-containing-qdiscs!
|
||||||
</Para>
|
</Para>
|
||||||
|
|
||||||
<Para>
|
<Para>
|
||||||
|
@ -2049,7 +2049,7 @@ and passes the queue without delay.
|
||||||
The data arrives in TBF at a rate that's <Emphasis>smaller</Emphasis> than the
|
The data arrives in TBF at a rate that's <Emphasis>smaller</Emphasis> than the
|
||||||
token rate. Only a part of the tokens are deleted at output of each data packet
|
token rate. Only a part of the tokens are deleted at output of each data packet
|
||||||
that's sent out the queue, so the tokens accumulate, up to the bucket size.
|
that's sent out the queue, so the tokens accumulate, up to the bucket size.
|
||||||
The unused tokens can then be used to send data a a speed that's exceeding the
|
The unused tokens can then be used to send data at a speed that's exceeding the
|
||||||
standard token rate, in case short data bursts occur.
|
standard token rate, in case short data bursts occur.
|
||||||
|
|
||||||
</Para>
|
</Para>
|
||||||
|
@ -4116,7 +4116,7 @@ need to be sent from A to B - eth1 might get 1, 3 and 5. eth2 would then do
|
||||||
3, 4, 5, 6. But the possibility is very real that the kernel gets it like
|
3, 4, 5, 6. But the possibility is very real that the kernel gets it like
|
||||||
this: 2, 1, 4, 3, 6, 5. The problem is that this confuses TCP/IP. While not
|
this: 2, 1, 4, 3, 6, 5. The problem is that this confuses TCP/IP. While not
|
||||||
a problem for links carrying many different TCP/IP sessions, you won't be
|
a problem for links carrying many different TCP/IP sessions, you won't be
|
||||||
able to to a bundle multiple links and get to ftp a single file lots faster,
|
able to bundle multiple links and get to ftp a single file lots faster,
|
||||||
except when your receiving or sending OS is Linux, which is not easily
|
except when your receiving or sending OS is Linux, which is not easily
|
||||||
shaken by some simple reordering.
|
shaken by some simple reordering.
|
||||||
</Para>
|
</Para>
|
||||||
|
|
|
@ -1281,7 +1281,7 @@ RoamingAlias /roaming /usr/local/apache/roaming
|
||||||
<title>Compressed delivery</title>
|
<title>Compressed delivery</title>
|
||||||
<para>
|
<para>
|
||||||
There are basically two modules available for output compression: mod_gzip and mod_gunzip. They are using different approaches
|
There are basically two modules available for output compression: mod_gzip and mod_gunzip. They are using different approaches
|
||||||
to reach the the goal of bandwidth reduction.
|
to reach the same goal of bandwidth reduction.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
|
|
@ -981,7 +981,7 @@ One way to secure the decrypted Private Key is to make readable only by the root
|
||||||
|
|
||||||
<sect2><title>SSL Performance Tuning</title>
|
<sect2><title>SSL Performance Tuning</title>
|
||||||
<sect3><title>Inter Process SSL Session Cache</title>
|
<sect3><title>Inter Process SSL Session Cache</title>
|
||||||
<para>Apache uses a multi-process model, in which all the request are NOT handled by the same process. This causes the SSL Session Information to be lost when a Client makes multiple requests. Multiple SSL HandShakes causes lot of overhead on the webserver and the client. To avoid this, SSL Session Information must be stored in a inter-process Session Cache, allowing all the processes to have access to to handshake information. SSLSessionCache Directive the in <filename>/usr/local/apache2/conf/ssl.conf</filename> file can be used to specify the location of the SSL Session Cache:</para>
|
<para>Apache uses a multi-process model, in which all the request are NOT handled by the same process. This causes the SSL Session Information to be lost when a Client makes multiple requests. Multiple SSL HandShakes causes lot of overhead on the webserver and the client. To avoid this, SSL Session Information must be stored in a inter-process Session Cache, allowing all the processes to have access to the handshake information. SSLSessionCache Directive the in <filename>/usr/local/apache2/conf/ssl.conf</filename> file can be used to specify the location of the SSL Session Cache:</para>
|
||||||
<screen>
|
<screen>
|
||||||
SSLSessionCache shmht:logs/ssl_scache(512000)
|
SSLSessionCache shmht:logs/ssl_scache(512000)
|
||||||
#SSLSessionCache shmcb:logs/ssl_scache(512000)
|
#SSLSessionCache shmcb:logs/ssl_scache(512000)
|
||||||
|
|
|
@ -1455,7 +1455,7 @@ As an interesting historic remark, on
|
||||||
|
|
||||||
"There's no reason that assemblers have to have awful syntax. About
|
"There's no reason that assemblers have to have awful syntax. About
|
||||||
30 years ago I used Niklaus Wirth's PL360, which was basically a S/360
|
30 years ago I used Niklaus Wirth's PL360, which was basically a S/360
|
||||||
assembler with Algol syntax and a a little syntactic sugar like while
|
assembler with Algol syntax and a little syntactic sugar like while
|
||||||
loops that turned into the obvious branches. It really was an
|
loops that turned into the obvious branches. It really was an
|
||||||
assembler, e.g., you had to write out your expressions with explicit
|
assembler, e.g., you had to write out your expressions with explicit
|
||||||
assignments of values to registers, but it was nice. Wirth used it to
|
assignments of values to registers, but it was nice. Wirth used it to
|
||||||
|
@ -3293,7 +3293,7 @@ Rewrite of sgml source.
|
||||||
<authorinitials>konst</authorinitials>
|
<authorinitials>konst</authorinitials>
|
||||||
<revremark>
|
<revremark>
|
||||||
Discussion about libc or not libc continues.
|
Discussion about libc or not libc continues.
|
||||||
New web pointers and and overall updates.
|
New web pointers and overall updates.
|
||||||
</revremark>
|
</revremark>
|
||||||
</revision>
|
</revision>
|
||||||
|
|
||||||
|
|
|
@ -1229,7 +1229,7 @@ root@mbb-1:~ # ifconfig eth<userinput>n</userinput> promisc up
|
||||||
|
|
||||||
<note>
|
<note>
|
||||||
<para>To be able to see nicely formatted stp packages in your
|
<para>To be able to see nicely formatted stp packages in your
|
||||||
network take a look at at the bridge homepage for the patches
|
network take a look at the bridge homepage for the patches
|
||||||
to tcpdump.
|
to tcpdump.
|
||||||
</para>
|
</para>
|
||||||
</note>
|
</note>
|
||||||
|
|
|
@ -455,7 +455,7 @@ source and a patch must be fetched and applied to your source, found at the
|
||||||
<para>
|
<para>
|
||||||
If you are running a 2.4 series kernel, <command>btaudio</command>
|
If you are running a 2.4 series kernel, <command>btaudio</command>
|
||||||
in the OSS "Sound" category is optional if you want to use external speakers
|
in the OSS "Sound" category is optional if you want to use external speakers
|
||||||
attached to the the card's audio out jack, and either (or both) OSS or
|
attached to the card's audio out jack, and either (or both) OSS or
|
||||||
ALSA sound system btaudio drivers in the 2.6+ series.
|
ALSA sound system btaudio drivers in the 2.6+ series.
|
||||||
</para>
|
</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
|
@ -86,7 +86,7 @@
|
||||||
<para>
|
<para>
|
||||||
As for now, the choice is mainly between windows-1251 and
|
As for now, the choice is mainly between windows-1251 and
|
||||||
iso-8859-5. Windows-1251 provides compatibility with M$
|
iso-8859-5. Windows-1251 provides compatibility with M$
|
||||||
Windows and it is is by far the most popular charset for
|
Windows and it is by far the most popular charset for
|
||||||
nearly all slavic languages. On the other side, iso-8859-5 is
|
nearly all slavic languages. On the other side, iso-8859-5 is
|
||||||
better supported and easier to set up.
|
better supported and easier to set up.
|
||||||
</para>
|
</para>
|
||||||
|
|
|
@ -500,7 +500,7 @@ extern "C" void bar();
|
||||||
|
|
||||||
<para>To use the class from the module, load the two factory
|
<para>To use the class from the module, load the two factory
|
||||||
functions using <function>dlsym</function> just <link
|
functions using <function>dlsym</function> just <link
|
||||||
linkend="loadingfunctions">as we loaded the the hello
|
linkend="loadingfunctions">as we loaded the hello
|
||||||
function</link>; then, we can create and destroy as many
|
function</link>; then, we can create and destroy as many
|
||||||
instances as we wish.</para>
|
instances as we wish.</para>
|
||||||
|
|
||||||
|
|
|
@ -1766,7 +1766,7 @@ sub cortar_linea ()
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Download the cleanup[lowbar]ld2db.pl perl script from from
|
Download the cleanup[lowbar]ld2db.pl perl script from
|
||||||
<ulink url="http://www.milkywaygalaxy.freeservers.com">
|
<ulink url="http://www.milkywaygalaxy.freeservers.com">
|
||||||
Milkyway Galaxy
|
Milkyway Galaxy
|
||||||
</ulink>
|
</ulink>
|
||||||
|
|
|
@ -119,7 +119,7 @@ the output (e.g., the date).</para>
|
||||||
<title>Networking and Ethernet Support</title>
|
<title>Networking and Ethernet Support</title>
|
||||||
<para>Most, if not all, cable modems are easily configured for use with Linux.
|
<para>Most, if not all, cable modems are easily configured for use with Linux.
|
||||||
Most cable modems have two possible interfaces for connection to your computer:
|
Most cable modems have two possible interfaces for connection to your computer:
|
||||||
Ethernet or USB. If your version of Linux is like most, there is very little you will need to do to to get your cable modem
|
Ethernet or USB. If your version of Linux is like most, there is very little you will need to do to get your cable modem
|
||||||
working with an Ethernet interface as long as you have support for networking and the driver for your specific networking hardware installed.
|
working with an Ethernet interface as long as you have support for networking and the driver for your specific networking hardware installed.
|
||||||
</para>
|
</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
|
@ -436,7 +436,7 @@
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
The location of of apachectl may vary; find it with
|
The location of apachectl may vary; find it with
|
||||||
<command>locate apachectl</command>. If you installed
|
<command>locate apachectl</command>. If you installed
|
||||||
the Apache server yourself, you may want to use apachectl.
|
the Apache server yourself, you may want to use apachectl.
|
||||||
If you used the Apache default file locations, it would be
|
If you used the Apache default file locations, it would be
|
||||||
|
|
|
@ -115,7 +115,7 @@
|
||||||
|
|
||||||
<sect2>
|
<sect2>
|
||||||
<title>Feedback</title>
|
<title>Feedback</title>
|
||||||
<para>Comments and feedback should go the the author listed at the head of the document.</para>
|
<para>Comments and feedback should go to the author listed at the head of the document.</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
|
|
||||||
|
|
|
@ -830,7 +830,7 @@ When running ./ins_alI get the error "No matching INF file is found for SoftK56
|
||||||
</question>
|
</question>
|
||||||
<answer>
|
<answer>
|
||||||
<para>
|
<para>
|
||||||
This occurs when the driver can't find the correct %HSFModem% line in the lin_hsf.inf line, go back through the instructions and make sure that you didn't make a mistake when making or entering the the %HSFModem% line.
|
This occurs when the driver can't find the correct %HSFModem% line in the lin_hsf.inf line, go back through the instructions and make sure that you didn't make a mistake when making or entering the %HSFModem% line.
|
||||||
</para>
|
</para>
|
||||||
</answer>
|
</answer>
|
||||||
</qandaentry>
|
</qandaentry>
|
||||||
|
|
|
@ -637,7 +637,7 @@ This is not a real glossary, it's just an example.
|
||||||
</Para>
|
</Para>
|
||||||
|
|
||||||
<Para>
|
<Para>
|
||||||
You can get a copy of the GNU GPL at at <ULink
|
You can get a copy of the GNU GPL at <ULink
|
||||||
URL="http://www.gnu.org/copyleft/gpl.html">GNU GPL</ULink>.
|
URL="http://www.gnu.org/copyleft/gpl.html">GNU GPL</ULink>.
|
||||||
</Para>
|
</Para>
|
||||||
|
|
||||||
|
@ -2972,7 +2972,7 @@ defaultroute
|
||||||
|
|
||||||
<Blockquote>
|
<Blockquote>
|
||||||
<Para>
|
<Para>
|
||||||
The commonly used formula for working out the the tcp buffer is the
|
The commonly used formula for working out the tcp buffer is the
|
||||||
<Quote>bandwidth delay product</Quote> one:
|
<Quote>bandwidth delay product</Quote> one:
|
||||||
</para>
|
</para>
|
||||||
<Para>
|
<Para>
|
||||||
|
@ -4946,7 +4946,7 @@ Downstream/Upstream
|
||||||
<Para>
|
<Para>
|
||||||
<Emphasis>Installation</Emphasis>. A self-install option, of course, let's
|
<Emphasis>Installation</Emphasis>. A self-install option, of course, let's
|
||||||
anyone get up and running, and is less expensive. But if there is no
|
anyone get up and running, and is less expensive. But if there is no
|
||||||
self-install available, will the the provider install onto a Linux only
|
self-install available, will the provider install onto a Linux only
|
||||||
site? Many will not! Having a Windows (or Mac) box temporarily available
|
site? Many will not! Having a Windows (or Mac) box temporarily available
|
||||||
is a work around here. Even a laptop may be enough.
|
is a work around here. Even a laptop may be enough.
|
||||||
|
|
||||||
|
|
|
@ -227,7 +227,7 @@ stylesheet that would tell the formatter "render emphasis as a font
|
||||||
change to boldface". One advantage of structural-markup languages
|
change to boldface". One advantage of structural-markup languages
|
||||||
is that by changing a stylesheet you can globally change the
|
is that by changing a stylesheet you can globally change the
|
||||||
presentation of the document (to use different fonts, for example)
|
presentation of the document (to use different fonts, for example)
|
||||||
without having to hack all the the individual instances of (say)
|
without having to hack all the individual instances of (say)
|
||||||
<markup>.B</markup> in the document itself.</para>
|
<markup>.B</markup> in the document itself.</para>
|
||||||
|
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
|
@ -856,7 +856,7 @@ route add -host 11.22.33.44 gw 12.34.56.1
|
||||||
</programlisting>
|
</programlisting>
|
||||||
You must also keep the route to the client's local network,
|
You must also keep the route to the client's local network,
|
||||||
necessary for linux kernel 2.0 and earlier,
|
necessary for linux kernel 2.0 and earlier,
|
||||||
but but unnecessary for linux kernel 2.2 and later
|
but unnecessary for linux kernel 2.2 and later
|
||||||
(that implicitly adds it during the <command>ifconfig</command>):
|
(that implicitly adds it during the <command>ifconfig</command>):
|
||||||
<programlisting>
|
<programlisting>
|
||||||
route add -net 12.34.56.0 netmask 255.255.255.0 dev eth0
|
route add -net 12.34.56.0 netmask 255.255.255.0 dev eth0
|
||||||
|
|
|
@ -979,7 +979,7 @@ small caps fonts, and swash capitals (fancy, calligraphic letters).</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<emphasis>Ethical issues:</emphasis> The cheaper fonts are almost always ripoffs. Type design takes a long time and and experienced designer. Fonts that are sold for less than $1-per font were almost certainly not designed by the vendor. CDs with insane quantities of fonts on the are almost always ripoffs (the possible exceptions being collections from major foundries that cost thousands of dollars). Usually, the ripoffs lack the quality of fonts from respectable founries.</para>
|
<emphasis>Ethical issues:</emphasis> The cheaper fonts are almost always ripoffs. Type design takes a long time and an experienced designer. Fonts that are sold for less than $1-per font were almost certainly not designed by the vendor. CDs with insane quantities of fonts on the are almost always ripoffs (the possible exceptions being collections from major foundries that cost thousands of dollars). Usually, the ripoffs lack the quality of fonts from respectable founries.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
|
|
|
@ -2338,7 +2338,7 @@ startx -- :\!* -bpp 16 vt0`echo $tty | cut -dy f 2`' # X on this tty.
|
||||||
of those. So you can only have
|
of those. So you can only have
|
||||||
the one
|
the one
|
||||||
("<code>default</code>")
|
("<code>default</code>")
|
||||||
setting at at time (the same
|
setting at a time (the same
|
||||||
one you had in text
|
one you had in text
|
||||||
mode).</para></listitem>
|
mode).</para></listitem>
|
||||||
|
|
||||||
|
|
|
@ -408,7 +408,7 @@ good idea to add a separate configuration to your
|
||||||
<sect2 id="grub">
|
<sect2 id="grub">
|
||||||
<title>Grub</title>
|
<title>Grub</title>
|
||||||
<para>Grub is a newer bootloader, with enhanced support for different
|
<para>Grub is a newer bootloader, with enhanced support for different
|
||||||
operating systems and and file system types (eg. it supports booting from
|
operating systems and file system types (eg. it supports booting from
|
||||||
reiserfs partitions). If you would like to know more go to:
|
reiserfs partitions). If you would like to know more go to:
|
||||||
<ulink url="http://www.gnu.org/software/grub/">http://www.gnu.org/software/grub/</ulink>, where you will find all the stuff you need.</para>
|
<ulink url="http://www.gnu.org/software/grub/">http://www.gnu.org/software/grub/</ulink>, where you will find all the stuff you need.</para>
|
||||||
<para>If you already have Grub installed, you probably use the
|
<para>If you already have Grub installed, you probably use the
|
||||||
|
|
|
@ -8224,7 +8224,7 @@ The PA-Risc range is achitectured around a processor designed and realised by HP
|
||||||
|
|
||||||
|
|
||||||
The initiative to port Linux on the PA-RISC architecture was taken during the Atlanta Linux exhibition in October 1998.
|
The initiative to port Linux on the PA-RISC architecture was taken during the Atlanta Linux exhibition in October 1998.
|
||||||
HP has announced in February 1999 its sponsorship to to this port of Linux. This port is a native one, which is different from a preceding project which used MkLinux on machines based on PA-7200.
|
HP has announced in February 1999 its sponsorship to this port of Linux. This port is a native one, which is different from a preceding project which used MkLinux on machines based on PA-7200.
|
||||||
The work is currently done with
|
The work is currently done with
|
||||||
|
|
||||||
<ulink url="http://www.thepuffingroup.com">The Puffin Group</ulink>
|
<ulink url="http://www.thepuffingroup.com">The Puffin Group</ulink>
|
||||||
|
|
|
@ -162,7 +162,7 @@
|
||||||
<para>
|
<para>
|
||||||
To syncronize your Handspring Visor onto your linux computer, you
|
To syncronize your Handspring Visor onto your linux computer, you
|
||||||
need to configure linux to know how to do the low-level communication
|
need to configure linux to know how to do the low-level communication
|
||||||
with your device, and then a a user-space program to do the actual
|
with your device, and then a user-space program to do the actual
|
||||||
communication with the device.
|
communication with the device.
|
||||||
</para>
|
</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
@ -808,7 +808,7 @@ pilot-xfer -p /dev/ttyUSB1 -b visorbackup
|
||||||
</ListItem>
|
</ListItem>
|
||||||
<ListItem>
|
<ListItem>
|
||||||
<para>
|
<para>
|
||||||
Documentation to figure out type type of controller
|
Documentation to figure out the type of controller
|
||||||
was leached from the kernel documentation,
|
was leached from the kernel documentation,
|
||||||
Documentation/usb/scanner.txt.
|
Documentation/usb/scanner.txt.
|
||||||
</para>
|
</para>
|
||||||
|
|
|
@ -1041,7 +1041,7 @@
|
||||||
files, you should check that the sizes of the downloaded files
|
files, you should check that the sizes of the downloaded files
|
||||||
are correct. Some versions of Netscape tend to uncompress
|
are correct. Some versions of Netscape tend to uncompress
|
||||||
compressed files, and we want to keep them compressed. If
|
compressed files, and we want to keep them compressed. If
|
||||||
strange things things happen at boot time, try using another
|
strange things happen at boot time, try using another
|
||||||
program for downloading the files, like wget or lynx.
|
program for downloading the files, like wget or lynx.
|
||||||
</para>
|
</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
@ -1541,7 +1541,7 @@ rm -rf bamboo1
|
||||||
also be able to do the job. The trick is to download all
|
also be able to do the job. The trick is to download all
|
||||||
necessary files, and change the installer file
|
necessary files, and change the installer file
|
||||||
Mandrake/base/mdkinst_stage2.bz with a patched one. Below
|
Mandrake/base/mdkinst_stage2.bz with a patched one. Below
|
||||||
the the steps to get this done with the Apache web server on
|
the steps to get this done with the Apache web server on
|
||||||
a RedHat Linux installtion, and with the CD iso image files,
|
a RedHat Linux installtion, and with the CD iso image files,
|
||||||
is described. (A complete download of the ppc archive from a
|
is described. (A complete download of the ppc archive from a
|
||||||
Mandrake ftp mirror should work allright too, but I prefer
|
Mandrake ftp mirror should work allright too, but I prefer
|
||||||
|
@ -2577,8 +2577,8 @@ apt-get install xserver-xfree86 xfonts-100dpi xfonts-base xbase-clients xdm
|
||||||
<para>
|
<para>
|
||||||
The 7248 and it's cousines with Carolina motherboard do use
|
The 7248 and it's cousines with Carolina motherboard do use
|
||||||
special RAM, more specifically, they use only parity RAM. The
|
special RAM, more specifically, they use only parity RAM. The
|
||||||
spesifications are as follows: 72-pin SIMM, 5 Volt, Fast Page
|
specifications are as follows: 72-pin SIMM, 5 Volt, Fast Page
|
||||||
Memory with Parity, 70 ns. David Monro states that is is
|
Memory with Parity, 70 ns. David Monro states that it is
|
||||||
possible to make Carolinas work with other types of RAM if you
|
possible to make Carolinas work with other types of RAM if you
|
||||||
remove the cache. Look at <xref LinkEnd="resources"> for
|
remove the cache. Look at <xref LinkEnd="resources"> for
|
||||||
details.
|
details.
|
||||||
|
|
|
@ -1932,7 +1932,7 @@ of the kernel.
|
||||||
(H.323 protocol, specific issues with network games), etc. It should be
|
(H.323 protocol, specific issues with network games), etc. It should be
|
||||||
noted that the Patch-O-Matic patches used to come with the IPTABLES archive.
|
noted that the Patch-O-Matic patches used to come with the IPTABLES archive.
|
||||||
This is no longer the case and you have to download them (if any) seperately.
|
This is no longer the case and you have to download them (if any) seperately.
|
||||||
You can find the the various URLs for downloading IPTABLES, the
|
You can find the various URLs for downloading IPTABLES, the
|
||||||
Patch-o-matic system, etc. <XRef LinkEnd="kernel-2.4.x-Requirements">.
|
Patch-o-matic system, etc. <XRef LinkEnd="kernel-2.4.x-Requirements">.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
@ -3601,7 +3601,7 @@ for 2.2.x kernels in <XRef LinkEnd="rc.firewall-ipchains-stronger">, and
|
||||||
the Stronger IPFWADM ruleset for 2.0.x kernels in
|
the Stronger IPFWADM ruleset for 2.0.x kernels in
|
||||||
<XRef LinkEnd="rc.firewall-ipfwadm-stronger">. Please note that these
|
<XRef LinkEnd="rc.firewall-ipfwadm-stronger">. Please note that these
|
||||||
stronger firewall rulesets are more of a template than anything else.
|
stronger firewall rulesets are more of a template than anything else.
|
||||||
For truly secure firewall rulesets, check out the the requirements section
|
For truly secure firewall rulesets, check out the requirements section
|
||||||
of the HOWTO ( 2.4.x - <XRef LinkEnd="kernel-2.4.x-Requirements">, 2.2.x -
|
of the HOWTO ( 2.4.x - <XRef LinkEnd="kernel-2.4.x-Requirements">, 2.2.x -
|
||||||
<XRef LinkEnd="kernel-2.2.x-Requirements">, 2.0.x -
|
<XRef LinkEnd="kernel-2.2.x-Requirements">, 2.0.x -
|
||||||
<XRef LinkEnd="kernel-2.0.x-Requirements"> ).
|
<XRef LinkEnd="kernel-2.0.x-Requirements"> ).
|
||||||
|
@ -4169,7 +4169,7 @@ ruleset, the firewall isn't executed until the last stages of booting. The
|
||||||
preferred approach is to have the firewall loaded just after the networking
|
preferred approach is to have the firewall loaded just after the networking
|
||||||
subsystem is loaded. For now, the HOWTO only covers how to do so using
|
subsystem is loaded. For now, the HOWTO only covers how to do so using
|
||||||
/etc/rc.d/rc.local but if you know what you're doing (it's easy), go ahead
|
/etc/rc.d/rc.local but if you know what you're doing (it's easy), go ahead
|
||||||
and and modify the inet2 startup script to load the
|
and modify the inet2 startup script to load the
|
||||||
/etc/rc.d/rc.firewall-iptables file just after the network is up. If you
|
/etc/rc.d/rc.firewall-iptables file just after the network is up. If you
|
||||||
want a more detailed guide and/or a stronger firewall ruleset, I recommend
|
want a more detailed guide and/or a stronger firewall ruleset, I recommend
|
||||||
you check out Section 10 of TrinityOS found in the links section at
|
you check out Section 10 of TrinityOS found in the links section at
|
||||||
|
@ -4395,7 +4395,7 @@ $MODPROBE ip_masq_raudio
|
||||||
|
|
||||||
|
|
||||||
# Supports the masquerading of Quake and QuakeWorld by default. This modules is
|
# Supports the masquerading of Quake and QuakeWorld by default. This modules is
|
||||||
# for for multiple users behind the Linux MASQ server. If you are going to
|
# for multiple users behind the Linux MASQ server. If you are going to
|
||||||
# play Quake I, II, and III, use the second example.
|
# play Quake I, II, and III, use the second example.
|
||||||
#
|
#
|
||||||
# NOTE: If you get ERRORs loading the QUAKE module, you are running an old
|
# NOTE: If you get ERRORs loading the QUAKE module, you are running an old
|
||||||
|
@ -4720,7 +4720,7 @@ ruleset, the firewall isn't executed until the last stages of booting. The
|
||||||
preferred approach is to have the firewall loaded just after the networking
|
preferred approach is to have the firewall loaded just after the networking
|
||||||
subsystem is loaded. For now, the HOWTO only covers how to do so using
|
subsystem is loaded. For now, the HOWTO only covers how to do so using
|
||||||
/etc/rc.d/rc.local but if you know what you're doing (it's easy), go ahead
|
/etc/rc.d/rc.local but if you know what you're doing (it's easy), go ahead
|
||||||
and and modify the inet2 startup script to load the
|
and modify the inet2 startup script to load the
|
||||||
/etc/rc.d/rc.firewall-ipchains file just after the network is up. If you
|
/etc/rc.d/rc.firewall-ipchains file just after the network is up. If you
|
||||||
want a more detailed guide and/or a stronger firewall ruleset, I recommend
|
want a more detailed guide and/or a stronger firewall ruleset, I recommend
|
||||||
you check out Section 10 of TrinityOS found in the links section at
|
you check out Section 10 of TrinityOS found in the links section at
|
||||||
|
@ -5214,7 +5214,7 @@ ruleset, the firewall isn't executed until the last stages of booting. The
|
||||||
preferred approach is to have the firewall loaded just after the networking
|
preferred approach is to have the firewall loaded just after the networking
|
||||||
subsystem is loaded. For now, the HOWTO only covers how to do so using
|
subsystem is loaded. For now, the HOWTO only covers how to do so using
|
||||||
/etc/rc.d/rc.local but if you know what you're doing (it's easy), go ahead
|
/etc/rc.d/rc.local but if you know what you're doing (it's easy), go ahead
|
||||||
and and modify the inet2 startup script to load the
|
and modify the inet2 startup script to load the
|
||||||
/etc/rc.d/rc.firewall-ipfwadm file just after the network is up. If you
|
/etc/rc.d/rc.firewall-ipfwadm file just after the network is up. If you
|
||||||
want a more detailed guide and/or a stronger firewall ruleset, I recommend
|
want a more detailed guide and/or a stronger firewall ruleset, I recommend
|
||||||
you check out Section 10 of TrinityOS found in the links section at
|
you check out Section 10 of TrinityOS found in the links section at
|
||||||
|
@ -5700,7 +5700,7 @@ the system.
|
||||||
<Literal>As an initial test, ping</Literal> the Linux MASQ server to test the
|
<Literal>As an initial test, ping</Literal> the Linux MASQ server to test the
|
||||||
network connection: <Emphasis role="strong">'File/Run'</Emphasis>, type:
|
network connection: <Emphasis role="strong">'File/Run'</Emphasis>, type:
|
||||||
<Literal>ping 192.168.0.1</Literal>(This is only an INTERNAL LAN connection
|
<Literal>ping 192.168.0.1</Literal>(This is only an INTERNAL LAN connection
|
||||||
test, you you might not be able to <Literal>ping</Literal> the outside world
|
test, you might not be able to <Literal>ping</Literal> the outside world
|
||||||
yet.) If you don't see any "replies" to your PINGs, please verify your network
|
yet.) If you don't see any "replies" to your PINGs, please verify your network
|
||||||
configuration.
|
configuration.
|
||||||
</para>
|
</para>
|
||||||
|
@ -6678,7 +6678,7 @@ connectivity</Emphasis>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Next, from the same internal MASQed computer, try pinging the the IP address of
|
Next, from the same internal MASQed computer, try pinging the IP address of
|
||||||
the Linux MASQ server's INTERNAL interface (i.e. <Emphasis role="strong">ping
|
the Linux MASQ server's INTERNAL interface (i.e. <Emphasis role="strong">ping
|
||||||
192.168.0.1 </Emphasis>). This will verify that TCP/IP is correctly working
|
192.168.0.1 </Emphasis>). This will verify that TCP/IP is correctly working
|
||||||
on both the local and Linux MASQ machine. Almost ALL modern operating systems
|
on both the local and Linux MASQ machine. Almost ALL modern operating systems
|
||||||
|
@ -9412,7 +9412,7 @@ Using -I (input ) rules:
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Probably the fastest and most efficient method to block traffic but it only
|
Probably the fastest and most efficient method to block traffic but it only
|
||||||
stops the MASQed machines, and NOT the the firewall machine itself. Of course,
|
stops the MASQed machines, and NOT the firewall machine itself. Of course,
|
||||||
you might want to allow that combination.
|
you might want to allow that combination.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
@ -9965,7 +9965,7 @@ $PORTFWIP variable:
|
||||||
<Emphasis role="strong">PORTFW FTP: </Emphasis>If you have the
|
<Emphasis role="strong">PORTFW FTP: </Emphasis>If you have the
|
||||||
"ip_conntrack_ftp" and "ip_nat_ftp" kernel modules loaded into kernel space
|
"ip_conntrack_ftp" and "ip_nat_ftp" kernel modules loaded into kernel space
|
||||||
(as already done in the rc.firewall-iptables script), the simple PREROUTING
|
(as already done in the rc.firewall-iptables script), the simple PREROUTING
|
||||||
command like the one shown above changed for for port "21" should do the
|
command like the one shown above changed for port "21" should do the
|
||||||
trick. This is much easier than the configuration for the older IPCHAINS /
|
trick. This is much easier than the configuration for the older IPCHAINS /
|
||||||
IPFWADM tools for the 2.2.x / 2.0.x kernels!
|
IPFWADM tools for the 2.2.x / 2.0.x kernels!
|
||||||
</para>
|
</para>
|
||||||
|
@ -10285,7 +10285,7 @@ Masqueraded machine at IP address 192.168.0.10.
|
||||||
port 80, that port can no longer be used by the Linux IP Masquerade server.
|
port 80, that port can no longer be used by the Linux IP Masquerade server.
|
||||||
To be more specific, if you have a WWW server already running on the MASQ
|
To be more specific, if you have a WWW server already running on the MASQ
|
||||||
server and then you port forward port 80 to an internal MASQed computer, ALL
|
server and then you port forward port 80 to an internal MASQed computer, ALL
|
||||||
internet users will see the WWW pages pages from the -INTERNAL- WWW server and
|
internet users will see the WWW pages, pages from the -INTERNAL- WWW server and
|
||||||
not the pages on your IP MASQ server. This only performs a port forward to
|
not the pages on your IP MASQ server. This only performs a port forward to
|
||||||
some other port, say 8080, to your internal MASQ machine. Though this will
|
some other port, say 8080, to your internal MASQ machine. Though this will
|
||||||
work, all Internet users will have to append <Emphasis role="strong">:8080
|
work, all Internet users will have to append <Emphasis role="strong">:8080
|
||||||
|
@ -12041,7 +12041,7 @@ nasty MTU problem:
|
||||||
Change your MASQ server's Internet Link MTU
|
Change your MASQ server's Internet Link MTU
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>This solution will work for any Linux kernel version but is is NOT a
|
<para>This solution will work for any Linux kernel version but is NOT a
|
||||||
solution if you have a PPPoE connection for DSL or Cablemodem users.
|
solution if you have a PPPoE connection for DSL or Cablemodem users.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
@ -13588,7 +13588,7 @@ etc.). Fortunately, setting up this form of accounting is easy.
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Idea #3: Say you want to log all traffic going out onto the internet. You
|
Idea #3: Say you want to log all traffic going out onto the internet. You
|
||||||
can setup a firewall rule to accept port 80 traffic with with the SYN bit set
|
can setup a firewall rule to accept port 80 traffic with the SYN bit set
|
||||||
and log it. Now mind you, this will create smaller log files than the idea
|
and log it. Now mind you, this will create smaller log files than the idea
|
||||||
above but you will only know the destination IP address and NOT the WWW pages
|
above but you will only know the destination IP address and NOT the WWW pages
|
||||||
viewed.
|
viewed.
|
||||||
|
@ -15955,7 +15955,7 @@ added additional formatting.
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
05/18/02: Added some extra # lines the commented section of the the
|
05/18/02: Added some extra # lines the commented section of the
|
||||||
rc.firewall-2.4-stronger ruleset to better serve Cut and Paste users.
|
rc.firewall-2.4-stronger ruleset to better serve Cut and Paste users.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
@ -17009,7 +17009,7 @@ for the latter 2.2.x kernels.
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Added a a possible solution for users that fail to get past MASQ test #5.
|
Added a possible solution for users that fail to get past MASQ test #5.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
|
|
@ -194,7 +194,7 @@
|
||||||
Windows it boots Windows and you are met with the familiar windows screen
|
Windows it boots Windows and you are met with the familiar windows screen
|
||||||
or if you select Linux it boots Linux and if you don't make a choice in
|
or if you select Linux it boots Linux and if you don't make a choice in
|
||||||
the stipulated time – could be anything from
|
the stipulated time – could be anything from
|
||||||
±<literal>5</literal> seconds depending on on how you set it up
|
±<literal>5</literal> seconds depending on how you set it up
|
||||||
– it boots the default operating system, Windows or Linux, again
|
– it boots the default operating system, Windows or Linux, again
|
||||||
depending on how you set it up. You can restore your original
|
depending on how you set it up. You can restore your original
|
||||||
<acronym>MBR</acronym> anytime, when uninstalling Linux for instance,
|
<acronym>MBR</acronym> anytime, when uninstalling Linux for instance,
|
||||||
|
@ -413,7 +413,7 @@
|
||||||
understand why they have to delete the partition they just created at
|
understand why they have to delete the partition they just created at
|
||||||
considerable risk. This new partition is actually a
|
considerable risk. This new partition is actually a
|
||||||
<acronym>FAT32</acronym> partiton which Linux cannot use and when you
|
<acronym>FAT32</acronym> partiton which Linux cannot use and when you
|
||||||
delete it it doesn't revert to being a part of <medialabel>C</medialabel>
|
delete it, it doesn't revert to being a part of <medialabel>C</medialabel>
|
||||||
but is actually <guilabel>UNPARTITIONED FREE SPACE</guilabel> which you
|
but is actually <guilabel>UNPARTITIONED FREE SPACE</guilabel> which you
|
||||||
can use to create new partitions.</simpara>
|
can use to create new partitions.</simpara>
|
||||||
|
|
||||||
|
|
|
@ -655,7 +655,7 @@ $ dd if=bare of=/dev/rfd0 obs=18k
|
||||||
|
|
||||||
<para>You must provide the appropriate output block size argument (the `obs'
|
<para>You must provide the appropriate output block size argument (the `obs'
|
||||||
argument) on some workstations (e.g., Suns) or this will fail. If
|
argument) on some workstations (e.g., Suns) or this will fail. If
|
||||||
you have problems the man page for dd(1) may be be instructive.</para>
|
you have problems the man page for dd(1) may be instructive.</para>
|
||||||
|
|
||||||
<para>Be sure that you're using brand-new, error-free floppies. The
|
<para>Be sure that you're using brand-new, error-free floppies. The
|
||||||
floppies must have no bad blocks on them.</para>
|
floppies must have no bad blocks on them.</para>
|
||||||
|
|
|
@ -554,7 +554,7 @@ and 'Made in Taiwan'.
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
The motherboard is 'baby ATX' in configuration, but not
|
The motherboard is 'baby ATX' in configuration, but not
|
||||||
quite totally. Near the the front of the case is a fan that points
|
quite totally. Near the front of the case is a fan that points
|
||||||
at the CPU heat sink. The CPU heat sink has another fan on top of it.
|
at the CPU heat sink. The CPU heat sink has another fan on top of it.
|
||||||
The motherboard has a Socket 7 CPU socket that houses a Cyrix MediaGCm-266GP
|
The motherboard has a Socket 7 CPU socket that houses a Cyrix MediaGCm-266GP
|
||||||
CPU. There are typical PC motherboard jumpers with silk-screened legends
|
CPU. There are typical PC motherboard jumpers with silk-screened legends
|
||||||
|
@ -981,7 +981,7 @@ JavaOS was always sluggish in performance for us. It was rated as
|
||||||
having one of the slowest Java VMs by a ZDNet Online Magazane review at
|
having one of the slowest Java VMs by a ZDNet Online Magazane review at
|
||||||
<ulink url="http://www.zdnet.com/pcmag/features/javaguide/jfgr10.htm">
|
<ulink url="http://www.zdnet.com/pcmag/features/javaguide/jfgr10.htm">
|
||||||
http://www.zdnet.com/pcmag/features/javaguide/hfgr10.htm</ulink>
|
http://www.zdnet.com/pcmag/features/javaguide/hfgr10.htm</ulink>
|
||||||
. I speculate this was the the main cause of delaying the
|
. I speculate this was the main cause of delaying the
|
||||||
JavaStation's formal public release to April 1998.
|
JavaStation's formal public release to April 1998.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
|
|
@ -4005,7 +4005,7 @@ Initializing RT netlink socket
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Download the cleanup_ld2db.pl perl script from from
|
Download the cleanup_ld2db.pl perl script from
|
||||||
<ulink url="http://milkyway.has.it">
|
<ulink url="http://milkyway.has.it">
|
||||||
"http://milkyway.has.it"
|
"http://milkyway.has.it"
|
||||||
</ulink>
|
</ulink>
|
||||||
|
@ -5373,7 +5373,7 @@ bash# cp /usr/src/kernelconfigs/.config.save .config # In case you want to reus
|
||||||
don't use it, don't configure it, because it does take up memory. The
|
don't use it, don't configure it, because it does take up memory. The
|
||||||
most obvious symptom of kernel bloat is extreme swapping in and out of
|
most obvious symptom of kernel bloat is extreme swapping in and out of
|
||||||
memory to disk; if your disk is making a lot of noise and it's not one
|
memory to disk; if your disk is making a lot of noise and it's not one
|
||||||
of those old Fujitsu Eagles that sound like like a jet landing when
|
of those old Fujitsu Eagles that sound like a jet landing when
|
||||||
turned off, look over your kernel configuration.
|
turned off, look over your kernel configuration.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
|
|
|
@ -1007,7 +1007,7 @@ post-install sound /usr/local/bin/setmix -f /etc/volume.conf
|
||||||
<para>Why do I get <errorname>Ouch, kerneld timed out,
|
<para>Why do I get <errorname>Ouch, kerneld timed out,
|
||||||
message failed</errorname> messages ?</para></question>
|
message failed</errorname> messages ?</para></question>
|
||||||
<answer>
|
<answer>
|
||||||
<para>When the kernel sends a request off to to kerneld,
|
<para>When the kernel sends a request off to kerneld,
|
||||||
it expects to receive an acknowledgment back within one
|
it expects to receive an acknowledgment back within one
|
||||||
second. If kerneld does not send this acknowledgment,
|
second. If kerneld does not send this acknowledgment,
|
||||||
this message is logged. The request is retransmitted, and
|
this message is logged. The request is retransmitted, and
|
||||||
|
|
|
@ -1392,7 +1392,7 @@ bash$ for file in $(python cdp.py); do python cdp.py $file; done
|
||||||
The linux-kernel mailing list is a very high traffic mailing list detailing all aspects of the Linux kernel. This list is only for those who wish to have more information than the Linux-USB list and the gPhoto-Kodak lists contain. However, it covers much more of a broad spectrum of topics than Kodak digital camera support under Linux.
|
The linux-kernel mailing list is a very high traffic mailing list detailing all aspects of the Linux kernel. This list is only for those who wish to have more information than the Linux-USB list and the gPhoto-Kodak lists contain. However, it covers much more of a broad spectrum of topics than Kodak digital camera support under Linux.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
Before posting or subscribing to the Linux-kernel mailing list is is highly suggested reading the <ulink url="http://www.tux.org/lkml/">Linux-kernel mailing list FAQ</ulink>. It could save much time and embarrassment. It also contains useful information on who certain individuals are in the Linux community in relation to their standing on the list.
|
Before posting or subscribing to the Linux-kernel mailing list is highly suggested reading the <ulink url="http://www.tux.org/lkml/">Linux-kernel mailing list FAQ</ulink>. It could save much time and embarrassment. It also contains useful information on who certain individuals are in the Linux community in relation to their standing on the list.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
To subscribe to the list (remember, it is about 200 emails a day) send an email to <ulink url="mailto:majordomo@vger.rutgers.edu">majordomo@vger.rutgers.edu</ulink> with "subscribe linux-kernel username@mailserver" in the body of the message where username is the email account to be used and mailserver is the name of the mail server. Remember to omit the quotation marks.
|
To subscribe to the list (remember, it is about 200 emails a day) send an email to <ulink url="mailto:majordomo@vger.rutgers.edu">majordomo@vger.rutgers.edu</ulink> with "subscribe linux-kernel username@mailserver" in the body of the message where username is the email account to be used and mailserver is the name of the mail server. Remember to omit the quotation marks.
|
||||||
|
|
|
@ -254,7 +254,7 @@ and make any necessary changes. If changes are
|
||||||
<para>When doing this type of review, consider if the information is only valid for certain types
|
<para>When doing this type of review, consider if the information is only valid for certain types
|
||||||
of hardware or software. If this is the case, make sure to note the limitations of the document within
|
of hardware or software. If this is the case, make sure to note the limitations of the document within
|
||||||
the document, either within the abstract or as a note at the beginning of the document. For example, if the
|
the document, either within the abstract or as a note at the beginning of the document. For example, if the
|
||||||
solutions in the document only are relevant for one type or brand of hardware, make sure that that
|
solutions in the document only are relevant for one type or brand of hardware, make sure that the
|
||||||
limitation is defined. This will keep readers from trying to apply a certain type of technology to an application or
|
limitation is defined. This will keep readers from trying to apply a certain type of technology to an application or
|
||||||
situation where it will not work. </para>
|
situation where it will not work. </para>
|
||||||
|
|
||||||
|
|
|
@ -1308,7 +1308,7 @@ bash$ acroread output.pdf &</programlisting>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Download the cleanup[lowbar]ld2db.pl perl script from from
|
Download the cleanup[lowbar]ld2db.pl perl script from
|
||||||
<ulink url="http://www.milkywaygalaxy.freeservers.com">
|
<ulink url="http://www.milkywaygalaxy.freeservers.com">
|
||||||
Milkyway Galaxy site
|
Milkyway Galaxy site
|
||||||
</ulink>
|
</ulink>
|
||||||
|
|
|
@ -1905,7 +1905,7 @@ update -d -P
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
You may also want to edit the the file
|
You may also want to edit the file
|
||||||
<filename>/etc/rc.d/init.d/halt</filename> to deactivate the volume
|
<filename>/etc/rc.d/init.d/halt</filename> to deactivate the volume
|
||||||
groups at shutdown. Insert the
|
groups at shutdown. Insert the
|
||||||
<screen>
|
<screen>
|
||||||
|
@ -2002,7 +2002,7 @@ if [ -e /proc/lvm -a -x /sbin/vgchange -a -f /etc/lvmtab ]; then
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
You may also want to edit the the file
|
You may also want to edit the file
|
||||||
<filename>/etc/rc.d/init.d/halt</filename> to deactivate the volume
|
<filename>/etc/rc.d/init.d/halt</filename> to deactivate the volume
|
||||||
groups at shutdown. Insert the
|
groups at shutdown. Insert the
|
||||||
<screen>
|
<screen>
|
||||||
|
|
|
@ -318,7 +318,7 @@ There are some further subtypes defined, see below:</para><sect3>
|
||||||
<![CDATA[3ffe:ffff:100:f102::1
|
<![CDATA[3ffe:ffff:100:f102::1
|
||||||
]]></screen><para>A special 6bone test address which will never be globally unique begins with </para><screen>
|
]]></screen><para>A special 6bone test address which will never be globally unique begins with </para><screen>
|
||||||
<![CDATA[3ffe:ffff:
|
<![CDATA[3ffe:ffff:
|
||||||
]]></screen><para>and is mostly shown in older examples. The reason for this is, if real addresses are are shown, it's possible for someone to do a copy & paste to their configuration files, thus inadvertently causing duplicates on a globally unique address. This would cause serious problems for the original host (e.g. getting answer packets for request that were never sent).
|
]]></screen><para>and is mostly shown in older examples. The reason for this is, if real addresses are shown, it's possible for someone to do a copy & paste to their configuration files, thus inadvertently causing duplicates on a globally unique address. This would cause serious problems for the original host (e.g. getting answer packets for request that were never sent).
|
||||||
Because IPv6 is now in production, this prefix is no longer be delegated and is removed from routing after 6.6.2006 (see <ulink url="http://www.faqs.org/rfcs/rfc3701.html">RFC 3701 / 6bone Phaseout</ulink> for more).</para></sect3><sect3>
|
Because IPv6 is now in production, this prefix is no longer be delegated and is removed from routing after 6.6.2006 (see <ulink url="http://www.faqs.org/rfcs/rfc3701.html">RFC 3701 / 6bone Phaseout</ulink> for more).</para></sect3><sect3>
|
||||||
<title>6to4 addresses</title>
|
<title>6to4 addresses</title>
|
||||||
<para>These addresses, designed for a special tunneling mechanism [<ulink url="http://www.faqs.org/rfcs/rfc3056.html">RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds</ulink> and <ulink url="http://www.faqs.org/rfcs/rfc2893.html">RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers</ulink>], encode a given IPv4 address and a possible subnet and begin with </para><screen>
|
<para>These addresses, designed for a special tunneling mechanism [<ulink url="http://www.faqs.org/rfcs/rfc3056.html">RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds</ulink> and <ulink url="http://www.faqs.org/rfcs/rfc2893.html">RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers</ulink>], encode a given IPv4 address and a possible subnet and begin with </para><screen>
|
||||||
|
@ -677,7 +677,7 @@ user@::1's password: ******
|
||||||
# /sbin/ifconfig eth0 down
|
# /sbin/ifconfig eth0 down
|
||||||
]]></screen></sect2></sect1></chapter><chapter id='chapter-configuration-address' >
|
]]></screen></sect2></sect1></chapter><chapter id='chapter-configuration-address' >
|
||||||
<title><!-- anchor id="chapter-configuration-address" -->Configuring IPv6 addresses</title>
|
<title><!-- anchor id="chapter-configuration-address" -->Configuring IPv6 addresses</title>
|
||||||
<para>There are different ways to configure an IPv6 address on an interface. You can use use "ifconfig" or "ip".</para><sect1>
|
<para>There are different ways to configure an IPv6 address on an interface. You may use "ifconfig" or "ip".</para><sect1>
|
||||||
<title>Displaying existing IPv6 addresses</title>
|
<title>Displaying existing IPv6 addresses</title>
|
||||||
<para>First you should check, whether and which IPv6 addresses are already configured (perhaps auto-magically during stateless auto-configuration).</para>
|
<para>First you should check, whether and which IPv6 addresses are already configured (perhaps auto-magically during stateless auto-configuration).</para>
|
||||||
<para>Just note that addresses beginning with “fec0” are deprecated, but shown here for completness!</para><sect2>
|
<para>Just note that addresses beginning with “fec0” are deprecated, but shown here for completness!</para><sect2>
|
||||||
|
@ -1091,7 +1091,7 @@ ff00::/8 :: UA 256 0 0 sit0
|
||||||
<title>Numbered point-to-point tunnels</title>
|
<title>Numbered point-to-point tunnels</title>
|
||||||
<para>Sometimes it's needed to configure a point-to-point tunnel with IPv6 addresses like in IPv4 today. This is only possible with the first (ifconfig+route - deprecated) and third (ip+route) tunnel setup. In such cases, you can add the IPv6 address to the tunnel interface like shown on interface configuration. </para></sect2></sect1><sect1 id='configuring-ipv6to4-tunnels' >
|
<para>Sometimes it's needed to configure a point-to-point tunnel with IPv6 addresses like in IPv4 today. This is only possible with the first (ifconfig+route - deprecated) and third (ip+route) tunnel setup. In such cases, you can add the IPv6 address to the tunnel interface like shown on interface configuration. </para></sect2></sect1><sect1 id='configuring-ipv6to4-tunnels' >
|
||||||
<title><!-- anchor id="configuring-ipv6to4-tunnels" -->Setup of 6to4 tunnels</title>
|
<title><!-- anchor id="configuring-ipv6to4-tunnels" -->Setup of 6to4 tunnels</title>
|
||||||
<para>Pay attention that the support of 6to4 tunnels currently lacks on vanilla kernel series 2.2.x (see <link linkend="systemcheck-kernel">systemcheck/kernel</link> for more information). Also note that that the prefix length for a 6to4 address is 16 because of from network point of view, all other 6to4 enabled hosts are on the same layer 2.</para><sect2>
|
<para>Pay attention that the support of 6to4 tunnels currently lacks on vanilla kernel series 2.2.x (see <link linkend="systemcheck-kernel">systemcheck/kernel</link> for more information). Also note that the prefix length for a 6to4 address is 16 because of from network point of view, all other 6to4 enabled hosts are on the same layer 2.</para><sect2>
|
||||||
<title>Add a 6to4 tunnel</title>
|
<title>Add a 6to4 tunnel</title>
|
||||||
<para>First, you have to calculate your 6to4 prefix using your local assigned global routable IPv4 address (if your host has no global routable IPv4 address, in special cases NAT on border gateways is possible):</para>
|
<para>First, you have to calculate your 6to4 prefix using your local assigned global routable IPv4 address (if your host has no global routable IPv4 address, in special cases NAT on border gateways is possible):</para>
|
||||||
<para>Assuming your IPv4 address is </para><screen>
|
<para>Assuming your IPv4 address is </para><screen>
|
||||||
|
@ -2546,7 +2546,7 @@ Big pipe Queue 2 Queue 1 / Queue 2 / Queue 3 Thin Pipe
|
||||||
<![CDATA[# ip6tables -A POSTROUTING -t mangle -p tcp --dport 5003 -j MARK --set-mark 32
|
<![CDATA[# ip6tables -A POSTROUTING -t mangle -p tcp --dport 5003 -j MARK --set-mark 32
|
||||||
]]></screen></sect3><sect3>
|
]]></screen></sect3><sect3>
|
||||||
<title>Testing filter definitions using iperf</title>
|
<title>Testing filter definitions using iperf</title>
|
||||||
<para>Start on server side each one one separate console:</para><screen>
|
<para>Start on server side each one in a separate console:</para><screen>
|
||||||
<![CDATA[# iperf -V -s -p 5001
|
<![CDATA[# iperf -V -s -p 5001
|
||||||
# iperf -V -s -p 5002
|
# iperf -V -s -p 5002
|
||||||
# iperf -V -s -p 5003
|
# iperf -V -s -p 5003
|
||||||
|
|
|
@ -664,7 +664,7 @@ diff /mnt/zip/metadata/rpmVa.txt ~/foo.txt</command></programlisting>
|
||||||
<para>For me the best thing about using Knoppix is that I don't need a specific boot medium for each machine, but I can use the same tools all the time. And hardware support in Knoppix is really great. I don't have that much experience with different platforms, but all the machines I've tried have worked fine, scsi drivers are found and so on.</para>
|
<para>For me the best thing about using Knoppix is that I don't need a specific boot medium for each machine, but I can use the same tools all the time. And hardware support in Knoppix is really great. I don't have that much experience with different platforms, but all the machines I've tried have worked fine, scsi drivers are found and so on.</para>
|
||||||
<para>I'm doing this recovery thing by copying the backups over the network to other machine. The restore involves booting the Knoppix cd, fetching the metadata.tar.gz from the network machine. Then make.dev, mount.dev, fetching the other tar.gz files, grub and reboot. Some typing involved but thanks to your scripts it's quite straighforward. Unless changing from ide to scsi or something, but even then it's not that difficult, since Linux is easy to restore to different hardware.</para>
|
<para>I'm doing this recovery thing by copying the backups over the network to other machine. The restore involves booting the Knoppix cd, fetching the metadata.tar.gz from the network machine. Then make.dev, mount.dev, fetching the other tar.gz files, grub and reboot. Some typing involved but thanks to your scripts it's quite straighforward. Unless changing from ide to scsi or something, but even then it's not that difficult, since Linux is easy to restore to different hardware.</para>
|
||||||
</blockquote>
|
</blockquote>
|
||||||
<para>Let me add to that that <ulink url="http://www.knoppix.org/">Knoppix</ulink> detects USB devices for you, which is really nice. They make excellent (and roomier) substitutes for the ZIP drive.</para>
|
<para>Let me add to that <ulink url="http://www.knoppix.org/">Knoppix</ulink> detects USB devices for you, which is really nice. They make excellent (and roomier) substitutes for the ZIP drive.</para>
|
||||||
<para>Also see <ulink url="http://www-106.ibm.com/developerworks/linux/library/l-knopx.html?ca=dgr-lnxw04Knoppix"><quote>System recovery with Knoppix</quote></ulink>.</para>
|
<para>Also see <ulink url="http://www-106.ibm.com/developerworks/linux/library/l-knopx.html?ca=dgr-lnxw04Knoppix"><quote>System recovery with Knoppix</quote></ulink>.</para>
|
||||||
<para>Do your restore as user <quote>root</quote> rather than as user <quote>knoppix</quote>. Otherwise you may get some directories and files owned by an oddball user or group. Also, for <ulink url="http://www.knoppix.org/">Knoppix</ulink>, we tar the first stage stuff saving numeric user & group values instead of by name. The names may point to different numbers on knoppix, so we would be restoring the files with incorrect user and group IDs.</para>
|
<para>Do your restore as user <quote>root</quote> rather than as user <quote>knoppix</quote>. Otherwise you may get some directories and files owned by an oddball user or group. Also, for <ulink url="http://www.knoppix.org/">Knoppix</ulink>, we tar the first stage stuff saving numeric user & group values instead of by name. The names may point to different numbers on knoppix, so we would be restoring the files with incorrect user and group IDs.</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
@ -798,7 +798,7 @@ tar cf - usr/knox | gzip -c > $zip/arkeia.tar.gz]]></programlisting>
|
||||||
<title>First Stage</title>
|
<title>First Stage</title>
|
||||||
<sect3 id="make.fdisk">
|
<sect3 id="make.fdisk">
|
||||||
<title><filename>make.fdisk</filename></title>
|
<title><filename>make.fdisk</filename></title>
|
||||||
<para>This script, run at backup time, creates scripts similar to <link linkend="make.dev.hda"><filename>make.dev.hda</filename></link> and <link linkend="mount.dev.hda"><filename>mount.dev.x</filename></link>, below, for you to run at restore time. It also produces data files similar to <link linkend="dev.hda"><filename>dev.hda</filename></link> and <link linkend="dev.hda.sfd"><filename>dev.hda.sfd</filename></link>, below. The names of the scripts and data files produced depend on the device given this script as a a parameter. Those script, run at restore time, build and mount the partitions on the hard drive. <filename>make.fdisk</filename> is called from <link linkend="save.metadata"><filename>save.metadata</filename></link>, below.</para>
|
<para>This script, run at backup time, creates scripts similar to <link linkend="make.dev.hda"><filename>make.dev.hda</filename></link> and <link linkend="mount.dev.hda"><filename>mount.dev.x</filename></link>, below, for you to run at restore time. It also produces data files similar to <link linkend="dev.hda"><filename>dev.hda</filename></link> and <link linkend="dev.hda.sfd"><filename>dev.hda.sfd</filename></link>, below. The names of the scripts and data files produced depend on the device given this script as a parameter. Those script, run at restore time, build and mount the partitions on the hard drive. <filename>make.fdisk</filename> is called from <link linkend="save.metadata"><filename>save.metadata</filename></link>, below.</para>
|
||||||
<!-- #include program listings to make updates easier. C^2 -->
|
<!-- #include program listings to make updates easier. C^2 -->
|
||||||
<programlisting>&make.fdisk;</programlisting>
|
<programlisting>&make.fdisk;</programlisting>
|
||||||
</sect3>
|
</sect3>
|
||||||
|
|
|
@ -1735,7 +1735,7 @@
|
||||||
competitor, was about a year late which is very bad when you're competing for a bleeding edge
|
competitor, was about a year late which is very bad when you're competing for a bleeding edge
|
||||||
market. While nVidia was putting real R&D into their cards, 3dfx was simply adding more
|
market. While nVidia was putting real R&D into their cards, 3dfx was simply adding more
|
||||||
and faster RAM. The Voodoo IV and V rendered in full 32bpp color, had great AA support (<xref
|
and faster RAM. The Voodoo IV and V rendered in full 32bpp color, had great AA support (<xref
|
||||||
linkend="aa">), featured a 2nd GPU, more memory, and was arguably the king of of video cards.
|
linkend="aa">), featured a 2nd GPU, more memory, and was arguably the king of video cards.
|
||||||
However, 3dfx's late release of the Voodoo IV and V coupled with the fact that the GeForce
|
However, 3dfx's late release of the Voodoo IV and V coupled with the fact that the GeForce
|
||||||
could be had for half the price meant that 3dfx was sinking fast. For Linux, the newest
|
could be had for half the price meant that 3dfx was sinking fast. For Linux, the newest
|
||||||
Voodoo's could only accelerate at 16 and 24 bit color. Worse still, the Voodoo V's 2nd GPU
|
Voodoo's could only accelerate at 16 and 24 bit color. Worse still, the Voodoo V's 2nd GPU
|
||||||
|
|
|
@ -122,7 +122,7 @@ many programs to burn music CDs from MP3 files, and many of them do the
|
||||||
conversion transparently. But I haven't seen a single tool that also
|
conversion transparently. But I haven't seen a single tool that also
|
||||||
normalizes the volume, so that's why I worked out my own CD-burning recipe.
|
normalizes the volume, so that's why I worked out my own CD-burning recipe.
|
||||||
</para>
|
</para>
|
||||||
<para>If you you just want to make a CD filled with music, and not be bothered with all of the details, I have good news for you: Kees Cook (<email>kees@outflux.net</email>) put together a tool based on this HOWTO, which automates all of the tasks outlined here. His program can be obtained from <ulink url="http://outflux.net/unix/software/mp3cd/">http://outflux.net/unix/software/mp3cd/</ulink>. Thanks, Kees!
|
<para>If you just want to make a CD filled with music, and not be bothered with all of the details, I have good news for you: Kees Cook (<email>kees@outflux.net</email>) put together a tool based on this HOWTO, which automates all of the tasks outlined here. His program can be obtained from <ulink url="http://outflux.net/unix/software/mp3cd/">http://outflux.net/unix/software/mp3cd/</ulink>. Thanks, Kees!
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
This HOWTO is just about one thing - putting MP3 music on a CD, so that you can
|
This HOWTO is just about one thing - putting MP3 music on a CD, so that you can
|
||||||
|
|
|
@ -288,7 +288,7 @@ everyone, both on your machine and remotely. To create MTA aliases
|
||||||
you must modify a system file, usually but not always
|
you must modify a system file, usually but not always
|
||||||
<filename>/etc/aliases</filename> or
|
<filename>/etc/aliases</filename> or
|
||||||
<filename>/etc/mail/aliases</filename> (the location depends on your
|
<filename>/etc/mail/aliases</filename> (the location depends on your
|
||||||
MTA). It may be instructive for you to look at the the aliases on
|
MTA). It may be instructive for you to look at the aliases on
|
||||||
your system; it should contain a number of standard aliases such as
|
your system; it should contain a number of standard aliases such as
|
||||||
`postmaster'.</para>
|
`postmaster'.</para>
|
||||||
|
|
||||||
|
|
|
@ -353,7 +353,7 @@ will hold pathnames, filenames or default options.</para>
|
||||||
|
|
||||||
<para>...should give an overview of the most common error messages
|
<para>...should give an overview of the most common error messages
|
||||||
from your program and how to cope with them. There's no need to
|
from your program and how to cope with them. There's no need to
|
||||||
explain system error error messages (from
|
explain system error messages (from
|
||||||
<literal>perror</literal>(3)) or fatal signals (from
|
<literal>perror</literal>(3)) or fatal signals (from
|
||||||
<literal>psignal</literal>(3)) as they can appear during execution
|
<literal>psignal</literal>(3)) as they can appear during execution
|
||||||
of any program.</para>
|
of any program.</para>
|
||||||
|
@ -497,7 +497,7 @@ provided by the <literal>.so</literal> macro.</para>
|
||||||
<para>The first way is obviously a waste of disk space. The second
|
<para>The first way is obviously a waste of disk space. The second
|
||||||
is not recommended because intelligent versions of the
|
is not recommended because intelligent versions of the
|
||||||
<literal>catman</literal> program can save a lot of work by looking
|
<literal>catman</literal> program can save a lot of work by looking
|
||||||
at the the file type or contents. Hard links will prevent
|
at the file type or contents. Hard links will prevent
|
||||||
<literal>catman</literal> from being clever. (Note that
|
<literal>catman</literal> from being clever. (Note that
|
||||||
<literal>catman</literal>'s purpose is to format all man pages
|
<literal>catman</literal>'s purpose is to format all man pages
|
||||||
so they can be displayed quickly.) The third alternative has a
|
so they can be displayed quickly.) The third alternative has a
|
||||||
|
|
|
@ -95,7 +95,7 @@
|
||||||
</para><para>
|
</para><para>
|
||||||
This is NOT a replacement for the IP-Masquerading HOWTO - it is to
|
This is NOT a replacement for the IP-Masquerading HOWTO - it is to
|
||||||
complement it, and the two should be read side by side. I do not include
|
complement it, and the two should be read side by side. I do not include
|
||||||
things in here that are covered by the the other HOWTO, nor do I explain
|
things in here that are covered by the other HOWTO, nor do I explain
|
||||||
what it all means, or what it is all about. See
|
what it all means, or what it is all about. See
|
||||||
<ulink url="http://ipmasq.cjb.net">http://ipmasq.cjb.net</ulink>
|
<ulink url="http://ipmasq.cjb.net">http://ipmasq.cjb.net</ulink>
|
||||||
and the standard Masq-HOWTO for a much better guides.
|
and the standard Masq-HOWTO for a much better guides.
|
||||||
|
|
|
@ -907,7 +907,7 @@ www.TxOutcome.Org
|
||||||
</sect3>
|
</sect3>
|
||||||
|
|
||||||
<sect3>
|
<sect3>
|
||||||
<title>Where to to get it</title>
|
<title>Where to get it</title>
|
||||||
<para>You can get the entire package which include everything you need like Zope products and even python from <ulink url="http://www.freepm.org:8080/freepm_download/fpm_downloads">Here</ulink> and choosing FreePM-1.0b6-FULL-linux2-x86.tar.gz. This will include all the documentation.
|
<para>You can get the entire package which include everything you need like Zope products and even python from <ulink url="http://www.freepm.org:8080/freepm_download/fpm_downloads">Here</ulink> and choosing FreePM-1.0b6-FULL-linux2-x86.tar.gz. This will include all the documentation.
|
||||||
</para>
|
</para>
|
||||||
</sect3>
|
</sect3>
|
||||||
|
@ -951,9 +951,9 @@ www.TxOutcome.Org
|
||||||
|
|
||||||
<para>Go ahead and click on the link that says Zope management interface or enter http:127.0.0.1:8080/manage and you should the zope management screen. You know you are in the correct section if you see a root folder at the top of the Left Frame. To make sure we are on the same page, go ahead and click on the Root Folder icon in the right Frame.</para>
|
<para>Go ahead and click on the link that says Zope management interface or enter http:127.0.0.1:8080/manage and you should the zope management screen. You know you are in the correct section if you see a root folder at the top of the Left Frame. To make sure we are on the same page, go ahead and click on the Root Folder icon in the right Frame.</para>
|
||||||
<para>You then should see the list of contents of the Root Folder on the Right Frame.</para>
|
<para>You then should see the list of contents of the Root Folder on the Right Frame.</para>
|
||||||
<para>Look for and click on the <emphasis>acl_users</emphasis> folder. select add new user, fill in the required fields. You leave the domain field blank. And then be sure sure to select role. In this case, click on <emphasis>manager</emphasis> for this user.</para>
|
<para>Look for and click on the <emphasis>acl_users</emphasis> folder. select add new user, fill in the required fields. You leave the domain field blank. And then be sure to select role. In this case, click on <emphasis>manager</emphasis> for this user.</para>
|
||||||
<para>I am having problems successfully logging out completely using zope, so when you intend to switch users, be sure to completely close all browser windows.</para>
|
<para>I am having problems successfully logging out completely using zope, so when you intend to switch users, be sure to completely close all browser windows.</para>
|
||||||
<para>Once you added a new user that has the role of manager, log back in. That is to say, Close all browsers and open up a new browsers and go the the zope management screen. You should be asked for a login at this point. Go ahead and enter in you new user login and password.</para>
|
<para>Once you added a new user that has the role of manager, log back in. That is to say, Close all browsers and open up a new browsers and go to the zope management screen. You should be asked for a login at this point. Go ahead and enter in you new user login and password.</para>
|
||||||
<para>Once you are logged in as an user (not the admin user), go ahead and click on the Root Folder on the top of the left frame. Scroll to the bottom of the Right Frame and you should see the Import/Export button. You see a new screen. In the Field Import File Name, enter FreePM Product.zexp and then hit the import button. You should see a new scree indicating success</para>
|
<para>Once you are logged in as an user (not the admin user), go ahead and click on the Root Folder on the top of the left frame. Scroll to the bottom of the Right Frame and you should see the Import/Export button. You see a new screen. In the Field Import File Name, enter FreePM Product.zexp and then hit the import button. You should see a new scree indicating success</para>
|
||||||
<para>The next step, is to again hit on the Root Folder Icon at the TOP LEFT FRAME. Again hit the Import/Export button, but this time, you want to import FreePM.zexp. Then hit the Import button. <caution><para>Note that it will take some time to import the FreePM.zexp Zope product as it is quite large and you may get a browser error. I almost lost hair doing this stage because I could not figure out what was going wrong. In fact nothing was going wrong, it just took some time to import this large (32MB) zope product. If you want to make sure something is actually going on, I recommend using the <userinput>top</userinput> unix command, which will show you that python is actively still working to import FreePM.zexp.</para> </caution></para>
|
<para>The next step, is to again hit on the Root Folder Icon at the TOP LEFT FRAME. Again hit the Import/Export button, but this time, you want to import FreePM.zexp. Then hit the Import button. <caution><para>Note that it will take some time to import the FreePM.zexp Zope product as it is quite large and you may get a browser error. I almost lost hair doing this stage because I could not figure out what was going wrong. In fact nothing was going wrong, it just took some time to import this large (32MB) zope product. If you want to make sure something is actually going on, I recommend using the <userinput>top</userinput> unix command, which will show you that python is actively still working to import FreePM.zexp.</para> </caution></para>
|
||||||
</sect4>
|
</sect4>
|
||||||
|
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue