From a292182f917a4104b223016e041410498f4d47a3 Mon Sep 17 00:00:00 2001
From: Jeroen Schot <schot@a-eskwadraat.nl>
Date: Wed, 29 Aug 2012 15:10:27 +0000
Subject: Restart Dutch translation of D-I manual in PO format.

---
 nl/using-d-i/modules/sparc/silo-installer.xml | 25 -------------------------
 1 file changed, 25 deletions(-)
 delete mode 100644 nl/using-d-i/modules/sparc/silo-installer.xml

(limited to 'nl/using-d-i/modules/sparc/silo-installer.xml')

diff --git a/nl/using-d-i/modules/sparc/silo-installer.xml b/nl/using-d-i/modules/sparc/silo-installer.xml
deleted file mode 100644
index 3ce2b6ac6..000000000
--- a/nl/using-d-i/modules/sparc/silo-installer.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-<!-- 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