summaryrefslogtreecommitdiff
path: root/en/preparing/bios-setup
diff options
context:
space:
mode:
Diffstat (limited to 'en/preparing/bios-setup')
-rw-r--r--en/preparing/bios-setup/s390.xml4
-rw-r--r--en/preparing/bios-setup/sparc.xml2
2 files changed, 4 insertions, 2 deletions
diff --git a/en/preparing/bios-setup/s390.xml b/en/preparing/bios-setup/s390.xml
index b65f25f14..a0cf8e648 100644
--- a/en/preparing/bios-setup/s390.xml
+++ b/en/preparing/bios-setup/s390.xml
@@ -8,8 +8,8 @@
In order to install &debian-gnu; on a &arch-title; or zSeries
machine you have first boot a kernel into the system. The boot
mechanism of this platform is inherently different to other ones,
-especially from PC-like systems: there are no floppy devices available
-at all. You will notice another big difference while you work with
+especially from PC-like systems, and
+you will notice a big difference while you work with
this platform: most (if not all) of the time you will work remote,
with the help of some client session software like telnet, or a
browser. This is due to that special system architecture where the
diff --git a/en/preparing/bios-setup/sparc.xml b/en/preparing/bios-setup/sparc.xml
index 7def315bc..a88c9fe1a 100644
--- a/en/preparing/bios-setup/sparc.xml
+++ b/en/preparing/bios-setup/sparc.xml
@@ -49,6 +49,7 @@ the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>.
</para><para>
+<!--
Typically, with newer revisions, you can use OpenBoot devices such as
<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>,
<quote>disk</quote>, or <quote>disk2</quote>. These have the obvious
@@ -75,6 +76,7 @@ whatever your revision, see the
<ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>.
</para><para>
+-->
To boot from a specific device, use the command <userinput>boot
<replaceable>device</replaceable></userinput>. You can set this