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

- ispelled + small fixes

This commit is contained in:
malekith 2002-05-02 08:56:02 +00:00
parent 9fd0bb801d
commit 89c44b58e6
10 changed files with 87 additions and 92 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
LDP/guide/docbook/PLD-Guide/admin-manual/basics.xml
View File

@ -13,10 +13,10 @@
But two simple commands can be used instead:
<itemizedlist>
<listitem>
<para><command>halt</command> immediatelly runs shutdown procedure</para>
<para><command>halt</command> immediately runs shutdown procedure</para>
</listitem>
<listitem>
<para><command>reboot</command> immediatelly runs reboot procedure</para>
<para><command>reboot</command> immediately runs reboot procedure</para>
</listitem>
</itemizedlist>
On PC computers reboot can be also invoked by pressing Ctrl-Alt-Del sequence.

28
LDP/guide/docbook/PLD-Guide/admin-manual/netconfig.xml
View File

@ -18,8 +18,8 @@
<para>Written by Olgierd Pieczul</para>
</abstract>
<!-- tu powinien sie znalezc opis tego co jest w static-routes
(jest taki w dokumentacji rc-scripts (sysconfig.docb))
<!-- here should go description of what's in static-routes
(there is on in rc-scripts docs (sysconfig.docb))
-->
<para>
@ -89,7 +89,7 @@ from 10.0.1/24 to 10.2/16 fwmark 3 table 4 nat 10.3.0.1
A very convenient support for software VLANs (Virtual Local Area Network)
IEEE 802.1Q is provided by PLD rc-scripts.
Software VLANs are available both in 2.4 kernels, and 2.2 kernels from PLD.
<!-- sprawdzic! -->
<!-- check it out! -->
</para>
<para>
To be able to use VLAN, an extra software is necessary
@ -119,14 +119,6 @@ from 10.0.1/24 to 10.2/16 fwmark 3 table 4 nat 10.3.0.1
interface eth0 that must be also present in the directory.
</para>
</note>
<!--
Nie wiem czy zrozumialem dobrze jak to dziala /klakier
Tu jest oryginal
Podniesienie tego interfejsu spowoduje utworzenie vlanu 4 na interfejsie eth0 z odpowiednim
adresem. Kluczowa jest tutaj cyfra po kropce w linijce DEVICE, poniewaz to wlasnie ona mowi w jakim
VLANie bedzie interfejs.
-->
</section>
<section id="vlan-hardware">
<title>Hardware VLAN</title>
@ -161,15 +153,15 @@ VLANie bedzie interfejs.
<note>
<para>
It is <emphasis>not</emphasis> possible to simultaneously use eepro100 and e100 modules because
intel module, once loaded, immediatelly searches for
intel module, once loaded, immediately searches for
<emphasis>all</emphasis> installed cards.
</para>
</note>
<para>
Next step is to turn down all interaces based on Intel
Next step is to turn down all interfaces based on Intel
adapters if they are running. That can be done be stopping network subsystem
that (as described in <xref linkend="subsystems"/>),
or by stopping particular intefaces
or by stopping particular interfaces
(that can be found in <xref linkend="interfaces"/>).
Also remove old module, if it is still present (<command>rmmod eepro100</command>).
</para>
@ -277,7 +269,7 @@ VLANie bedzie interfejs.
<listitem>
<para>
Allows for sharing the load among 2-8 network cards, but only
primary receives and transmites packets.
primary receives and transmits packets.
</para>
</listitem>
</varlistentry>
@ -288,10 +280,10 @@ VLANie bedzie interfejs.
<listitem>
<para>
FEC*/LA/802.3ad (Cisco*'s Fast EtherChannel* Technology
(FEC)/Intel Link Aggregation lub IEEE 802.3ad Link Aggregation)
(FEC)/Intel Link Aggregation or IEEE 802.3ad Link Aggregation)
allows for collective work of 2-8 adapters in receiving/transmitting packets.
All cards must work with the same speed and the same duplex.
Aggregation must be supported by switch and spannig tree must be
Aggregation must be supported by switch and spanning tree must be
enabled.
</para>
</listitem>
@ -316,7 +308,7 @@ VLANie bedzie interfejs.
ianscfg -c ve0
</programlisting>
<para>Additionally, the team can handle VLANs on team.</para>
<!-- o co chodzi w powyzszym? -->
<!-- Hmm.. what does it mean? -->
</section>
</section>

