[CVS] di-docs/install-methods automatic-install.po,1.8,1.9 boot-usb-files.po,1.3,1.4 create-floppy.po,1.3,1.4 install-methods.po,1.4,1.5 install-tftp.po,1.6,1.7

[Nikolai Prokoschenko <pronik-guest@alioth.debian.org>]

Update of /cvsroot/l10n-russian/di-docs/install-methods
In directory haydn:/tmp/cvs-serv22835/install-methods

Modified Files:
	automatic-install.po boot-usb-files.po create-floppy.po 
	install-methods.po install-tftp.po 
Log Message:
Автоматическая синхронизация шаблонов

Index: install-methods.po
===================================================================
RCS file: /cvsroot/l10n-russian/di-docs/install-methods/install-methods.po,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- install-methods.po	22 Sep 2004 15:55:13 -0000	1.4
+++ install-methods.po	18 Oct 2004 12:36:05 -0000	1.5
@@ -14,21 +14,14 @@
 "Content-Transfer-Encoding: 8bit\n"
 "X-Generator: KBabel 1.3.1\n"
 
-#. Tag: title
-#: install-methods.xml:5
-#, no-c-format
-msgid "Obtaining System Installation Media"
-msgstr "Получение носителя с дистрибутивом"
-
-#. Tag: chapter
-#: install-methods.xml:5
-#, no-c-format
-msgid ""
-"&official-cdrom.xml; &downloading-files.xml; &ipl-tape.xml; &create-floppy."
-"xml; &boot-usb-files.xml; &boot-drive-files.xml; &install-tftp.xml; "
-"&automatic-install.xml;"
-msgstr ""
-"&official-cdrom.xml; &downloading-files.xml; &ipl-tape.xml; &create-floppy."
-"xml; &boot-usb-files.xml; &boot-drive-files.xml; &install-tftp.xml; "
-"&automatic-install.xml;"
+#~ msgid "Obtaining System Installation Media"
+#~ msgstr "Получение носителя с дистрибутивом"
 
+#~ msgid ""
+#~ "&official-cdrom.xml; &downloading-files.xml; &ipl-tape.xml; &create-"
+#~ "floppy.xml; &boot-usb-files.xml; &boot-drive-files.xml; &install-tftp."
+#~ "xml; &automatic-install.xml;"
+#~ msgstr ""
+#~ "&official-cdrom.xml; &downloading-files.xml; &ipl-tape.xml; &create-"
+#~ "floppy.xml; &boot-usb-files.xml; &boot-drive-files.xml; &install-tftp."
+#~ "xml; &automatic-install.xml;"

