diff options
| author | Frans Pop <elendil@planet.nl> | 2009-07-26 01:05:09 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2009-07-26 01:05:09 +0000 |
| commit | 99c0ce2062388ace5ecd6088c272f709dfb0c6fe (patch) | |
| tree | 1e57176df5a463b378b65eda5f451b571a74e73b /nl/install-methods | |
| parent | 841458646648bf07bc3c19b2129a5884e1d02a8d (diff) | |
| download | installation-guide-99c0ce2062388ace5ecd6088c272f709dfb0c6fe.zip | |
Dutch translation update for untranslated files
Diffstat (limited to 'nl/install-methods')
| -rw-r--r-- | nl/install-methods/download/arm.xml | 22 | ||||
| -rw-r--r-- | nl/install-methods/install-tftp.xml | 4 | ||||
| -rw-r--r-- | nl/install-methods/tftp/bootp.xml | 7 |
3 files changed, 7 insertions, 26 deletions
diff --git a/nl/install-methods/download/arm.xml b/nl/install-methods/download/arm.xml index 4c7355ee3..948c05da7 100644 --- a/nl/install-methods/download/arm.xml +++ b/nl/install-methods/download/arm.xml @@ -1,27 +1,7 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 55541 untranslated --> +<!-- original version: 58440 untranslated --> - <sect3 arch="arm" id="netwinder-install-files"> - <title>Netwinder Installation Files</title> -<para> - -The easiest way to boot a Netwinder is over the network, using the -supplied TFTP image &netwinder-boot-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="cats-install-files"> - <title>CATS Installation Files</title> -<para> - -CATS can be booted either via the network or from CD-ROM. The kernel and -initrd can be obtained from &cats-boot-img;. - -</para> - </sect3> - <sect3 arch="arm" id="nslu2-install-files"> <title>NSLU2 Installation Files</title> <para> diff --git a/nl/install-methods/install-tftp.xml b/nl/install-methods/install-tftp.xml index cceb18915..57af26da4 100644 --- a/nl/install-methods/install-tftp.xml +++ b/nl/install-methods/install-tftp.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 56425 untranslated --> +<!-- original version: 58446 untranslated --> <sect1 condition="supports-tftp" id="install-tftp"> <title>Preparing Files for TFTP Net Booting</title> @@ -308,7 +308,7 @@ the <userinput>filename=</userinput> option in </para> </sect3> - <sect3 arch="mips"> + <sect3 arch="mips;mipsel"> <title>Broadcom BCM91250A and BCM91480B TFTP Booting</title> <para> diff --git a/nl/install-methods/tftp/bootp.xml b/nl/install-methods/tftp/bootp.xml index 97ef2f793..913b22f98 100644 --- a/nl/install-methods/tftp/bootp.xml +++ b/nl/install-methods/tftp/bootp.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 43558 untranslated --> +<!-- original version: 59293 untranslated --> <sect2 condition="supports-bootp" id="tftp-bootp"> @@ -61,10 +61,11 @@ 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"/>. In that case, you +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 +block for the subnet containing the client in +<filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>. |