20
LDP/guide/docbook/PLD-Guide/admin-manual/sysadm.xml
View File

@ -9,9 +9,9 @@
<section>
<title>Managing packages with <application>apt</application></title>
<para>
Apt is powerfull package installer/updater originally
Apt is powerful package installer/updater originally
written for Debian and its .deb package system, adapted for
RPM based systems by Conectiva people. Apt can be used to install
RPM based systems by Connectiva people. Apt can be used to install
packages from various sources (filesystem, cdrom, nfs, http).
Here the net method is described (ftp or http).
</para>
@ -56,7 +56,7 @@
<para>
Apt is very strict about dependencies.
If you had ever issued --force and --nodeps options to rpm program,
then you may get a lot of messages about broken dependecies
then you may get a lot of messages about broken dependencies
when you run apt first time. That means your rpm database is messy.
In that case it is wise to run
<command>apt-get check</command> to see more details and then
@ -69,7 +69,7 @@
<section>
<title>Managing packages with <application>poldek</application></title>
<para>
Poldek is batch-mode rpm package installer/udpater written
Poldek is batch-mode rpm package installer/updater written
by Pawel Gajda as a part of PLD installer.
It is software in beta stage.
</para>
@ -139,17 +139,17 @@ source=Primary PLD ftp server,ftp,ftp.pld.org.pl,/PLD-1.0/i586/PLD/,RPMS,inst</p
For more details see comments in initial wuch.conf.
</para>
<para>
Unfortunatelly, program is not very well documented (you may
Unfortunately, program is not very well documented (you may
find some docs in program sources), nevertheless
it has very simple and intuitive interface.
Simply type <command>wuch</command> and enjoy.
</para>
</section>
</section>
<section id="user-managment">
<section id="user-management">
<title>Managing users</title>
<para>
PLD provides both standart <command>useradd</command> command (from shadow package),
PLD provides both standard <command>useradd</command> command (from shadow package),
as well as interactive script <command>adduser</command> (from package adduser).
</para>
</section>
@ -195,7 +195,7 @@ source=Primary PLD ftp server,ftp,ftp.pld.org.pl,/PLD-1.0/i586/PLD/,RPMS,inst</p
LILO: pld runlevel=2
</programlisting>
Runlevel 1 can be specified with <literal>runlevel=1</literal> but also
with <literal>sigle</literal>.
with <literal>single</literal>.
</para>
<para>
Single mode is especially provided for system maintenance and
@ -222,7 +222,7 @@ source=Primary PLD ftp server,ftp,ftp.pld.org.pl,/PLD-1.0/i586/PLD/,RPMS,inst</p
When some serious error has been detected on root filesystem,
init scripts invoke "emergency shell" and expect administrator
to fix the problems manually.
Usuall reaction is using fsck program on root disk to check/repair disk data.
Usual reaction is using fsck program on root disk to check/repair disk data.
</para>
<para>
After problem has been fixed, shell should be closed (with <command>exit</command>)
@ -250,7 +250,7 @@ source=Primary PLD ftp server,ftp,ftp.pld.org.pl,/PLD-1.0/i586/PLD/,RPMS,inst</p
what bootloader should rc-boot use, and what are bootloader options,
this is specified in uniform way
in rc-boot config files instead of particular bootloader's config files.
Basic rc-boot behaviour is controlled by file
Basic rc-boot behavior is controlled by file
<filename>/etc/sysconfig/rc-boot/config</filename>.
To know what linux kernels or other systems should be available
at boot time, rc-boot needs also <quote>image description</quote>

10
LDP/guide/docbook/PLD-Guide/admin-manual/sysconfig.xml
View File

@ -27,7 +27,7 @@
<para>
Some devices (mainly disk interfaces)
need support at very very early stage of system boot-up.
Modules for these devices must be loade from
Modules for these devices must be loaded from
so-called <emphasis>initrd</emphasis>
(see more in <xref linkend="bootloaders"/>)
</para>
@ -98,7 +98,7 @@ scsi_hostadapter aic7xxx
<para>
The file <filename>/etc/inittab</filename> is read by
<command>init</command> process to control
system behaviour in particular runlevel. Full description
system behavior in particular runlevel. Full description
of this file can be found in
<citerefentry>
<refentrytitle>inittab</refentrytitle>
@ -169,7 +169,7 @@ ca::ctrlaltdel:/sbin/shutdown -t3 -r now
contains basic console settings.
</para>
<para>
After modyfying config file, issue
After modifying config file, issue
<programlisting>/etc/rc.d/init.d/console restart</programlisting>
if you want the changes to take effect.
</para>
@ -184,7 +184,7 @@ ca::ctrlaltdel:/sbin/shutdown -t3 -r now
<!-- (see <xref linkend="x-repeater"/>) -->
</para>
<para>
After modyfying config file, issue
After modifying config file, issue
<programlisting>/etc/rc.d/init.d/gpm restart</programlisting>
if you want the changes to take effect.
</para>
@ -206,7 +206,7 @@ ca::ctrlaltdel:/sbin/shutdown -t3 -r now
<title>system</title>
<para>
Its content is used by rc-scripts at very early stage of system bootup.
It contains some basic settings, e.g. system behaviour in case of kernel
It contains some basic settings, e.g. system behavior in case of kernel
panic, etc.
</para>
</section>

18
LDP/guide/docbook/PLD-Guide/concept.xml
View File

@ -6,9 +6,9 @@
PLD is a Linux distribution developed since 1998
mainly in Poland.
It is a product of bevy of Linux enthusiasts. We have
around 200 people expresing their interests in
developing PLD, however number of activelly working
developers is approximatlly 50.
around 200 people expressing their interests in
developing PLD, however number of actively working
developers is approximately 50.
</para>
<para>
PLD stands for PLD Linux Distribution.
@ -24,7 +24,7 @@
<orderedlist>
<listitem>
<para>
Packages very often comes in sensible
Packages very often come in reasonable
default configuration, with bunch
of useful patches applied -- that's
because packagers use packages
@ -57,7 +57,7 @@
for wide variety of languages. This includes such
"standard" things like C (three compilers available),
C++, Perl or Python, but also some less
standard things like two implementationsof SML and
standard things like two implementations of SML and
Prolog, OCaml with several utility programs and
libraries and even experimental compilers, like
Cyclone or Ksi. As with other packages they are often
@ -123,7 +123,7 @@
</listitem>
<listitem>
<para>
automatic system updates supported and ready, including restarting updated services, proper hadling of config files, even modified ones
automatic system updates supported and ready, including restarting updated services, proper handling of config files, even modified ones
</para>
</listitem>
<listitem>
@ -133,14 +133,14 @@
</listitem>
<listitem>
<para>
iproute2 as a basic tool for network interfaces manipulation. PLD runtime scripts are simplier and shorter then, offering larger functionality compared to RedHat. This version of initscripts can be easily localized, accordingly to the tastes of the user
iproute2 as a basic tool for network interfaces manipulation. PLD runtime scripts are simpler and shorter then, offering larger functionality compared to RedHat. This version of initscripts can be easily localized, accordingly to the tastes of the user
</para>
</listitem>
<listitem>
<para>
support for easy switching to alternative
authentication methods (and, if you need it,
cyphering) for network communication, such as
ciphering) for network communication, such as
PAM, GASPI, TSL/SSL etc. It's quite possible
that soon SASL will take the lead in
authentication systems. In practice this easy
@ -167,7 +167,7 @@
</listitem>
<listitem>
<para>
many different frequently repeated tasks can be automaticly done (with regards to current work methodology and package contents)
many different frequently repeated tasks can be automatically done (with regards to current work methodology and package contents)
</para>
</listitem>
</orderedlist>