Index: install-tftp.po
===================================================================
RCS file: /cvsroot/l10n-russian/di-docs/install-methods/install-tftp.po,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- install-tftp.po	16 Oct 2004 07:35:15 -0000	1.6
+++ install-tftp.po	18 Oct 2004 12:36:05 -0000	1.7
@@ -13,394 +13,3 @@
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: ENCODING\n"
-
-#. Tag: title
-#: install-tftp.xml:5
-#, no-c-format
-msgid "Preparing Files for TFTP Net Booting"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:6
-#, no-c-format
-msgid ""
-"If your machine is connected to a local area network, you may be able to "
-"boot it over the network from another machine, using TFTP. If you intend to "
-"boot the installation system from another machine, the boot files will need "
-"to be placed in specific locations on that machine, and the machine "
-"configured to support booting of your specific machine."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:14
-#, no-c-format
-msgid ""
-"You need to setup a TFTP server, and for many machines, a BOOTP server "
-"<phrase condition=\"supports-rarp\">, or RARP server</phrase> <phrase "
-"condition=\"supports-dhcp\">, or DHCP server</phrase>."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:20
-#, no-c-format
-msgid ""
-"<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
-"(RARP) is one way to tell your client what IP address to use for itself. "
-"Another way is to use the BOOTP protocol. </phrase> <phrase condition="
-"\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP "
-"address and where on the network to obtain a boot image. </phrase> <phrase "
-"arch=\"m68k\"> Yet another alternative exists on VMEbus systems: the IP "
-"address can be manually configured in boot ROM. </phrase> <phrase condition="
-"\"supports-dhcp\">The DHCP (Dynamic Host Configuration Protocol) is a more "
-"flexible, backwards-compatible extension of BOOTP. Some systems can only be "
-"configured via DHCP. </phrase>"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:37
-#, no-c-format
-msgid ""
-"For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
-"idea to use DHCP instead of BOOTP. Some of the latest machines are unable to "
-"boot using BOOTP."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:43
-#, no-c-format
-msgid ""
-"Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM "
-"console will <emphasis>not</emphasis> use RARP to obtain its IP address, and "
-"therefore you must use BOOTP for net booting your Alpha. You can also enter "
-"the IP configuration for network interfaces directly in the SRM console."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:52
-#, no-c-format
-msgid ""
-"Alpha systems can also be net-booted using the DECNet MOP (Maintenance "
-"Operations Protocol), but this is not covered here. Presumably, your local "
-"OpenVMS operator will be happy to assist you should you have some burning "
-"need to use MOP to boot Linux on your Alpha."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:60
-#, no-c-format
-msgid ""
-"Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. An "
-"RBOOTD package is available on the parisc-linux web site."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:65
-#, no-c-format
-msgid ""
-"The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
-"the client. Theoretically, any server, on any platform, which implements "
-"these protocols, may be used. In the examples in this section, we shall "
-"provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
-msgstr ""
-
-#. Tag: sect1
-#: install-tftp.xml:73
-#, no-c-format
-msgid "&tftp-rarp.xml; &tftp-bootp.xml; &tftp-dhcp.xml;"
-msgstr ""
-
-#. Tag: title
-#: install-tftp.xml:80
-#, no-c-format
-msgid "Enabling the TFTP Server"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:81
-#, no-c-format
-msgid ""
-"To get the TFTP server ready to go, you should first make sure that "
-"<command>tftpd</command> is enabled. This is usually enabled by having "
-"something like the following line in <filename>/etc/inetd.conf</filename>: "
-"<informalexample><screen>\n"
-"\n"
-"tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot\n"
-"\n"
-"</screen></informalexample> Debian packages will in general set this up "
-"correctly by default when they are installed."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:92
-#, no-c-format
-msgid ""
-"Look in that file and remember the directory which is used as the argument "
-"of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</"
-"userinput> argument enables some versions of <command>in.tftpd</command> to "
-"log all requests to the system logs; this is useful for diagnosing boot "
-"errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll "
-"have to notify the running <command>inetd</command> process that the file "
-"has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</"
-"userinput>; on other machines, find out the process ID for <command>inetd</"
-"command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></"
-"userinput>."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:106
-#, no-c-format
-msgid ""
-"To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you "
-"will need a TFTP server with <userinput>tsize</userinput> support. On a "
-"&debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</"
-"classname> packages qualify; we recommend <classname>tftpd-hpa</classname>."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:114
-#, no-c-format
-msgid ""
-"If you intend to install Debian on an SGI machine and your TFTP server is a "
-"GNU/Linux box running Linux 2.4, you'll need to set the following on your "
-"server: <informalexample><screen>\n"
-"\n"
-"echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
-"\n"
-"</screen></informalexample> to turn off Path MTU discovery, otherwise the "
-"Indy's PROM can't download the kernel. Furthermore, make sure TFTP packets "
-"are sent from a source port no greater than 32767, or the download will "
-"stall after the first packet. Again, it's Linux 2.4.X tripping this bug in "
-"the PROM, and you can avoid it by setting <informalexample><screen>\n"
-"\n"
-"echo \"2048 32767\" > /proc/sys/net/ipv4/ip_local_port_range\n"
-"\n"
-"</screen></informalexample> to adjust the range of source ports the Linux "
-"TFTP server uses."
-msgstr ""
-
-#. Tag: title
-#: install-tftp.xml:136
-#, no-c-format
-msgid "Move TFTP Images Into Place"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:137
-#, no-c-format
-msgid ""
-"Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
-"files\"/>, in the <command>tftpd</command> boot image directory. Generally, "
-"this directory will be <filename>/tftpboot</filename>. You'll have to make a "
-"link from that file to the file which <command>tftpd</command> will use for "
-"booting a particular client. Unfortunately, the file name is determined by "
-"the TFTP client, and there are no strong standards."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:147
-#, no-c-format
-msgid ""
-"On NewWorld Power Macintosh machines, you will need to set up the "
-"<command>yaboot</command> boot loader as the TFTP boot image. "
-"<command>Yaboot</command> will then retrieve the kernel and RAMdisk images "
-"via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</"
-"filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP "
-"directory."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:156
-#, no-c-format
-msgid ""
-"For PXE booting, everything you should need is set up in the "
-"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
-"tarball into the <command>tftpd</command> boot image directory. Make sure "
-"your dhcp server is configured to pass <filename>/pxelinux.0</filename> to "
-"<command>tftpd</command> as the filename to boot."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:164
-#, no-c-format
-msgid ""
-"For PXE booting, everything you should need is set up in the "
-"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
-"tarball into the <command>tftpd</command> boot image directory. Make sure "
-"your dhcp server is configured to pass <filename>/debian-installer/ia64/"
-"elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
-msgstr ""
-
-#. Tag: title
-#: install-tftp.xml:176
-#, no-c-format
-msgid "DECstation TFTP Images"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:177
-#, no-c-format
-msgid ""
-"For DECstations, there are tftpimage files for each subarchitecture, which "
-"contain both kernel and installer in one file. The naming convention is "
-"<replaceable>subarchitecture</replaceable>/netboot-boot.img. Copy the "
-"tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</"
-"userinput> if you work with the example BOOTP/DHCP setups described above."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:186
-#, no-c-format
-msgid ""
-"The DECstation firmware boots by TFTP with the command <userinput>boot "
-"<replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</"
-"replaceable> is the number of the TurboChannel device from which to boot. On "
-"most DECstations this is \"3\". If the BOOTP/DHCP server does not supply the "
-"filename or you need to pass additional parameters, they can optionally be "
-"appended with the following syntax:"
-msgstr ""
-
-#. Tag: userinput
-#: install-tftp.xml:198
-#, no-c-format
-msgid "boot #/tftp/filename param1=value1 param2=value2 ..."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:200
-#, no-c-format
-msgid ""
-"Several DECstation firmware revisions show a problem with regard to net "
-"booting: the transfer starts, but after some time it stops with an "
-"<computeroutput>a.out err</computeroutput>. This can have several reasons: "
-"<orderedlist> <listitem><para> The firmware does not respond to ARP requests "
-"during a TFTP transfer. This leads to an ARP timeout and the transfer stops. "
-"The solution is to add the MAC address of the Ethernet card in the "
-"DECstation statically to the ARP table of the TFTP server. This is done by "
-"running <userinput>arp -s <replaceable>IP-address</replaceable> "
-"<replaceable>MAC-address</replaceable></userinput> as root on the machine "
-"acting as TFTP server. The MAC-address of the DECstation can be read out by "
-"entering <command>cnfg</command> at the DECstation firmware prompt. </para></"
-"listitem> <listitem><para> The firmware has a size limit on the files that "
-"can be booted by TFTP. </para></listitem> </orderedlist> There are also "
-"firmware revisions that cannot boot via TFTP at all. An overview about the "
-"different firmware revisions can be found at the NetBSD web pages: <ulink "
-"url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\";></ulink>."
-msgstr ""
-
-#. Tag: title
-#: install-tftp.xml:238
-#, no-c-format
-msgid "Alpha TFTP Booting"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:239
-#, no-c-format
-msgid ""
-"On Alpha, you must specify the filename (as a relative path to the boot "
-"image directory) using the <userinput>-file</userinput> argument to the SRM "
-"<userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</"
-"userinput> environment variable. Alternatively, the filename can be given "
-"via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</"
-"userinput> directive). Unlike Open Firmware, there is <emphasis>no default "
-"filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a "
-"filename by either one of these methods."
-msgstr ""
-
-#. Tag: title
-#: install-tftp.xml:254
-#, no-c-format
-msgid "SPARC TFTP Booting"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:255
-#, no-c-format
-msgid ""
-"SPARC architectures for instance use the subarchitecture names, such as "
-"``SUN4M'' or ``SUN4C''; in some cases, the architecture is left blank, so "
-"the file the client looks for is just <filename>client-ip-in-hex</filename>. "
-"Thus, if your system subarchitecture is a SUN4C, and its IP is 192.168.1.3, "
-"the filename would be <filename>C0A80103.SUN4C</filename>. An easy way to "
-"determine this is to pull up a shell on another Unix machine and:"
-msgstr ""
-
-#. Tag: userinput
-#: install-tftp.xml:266
-#, no-c-format
-msgid "printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:267
-#, no-c-format
-msgid ""
-"if the machine's intended IP is 10.0.0.4. This will spit out the IP in "
-"hexadecimal; you will need to change all letters to uppercase and append the "
-"subarchitecture name if necessary, to get to the correct filename."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:273
-#, no-c-format
-msgid ""
-"You can also force some sparc systems to look for a specific file name by "
-"adding it to the end of the OpenPROM boot command, such as <userinput>boot "
-"net my-sparc.image</userinput>. This must still reside in the directory that "
-"the TFTP server looks in."
-msgstr ""
-
-#. Tag: title
-#: install-tftp.xml:284
-#, no-c-format
-msgid "BVM/Motorola TFTP Booting"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:285
-#, no-c-format
-msgid ""
-"For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to "
-"<filename>/tftpboot/</filename>."
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:290
-#, no-c-format
-msgid ""
-"Next, configure your boot ROMs or BOOTP server to initially load the "
-"<filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> "
-"files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> "
-"file for your subarchitecture for additional system-specific configuration "
-"information."
-msgstr ""
-
-#. Tag: title
-#: install-tftp.xml:302
-#, no-c-format
-msgid "SGI Indys TFTP Booting"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:303
-#, no-c-format
-msgid ""
-"On SGI Indys you can rely on the <command>bootpd</command> to supply the "
-"name of the TFTP file. It is given either as the <userinput>bf=</userinput> "
-"in <filename>/etc/bootptab</filename> or as the <userinput>filename=</"
-"userinput> option in <filename>/etc/dhcpd.conf</filename>."
-msgstr ""
-
-#. Tag: title
-#: install-tftp.xml:315
-#, no-c-format
-msgid "Broadcom BCM91250A TFTP Booting"
-msgstr ""
-
-#. Tag: para
-#: install-tftp.xml:316
-#, no-c-format
-msgid ""
-"You don't have to configure DHCP in a special way because you'll pass the "
-"full path of the file to the loaded to CFE."
-msgstr ""

