/[d-i]/trunk/installer/doc/manual/en/boot-installer/ia64.xml
ViewVC logotype

Diff of /trunk/installer/doc/manual/en/boot-installer/ia64.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 14092 by bdale, Tue Apr 20 06:28:59 2004 UTC revision 14093 by bdale, Wed Apr 21 19:32:34 2004 UTC
# Line 46  the vmlinuz and initrd.gz files from the Line 46  the vmlinuz and initrd.gz files from the
46    
47  </para><para>  </para><para>
48    
49  Copy elilo.efi from an IA-64 machine to your tftpboot directory and make it  Copy elilo.efi to your tftpboot directory and make it world readable.
 world readable.  
50  This file can usually be found in the elilo package in IA64 distributions,  This file can usually be found in the elilo package in IA64 distributions,
51  or in /usr/lib/elilo or in a subdirectory of /boot/efi.  or in /usr/lib/elilo or in a subdirectory of /boot/efi.  A suitable copy is
52    provided in the Debian installer netboot directory.
53    
54  </para><para>  </para><para>
55    
56  Create an elilo.conf file in your tftpboot directory.  This will  Create an elilo.conf file in your tftpboot directory.  This will
57  be loaded by elilo.efi once it is running on the client, and controls what  be loaded by elilo.efi once it is running on the client, and controls what
58  happens next, including the choice of kernel, initrd image, etc.  A reasonable  happens next, including the choice of kernel, initrd image, etc.  An
59  example for booting with a serial console might look something like this:  example file is provided in the Debian installer netboot directory, review
60    the contents and update as needed for your choice of paths, etc.
 <informalexample><screen>  
   
 #  
 # elilo.conf for netbooting ia64 client  
 #  
 default=Installer  
   
 image=ia64/vmlinuz  
     label=Installer  
     initrd=ia64/initrd.gz  
     root=/dev/ram  
     append="ramdisk_size=32768 console=ttyS0,9600n8"  
     read-only  
   
 </screen></informalexample>  
61    
62  It is possible to have different config files for different clients by naming  It is possible to have different config files for different clients by naming
63  them using the client's IP address in hex with the suffix .conf instead of  them using the client's IP address in hex with the suffix .conf instead of
Legend:
Removed from v.14092  
changed lines
  Added in v.14093
  ViewVC Help
Powered by ViewVC 1.1.5