17
LDP/guide/docbook/PLD-Guide/cvs.xml
View File

@ -3,11 +3,11 @@
<para>
All resources of PLD are kept in CVS repository. CVS is designed to
hold data with possibility of modification by many people (with
different access rights) allowing effective version control. Noone can
remove resources - they are only moved to other directory (to junkyard
different access rights) allowing effective version control. No one can
remove resources - they are only moved to other directory (to junk yard
:-). Also every version is being kept, so you can download distribution
in state from last month or last hour. Resources marked by STABLE flag
are being built by correct people with many different optimalization
are being built by correct people with many different optimization
(i386, i586, i686 etc.) and you can find them as rpm packages on
<link linkend="ftp">FTP</link> Server.
</para>
@ -93,10 +93,6 @@
<entry>Polish Manuals Translation
Project</entry>
</row>
<row>
<entry>LDP</entry>
<entry>linuxdoc.org project</entry>
</row>
<row>
<entry>shadow</entry>
<entry>Shadow passwords for
@ -106,7 +102,12 @@
</tgroup>
</table>
<para>
To dowload contents of some module you should use command:
There are also several other modules in PLD repo. Most of them
are open source project of PLD developers, more or less connected
with PLD itself. You can use CVSWeb to view complete list.
</para>
<para>
To download contents of some module you should use command:
</para>
<screen format="linespecific">
<prompt>bash$</prompt> <command>cvs -d :pserver:cvs@cvs.pld.org.pl:/cvsroot