Index: automatic-install.po
===================================================================
RCS file: /cvsroot/l10n-russian/di-docs/install-methods/automatic-install.po,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- automatic-install.po	9 Oct 2004 19:20:44 -0000	1.8
+++ automatic-install.po	18 Oct 2004 12:36:05 -0000	1.9
@@ -13,118 +13,3 @@
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: ENCODING\n"
-
-#. Tag: title
-#: automatic-install.xml:5
-#, no-c-format
-msgid "Automatic Installation"
-msgstr ""
-
-#. Tag: para
-#: automatic-install.xml:6
-#, no-c-format
-msgid ""
-"For installing on multiple computers it's possible to do fully automatic "
-"installations. Debian packages intended for this include <classname>fai</"
-"classname> (which uses an install server), <classname>replicator</"
-"classname>, <classname>systemimager</classname>, <classname>autoinstall</"
-"classname>, and the Debian Installer itself."
-msgstr ""
-
-#. Tag: title
-#: automatic-install.xml:19
-#, no-c-format
-msgid "Automatic installation using the Debian Installer"
-msgstr ""
-
-#. Tag: para
-#: automatic-install.xml:21
-#, no-c-format
-msgid ""
-"The Debian Installer supports automating installs via preconfiguration "
-"files. A preconfiguration file can be loaded from the network or from "
-"removable media, and used to fill in answers to question asked during the "
-"installation process."
-msgstr ""
-
-#. Tag: para
-#: automatic-install.xml:27
-#, no-c-format
-msgid ""
-"The preconfiguration file is in the format used by the debconf-set-"
-"selections command. A well documented and working example that you can edit "
-"is in <xref linkend=\"example-preseed\"/>."
-msgstr ""
-
-#. Tag: para
-#: automatic-install.xml:33
-#, no-c-format
-msgid ""
-"The preconfiguration file is in the format used by the debconf-set-"
-"selections command, and one way to get a complete file listing all the "
-"values that can be preseeded is to do a manual install, and then use "
-"<filename>debconf-get-selections</filename>, from the <classname>debconf-"
-"utils</classname> package, to dump both the debconf database and the "
-"cdebconf database in /var/log/debian-installer/cdebconf to a single file:"
-msgstr ""
-
-#. Tag: screen
-#: automatic-install.xml:43
-#, no-c-format
-msgid ""
-"debconf-get-selections --installer > file\n"
-"debconf-get-selections >> file"
-msgstr ""
-
-#. Tag: para
-#: automatic-install.xml:45
-#, no-c-format
-msgid ""
-"However, a file generated in this manner will have some items that should "
-"not be preseeded, and the file in <xref linkend=\"example-preseed\"/> is a "
-"better starting place for most users."
-msgstr ""
-
-#. Tag: para
-#: automatic-install.xml:51
-#, no-c-format
-msgid ""
-"Once you have a preconfiguration file, you can edit it if necessary, and "
-"place it on a web server, or copy it onto the installer's boot media. "
-"Wherever you place the file, you need to pass a parameter to the installer "
-"at boot time to tell it to use the file."
-msgstr ""
-
-#. Tag: para
-#: automatic-install.xml:58
-#, no-c-format
-msgid ""
-"To make the installer use a preconfiguration file downloaded from the "
-"network, add preseed/url=http://url/to/preseed.cfg to the kernel boot "
-"parameters. Of course the preconfiguration will not take effect until the "
-"installer manages to set up the network to download the file, so this is "
-"most useful if the installer can set up the network via DHCP without asking "
-"any questions. You may want to set the installation priority to critical to "
-"avoid any questions while the network is being configured. See <xref linkend="
-"\"installer-args\"/>."
-msgstr ""
-
-#. Tag: para
-#: automatic-install.xml:69
-#, no-c-format
-msgid ""
-"To place a preconfiguration file on a CD, you would need to remaster the ISO "
-"image to include your preconfiguration file. See the manual page for mkisofs "
-"for details. Alternatively, put the preseed file on a floppy, and use "
-"preseed/file=/floppy/preseed.cfg"
-msgstr ""
-
-#. Tag: para
-#: automatic-install.xml:76
-#, no-c-format
-msgid ""
-"If you'll be booting from a USB memory stick, then you can simply copy your "
-"preconfiguration file onto the memory stick's filesystem, and edit the "
-"syslinux.cfg file to add preseed/file=/hd-media/preseed.cfg to the kernel "
-"boot parameters."
-msgstr ""

