git://git.onelab.eu
/
bootcd.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
3f2f2bf
)
fix grammar errors
author
Aaron Klingaman
<alk@cs.princeton.edu>
Fri, 18 Nov 2005 18:39:54 +0000
(18:39 +0000)
committer
Aaron Klingaman
<alk@cs.princeton.edu>
Fri, 18 Nov 2005 18:39:54 +0000
(18:39 +0000)
documentation/bootcd-tech-doc.xml
patch
|
blob
|
history
diff --git
a/documentation/bootcd-tech-doc.xml
b/documentation/bootcd-tech-doc.xml
index
1f18f12
..
bb4d78b
100644
(file)
--- a/
documentation/bootcd-tech-doc.xml
+++ b/
documentation/bootcd-tech-doc.xml
@@
-66,7
+66,7
@@
<title>Basic Operation</title>
<para>The operation of the boot cd, when a machine is started off of one,
<title>Basic Operation</title>
<para>The operation of the boot cd, when a machine is started off of one,
- is fairly straight
forward. Essentially, it loads a l
inux kernel,
+ is fairly straight
forward. Essentially, it loads a L
inux kernel,
configures the hardware and network, and fetches a signed script to
execute. This generic operation allows for the boot cds to be used for any
number of operations, whether they are installing machines or debug
configures the hardware and network, and fetches a signed script to
execute. This generic operation allows for the boot cds to be used for any
number of operations, whether they are installing machines or debug
@@
-96,7
+96,7
@@
<orderedlist>
<listitem>
<para>The boot cd should be immutable. At any point, a PlanetLab
<orderedlist>
<listitem>
<para>The boot cd should be immutable. At any point, a PlanetLab
- administator should be able to reboot a machine into a known safe
+ administ
r
ator should be able to reboot a machine into a known safe
environment to inspect or debug the node.</para>
</listitem>
environment to inspect or debug the node.</para>
</listitem>
@@
-114,7
+114,7
@@
<para>Accomplishing 1. is fairly easy: simply require the cds to be burned
onto a write once media. Once that is accomplished, it is up to local site
<para>Accomplishing 1. is fairly easy: simply require the cds to be burned
onto a write once media. Once that is accomplished, it is up to local site
- administators to ensure physical security of the node so the cd is not
+ administ
r
ators to ensure physical security of the node so the cd is not
switched out. Further work may be done by executed scripts to validate a
boot cd, if necessary (though not currently implemented).</para>
switched out. Further work may be done by executed scripts to validate a
boot cd, if necessary (though not currently implemented).</para>
@@
-126,7
+126,7
@@
scripts on the cd can ensure they are contacting a PlanetLab boot server,
and not someone attempting to spoof one.</para>
scripts on the cd can ensure they are contacting a PlanetLab boot server,
and not someone attempting to spoof one.</para>
- <para>Number is
is
accomplished through the use of GPG public and private
+ <para>Number is accomplished through the use of GPG public and private
keys. There exists at PlanetLab Central a GPG private key that is used to
sign the scripts downloaded and executed by the cd. The public key is
located on the cd, and used to validate the signatures of the packages
keys. There exists at PlanetLab Central a GPG private key that is used to
sign the scripts downloaded and executed by the cd. The public key is
located on the cd, and used to validate the signatures of the packages
@@
-143,7
+143,7
@@
process, the script sources/merge_hw_table.py from the bootmanager
repository is invoked to create a lookup table to map PCI ids onto kernel
modules. For more information about how this script operates, consult the
process, the script sources/merge_hw_table.py from the bootmanager
repository is invoked to create a lookup table to map PCI ids onto kernel
modules. For more information about how this script operates, consult the
- BootMan
ga
er technical documentation.</para>
+ BootMan
ag
er technical documentation.</para>
</section>
<section>
</section>
<section>
@@
-186,8
+186,8
@@
</listitem>
</orderedlist>
</listitem>
</orderedlist>
- <para>The default configuration buil
d
above produces a boot cd that is
- configured to contact the primar
il
y PlanetLab boot servers. To build a
+ <para>The default configuration buil
t
above produces a boot cd that is
+ configured to contact the primary PlanetLab boot servers. To build a
custom boot cd that contacts a different server, with a different SSL
certificate and GPG key, you will need to create a custom
configuration:</para>
custom boot cd that contacts a different server, with a different SSL
certificate and GPG key, you will need to create a custom
configuration:</para>
@@
-247,8
+247,8
@@
<listitem>
<para>ROOT_PASSWORD</para>
<listitem>
<para>ROOT_PASSWORD</para>
- <para>The
crypted password to use for the root account on the boot
- cd. Only applies to the boot cd, not the root account on an
+ <para>The
encrypted password to use for the root account on the
+
boot
cd. Only applies to the boot cd, not the root account on an
installed and fully running node.</para>
</listitem>
installed and fully running node.</para>
</listitem>
@@
-288,8
+288,8
@@
<listitem>
<para>PRIMARY_SERVER_GPG / BACKUP_SERVER_GPG</para>
<listitem>
<para>PRIMARY_SERVER_GPG / BACKUP_SERVER_GPG</para>
- <para>The GPG public key(s) of the private key(s)
. that was used
-
to
sign the script that will be returned by PRIMARY_SERVER_PATH or
+ <para>The GPG public key(s) of the private key(s)
that was used to
+ sign the script that will be returned by PRIMARY_SERVER_PATH or
BACKUP_SERVER_PATH</para>
</listitem>
BACKUP_SERVER_PATH</para>
</listitem>