Diff for /wikisrc/ports/sandpoint/instnh23x.mdwn between versions 1.1 and 1.2

version 1.1, 2013/10/31 21:05:10 version 1.2, 2015/09/04 22:22:18
Line 2  Introduction Line 2  Introduction
 ============  ============
   
 This document describes in depth how to prepare your NH-230/231 NAS for  This document describes in depth how to prepare your NH-230/231 NAS for
 installing OS/sandpoint. Models based on the NH-230 have an ITE PATA  installing NetBSD/sandpoint. Models based on the NH-230 have an ITE PATA
 controller while those based on the NH-231 have a SiliconImage SataLink  controller while those based on the NH-231 have a SiliconImage SataLink
 SATA controller. The following models are known to be compatible:  SATA controller. The following models are known to be compatible:
   
Line 88  standard RS232 interface and for an USB  Line 88  standard RS232 interface and for an USB 
 -   USB to TLL serial level shifter / breakout board (FT232 based)  -   USB to TLL serial level shifter / breakout board (FT232 based)
   
 Now you can connect with any terminal program to the NH-230/231 serial  Now you can connect with any terminal program to the NH-230/231 serial
 console. The easiest approach may be to use OS's `tip(1)` command to  console. The easiest approach may be to use NetBSD's `tip(1)` command to
 make a direct console connection at 9600bps.  make a direct console connection at 9600bps.
   
     # tip console      # tip console
Line 103  The altboot bootloader Line 103  The altboot bootloader
 ----------------------  ----------------------
   
 The `altboot(8)` utility functions as a bridge between the PPCBoot  The `altboot(8)` utility functions as a bridge between the PPCBoot
 firmware and the OS kernel startup environment. NAS firmware often  firmware and the NetBSD kernel startup environment. NAS firmware often
 provides no means to boot a kernel from disk or from the network and  provides no means to boot a kernel from disk or from the network and
 doesn't initialize all hardware correctly. We will also use it to pass a  doesn't initialize all hardware correctly. We will also use it to pass a
 bootinfo list to the kernel.  bootinfo list to the kernel.
Line 177  Boot the INSTALL kernel with altboot Line 177  Boot the INSTALL kernel with altboot
 ------------------------------------  ------------------------------------
   
 Now you can use `altboot` to launch the `netbsd-INSTALL` kernel for  Now you can use `altboot` to launch the `netbsd-INSTALL` kernel for
 installing OS. You may choose to load it with TFTP or from NFS. For TFTP  installing NetBSD. You may choose to load it with TFTP or from NFS. For TFTP
 you have to enable `tftpd(8)` in `/etc/inetd.conf`, and for NFS there is  you have to enable `tftpd(8)` in `/etc/inetd.conf`, and for NFS there is
 a documentation at [The Network File  a documentation at [The Network File
 System](http://www.&os;.org/docs/guide/en/chap-net-services.html#chap-net-services-nfs).  System](http://www.&os;.org/docs/guide/en/chap-net-services.html#chap-net-services-nfs).
Line 194  appropriate `dhcpd.conf` entry could loo Line 194  appropriate `dhcpd.conf` entry could loo
   
 The `root-path` option is only needed when using NFS and should match  The `root-path` option is only needed when using NFS and should match
 your exported NFS directory. Uncompress `netbsd-INSTALL.gz` from the  your exported NFS directory. Uncompress `netbsd-INSTALL.gz` from the
 OS/sandpoint distribution and copy it into the NFS or TFTP directory.  NetBSD/sandpoint distribution and copy it into the NFS or TFTP directory.
 Then start the DHCP, NFS or TFTP server and boot the installation kernel  Then start the DHCP, NFS or TFTP server and boot the installation kernel
 from the firmware either with  from the firmware either with
   
Line 283  the kernel via network and launches it: Line 283  the kernel via network and launches it:
     erase ^H, werase ^W, kill ^U, intr ^C, status ^T      erase ^H, werase ^W, kill ^U, intr ^C, status ^T
     Terminal type? [vt100]      Terminal type? [vt100]
   
 Just follow the usual procedure to install a OS system.  Just follow the usual procedure to install a NetBSD system.
   
 Sandpoint installation window  Sandpoint installation window
 Post installation steps  Post installation steps
Line 295  you have to find a way to make your firm Line 295  you have to find a way to make your firm
 `altboot` and the kernel.  `altboot` and the kernel.
   
 Without a working `cp` command the only way to make your system  Without a working `cp` command the only way to make your system
 automatically boot OS is to replace the Linux kernel on flash by  automatically boot NetBSD is to replace the Linux kernel on flash by
 `altboot.img`, which is our bootloader in PPCBoot image format, faking a  `altboot.img`, which is our bootloader in PPCBoot image format, faking a
 Linux kernel.  Linux kernel.
   
Line 344  process, but is not really required. Line 344  process, but is not really required.
     Erased 14 sectors      Erased 14 sectors
     Writing to Flash... done      Writing to Flash... done
   
 Have fun with your mini OS server!  Have fun with your mini NetBSD server!

Removed from v.1.1  
changed lines
  Added in v.1.2


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb