=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/hppa.html,v retrieving revision 1.129 retrieving revision 1.130 diff -c -r1.129 -r1.130 *** www/hppa.html 2004/05/04 20:55:37 1.129 --- www/hppa.html 2004/05/04 23:47:35 1.130 *************** *** 49,55 ****
  • Supported hardware list
  • Hardware documentation
  • Getting and installing OpenBSD/hppa -
  • Netbooting the installation media
    --- 49,54 ---- *************** *** 384,498 ****


    - -

    Netbooting the installation media:

    - -

    - The lif35.fs file contains both a bootloader and an installation - miniroot. - To boot it from the network, a server machine has to be setup so as to - let the hppa machine retrieve it: -

      -
    1. Server setup -
        -
      • For older machines (705, 7[1235]0, 715/33/50/75, 725/50/75, 735, 755) - rbootd - must be setup and started. -
          -
        • /etc/rbootd.conf contains a single line per machine - needing to boot from the server. Each line contains the ethernet - address of the client hppa machine, and the filename to be loaded from - the tftp server (relative to /usr/mdec/rbootd). - For example: -
          - 	8:0:9:70:c4:11    lif35.fs    # 9000/720
          - 	8:0:9:19:fb:a0    lif35.fs    # 9000/725
          - 	
          -
        • -
        -
      • -
      • Recent machines (712, 715/64/80/100, 725/64/100, ABC class, etc.) - will not look for rbootd at all, but instead require a bootp setup. -
          -
        • /etc/bootptab - contains an information block for each machine. For example: -
          - 	# 9000/715
          - 	boron:\
          -         	ha=0800095f5a6e:\
          -         	bf=lif35.fs:\
          -         	hd=:\
          -         	ht=ethernet:\
          -         	ip=10.0.1.143:\
          -         	sm=255.255.255.0:\
          -         	td=/tftpboot:
          - 	
          -
        • -
        • - Create directory /tftpboot and put the - lif35.fs file in it.
          -
        • -
        • - Write an entry for the hppa in /etc/ethers: -
          - 	08:00:09:5f:5a:6e	boron
          - 	
          -
        • -
        • - Write another entry for it in /etc/hosts: -
          - 	10.0.1.143	boron
          - 	
          -
        • -
        • - The last step is to enable the necessary daemons for all of this to - work. - bootpd - and - tftpd - are usually run from - inetd, - so /etc/inetd.conf has to be modified and - inetd - restarted. Also, - rarpd - needs to be enabled in - rc.conf. -
        • -
        -
      • -
      • For further reading on server setup for network booting in general, - please refer to the - diskless(8) - manual page. -
      • -
      -

      -

    2. Client Network Boot -
        -
      • BOOT_ADMIN
        - In order to get to the BOOT_ADMIN prompt, hit the <esc> - key as the machine is coming up. Once it has probed bootable devices, - a menu will be displayed; if the prompt is not BOOT_ADMIN, - it will be necessary to type ``a'' to access it. -
      • -
      • Network boot command
        - Once at the 'BOOT_ADMIN' prompt, the command -
        - 	BOOT_ADMIN> boot lan isl
        - 
        - will proceed to the bootstrap of lif35.fs. -
      -
    3. -
    - -
    Supported platforms
    www@openbsd.org
    ! $OpenBSD: hppa.html,v 1.129 2004/05/04 20:55:37 david Exp $ --- 383,394 ----


    Supported platforms
    www@openbsd.org
    ! $OpenBSD: hppa.html,v 1.130 2004/05/04 23:47:35 mickey Exp $