70
LDP/guide/docbook/PLD-Guide/installer-theory.xml
View File

@ -79,7 +79,7 @@
<orderedlist>
<listitem>
<para>
they absorb user attention during all instalation time
they absorb user attention during all installation time
</para>
</listitem>
<listitem>
@ -94,11 +94,11 @@
</listitem>
</orderedlist>
Noniteractive installers (e.g kickstart from RH) do not have those
Noninteractive installers (e.g kickstart from RH) do not have those
disadvantages (they have others ;) ).
</para>
<para>
PLD installer will be basically noniteractive, but will also offer
PLD installer will be basically noninteractive, but will also offer
some additional interactive features. Nevertheless it is crucial to
be able to duplicate installation noninteractively.
</para>
@ -133,7 +133,7 @@
be performed automatically, without any user
intervention. Batch installer reads special file that
user prepared before. User can create this file in arbitrary way
althrough some facility is provided - it is text mode <emphasis>UI</emphasis>.
although some facility is provided - it is text mode <emphasis>UI</emphasis>.
Before the real installation starts, installer
validates the input file with <emphasis>validator</emphasis>.
</para>
@ -153,7 +153,7 @@
Separation of install / configure
</para>
<para>
UI+batch-installer are reponsible for
UI+batch-installer are responsible for
<emphasis>installation</emphasis>. <emphasis>Configuration</emphasis>
of newly installed box (either before or after first boot) is another piece
of cake.
@ -169,7 +169,7 @@
<listitem>
<para>
Installer system configuration (what modules to load, path to
source of distibution, sometimes also basic net config).
source of distribution, sometimes also basic net config).
It is stored in <filename>installer.conf</filename>
</para>
</listitem>
@ -211,14 +211,14 @@
Pre-setup of installer/box and one step batch installation
</para>
<para>
As regards specyfing configuration, as much as possible should be done
As regards specifying configuration, as much as possible should be done
before batch-installer is launched. Things like partitioning scheme and
set of packages to install should be possibly specified
before running batch installer.
</para>
<para>
Batch installer should be run once and do job with no user intevention
and without any qestions. Only exception is an error: in that case,
Batch installer should be run once and do job with no user intervention
and without any questions. Only exception is an error: in that case,
after fixing <filename>installer.conf</filename>,
batch-installer should be invoked once
again and be able to start working with the beginning
@ -246,7 +246,7 @@
filesystem). It is responsible for assisting user to
create good installer.conf, possibly checking and
validating as much as possible to increase the
probability of succesfull batch installation.</para>
probability of successful batch installation.</para>
</listitem>
<listitem>
<para>
@ -293,7 +293,7 @@
<term>source</term>
<listitem>
<para>
Source of distibution - a place where installer can find
Source of distribution - a place where installer can find
<emphasis>distribution</emphasis> and some special
<filename>.tar.gz</filename> packages used by installer.
Depending of the type of installation, source can be
@ -329,10 +329,10 @@
The whole installation process consists of several steps.
The general list is here, divided into stages, related
to avaliability of certain resources:
to availability of certain resources:
<variablelist>
<title>Stages of instalation</title>
<title>Stages of installation</title>
<varlistentry>
<term>Stage 1 (have <emphasis>initrd</emphasis> only)</term>
<listitem>
@ -404,7 +404,7 @@
on <emphasis>initrd</emphasis>.
I will call it <emphasis>bootdisk</emphasis>.</para>
<para>
Tools avaliable on bootdisk include:
Tools available on bootdisk include:
<itemizedlist>
<listitem>
<para>
@ -573,13 +573,13 @@
(if necessary), and finally loads modules and programs needed by installer-dest
(like reiserfs.o or mke2fs).</para>
<para>
After succesfull running, the installation is in Stage 2 (we have source, and
After successful running, the installation is in Stage 2 (we have source, and
can fetch additional packages from it).</para>
<note>
<para>
To save inird space, all modules that was on bootdisk initiall are deleted
from initrd after script succesfully get to the source you requested.
Therefore it is not possible to change source after you succesfully
To save initrd space, all modules that was on bootdisk initial are deleted
from initrd after script successfully get to the source you requested.
Therefore it is not possible to change source after you successfully
attach to the one selected.
</para>
</note>
@ -714,7 +714,7 @@
<para>
If the <literal>source</literal> is <quote>net</quote> or <quote>nfs</quote>
one must have at least one network device to get to source.
The device will be configured by installer (particulary
The device will be configured by installer (particularly
<command>installer-dest</command> script). Therefore some additional info
is necessary:
<variablelist>
@ -755,7 +755,7 @@
<listitem>
<para>
List of extra options to be given to <command>modprobe</command>
program, whe loading module, like <quote>irq=xx io=yy</quote>, etc.
program, when loading module, like <quote>irq=xx io=yy</quote>, etc.
</para>
</listitem>
</varlistentry>
@ -765,7 +765,7 @@
<term><literal>net_ipaddr</literal></term>
<listitem>
<para>
Addres of machine. May be static, like <quote>192.168.0.3</quote>
Address of machine. May be static, like <quote>192.168.0.3</quote>
or <quote>dhcp</quote>.
</para>
</listitem>
@ -812,7 +812,7 @@
<title>Dest</title>
<para>
Dest configuration consist of two parts: one is short, general
part, second consist of series of per-parition configurations.
part, second consist of series of per-partition configurations.
General part include:
<variablelist>
<varlistentry>
@ -873,10 +873,10 @@
<listitem>
<para>use_existing</para>
<para>
Use existing partions, do not create or delete anything.
Use existing partitions, do not create or delete anything.
You may choose to prepare disk "by hand" and then
run installer, or you may have disk already
paritioned correctly, then this option would be useful.
partitioned correctly, then this option would be useful.
</para>
</listitem>
</itemizedlist>
@ -892,14 +892,14 @@
<listitem>
<para>
Extra kernel modules needed to support dest_devices (or to source
if you are installing from SCSI cdrom or disk). It is space delimated
if you are installing from SCSI cdrom or disk). It is space decimated
list of modules to load. It can be also single word <literal>auto</literal>
which instructs the installer to automagicly detect it.
which instructs the installer to automagicaly detect it.
</para>
<para>
If you want to install <emphasis>from</emphasis> SCSI, you need to
make specialized bootdisk using <command>mkinstaller</command> command.
See appropiate section in this documentation.
See appropriate section in this documentation.
Installation <emphasis>to</emphasis> SCSI is supported out of the box.
</para>
</listitem>
@ -908,14 +908,14 @@
</variablelist>
The second part of dest specification is per-partition config.
Each partition config starts with <literal>dest_partX_</literal>
where X is number (1,2,3...). When specyfing multiple
where X is number (1,2,3...). When specifying multiple
partitions, be sure you did not missed any number (e.g 1,3,4),
because installer starts with 1 and processes subsequent numbers
until no variables are found for given number.
</para>
<para>
The X numbers are used only within installer to distinguish
configs. They are not related to partion numers within disks
configs. They are not related to partition numbers within disks
(e.g. /dev/hda2). Partition numbers that will be created by installer
are assigned automatically.
</para>
@ -939,7 +939,7 @@
<term><literal>dest_partX_device</literal></term>
<listitem>
<para>
Disk to put partion onto, e.g. <quote>/dev/hda</quote>. The disk must be
Disk to put partition onto, e.g. <quote>/dev/hda</quote>. The disk must be
already specified in in <literal>dist_devices</literal> list.
If the action for given disk is use_existing, proper partition number
must be specified too, e.g. <quote>/dev/hda1</quote>.
@ -1009,13 +1009,13 @@
<para>absolute value in megabytes, e.g. <quote>500</quote></para>
</listitem>
<listitem>
<para>part of all avaliable space (in percents), e.g. <quote>20% of all</quote></para>
<para>part of all available space (in percents), e.g. <quote>20% of all</quote></para>
</listitem>
<listitem>
<para>part of rest - space that left (in percents), e.g. <quote>100% of free</quote></para>
</listitem>
</itemizedlist>
If this partiton will not be created (existing one is used)
If this partition will not be created (existing one is used)
this variable is not recognized, and should be empty.
</para>
</listitem>
@ -1057,7 +1057,7 @@
<note>
<para>
stride=X ext2 option for RAID drives is computed
and added automagicly, unless specified here.
and added automagicaly, unless specified here.
</para>
</note>
</para>
@ -1105,7 +1105,7 @@
</varlistentry>
</variablelist>
List of packages to install is flat text file stored in
<filename>/etc/installer.pkgs</filename>. It can be easly created
<filename>/etc/installer.pkgs</filename>. It can be easily created
using UI and groups of packages.
</para>
</section>
@ -1168,7 +1168,7 @@
</listitem>
<listitem>
<para>Michal Moskal</para>
<para>Wrote fine <command>dml</command>, one of batch-installer architects, contibuted many parts of installer</para>
<para>Wrote fine <command>dml</command>, one of batch-installer architects, contributed many parts of installer</para>
</listitem>
<listitem>
<para>Sergiusz Pawlowicz</para>

8
LDP/guide/docbook/PLD-Guide/join.xml
View File

@ -6,8 +6,8 @@
If you decided to join PLD, you are welcome.
</para>
<para>
The first step is to subscribe developement e-lists.
You should obligatorily subscribe general discuss list and optionally
The first step is to subscribe development e-lists.
You should obligatory subscribe general discuss list and optionally
others.
</para>
</section>
@ -77,7 +77,9 @@
If you have already subscribed to devel e-list, and if
you have idea how to do something concrete, you can
ask for CVS Read-Write account by filling <ulink
url="http://linuxdoc.org/cvs/pld.html">the form</ulink>.
url="http://www.tldp.org/cvs/pld.html">the form</ulink>.
If you already know some members of PLD-team, you can
ask them to recommend you as a new developer.
</para>
</section>

2
LDP/guide/docbook/PLD-Guide/people/people.xml
View File

@ -3,7 +3,7 @@
<para>
PLD staff people are volunteers, who come mostly from Poland.
We are young (under 30th) system administrators, software
engineers, biotechnologists, phisicians &amp; students. We are making PLD
engineers, biotechnologists, physicians &amp; students. We are making PLD
Linux Distro for our pleasure, home and company needs. We are
really using it, every day.
</para>

2
LDP/guide/docbook/PLD-Guide/stylesheet/links.xml
View File

@ -1,4 +1,4 @@
<links>
<link>http://www.pld.org.pl/</link>
<link>http://www.pld.net.pl/</link>
<link>http://irc.pld.org.pl/</link>
</links>