From 1ea73eea5ecc6a8ed901316049259aee737ee554 Mon Sep 17 00:00:00 2001
From: Joey Hess <joeyh@debian.org>
Date: Fri, 7 Oct 2005 19:51:38 +0000
Subject: move manual to top-level directory, split out of debian-installer
 package

---
 ca/using-d-i/modules/sparc/silo-installer.xml | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 ca/using-d-i/modules/sparc/silo-installer.xml

(limited to 'ca/using-d-i/modules/sparc')

diff --git a/ca/using-d-i/modules/sparc/silo-installer.xml b/ca/using-d-i/modules/sparc/silo-installer.xml
new file mode 100644
index 000000000..3ce2b6ac6
--- /dev/null
+++ b/ca/using-d-i/modules/sparc/silo-installer.xml
@@ -0,0 +1,25 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 24582 untranslated -->
+
+  <sect3 arch="sparc">
+  <title>Install the <command>SILO</command> Boot Loader
+         on a Hard Disk</title>
+<para>
+
+The standard &architecture; boot loader is called <quote>silo</quote>.
+It is documented in
+<filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is
+similar in configuration and usage to <command>LILO</command>, with
+a few exceptions. First of all, <command>SILO</command> allows you to
+boot any kernel image on your drive, even if it is not listed in
+<filename>/etc/silo.conf</filename>.  This is because
+<command>SILO</command> can actually read Linux partitions.  Also,
+<filename>/etc/silo.conf</filename> is read at boot time, so there is
+no need to rerun <command>silo</command> after installing a new kernel
+like you would with <command>LILO</command>. <command>SILO</command>
+can also read UFS partitions, which means it can boot SunOS/Solaris
+partitions as well. This is useful if you want to install GNU/Linux
+alongside an existing SunOS/Solaris install.
+
+</para>
+  </sect3>
-- 
cgit v1.2.3