[Fai-commit] r5223 - in trunk: debian doc
lange at alioth.debian.org
lange at alioth.debian.org
Tue Dec 9 12:51:26 UTC 2008
Author: lange
Date: 2008-12-09 12:51:26 +0000 (Tue, 09 Dec 2008)
New Revision: 5223
Modified:
trunk/debian/changelog
trunk/doc/fai-guide.sgml
Log:
fai-cd.8, fai-guide.sgml
Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog 2008-12-09 12:15:53 UTC (rev 5222)
+++ trunk/debian/changelog 2008-12-09 12:51:26 UTC (rev 5223)
@@ -3,12 +3,12 @@
[ Thomas Lange ]
* fai-server.manpages: faimond-gui.1 was not included into the package
* fix typos in mkdebmirror, NEWS, classes_description.txt, fai-mirror,
- fai-cd.8
+ fai-cd.8, fai-guide.sgml
[ Colin Tuckley ]
* fixed spelling mistakes in fai-do-scripts.1, fai-mirror.1
- -- Thomas Lange <lange at debian.org> Tue, 09 Dec 2008 13:15:37 +0100
+ -- Thomas Lange <lange at debian.org> Tue, 09 Dec 2008 13:51:13 +0100
fai (3.2.14) unstable; urgency=low
Modified: trunk/doc/fai-guide.sgml
===================================================================
--- trunk/doc/fai-guide.sgml 2008-12-09 12:15:53 UTC (rev 5222)
+++ trunk/doc/fai-guide.sgml 2008-12-09 12:51:26 UTC (rev 5223)
@@ -9,8 +9,8 @@
<!entity faiver "3.2.14">
<!entity faiverdate "28 Oct 2008">
-<!entity version "2.8.2">
-<!entity date "27 Oct 2008">
+<!entity version "2.8.3">
+<!entity date "9 dec 2008">
<!entity faisetup system "entities/faisetup.sgml">
<!entity bootexample system "entities/bootexample.sgml">
@@ -256,7 +256,7 @@
<item> <p>Diskless client support</p> </item>
<item> <p>Easily add your own functions via hooks.</p> </item>
<item> <p>Easily change the default behavior via hooks.</p> </item>
- <!--MT: SVN/CVS config management, softupdates, dirinstall-->
+ <!--MT: SVN/CVS config management, softupdate, dirinstall-->
</list>
<chapt id=impatient>Quickstart - For the impatient user<p>
@@ -875,7 +875,7 @@
You will get a shell prompt and can look at the log files, for
examples <file>/live.log</file> or <file>/tmp/net-eth0.conf</file>.
<p>
-Use the following command on the isntall server to see which directories are exported
+Use the following command on the install server to see which directories are exported
from the install server (named faiserver):
<example>showmount -e faiserver</example>
@@ -1698,7 +1698,7 @@
The list of all defined classes is stored in the variable
<var>$classes</var> and saved to
<file>/tmp/fai/FAI_CLASSES</file>. The list of all classes is
-transfered to <prgn>cfengine</prgn>, so it can use them too. The
+transferred to <prgn>cfengine</prgn>, so it can use them too. The
script <file>10-base-classes</file> (below is a stripped version) is used to
define classes depending on the host name. First this script defines
the class with the name of the hardware architecture in uppercase
@@ -1834,7 +1834,7 @@
<file>/dev/hdb</file> and <file>/dev/sdb</file> and so on.
<p>
After <tt>disk_config</tt> one line containing the type, mount point
-and size is added for each partition on the harddisk. Mount options
+and size is added for each partition on the hard disk. Mount options
and additional parameters for <prgn>mke2fs</prgn> -- separated from
the mount options by a semicolon -- can be added.
@@ -2218,7 +2218,7 @@
hooks located in <var>$nfsroot</var><file>/fai/hooks</file> on the
install server. All other hooks are found in
<file>$FAI_CONFIGDIR/hooks</file> on the install server.
-<!--MT: what about softupdates?-->
+<!--MT: what about softupdate?-->
All hooks that are called before classes are defined can only use the
following classes: <tt>DEFAULT $HOSTNAME LAST</tt>. If a hook for
@@ -2328,7 +2328,7 @@
access the master node with the name <em>atom00</em>, which is a name
for the second network interface. The master server is also the
install server for the computing nodes. A local Debian mirror will be
-installed on the local harddisk. The home directories of all user
+installed on the local hard disk. The home directories of all user
accounts are also located on the master server. It will be exported via
NFS to all computing nodes. NIS will be used to distribute account,
host, and printer information to all nodes.
@@ -2677,7 +2677,7 @@
the FAI config).</p>
<sect1 id=aboutsoftupdate>How does a softupdate work?
-<p>Softupdates use the same configuration files as a new FAI installation. They
+<p>Softupdate use the same configuration files as a new FAI installation. They
even use the default FAI commands, so they behave <em>nearly</em> in
the same way as an installation, though some things are different:
<list>
@@ -2704,7 +2704,7 @@
</sect1>
<sect1 id=runsoftupdate>How to run a softupdate
-<p>As softupdates use the same infrastructure as a FAI installation, you even
+<p>As softupdate use the same infrastructure as a FAI installation, you even
start them by using the same command <manref name="fai" section="8"> which is used for
installation:
<example>
@@ -2712,7 +2712,7 @@
</example>
starts a softupdate.
-If you want to use softupdates on a system not installed with fai,
+If you want to use softupdate on a system not installed with fai,
the first time you need to run fai with the -N switch: <tt>fai -N softupdate</tt> - see <manref name="fai" section="8"> for details.
Make sure to set the variable <var>LOGSERVER</var> (done in a <tt>class/*.var</tt>
@@ -2740,8 +2740,8 @@
</sect2>
</sect1>
-<sect1 id=confsoftupdate>How to write a configuration suitable for softupdates
-<p>When you want to do softupdates, you have to be even more careful when
+<sect1 id=confsoftupdate>How to write a configuration suitable for softupdate
+<p>When you want to do softupdate, you have to be even more careful when
writing your configuration: it has to be <strong>idempotent</strong>, i.e.
running all the scripts twice should result in the same system configuration
as running them once. Some things to keep an eye on:
@@ -2762,11 +2762,11 @@
<taglist>
<tag><var>FAI_ROOT</var></tag>
<item>points to the client's rootdir.
- In case of softupdates: <tt>/</tt></item>
+ In case of softupdate: <tt>/</tt></item>
<tag><var>ROOTCMD</var></tag>
<item>contains a command for <tt>chrooting</tt>
into the client. This is empty when doing
- softupdates (as <tt>/</tt> is already our
+ softupdate (as <tt>/</tt> is already our
root...).</item>
<tag><var>FAI_ACTION</var></tag>
<item>contains the currently executed action:
@@ -2860,7 +2860,7 @@
command.
-You can calculate the IP subnet adress (which is used in
+You can calculate the IP subnet address (which is used in
&mfnc; for the variable <var>FAICLIENTS</var> by using
the nice tool ipcalc. Following example gives you the notation for a
class C network (16) when the server netork interface has the IP address
More information about the Fai-commit
mailing list