Index: boot-usb-files.po
===================================================================
RCS file: /cvsroot/l10n-russian/di-docs/install-methods/boot-usb-files.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- boot-usb-files.po	9 Oct 2004 19:20:44 -0000	1.3
+++ boot-usb-files.po	18 Oct 2004 12:36:05 -0000	1.4
@@ -11,198 +11,3 @@
 "X-Generator: KBabel 1.3.1\n"
 "Plural-Forms:  nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%"
 "10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
-
-#. Tag: title
-#: boot-usb-files.xml:5
-#, no-c-format
-msgid "Preparing Files for USB Memory Stick Booting"
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:7
-#, no-c-format
-msgid ""
-"For preparing the USB stick you will need a system where GNU/Linux is "
-"already running and where USB is supported. You should ensure that the usb-"
-"storage kernel module is loaded (<userinput>modprobe usb-storage</"
-"userinput>) and try to find out which SCSI device the USB stick has been "
-"mapped to (in this example <filename>/dev/sda</filename> is used). To write "
-"to your stick, you will probably have to turn off its write protection "
-"switch."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:17
-#, no-c-format
-msgid ""
-"Note, that the USB stick should be at least 128 MB in size (smaller setups "
-"are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
-msgstr ""
-
-#. Tag: title
-#: boot-usb-files.xml:25
-#, no-c-format
-msgid "Copying the files - the easy way"
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:26
-#, no-c-format
-msgid ""
-"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
-"contains all the installer files (including the kernel) as well as "
-"<command>SYSLINUX</command> and its configuration file. You only have to "
-"extract it directly to to your USB stick: <informalexample><screen>\n"
-"\n"
-"gzip -dc boot.img.gz >/dev/<replaceable>sda</replaceable>\n"
-"\n"
-"</screen></informalexample> Of course this will destroy anything already on "
-"the device, so take care that you use the correct device name for your USB "
-"stick."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:38
-#, no-c-format
-msgid ""
-"After that, mount the USB memory stick (<userinput>mount /dev/sda /mnt</"
-"userinput>), which will now have a FAT filesystem on it, and copy a Debian "
-"netinst or businesscard ISO image to it. Please note that the file name must "
-"end in <filename>.iso</filename>. Unmount the stick (<userinput>umount /mnt</"
-"userinput>) and you are done."
-msgstr ""
-
-#. Tag: title
-#: boot-usb-files.xml:50
-#, no-c-format
-msgid "Copying the files - the flexible way"
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:51
-#, no-c-format
-msgid ""
-"If you like more flexibility or just want to know what's going on, you "
-"should use the following method to put the files on your stick. We will show "
-"how to setup the memory stick to use the first partition, instead of entire "
-"device."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:58
-#, no-c-format
-msgid ""
-"Since most USB sticks come pre-configured with a single FAT16 partition, you "
-"probably won't have to repartition or reformat the stick. If you have to do "
-"that anyway, use <command>cfdisk</command> or any other partitioning tool "
-"for creating a FAT16 partition and then type <informalexample><screen>\n"
-"\n"
-"mkdosfs /dev/<replaceable>sda1</replaceable>\n"
-"\n"
-"</screen></informalexample> Take care that you use the correct device name "
-"for your USB stick. The <command>mkdosfs</command> command is contained in "
-"the <classname>dosfstools</classname> Debian package."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:72
-#, no-c-format
-msgid ""
-"In order to start the kernel after booting from the USB stick, we will put a "
-"boot loader on the stick. Although any boot loader (e.g. <command>LILO</"
-"command>) should work, it's convenient to use <command>SYSLINUX</command>, "
-"since it uses a FAT16 partition and can be reconfigured by just editing a "
-"text file. Any operating system which supports the FAT file system can be "
-"used to make changes to the configuration of the boot loader."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:82
-#, no-c-format
-msgid ""
-"To put <command>SYSLINUX</command> on the FAT16 partition on your USB stick, "
-"install the <classname>syslinux</classname> and <classname>mtools</"
-"classname> packages on your system, and type <informalexample><screen>\n"
-"\n"
-"syslinux /dev/<replaceable>sda1</replaceable>\n"
-"\n"
-"</screen></informalexample> Again, take care that you use the correct device "
-"name. The partition must not be mounted when starting <command>SYSLINUX</"
-"command>. This procedure writes a boot sector to the partition and creates "
-"the file <filename>ldlinux.sys</filename> which contains the boot loader "
-"code."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:95
-#, no-c-format
-msgid ""
-"Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and copy "
-"the following files from the Debian archives to the stick: <itemizedlist> "
-"<listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></"
-"listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk "
-"image) </para></listitem> <listitem><para> <filename>syslinux.cfg</filename> "
-"(SYSLINUX configuration file) </para></listitem> <listitem><para> Optional "
-"kernel modules </para></listitem> </itemizedlist> If you want to rename the "
-"files, please note that <command>SYSLINUX</command> can only process DOS "
-"(8.3) file names."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:126
-#, no-c-format
-msgid ""
-"The <filename>syslinux.cfg</filename> configuration file should contain the "
-"following two lines: <informalexample><screen>\n"
-"\n"
-"default vmlinuz\n"
-"append initrd=initrd.gz ramdisk_size=10000 root=/dev/rd/0 init=/linuxrc "
-"devfs=mount,dall rw\n"
-"\n"
-"</screen></informalexample> Please note, that the <userinput>ramdisk_size</"
-"userinput> parameter may need to be increased, depending on the image you "
-"are booting."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:136
-#, no-c-format
-msgid ""
-"Now you should put any Debian ISO image (businesscard, netinst or even a "
-"full one) onto your stick (if it fits). The file name of such an image must "
-"end in <filename>.iso</filename>."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:142
-#, no-c-format
-msgid ""
-"If you want to install over the network, without using an ISO image, you "
-"will of course skip the previous step. Moreover you will have to use the "
-"initial ramdisk from the <filename>netboot</filename> directory instead of "
-"the one from <filename>hd-media</filename>, because <filename>hd-media/"
-"initrd.gz</filename> does not have network support."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:151
-#, no-c-format
-msgid ""
-"When you are done, unmount the USB memory stick (<userinput>umount /mnt</"
-"userinput>) and activate its write protection switch."
-msgstr ""
-
-#. Tag: para
-#: boot-usb-files.xml:156
-#, no-c-format
-msgid ""
-"If your system refuses to boot from the memory stick, the stick may contain "
-"an invalid master boot record (MBR). To fix this, use the <command>install-"
-"mbr</command> command from the package <classname>mbr</classname>:"
-msgstr ""
-
-#. Tag: screen
-#: boot-usb-files.xml:163
-#, no-c-format
-msgid "install-mbr /dev/<replaceable>sda</replaceable>"
-msgstr ""

