summaryrefslogtreecommitdiff
path: root/nl/appendix
diff options
context:
space:
mode:
Diffstat (limited to 'nl/appendix')
-rw-r--r--nl/appendix/files.xml20
-rw-r--r--nl/appendix/plip.xml6
-rw-r--r--nl/appendix/preseed.xml23
3 files changed, 29 insertions, 20 deletions
diff --git a/nl/appendix/files.xml b/nl/appendix/files.xml
index 481a28aec..ea39f0903 100644
--- a/nl/appendix/files.xml
+++ b/nl/appendix/files.xml
@@ -1,18 +1,18 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 39463 untranslated -->
+<!-- original version: 39551 untranslated -->
<sect1 id="linuxdevices"><title>Linux Devices</title>
<para>
-In Linux you have various special files in
-<filename>/dev</filename>. These files are called device files. In
-the Unix world accessing hardware is different. There you have a
-special file which actually runs a driver which in turn accesses the
-hardware. The device file is an interface to the actual system
-component. Files under <filename>/dev</filename> also behave
-differently than ordinary files. Below are the most important device
-files listed.
+In Linux various special files can be found under the directory
+<filename>/dev</filename>. These files are called device files and
+behave unlike ordinary files. The most common types of device files
+are for block devices and character devices. These files are an
+interface to the actual driver (part of the Linux kernel) which in
+turn accesses the hardware. Another, less common, type of device file
+is the named <firstterm>pipe</firstterm>.
+The most important device files are listed in the tables below.
</para><para>
@@ -106,7 +106,7 @@ files listed.
<informaltable><tgroup cols="2"><tbody>
<row>
<entry><filename>null</filename></entry>
- <entry>Everything pointed to this device will disappear</entry>
+ <entry>Anything written to this device will disappear</entry>
</row><row>
<entry><filename>zero</filename></entry>
<entry>One can endlessly read zeros out of this device</entry>
diff --git a/nl/appendix/plip.xml b/nl/appendix/plip.xml
index 9c1532cba..a6b5361ba 100644
--- a/nl/appendix/plip.xml
+++ b/nl/appendix/plip.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 39614 untranslated -->
+<!-- original version: 39644 untranslated -->
<sect1 id="plip" arch="x86">
<title>Installing &debian; over Parallel Line IP (PLIP)</title>
@@ -100,7 +100,7 @@ echo 1 > /proc/sys/net/ipv4/ip_forward
Boot the installation media. The installation needs to be run in
expert mode; enter <userinput>expert</userinput> at the boot prompt.
-If you need to set paramenters for kernel modules, you also need to
+If you need to set parameters for kernel modules, you also need to
do this at the boot prompt. For example, to boot the installer and
set values for the <quote>io</quote> and <quote>irq</quote> options
for the parport_pc module, enter the following at the boot prompt:
@@ -117,7 +117,7 @@ the installation.
<orderedlist>
<listitem><para>
-<guimenuitem>Load installer components</guimenuitem>
+<guimenuitem>Load installer components from CD</guimenuitem>
</para><para>
diff --git a/nl/appendix/preseed.xml b/nl/appendix/preseed.xml
index d24188876..85113571c 100644
--- a/nl/appendix/preseed.xml
+++ b/nl/appendix/preseed.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 39468 untranslated -->
+<!-- original version: 40460 untranslated -->
<!--
Be carefull with the format of this file as it is parsed to generate
@@ -458,7 +458,7 @@ There are a few rules to keep in mind when writing a preconfiguration file.
<listitem><para>
Most questions need to be preseeded using the values valid in English and
not the translated values. However, there are some questions (for example
- in <classname>partman</classname> where the translated values need to be
+ in <classname>partman</classname>) where the translated values need to be
used.
</para></listitem>
<listitem><para>
@@ -739,11 +739,18 @@ correct one will be selected before using preseeding.
# select Use the largest continuous free space
# Alternatively, you can specify a disk to partition. The device name can
-# be given in either devfs or traditional non-devfs format.
-# For example, to use the first disk devfs knows of:
+# be given in either devfs or traditional non-devfs format. If the method
+# supports it, you can specify several disks separated by spaces.
+# For example, to use the first disk:
d-i partman-auto/disk string /dev/discs/disc0/disc
-# Or, if you want to use LVM:
-#d-i partman-auto-lvm/disk string /dev/discs/disc0/disc
+# In addition, you'll need to specify the method to use.
+# The presently available methods are: "regular", "lvm" and "crypto"
+d-i partman-auto/method string lvm
+
+# If one of the disks that are going to be automatically partitioned
+# contains an old LVM configuration, the user will normally receive a
+# warning. This can be preseeded away...
+d-i partman-auto/purge_lvm_from_device boolean true
# You can choose from any of the predefined partitioning recipes.
# Note: this must be preseeded with a localized (translated) value.
@@ -928,9 +935,11 @@ d-i grub-installer/with_other_os boolean true
# Alternatively, if you want to install to a location other than the mbr,
# uncomment and edit these lines:
-#d-i grub-installer/bootdev string (hd0,0)
#d-i grub-installer/only_debian boolean false
#d-i grub-installer/with_other_os boolean false
+#d-i grub-installer/bootdev string (hd0,0)
+# To install grub to multiple disks:
+#d-i grub-installer/bootdev string (hd0,0) (hd1,0) (hd2,0)
</screen></informalexample>
</sect2>