Update of /cvsroot/l10n-russian/di-docs/install-methods/tftp
In directory haydn:/tmp/cvs-serv18311/install-methods/tftp
Modified Files:
bootp.po dhcp.po rarp.po
Log Message:
big update to the docs
Index: bootp.po
===================================================================
RCS file: /cvsroot/l10n-russian/di-docs/install-methods/tftp/bootp.po,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -d -r1.1.1.1 -r1.2
--- bootp.po 30 Jan 2004 06:49:30 -0000 1.1.1.1
+++ bootp.po 10 Sep 2004 13:03:39 -0000 1.2
@@ -1,63 +1,89 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# FIRST AUTHOR <[EMAIL PROTECTED]>, YEAR.
-#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-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 PROTECTED]>\n"
-"Language-Team: LANGUAGE <[EMAIL PROTECTED]>\n"
+"PO-Revision-Date: 2004-07-03 14:45+1000\n"
+"Last-Translator: Nikolai Prokoschenko <[EMAIL PROTECTED]>\n"
+"Language-Team: Russian <debian-l10n-russian@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
-"Content-Transfer-Encoding: ENCODING\n"
+"Content-Transfer-Encoding: 8bit\n"
+"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
#: bootp.xml:6
#, no-c-format
-#. Tag: title
msgid "Setting up BOOTP server"
msgstr ""
+#. Tag: para
#: bootp.xml:7
#, no-c-format
-#. Tag: para
-msgid "There are two BOOTP servers available for GNU/Linux, the CMU
<command>bootpd</command> and the other is actually a DHCP server, ISC
<command>dhcpd</command>, which are contained in the
<classname>bootp</classname> and <classname>dhcp</classname> packages in
&debian;."
+msgid ""
+"There are two BOOTP servers available for GNU/Linux, the CMU "
+"<command>bootpd</command> and the other is actually a DHCP server, ISC "
+"<command>dhcpd</command>, which are contained in the <classname>bootp</"
+"classname> and <classname>dhcp</classname> packages in &debian;."
msgstr ""
+#. Tag: para
#: bootp.xml:15
#, no-c-format
-#. Tag: para
-msgid "To use CMU <command>bootpd</command>, you must first uncomment (or add)
the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can
run <userinput>update-inetd --enable bootps</userinput>, then
<userinput>/etc/init.d/inetd reload</userinput> to do so. Elsewhere, the line
in question should look like:"
+msgid ""
+"To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
+"relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can "
+"run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/"
+"etc/init.d/inetd reload</userinput> to do so. Elsewhere, the line in "
+"question should look like:"
msgstr ""
+#. Tag: screen
#: bootp.xml:24
#, no-c-format
-#. Tag: screen
-msgid "bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t
120"
+msgid "bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120"
msgstr ""
+#. Tag: para
#: bootp.xml:26
#, no-c-format
-#. Tag: para
msgid ""
- "Now, you must create an <filename>/etc/bootptab</filename> file. This
has the same sort of familiar and cryptic format as the good old BSD
<filename>printcap</filename>, <filename>termcap</filename>, and
<filename>disktab</filename> files. See the <filename>bootptab</filename>
manual page for more information. For CMU <command>bootpd</command>, you will
need to know the hardware (MAC) address of the client. Here is an example
<filename>/etc/bootptab</filename>: <informalexample><screen>\n"
- "\n"
- "client:\\\n"
- " hd=/tftpboot:\\\n"
- " bf=tftpboot.img:\\\n"
- " ip=192.168.1.90:\\\n"
- " sm=255.255.255.0:\\\n"
- " sa=192.168.1.1:\\\n"
- " ha=0123456789AB:\n"
- "\n"
- "</screen></informalexample> You will need to change at least the \"ha\"
option, which specifies the hardware address of the client. The \"bf\" option
specifies the file a client should retrieve via TFTP; see <xref
linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI Indys
you can just enter the command monitor and type
<userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput>
variable is the machine's MAC address. </phrase>"
+"Now, you must create an <filename>/etc/bootptab</filename> file. This has "
+"the same sort of familiar and cryptic format as the good old BSD "
+"<filename>printcap</filename>, <filename>termcap</filename>, and "
+"<filename>disktab</filename> files. See the <filename>bootptab</filename> "
+"manual page for more information. For CMU <command>bootpd</command>, you "
+"will need to know the hardware (MAC) address of the client. Here is an "
+"example <filename>/etc/bootptab</filename>: <informalexample><screen>\n"
+"\n"
+"client:\\\n"
+" hd=/tftpboot:\\\n"
+" bf=tftpboot.img:\\\n"
+" ip=192.168.1.90:\\\n"
+" sm=255.255.255.0:\\\n"
+" sa=192.168.1.1:\\\n"
+" ha=0123456789AB:\n"
+"\n"
+"</screen></informalexample> You will need to change at least the \"ha\" "
+"option, which specifies the hardware address of the client. The \"bf\" "
+"option specifies the file a client should retrieve via TFTP; see <xref "
+"linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI "
+"Indys you can just enter the command monitor and type <userinput>printenv</"
+"userinput>. The value of the <userinput>eaddr</userinput> variable is the "
+"machine's MAC address. </phrase>"
msgstr ""
+#. Tag: para
#: bootp.xml:50
#, no-c-format
-#. Tag: para
-msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is
really easy, because it treats BOOTP clients as a moderately special case of
DHCP clients. Some architectures require a complex configuration for booting
clients via BOOTP. If yours is one of those, read the section <xref
linkend=\"dhcpd\"/>. Otherwise, you will probably be able to get away with
simply adding the <userinput>allow bootp</userinput> directive to the
configuration block for the subnet containing the client, and restart
<command>dhcpd</command> with <userinput>/etc/init.d/dhcpd restart</userinput>."
+msgid ""
+"By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
+"easy, because it treats BOOTP clients as a moderately special case of DHCP "
+"clients. Some architectures require a complex configuration for booting "
+"clients via BOOTP. If yours is one of those, read the section <xref linkend="
+"\"dhcpd\"/>. Otherwise, you will probably be able to get away with simply "
+"adding the <userinput>allow bootp</userinput> directive to the configuration "
+"block for the subnet containing the client, and restart <command>dhcpd</"
+"command> with <userinput>/etc/init.d/dhcpd restart</userinput>."
msgstr ""
-
Index: dhcp.po
===================================================================
RCS file: /cvsroot/l10n-russian/di-docs/install-methods/tftp/dhcp.po,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -d -r1.1.1.1 -r1.2
--- dhcp.po 30 Jan 2004 06:49:30 -0000 1.1.1.1
+++ dhcp.po 10 Sep 2004 13:03:39 -0000 1.2
@@ -1,116 +1,126 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# FIRST AUTHOR <[EMAIL PROTECTED]>, YEAR.
-#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-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 PROTECTED]>\n"
-"Language-Team: LANGUAGE <[EMAIL PROTECTED]>\n"
+"PO-Revision-Date: 2004-07-03 14:45+1000\n"
+"Last-Translator: Nikolai Prokoschenko <[EMAIL PROTECTED]>\n"
+"Language-Team: Russian <debian-l10n-russian@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
-"Content-Transfer-Encoding: ENCODING\n"
+"Content-Transfer-Encoding: 8bit\n"
+"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
#: dhcp.xml:6
#, no-c-format
-#. Tag: title
msgid "Setting up a DHCP server"
msgstr ""
+#. Tag: para
#: dhcp.xml:7
#, no-c-format
-#. Tag: para
-msgid "At the time of this writing, there is only one DHCP server which is
free software, namely ISC <command>dhcpd</command>. In &debian;, this is
available in the <classname>dhcp</classname> package. Here is a sample
configuration file for it (usually <filename>/etc/dhcpd.conf</filename>):"
+msgid ""
+"One free software DHCP server is ISC <command>dhcpd</command>. In &debian;, "
+"this is available in the <classname>dhcp</classname> package. Here is a "
+"sample configuration file for it (usually <filename>/etc/dhcpd.conf</"
+"filename>): <informalexample><screen>\n"
+"\n"
+"option domain-name \"example.com\";\n"
+"option domain-name-servers ns1.example.com;\n"
+"option subnet-mask 255.255.255.0;\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"server-name \"servername\";\n"
+"\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+" range 192.168.1.200 192.168.1.253;\n"
+" option routers 192.168.1.1;\n"
+"}\n"
+"\n"
+"host clientname {\n"
+" filename \"/tftpboot/tftpboot.img\";\n"
+" server-name \"servername\";\n"
+" next-server servername;\n"
+" hardware ethernet 01:23:45:67:89:AB; \n"
+" fixed-address 192.168.1.90;\n"
+"}\n"
+"\n"
+"</screen></informalexample> Note: the new (and preferred) <classname>dhcp3</"
+"classname> package uses <filename>/etc/dhcp3/dhcpd.conf</filename>."
msgstr ""
-#: dhcp.xml:15
+#. Tag: para
+#: dhcp.xml:19
#, no-c-format
-#. Tag: screen
msgid ""
- "option domain-name \"example.com\";\n"
- "option domain-name-servers ns1.example.com;\n"
- "option subnet-mask 255.255.255.0;\n"
- "default-lease-time 600;\n"
- "max-lease-time 7200;\n"
- "server-name \"servername\";\n"
- "\n"
- "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
- " range 192.168.1.200 192.168.1.253;\n"
- " option routers 192.168.1.1;\n"
- "}\n"
- "\n"
- "host clientname {\n"
- " filename \"/tftpboot/tftpboot.img\";\n"
- " server-name \"servername\";\n"
- " next-server servername;\n"
- " hardware ethernet 01:23:45:67:89:AB; \n"
- " fixed-address 192.168.1.90;\n"
- "}"
+"In this example, there is one server <replaceable>\"servername\"</"
+"replaceable> which performs all of the work of DHCP, server, TFTP server, "
+"and network gateway. You will almost certainly need to change the domain-"
+"name options, as well as the server name and client hardware address. The "
+"<replaceable>\"filename\"</replaceable> option should be the name of the "
+"file which will be retrieved via TFTP."
msgstr ""
-#: dhcp.xml:17
-#, no-c-format
#. Tag: para
-msgid "In this example, there is one server
<replaceable>\"servername\"</replaceable> which performs all of the work of
DHCP, server, TFTP server, and network gateway. You will almost certainly need
to change the domain-name options, as well as the server name and client
hardware address. The <replaceable>\"filename\"</replaceable> option should be
the name of the file which will be retrieved via TFTP."
-msgstr ""
-
-#: dhcp.xml:27
+#: dhcp.xml:29
#, no-c-format
-#. Tag: para
-msgid "After you have edited the <command>dhcpd</command> configuration file,
restart it with <userinput>/etc/init.d/dhcpd restart</userinput>."
+msgid ""
+"After you have edited the <command>dhcpd</command> configuration file, "
+"restart it with <userinput>/etc/init.d/dhcpd restart</userinput>."
msgstr ""
-#: dhcp.xml:35
-#, no-c-format
#. Tag: title
+#: dhcp.xml:37
+#, no-c-format
msgid "PXE Booting"
msgstr ""
-#: dhcp.xml:36
-#, no-c-format
#. Tag: para
+#: dhcp.xml:38
+#, no-c-format
msgid ""
- "Here is another example for a <filename>dhcp.conf</filename> using the
Pre-boot Execution Environment (PXE) method of TFTP.
<informalexample><screen>\n"
- "\n"
- "option domain-name \"example.com\";\n"
- "\n"
- "default-lease-time 6048;\n"
- "max-lease-time 604800;\n"
- "\n"
- "allow booting;\n"
- "allow bootp;\n"
- "\n"
- "# The next paragraph needs to be modified to fit your case\n"
- "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
- " range 192.168.1.200 192.168.1.253;\n"
- " option subnet-mask 255.255.255.0;\n"
- " option broadcast-address 192.168.1.255;\n"
- "# the gateway address which can be different \n"
- "# (access to the internet for instance)\n"
- " option routers 192.168.1.1;\n"
- "# indicate the dns you want to use\n"
- " option domain-name-servers 192.168.1.3;\n"
- "}\n"
- "\n"
- "host tftpserver {\n"
- "# tftp server ip address\n"
- " fixed-address 192.168.1.90;\n"
- "# tftp server hardware address\n"
- " hardware ethernet 01:23:45:67:89:AB;\n"
- "}\n"
- "\n"
- "group {\n"
- " next-server 192.168.1.3;\n"
- " host tftpclient {\n"
- "# tftp client hardware address\n"
- " hardware ethernet 00:10:DC:27:6C:15;\n"
- " filename \"/tftpboot/pxelinux.0\";\n"
- " }\n"
- "}\n"
- "\n"
- "</screen></informalexample> Note that for PXE booting, the client
filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image
(see <xref linkend=\"tftp-images\"/> below)."
+"Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
+"boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
+"\n"
+"option domain-name \"example.com\";\n"
+"\n"
+"default-lease-time 6048;\n"
+"max-lease-time 604800;\n"
+"\n"
+"allow booting;\n"
+"allow bootp;\n"
+"\n"
+"# The next paragraph needs to be modified to fit your case\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+" range 192.168.1.200 192.168.1.253;\n"
+" option subnet-mask 255.255.255.0;\n"
+" option broadcast-address 192.168.1.255;\n"
+"# the gateway address which can be different \n"
+"# (access to the internet for instance)\n"
+" option routers 192.168.1.1;\n"
+"# indicate the dns you want to use\n"
+" option domain-name-servers 192.168.1.3;\n"
+"}\n"
+"\n"
+"host tftpserver {\n"
+"# tftp server ip address\n"
+" fixed-address 192.168.1.90;\n"
+"# tftp server hardware address\n"
+" hardware ethernet 01:23:45:67:89:AB;\n"
+"}\n"
+"\n"
+"group {\n"
+" next-server 192.168.1.3;\n"
+" host tftpclient {\n"
+"# tftp client hardware address\n"
+" hardware ethernet 00:10:DC:27:6C:15;\n"
+" filename \"/tftpboot/pxelinux.0\";\n"
+" }\n"
+"}\n"
+"\n"
+"</screen></informalexample> Note that for PXE booting, the client filename "
+"<filename>pxelinux.0</filename> is a boot loader, not a kernel image (see "
+"<xref linkend=\"tftp-images\"/> below)."
msgstr ""
-
Index: rarp.po
===================================================================
RCS file: /cvsroot/l10n-russian/di-docs/install-methods/tftp/rarp.po,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -d -r1.1.1.1 -r1.2
--- rarp.po 30 Jan 2004 06:49:30 -0000 1.1.1.1
+++ rarp.po 10 Sep 2004 13:03:39 -0000 1.2
@@ -1,67 +1,87 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# FIRST AUTHOR <[EMAIL PROTECTED]>, YEAR.
-#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-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 PROTECTED]>\n"
-"Language-Team: LANGUAGE <[EMAIL PROTECTED]>\n"
+"PO-Revision-Date: 2004-07-03 14:45+1000\n"
+"Last-Translator: Nikolai Prokoschenko <[EMAIL PROTECTED]>\n"
+"Language-Team: Russian <debian-l10n-russian@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
-"Content-Transfer-Encoding: ENCODING\n"
+"Content-Transfer-Encoding: 8bit\n"
+"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
#: rarp.xml:6
#, no-c-format
-#. Tag: title
msgid "Setting up RARP server"
msgstr ""
+#. Tag: para
#: rarp.xml:7
#, no-c-format
-#. Tag: para
-msgid "To setup RARP, you need to know the Ethernet address of the client
(a.k.a. the MAC address). If you don't know this information, you can <phrase
arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the
OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into
``Rescue'' mode (e.g., from the rescue floppy) and use the command
<userinput>/sbin/ifconfig eth0</userinput>."
+msgid ""
+"To setup RARP, you need to know the Ethernet address (a.k.a. the MAC "
+"address) of the client computers to be installed. If you don't know this "
+"information, you can <phrase arch=\"sparc\"> pick it off the initial "
+"OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> "
+"command, or </phrase> boot into ``Rescue'' mode (e.g., from the rescue "
+"floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>."
msgstr ""
-#: rarp.xml:18
-#, no-c-format
#. Tag: para
-msgid "On systems using a Linux 2.2.x kernel, you need to populate the
kernel's RARP table. To do this, run the following commands:"
+#: rarp.xml:19
+#, no-c-format
+msgid ""
+"On a RARP server system using a Linux 2.2.x kernel, you need to populate the "
+"kernel's RARP table. To do this, run the following commands:"
msgstr ""
-#: rarp.xml:26
-#, no-c-format
#. Tag: userinput
-msgid "/sbin/rarp -s <replaceable>client-hostname</replaceable>
<replaceable>client-enet-addr</replaceable>"
+#: rarp.xml:28
+#, no-c-format
+msgid ""
+"/sbin/rarp -s <replaceable>client-hostname</replaceable> <replaceable>client-"
+"enet-addr</replaceable>"
msgstr ""
-#: rarp.xml:33
-#, no-c-format
#. Tag: userinput
-msgid "/usr/sbin/arp -s <replaceable>client-ip</replaceable>
<replaceable>client-enet-addr</replaceable>"
+#: rarp.xml:35
+#, no-c-format
+msgid ""
+"/usr/sbin/arp -s <replaceable>client-ip</replaceable> <replaceable>client-"
+"enet-addr</replaceable>"
msgstr ""
-#: rarp.xml:40
-#, no-c-format
#. Tag: para
+#: rarp.xml:42
+#, no-c-format
msgid ""
- "If you get <informalexample><screen>\n"
- "SIOCSRARP: Invalid argument\n"
- "</screen></informalexample> you probably need to load the RARP kernel
module or else recompile the kernel to support RARP. Try <userinput>modprobe
rarp</userinput> and then try the <command>rarp</command> command again."
+"If you get <informalexample><screen>\n"
+"SIOCSRARP: Invalid argument\n"
+"</screen></informalexample> you probably need to load the RARP kernel module "
+"or else recompile the kernel to support RARP. Try <userinput>modprobe rarp</"
+"userinput> and then try the <command>rarp</command> command again."
msgstr ""
-#: rarp.xml:50
-#, no-c-format
#. Tag: para
-msgid "On systems using a Linux 2.4.x kernel, there is no RARP module, and you
should instead use the <command>rarpd</command> program. The procedure is
similar to that used under SunOS in the following paragraph."
+#: rarp.xml:52
+#, no-c-format
+msgid ""
+"On a RARP server system using a Linux 2.4.x kernel, there is no RARP module, "
+"and you should instead use the <command>rarpd</command> program. The "
+"procedure is similar to that used under SunOS in the following paragraph."
msgstr ""
-#: rarp.xml:57
-#, no-c-format
#. Tag: para
-msgid "Under SunOS, you need to ensure that the Ethernet hardware address for
the client is listed in the ``ethers'' database (either in the
<filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the ``hosts''
database. Then you need to start the RARP daemon. In SunOS 4, issue the command
(as root): <userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use
<userinput>/usr/sbin/rarpd -a</userinput>."
+#: rarp.xml:60
+#, no-c-format
+msgid ""
+"Under SunOS, you need to ensure that the Ethernet hardware address for the "
+"client is listed in the ``ethers'' database (either in the <filename>/etc/"
+"ethers</filename> file, or via NIS/NIS+) and in the ``hosts'' database. Then "
+"you need to start the RARP daemon. In SunOS 4, issue the command (as root): "
+"<userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use <userinput>/usr/"
+"sbin/rarpd -a</userinput>."
msgstr ""
-
