[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[CVS] di-docs/using-d-i/modules/sparc silo-installer.po,NONE,1.1

Update of /cvsroot/l10n-russian/di-docs/using-d-i/modules/sparc
In directory haydn:/tmp/cvs-serv11849/using-d-i/modules/sparc

Added Files:
Log Message:
add missing files....

--- NEW FILE: silo-installer.po ---
# Copyright (C) YEAR Free Software Foundation, Inc.
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: ENCODING\n"

#: silo-installer.xml:5
#, no-c-format
#. Tag: title
msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
msgstr ""

#: silo-installer.xml:7
#, no-c-format
#. Tag: para
msgid "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 along side an existing SunOS/Solaris install."
msgstr ""

Reply to: