summaryrefslogtreecommitdiff
path: root/nl/boot-installer
diff options
context:
space:
mode:
authorSamuel Thibault <sthibault@debian.org>2010-09-16 22:09:05 +0000
committerSamuel Thibault <sthibault@debian.org>2010-09-16 22:09:05 +0000
commit5abaf8b8372e1937b1056785c6c38d41aa4347bc (patch)
treeba212a08f2e050b9cf98553083f18d1f400b3df4 /nl/boot-installer
parentdf6b242e0739fe779115bbb0664320d947725082 (diff)
downloadinstallation-guide-5abaf8b8372e1937b1056785c6c38d41aa4347bc.zip
Drop a few section from non-Linux archs.
Diffstat (limited to 'nl/boot-installer')
-rw-r--r--nl/boot-installer/parameters.xml8
-rw-r--r--nl/boot-installer/trouble.xml4
2 files changed, 6 insertions, 6 deletions
diff --git a/nl/boot-installer/parameters.xml b/nl/boot-installer/parameters.xml
index 631584476..71243ade1 100644
--- a/nl/boot-installer/parameters.xml
+++ b/nl/boot-installer/parameters.xml
@@ -2,7 +2,7 @@
<!-- original version: 62899 untranslated -->
<sect1 id="boot-parms"><title>Boot Parameters</title>
-<para>
+<para arch="linux-any">
Boot parameters are Linux kernel parameters which are generally used
to make sure that peripherals are dealt with properly. For the most
@@ -16,7 +16,7 @@ boot parameters (i.e., don't try setting parameters) and see if it works
correctly. It probably will. If not, you can reboot later and look for
any special parameters that inform the system about your hardware.
-</para><para>
+</para><para arch="linux-any">
Information on many boot parameters can be found in the
<ulink url="http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html"> Linux
@@ -25,7 +25,7 @@ section contains only a sketch of the most salient parameters. Some
common gotchas are included below in
<xref linkend="boot-troubleshooting"/>.
-</para><para>
+</para><para arch="linux-any">
When the kernel boots, a message
@@ -43,7 +43,7 @@ suffixed with <quote>k</quote> for kilobytes, or <quote>m</quote> for
megabytes. For example, both <userinput>mem=65536k</userinput> and
<userinput>mem=64m</userinput> mean 64MB of RAM.
-</para><para condition="supports-serial-console">
+</para><para arch="linux-any" condition="supports-serial-console">
If you are booting with a serial console, generally the kernel will
autodetect this.
diff --git a/nl/boot-installer/trouble.xml b/nl/boot-installer/trouble.xml
index 6a1404331..b28cd1834 100644
--- a/nl/boot-installer/trouble.xml
+++ b/nl/boot-installer/trouble.xml
@@ -68,7 +68,7 @@ at high speeds using a modern CD writer.
<listitem><para>
If your system boots correctly from the CD-ROM, it does not necessarily
-mean that Linux also supports the CD-ROM (or, more correctly, the controller
+mean that &arch-kernel; also supports the CD-ROM (or, more correctly, the controller
that your CD-ROM drive is connected to).
</para></listitem>
@@ -131,7 +131,7 @@ detected, sometimes simply trying again may solve the problem. If you have
more than one CD-ROM drive, try changing the CD-ROM to the other drive.
If that does not work or if the CD-ROM is recognized but there are errors
when reading from it, try the suggestions listed below. Some basic knowledge
-of Linux is required for this.
+of &arch-kernel; is required for this.
To execute any of the commands, you should first switch to the second
virtual console (VT2) and activate the shell there.