summaryrefslogtreecommitdiff
path: root/it/using-d-i/modules/hppa/palo-installer.xml
diff options
context:
space:
mode:
Diffstat (limited to 'it/using-d-i/modules/hppa/palo-installer.xml')
-rw-r--r--it/using-d-i/modules/hppa/palo-installer.xml18
1 files changed, 14 insertions, 4 deletions
diff --git a/it/using-d-i/modules/hppa/palo-installer.xml b/it/using-d-i/modules/hppa/palo-installer.xml
index 84a3608e8..1b87006d0 100644
--- a/it/using-d-i/modules/hppa/palo-installer.xml
+++ b/it/using-d-i/modules/hppa/palo-installer.xml
@@ -1,20 +1,30 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 14602 untranslated -->
+<!-- original version: 14602 -->
- <sect3 arch="hppa">
- <title><command>palo</command>-installer</title>
+ <sect3 arch="hppa">
+ <!-- <title><command>palo</command>-installer</title> -->
+ <title><command>palo</command>-installer</title>
<para>
+<!--
The bootloader on PA-RISC is <quote>palo</quote>.
<command>PALO</command> is similar in configuration and usage to
<command>LILO</command>, with a few exceptions. First of all,
<command>PALO</command> allows you to boot any kernel image on your
boot partition. This is because <command>PALO</command> can actually
read Linux partitions.
+-->
+
+Il boot loader per PA-RISC <quote>palo</quote>. L'uso e la
+configurazione di <command>PALO</command> è molto simile a quella per
+<command>LILO</command> ma con alcune eccezioni. La prima è che
+<command>PALO</command> permette di avviare qualsiasi immagine del kernel
+presente nella partizione boot, questo perché <command>PALO</command>
+può leggere le partizioni Linux.
</para><para condition="FIXME">
hppa FIXME ( need more info )
</para>
- </sect3>
+ </sect3>