Index: create-floppy.po
===================================================================
RCS file: /cvsroot/l10n-russian/di-docs/install-methods/create-floppy.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- create-floppy.po	10 Sep 2004 13:31:22 -0000	1.3
+++ create-floppy.po	18 Oct 2004 12:36:05 -0000	1.4
@@ -13,123 +13,3 @@
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: ENCODING\n"
-
-#. Tag: title
-#: create-floppy.xml:5
-#, no-c-format
-msgid "Creating Floppies from Disk Images"
-msgstr ""
-
-#. Tag: para
-#: create-floppy.xml:6
-#, no-c-format
-msgid ""
-"Bootable floppy disks are generally used as a last resort to boot the "
-"installer on hardware that cannot boot from CD or by other means."
-msgstr ""
-
-#. Tag: para
-#: create-floppy.xml:11
-#, no-c-format
-msgid "Floppy disk booting reportedly fails on Mac USB floppy drives."
-msgstr ""
-
-#. Tag: para
-#: create-floppy.xml:15
-#, no-c-format
-msgid "Floppy disk booting is not supported on Amigas or 68k Macs."
-msgstr ""
-
-#. Tag: para
-#: create-floppy.xml:20
-#, no-c-format
-msgid ""
-"Disk images are files containing the complete contents of a floppy disk in "
-"<emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</"
-"filename>, cannot simply be copied to floppy drives. A special program is "
-"used to write the image files to floppy disk in <emphasis>raw</emphasis> "
-"mode. This is required because these images are raw representations of the "
-"disk; it is required to do a <emphasis>sector copy</emphasis> of the data "
-"from the file onto the floppy."
-msgstr ""
-
-#. Tag: para
-#: create-floppy.xml:31
-#, no-c-format
-msgid ""
-"There are different techniques for creating floppies from disk images, which "
-"depend on your platform. This section describes how to create floppies from "
-"disk images on different platforms."
-msgstr ""
-
-#. Tag: para
-#: create-floppy.xml:37
-#, no-c-format
-msgid ""
-"No matter which method you use to create your floppies, you should remember "
-"to flip the write-protect tab on the floppies once you have written them, to "
-"ensure they are not damaged unintentionally."
-msgstr ""
-
-#. Tag: title
-#: create-floppy.xml:45
-#, no-c-format
-msgid "Writing Disk Images From a Linux or Unix System"
-msgstr ""
-
-#. Tag: para
-#: create-floppy.xml:46
-#, no-c-format
-msgid ""
-"To write the floppy disk image files to the floppy disks, you will probably "
-"need root access to the system. Place a good, blank floppy in the floppy "
-"drive. Next, use the command <informalexample><screen>\n"
-"dd if=<replaceable>file</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync\n"
-"</screen></informalexample> where <replaceable>file</replaceable> is one of "
-"the floppy disk image files (see <xref linkend=\"downloading-files\"/> for "
-"what <replaceable>file</replaceable> should be). <filename>/dev/fd0</"
-"filename> is a commonly used name of the floppy disk device, it may be "
-"different on your workstation <phrase arch=\"sparc\">(on Solaris, it is "
-"<filename>/dev/fd/0</filename>)</phrase>. The command may return to the "
-"prompt before Unix has finished writing the floppy disk, so look for the "
-"disk-in-use light on the floppy drive and be sure that the light is out and "
-"the disk has stopped revolving before you remove it from the drive. On some "
-"systems, you'll have to run a command to eject the floppy from the drive "
-"<phrase arch=\"sparc\">(on Solaris, use <command>eject</command>, see the "
-"manual page)</phrase>."
-msgstr ""
-
-#. Tag: para
-#: create-floppy.xml:70
-#, no-c-format
-msgid ""
-"Some systems attempt to automatically mount a floppy disk when you place it "
-"in the drive. You might have to disable this feature before the workstation "
-"will allow you to write a floppy in <emphasis>raw mode</emphasis>. "
-"Unfortunately, how to accomplish this will vary based on your operating "
-"system. <phrase arch=\"sparc\"> On Solaris, you can work around volume "
-"management to get raw access to the floppy. First, make sure that the floppy "
-"is auto-mounted (using <command>volcheck</command> or the equivalent command "
-"in the file manager). Then use a <command>dd</command> command of the form "
-"given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/"
-"rdsk/<replaceable>floppy_name</replaceable></filename>, where "
-"<replaceable>floppy_name</replaceable> is the name the floppy disk was given "
-"when it was formatted (unnamed floppies default to the name "
-"<filename>unnamed_floppy</filename>). On other systems, ask your system "
-"administrator. </phrase>"
-msgstr ""
-
-#. Tag: para
-#: create-floppy.xml:91
-#, no-c-format
-msgid ""
-"If writing a floppy on powerpc Linux, you will need to eject it. The "
-"<command>eject</command> program handles this nicely; you might need to "
-"install it."
-msgstr ""
-
-#. Tag: sect1
-#: create-floppy.xml:99
-#, no-c-format
-msgid "&floppy-i386.xml; &floppy-m68k.xml; &floppy-powerpc.xml;"
-msgstr ""