diff options
Diffstat (limited to 'en/install-methods/install-tftp.xml')
| -rw-r--r-- | en/install-methods/install-tftp.xml | 21 |
1 files changed, 0 insertions, 21 deletions
diff --git a/en/install-methods/install-tftp.xml b/en/install-methods/install-tftp.xml index efd69e631..eff4340da 100644 --- a/en/install-methods/install-tftp.xml +++ b/en/install-methods/install-tftp.xml @@ -28,9 +28,6 @@ way is to use the BOOTP protocol.</phrase> 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> - The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP. @@ -277,24 +274,6 @@ in the directory that the TFTP server looks in. </para> </sect3> - <sect3 arch="m68k"> - <title>BVM/Motorola TFTP Booting</title> -<para> - -For BVM and Motorola VMEbus systems copy the files -&bvme6000-tftp-files; to <filename>/tftpboot/</filename>. - -</para><para> - -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. - -</para> - </sect3> - <sect3 arch="mips"> <title>SGI TFTP Booting</title> <para> |