Diff for /wikisrc/ports/sandpoint/instsynology.mdwn between versions 1.7 and 1.8

version 1.7, 2014/01/12 16:39:12 version 1.8, 2015/09/04 22:22:18
Line 3  Introduction Line 3  Introduction
 ============  ============
   
 This document describes in depth how to prepare your Synology  This document describes in depth how to prepare your Synology
 Diskstation for installing OS/sandpoint. The following models are  Diskstation for installing NetBSD/sandpoint. The following models are
 supported:  supported:
   
 <table>  <table>
Line 116  supported: Line 116  supported:
 </tbody>  </tbody>
 </table>  </table>
   
 To install OS/sandpoint you will have to open the case, to get access to  To install NetBSD/sandpoint you will have to open the case, to get access to
 the serial console, and connect a serial converter from TTL to RS232  the serial console, and connect a serial converter from TTL to RS232
 signal levels.  signal levels.
   
Line 217  version `2.0.0` installed, but the newer Line 217  version `2.0.0` installed, but the newer
 limited functionality ([read below](#post_install)).  limited functionality ([read below](#post_install)).
   
 Now you can connect with any terminal program to the Diskstation's  Now you can connect with any terminal program to the Diskstation's
 serial console. The easiest approach may be to use OS's `tip(1)` command  serial console. The easiest approach may be to use NetBSD's `tip(1)` command
 to make a direct console connection at 115200bps.  to make a direct console connection at 115200bps.
   
     # tip -115200 console      # tip -115200 console
Line 265  altboot Line 265  altboot
 -------  -------
   
 The `altboot(8)` utility functions as a bridge between the Synology  The `altboot(8)` utility functions as a bridge between the Synology
 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 345  Boot the INSTALL kernel with altboot Line 345  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.NetBSD.org/docs/guide/en/chap-net-services.html#chap-net-services-nfs).  System](http://www.NetBSD.org/docs/guide/en/chap-net-services.html#chap-net-services-nfs).
Line 362  appropriate `dhcpd.conf` entry could loo Line 362  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 451  the kernel via network and launches it: Line 451  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.
   
 <img src="//www.netbsd.org/images/ports/sandpoint/install_window.jpg" alt="Sandpoint installation window" /></td>  <img src="//www.netbsd.org/images/ports/sandpoint/install_window.jpg" alt="Sandpoint installation window" /></td>
   
Line 520  New firmware (2007) Line 520  New firmware (2007)
 -------------------  -------------------
   
 Without a working `saveenv` command the only way to make your system  Without a working `saveenv` 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 557  with `gunzip(1)`). Or use `mkubootimage` Line 557  with `gunzip(1)`). Or use `mkubootimage`
 it to flash as shown above. This will speed up the boot process, but is  it to flash as shown above. This will speed up the boot process, but is
 not really required.  not really required.
   
 Have fun with your mini OS server!  Have fun with your mini NetBSD server!

Removed from v.1.7  
changed lines
  Added in v.1.8


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