mirror of
https://github.com/Zeckmathederg/glfs.git
synced 2025-01-23 22:42:14 +08:00
edited compound words
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1304 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
parent
5e18c49cdd
commit
c2ee009c74
@ -2,6 +2,6 @@
|
||||
<title>Contents</title>
|
||||
|
||||
<para>The zlib package contains the zlib library which is used by many
|
||||
programs for compression and uncompression functions.</para>
|
||||
programs for compression and decompression functions.</para>
|
||||
|
||||
</sect2>
|
||||
|
@ -6,11 +6,11 @@ mv conf-home~ conf-home
|
||||
sed 's/bin/sbin/' hier.c > hier.c~
|
||||
mv hier.c~ hier.c</command></screen>
|
||||
These commands change the installation directory to
|
||||
<filename>/usr/sbin</filename> from the default
|
||||
of <filename>/usr/local/bin</filename>. Since these tools are used in
|
||||
conjunction with daemons,
|
||||
they don't make much sense in general user directories. However, some of the
|
||||
example programs and the tcpclient program might be of use to non-root users.
|
||||
<filename class="directory">/usr/sbin</filename> from the default
|
||||
of <filename class="directory">/usr/local/bin</filename>. Since these tools
|
||||
are used in conjunction with daemons, they don't make much sense in general
|
||||
user directories. However, some of the example programs and the
|
||||
<command>tcpclient</command> program might be of use to non-root users.
|
||||
If you wish to make these available, then we would suggest installing as above,
|
||||
and then executing the following commands:
|
||||
<screen><command>cd /usr/sbin mv tcpclient *@ mconnect delcr addcr tcpcat /usr/bin</command></screen>
|
||||
|
@ -16,7 +16,7 @@ program.</para>
|
||||
<para><xref linkend="mozilla"/> includes both a mail client and newsreader in
|
||||
its installation along with notes for installing <application>Mozilla
|
||||
Thunderbird</application>, a mail/news client based on the
|
||||
<application>Mozilla</application> codebase.</para>
|
||||
<application>Mozilla</application> code base.</para>
|
||||
|
||||
<para><xref linkend="evolution"/> includes an <acronym>GTK</acronym>2
|
||||
based mail client.</para>
|
||||
|
@ -35,7 +35,7 @@ password is needed, for instance when using a guest account, a single '-'
|
||||
should be put in place of a password.</para>
|
||||
|
||||
<para>It should be noted that the ncpmount is not intended to mount
|
||||
individual volumes because each mountpoint creates a separate client
|
||||
individual volumes because each mount point creates a separate client
|
||||
connection to the Novell server. Mounting each individual volume
|
||||
separately would be unwise, as mounting all volumes on a server
|
||||
under one mount point uses only one client connection.</para>
|
||||
|
@ -3,7 +3,7 @@
|
||||
|
||||
<para><option>--enable-graphics</option>: Add this switch if you want to
|
||||
use <application>Links</application> in graphics mode. You will also need to
|
||||
enable framebuffer support in your kernel and install <xref linkend="gpm"/>
|
||||
enable frame buffer support in your kernel and install <xref linkend="gpm"/>
|
||||
or install one of the supported graphics libraries.</para>
|
||||
|
||||
</sect2>
|
||||
|
@ -65,10 +65,10 @@ server program.</para></sect3>
|
||||
|
||||
<sect3><title>logresolve</title>
|
||||
<para><command>logresolve</command> is a post-processing program to
|
||||
resolve <acronym>IP</acronym>-addresses in <application>Apache</application>'s access logfiles.</para></sect3>
|
||||
resolve <acronym>IP</acronym>-addresses in <application>Apache</application>'s access log files.</para></sect3>
|
||||
|
||||
<sect3><title>rotatelogs</title>
|
||||
<para><command>rotatelogs</command> is a simple program for use in
|
||||
conjunction with <application>Apache</application>'s piped logfile feature.</para></sect3>
|
||||
conjunction with <application>Apache</application>'s piped log file feature.</para></sect3>
|
||||
|
||||
</sect2>
|
||||
|
@ -38,6 +38,6 @@ surfaces.</para></sect3>
|
||||
<para>They provide hardware graphics acceleration, input device handling
|
||||
and abstraction, integrated windowing system with support for
|
||||
translucent windows and multiple display layers on top of the Linux
|
||||
framebuffer device.</para></sect3>
|
||||
frame buffer device.</para></sect3>
|
||||
|
||||
</sect2>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<sect2>
|
||||
<title>Introduction to <application>DirectFB</application></title>
|
||||
|
||||
<para><application>DirectFB</application> is a graphics library on top of the Linux framebuffer
|
||||
<para><application>DirectFB</application> is a graphics library on top of the Linux frame buffer
|
||||
device. It offers maximum hardware accelerated performance at a
|
||||
minimum of resource usage and overhead.</para>
|
||||
|
||||
|
@ -23,10 +23,10 @@ management facilities.</para></sect3>
|
||||
|
||||
<sect3><title>icclink</title>
|
||||
<para><command>icclink</command> links two or more profiles into a
|
||||
single devicelink profile.</para></sect3>
|
||||
single device link profile.</para></sect3>
|
||||
|
||||
<sect3><title>icctrans</title>
|
||||
<para><command>icctrans</command> is a ColorSpace conversion
|
||||
<para><command>icctrans</command> is a Color Space conversion
|
||||
calculator.</para></sect3>
|
||||
|
||||
<sect3><title>tifficc</title>
|
||||
|
@ -2,16 +2,16 @@
|
||||
<title>Introduction to <application>libungif</application></title>
|
||||
|
||||
<para>The libungif package contains libraries for reading all
|
||||
<acronym>GIF</acronym>s and writing uncompressed ones as well as programs for
|
||||
<acronym>GIF</acronym>s and writing non-compressed ones as well as programs for
|
||||
converting and working with <acronym>GIF</acronym> files. The libraries are
|
||||
useful for any graphics program wishing to deal with <acronym>GIF</acronym>
|
||||
files while the programs are useful for conversion purposes as well as cleaning
|
||||
up images.</para>
|
||||
|
||||
<para>The reason libungif only writes uncompressed <acronym>GIF</acronym>s
|
||||
<para>The reason libungif only writes non-compressed <acronym>GIF</acronym>s
|
||||
is due to a legal issue with <acronym>LZW</acronym> compression (which Unisys
|
||||
claims a patent on). Reading <acronym>GIF</acronym>s is not a problem as the
|
||||
uncompression routines do not seem to be limited in this way. Note that this
|
||||
decompression routines do not seem to be limited in this way. Note that this
|
||||
has in the past been disputed. The best way to avoid this whole mess is to
|
||||
simply use libungif for looking at <acronym>GIF</acronym> images on the web,
|
||||
while in any pages which you design, use the open source <acronym>PNG</acronym>
|
||||
|
@ -18,7 +18,7 @@ graphics library.</para></sect3>
|
||||
|
||||
<sect3><title>libvgagl library</title>
|
||||
<para><filename class="libraryfile">libvgagl</filename> is a fast
|
||||
framebuffer-level graphics library based on libvga.</para></sect3>
|
||||
frame buffer level graphics library based on libvga.</para></sect3>
|
||||
|
||||
<sect3><title>dumpreg</title>
|
||||
<para><command>dumpreg</command> dumps the state of the card as the
|
||||
|
@ -12,7 +12,7 @@ you wish to utilize this feature change the switch to
|
||||
installed, the make install script enters into a configuration routine.
|
||||
The first test will be whether to install a boot script in the <filename
|
||||
class="directory">/etc/rc.d/init.d</filename> directory with the
|
||||
appropriate symbolic links in runlevels 2, 3, 4, and 5. The second is to
|
||||
appropriate symbolic links in run levels 2, 3, 4, and 5. The second is to
|
||||
stop any current fcron processes and start a new one. Since this is
|
||||
probably your first install and we want a boot script based upon the
|
||||
<acronym>BLFS</acronym> template we answer 'n' to both tests.</para>
|
||||
|
@ -7,10 +7,11 @@
|
||||
make install</command></userinput></screen>
|
||||
|
||||
<para>Note that by default, <command>hdparm</command> is installed in
|
||||
<filename>/sbin</filename> as some systems may require it on bootup
|
||||
before <filename>/usr</filename> is mounted. If you wish to install
|
||||
<command>hdparm</command> under the <filename>/usr</filename> hierarchy, then replace the
|
||||
above commands with the following:</para>
|
||||
<filename class="directory">/sbin</filename> as some systems may require it
|
||||
during the boot process before <filename class="directory">/usr</filename>
|
||||
is mounted. If you wish to install <command>hdparm</command> under the
|
||||
<filename class="directory">/usr</filename> hierarchy, then replace the above
|
||||
commands with the following:</para>
|
||||
|
||||
<screen><userinput><command>make &&
|
||||
make binprefix=/usr install</command></userinput></screen>
|
||||
|
@ -10,7 +10,7 @@
|
||||
|
||||
<sect3><title>libart_lgpl libraries</title>
|
||||
<para><filename class="libraryfile">libart_lgpl</filename> library is
|
||||
used as the antialiased rendering engine for
|
||||
used as the anti-aliased render engine for
|
||||
<application>libgnomecanvas</application>.</para></sect3>
|
||||
|
||||
</sect2>
|
||||
|
@ -27,8 +27,8 @@ what to type.</para></blockquote>
|
||||
|
||||
<para><ulink url="http://www.linuxfromscratch.org/">http://www.linuxfromscratch.org/</ulink></para>
|
||||
|
||||
<blockquote><para>This form of text is used for hyperlinks, both within the
|
||||
book and to external pages such as HowTo's, download locations,
|
||||
<blockquote><para>This form of text is used for hypertext links, both within
|
||||
the book and to external pages such as HowTo's, download locations,
|
||||
websites, etc.</para></blockquote>
|
||||
|
||||
<screen><userinput><command>cat > $LFS/etc/group << "EOF"</command>>
|
||||
|
@ -16,8 +16,8 @@ and <command>mpeg3toc</command> utilities.</para>
|
||||
suitable for editing and playback.</para></sect3>
|
||||
|
||||
<sect3><title>mpeg3cat</title>
|
||||
<para><command>mpeg3cat</command> concatenates elementary streams or demultiplexes a program
|
||||
stream.</para></sect3>
|
||||
<para><command>mpeg3cat</command> concatenates elementary streams or
|
||||
demultiplexes a program stream (separates components of the stream).</para></sect3>
|
||||
|
||||
<sect3><title>mpeg3dump</title>
|
||||
<para><command>mpeg3dump</command> dumps information or extracts audio
|
||||
|
@ -9,8 +9,9 @@ class="libraryfile">libogg</filename> libraries.</para>
|
||||
<sect2><title>Description</title>
|
||||
|
||||
<sect3><title>ogg libraries</title>
|
||||
<para><filename class="libraryfile">libogg</filename> libraries provide the functions for programs
|
||||
wishing to read or write <filename>OGG</filename> formatted bitstreams.</para>
|
||||
<para><filename class="libraryfile">libogg</filename> libraries provide the
|
||||
functions for programs wishing to read or write <filename>OGG</filename>
|
||||
formatted bit streams.</para>
|
||||
</sect3>
|
||||
|
||||
|
||||
|
@ -3,7 +3,7 @@
|
||||
|
||||
<para>The <application>libogg</application> package contains the Ogg file
|
||||
structure. This is useful for creating (encoding) or playing (decoding) a
|
||||
single physical bitstream.</para>
|
||||
single physical bit stream.</para>
|
||||
|
||||
<sect3><title>Package information</title>
|
||||
<itemizedlist spacing='compact'>
|
||||
|
@ -11,6 +11,6 @@ the <userinput>Simple DirectMedia Layer</userinput>.</para>
|
||||
<sect3><title>Simple DirectMedia Layer</title>
|
||||
<para>The Simple DirectMedia Layer is a generic <acronym>API</acronym> that
|
||||
provides low level access to audio, keyboard, mouse, joystick, 3D hardware via
|
||||
OpenGL, and 2D framebuffer across multiple platforms.</para></sect3>
|
||||
OpenGL, and 2D frame buffer across multiple platforms.</para></sect3>
|
||||
|
||||
</sect2>
|
||||
|
@ -30,8 +30,8 @@ of <application>transcode</application>.</para></sect3>
|
||||
and <acronym>PCM</acronym> audio stream.</para></sect3>
|
||||
|
||||
<sect3><title>tcdemux</title>
|
||||
<para><command>tcdemux</command> demultiplexes audio/video input that contains
|
||||
multiple streams, e.g. <acronym>VOB</acronym> files.</para></sect3>
|
||||
<para><command>tcdemux</command> demultiplexes (separates) audio/video input
|
||||
that contains multiple streams, e.g. <acronym>VOB</acronym> files..</para></sect3>
|
||||
|
||||
<sect3><title>tcextract</title>
|
||||
<para><command>tcextract</command> grabs single streams from a file containing
|
||||
@ -76,7 +76,7 @@ synchronizing of audio and video data signal.</para></sect3>
|
||||
number of plugins to convert audio and video input to
|
||||
<filename>RAW</filename> format, process <filename>RAW</filename> video and
|
||||
audio and convert <filename>RAW</filename> audio and video to other formats to
|
||||
be written into a filetype of choice. Read the documentation.</para></sect3>
|
||||
be written into a file type of choice. Read the documentation.</para></sect3>
|
||||
|
||||
</sect2>
|
||||
|
||||
|
@ -22,11 +22,13 @@ following line.</para>
|
||||
|
||||
<para>In the above line, replace
|
||||
<filename>/dev/hd<replaceable>XX</replaceable></filename> by the
|
||||
partition (e.g. <filename>/dev/hda2</filename>), <filename class="directory">
|
||||
/mnt_point</filename> by the mount point (e.g. <filename>/home</filename>). The
|
||||
<option>0</option> in the last field ensures that the partition will not be checked for
|
||||
consistency during bootup by the checkfs script. You may replace the ext3 fs
|
||||
type in the above by auto if you want to ensure that the partition is mounted
|
||||
partition (e.g. <filename>/dev/hda2</filename>),
|
||||
<filename class="directory">/mnt_point</filename> by the mount point (e.g.
|
||||
<filename class="directory">/home</filename>). The <option>0</option> in the
|
||||
last field ensures that the partition will not be checked for
|
||||
consistency during the boot process by the <command>checkfs</command> script.
|
||||
You may replace the <option>ext3</option> fs type in the above by
|
||||
<option>auto</option> if you want to ensure that the partition is mounted
|
||||
if you accidentally skip enabling the ext3 support in the kernel.</para>
|
||||
|
||||
<para>For each partition that you have converted to ext3 in <filename>
|
||||
|
@ -97,11 +97,11 @@ iptables -A OUTPUT -p icmp --icmp-type 3 -j ACCEPT</screen></para></listitem>
|
||||
<!--</orderedlist>-->
|
||||
|
||||
<para>These are only examples to show you some of the capabilities of the new
|
||||
firewalling-code in Linux-Kernel 2.4. Have a look at the man page of
|
||||
firewall code in Linux-Kernel 2.4. Have a look at the man page of
|
||||
iptables.
|
||||
There you will find more of them. The port-numbers you'll need for this
|
||||
can be found in <filename>/etc/services</filename>, in case you didn't
|
||||
find them by trial and error in your logfile.</para>
|
||||
find them by trial and error in your log file.</para>
|
||||
|
||||
<para>If you add any of your offered or accessed services such as the above,
|
||||
maybe even in FORWARD and for intranet-communication, and delete the
|
||||
|
@ -9,15 +9,15 @@ DOCUMENT.</emphasis></para> -->
|
||||
firewall - it is not a complete guide to securing systems. Firewalling
|
||||
is a complex issue that requires careful configuration.
|
||||
The scripts quoted here are simply intended to give examples as to how
|
||||
firewalling works, they are not intended to fit into any imaginable
|
||||
a firewall works, they are not intended to fit into any imaginable
|
||||
configuration and may not prevent any imaginable attack.</para>
|
||||
|
||||
<para>The purpose of this text is simply to give you a hint on how to get
|
||||
started with firewalling.</para>
|
||||
started with a firewall.</para>
|
||||
|
||||
<para>Customization of these scripts for your specific situation will
|
||||
be necessary for an optimal configuration, but you should make a serious
|
||||
study of the iptables documentation and firewalling in general before hacking
|
||||
study of the iptables documentation and creating firewalls in general before hacking
|
||||
away. Have a look at the list of <xref linkend="postlfs-security-fw-library"/> at the end
|
||||
of this section for more details. Here you will find a list of URLs that
|
||||
contain quite comprehensive information about building your own firewall.</para>
|
||||
|
@ -10,7 +10,7 @@ of failure, but it can make the administrators life a lot easier.</para>
|
||||
on every machine was perfectly configured and was immune to, e.g.,
|
||||
buffer-overflows and any other imaginable problem regarding its
|
||||
security, and where you trusted every user accessing your services
|
||||
to aim no harm, you wouldn't need to do firewalling!
|
||||
to aim no harm, you wouldn't need to do have a firewall!
|
||||
In the real world however, daemons may be misconfigured,
|
||||
exploits against essential services are freely available, you
|
||||
may wish to choose which services are accessible by certain machines,
|
||||
@ -48,7 +48,7 @@ broadband links.</para></sect3>
|
||||
<para>This is a box placed between the Internet and an intranet.
|
||||
To minimize the risk of compromising the firewall itself it
|
||||
should generally have only one role, that of protecting the intranet.
|
||||
Although not completely riskless, the tasks of doing the routing
|
||||
Although not completely risk free, the tasks of doing the routing
|
||||
and eventually IP masquerading (rewriting IP-headers
|
||||
of the packets it routes from clients with private IP-addresses onto
|
||||
the Internet so that they seem to come from the firewall
|
||||
|
@ -1,9 +1,9 @@
|
||||
<sect2 id="postlfs-security-fw-kernel" xreflabel="getting a firewalling-enabled Kernel">
|
||||
<title>Getting a firewalling-enabled Kernel</title>
|
||||
<title>Getting a firewall enabled Kernel</title>
|
||||
|
||||
<para>If you want your Linux-Box to do firewalling you must first ensure
|
||||
<para>If you want your Linux-Box to have a firewall, you must first ensure
|
||||
that your kernel has been compiled with the relevant options turned on
|
||||
<!-- <footnote><para>If you needed assistance howto configure, compile and install
|
||||
<!-- <footnote><para>If you needed assistance how to configure, compile and install
|
||||
a new kernel, refer back to chapter VIII of the LinuxFromScratch book,
|
||||
<ulink url="http://www.linuxfromscratch.org/view/3.1/chapter08/kernel.html">Installing a kernel</ulink>
|
||||
and eventually
|
||||
@ -32,7 +32,7 @@ that the modules need to be loaded at first.</para>
|
||||
|
||||
<!--
|
||||
<table frame='none'>
|
||||
<title>Essential config-options for a firewalling-enabled Kernel</title>
|
||||
<title>Essential config-options for a firewall enabled Kernel</title>
|
||||
|
||||
<tgroup cols='5'>
|
||||
<colspec colnum='1' colwidth='8*' align='center'/>
|
||||
@ -121,7 +121,7 @@ ipfw-adm (2.0-style) support</userinput></literallayout></entry>
|
||||
<entry></entry>
|
||||
<entry><userinput>Fast switching</userinput></entry>
|
||||
<entry>Make sure to disable it because it would setup a bypass around
|
||||
your firewalling-rules.</entry>
|
||||
your firewall rules.</entry>
|
||||
<entry>w\</entry>
|
||||
<entry>CONFIG_NET_FASTROUTE</entry>
|
||||
</row>
|
||||
|
@ -1,5 +1,5 @@
|
||||
<sect3 id="postlfs-security-fw-library" xreflabel="Links for further reading">
|
||||
<title>Where to start with further reading on firewalling.</title>
|
||||
<title>Where to start with further reading on firewalls.</title>
|
||||
|
||||
<para><blockquote><literallayout>
|
||||
<ulink url="http://www.netfilter.org/">www.netfilter.org - Homepage of the netfilter/iptables project</ulink>
|
||||
|
@ -25,8 +25,8 @@ echo "to be a reference."
|
||||
echo "Firewall security is a complex issue, that exceeds the scope"
|
||||
echo "of the quoted configuration rules."
|
||||
echo "You can find some quite comprehensive information"
|
||||
echo "about firewalling in Chapter 4 of the BLFS book."
|
||||
echo "http://beyond.linuxfromscratch.org/"
|
||||
echo "about firewalls in Chapter 4 of the BLFS book."
|
||||
echo "http://www.linuxfromscratch.org/blfs"
|
||||
echo
|
||||
|
||||
# Insert iptables modules (not needed if built into the kernel).
|
||||
|
@ -1,7 +1,7 @@
|
||||
<sect3 id="postlfs-security-fw-stop" xreflabel="/etc/rc.d/init.d/firewall.stop">
|
||||
<title>firewall.stop</title>
|
||||
|
||||
<para>If you need to turn firewalling off, this script will do it:</para>
|
||||
<para>If you need to turn the firewall off, this script will do it:</para>
|
||||
|
||||
<screen><userinput><command>cat > /etc/rc.d/init.d/firewall.stop << "EOF"</command>
|
||||
#!/bin/sh
|
||||
|
@ -2,13 +2,13 @@
|
||||
<?dbhtml filename="iptables.html" dir="postlfs"?>
|
||||
<title>iptables-&iptables-version;</title>
|
||||
|
||||
<para>The next part of this chapter deals with firewalling. The
|
||||
principle firewalling tool for Linux, as of the 2.4 kernel series, is
|
||||
<para>The next part of this chapter deals with firewalls. The
|
||||
principle firewall tool for Linux, as of the 2.4 kernel series, is
|
||||
<application>iptables</application>. It replaces
|
||||
<application>ipchains</application> from the 2.2 series and
|
||||
<application>ipfwadm</application> from the
|
||||
2.0 series. You will need to install <application>iptables</application> if
|
||||
you intend on using any form of firewalling.</para>
|
||||
you intend on using any form of a firewall.</para>
|
||||
|
||||
&iptables-intro;
|
||||
&iptables-inst;
|
||||
|
@ -1,7 +1,7 @@
|
||||
<sect2>
|
||||
<title>Introduction to <application>iptables</application></title>
|
||||
|
||||
<para>To use firewalling, as well as installing
|
||||
<para>To use a firewall, as well as installing
|
||||
<application>iptables</application>, you will need
|
||||
to configure the relevant options into your kernel. This is discussed
|
||||
in the next part of this chapter - <xref linkend="postlfs-security-fw-kernel"/>.</para>
|
||||
|
@ -9,7 +9,7 @@ avoid the default of <filename class="directory">/usr/etc</filename>.</para>
|
||||
class="directory">/usr/libexec</filename>.</para>
|
||||
|
||||
<para><option>--enable-ldbm</option>: Build <command>slapd</command>
|
||||
with primary database backend using either <application>Berkeley
|
||||
with primary database back end using either <application>Berkeley
|
||||
DB</application> or
|
||||
<application><acronym>GNU</acronym> Database Manager</application>.</para>
|
||||
|
||||
|
@ -146,9 +146,7 @@ the second layout is active.</para>
|
||||
<para><command>xdm</command> provides a graphical logon capability and is
|
||||
normally set up in <filename>/etc/inittab</filename>. Most of the information
|
||||
you need to customize <command>xdm</command> is found in its man page. To
|
||||
execute <command>xdm</command> during bootup, change the initdefault level to 5 and
|
||||
add the following lines to
|
||||
<filename>/etc/inittab</filename>:</para>
|
||||
execute <command>xdm</command> during bootup, change the initdefault level to 5 and add the following lines to <filename>/etc/inittab</filename>:</para>
|
||||
|
||||
<para><screen><userinput># Run xdm as a separate service
|
||||
x:5:respawn:/usr/X11R6/bin/xdm -nodaemon</userinput></screen></para>
|
||||
|
@ -35,7 +35,7 @@ cd ..</command></userinput></screen>
|
||||
<screen><userinput><command>./bootstrap &&
|
||||
bash -c "source LinuxIntelEnv.Set.sh; dmake"</command></userinput></screen>
|
||||
|
||||
<para>If you have downloaded localized helpcontent zip files, you will need
|
||||
<para>If you have downloaded localized help content zip files, you will need
|
||||
to unzip them to the appropriate directory as mentioned below and then recreate
|
||||
the installation set.</para>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user