--- wikisrc/ports/evbarm/raspberry_pi.mdwn	2017/10/22 16:25:18	1.64
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	2017/10/28 00:43:01	1.65
@@ -55,32 +55,27 @@ Note that one can also use code for earl
 
 ## SD card structure
 
-The Raspberry Pi looks for firmware and a kernel on the first FAT32
-partition of the uSD card.  The NetBSD kernel will then use the FFS
-partition as the root filesystem.
+The Raspberry Pi looks for firmware and kernel.img on the first FAT32 partition of the uSD card.  A separate kernel (kernel7.img) is used on RPI2 and RPI3.
 
-A 2 GB card is the smallest workable size.  The NetBSD filesystem will
-be expanded to fit on larger cards.
+The NetBSD kernel will then use the FFS partition as the root filesystem.
+
+A 2 GB card is the smallest workable size.  The NetBSD filesystem will be expanded to fit.
 
 ## Choosing a version
 
-First, decide if you want to install a formal release (7.1), a stable
-branch build (netbsd-7, netbsd-8), or current.  Note that 7.1 predates
-Raspberry Pi 3 support.  For people who don't know how to choose among
-those, netbsd-8 is probably best.
+First, decide if you want to install a formal release (7.1), a stable branch build (netbsd-7, netbsd-8), or NetBSD-current.  Note that 7.1 predates Raspberry Pi 3 support.  For people who don't know how to choose among those, netbsd-8 is probably best.
+
+See also "ebijun's image", below, which is NetBSD-current and includes packages.
 
 ## Getting bits to install
 
 You can either build a release yourself with build.sh, or get one from the NetBSD FTP servers.
 
-Both will provide rpi.img.gz and rpi_inst.img.gz.  Each is an image to
-be written to a uSD card, and has a FAT32 partition for booting.  In
-rpi.img.gz, there is also an FFS partition for NetBSD.
+Both will provide rpi.img.gz and rpi_inst.img.gz.  Each is an image to be written to a uSD card, and has a FAT32 partition for booting.  In rpi.img.gz, there is also an FFS partition for NetBSD.
 
 ### Building yourself
 
-Getting sources and building a release with build.sh is not special for evbarm.
-Pick a CPU type alias and pass it to build.sh with -m.  Examples:
+Getting sources and building a release with build.sh is not special for evbarm.  Pick a CPU type alias and pass it to build.sh with -m.  Examples (the first two are equivalent):
  - ./build.sh -m earmv6hf -u release
  - ./build.sh -m evbarm -a earmv6hf -u release
  - ./build.sh -m evbarm -a earmv7hf -u release
@@ -95,9 +90,9 @@ NetBSD provides nightly builds on [nyftp
  - The not-yet-released stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/)
  - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201710202210Z/evbarm-earmv7hf/binary/gzimg/)
 
-## Installing to uSD
+## Preparing a uSD card
 
-Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for example:
+Once you have rpi.img.gz (or rpi_inst), put it on a uSD card using gunzip and dd, for example:
 
  - gunzip rpi.img.gz
  - dd if=rpi.i7mg of=/dev/disk1
@@ -113,9 +108,13 @@ edit cmdline.txt and remove '"console=fb
 
    In minicom, run "minicom -s" and set hardware flow control to "no"
 
+### Enabling ssh
+
+If you want to enable ssh with the standard image, so that you can log in over the net without either a serial or HDMI console, mount the ffs partition, place /root/.ssh/authorized_keys, uncomment PermitRootLogin in /etc/ssh/sshd_config, and comment out the rc_configure=NO in /etc/rc.conf.  Besides having to find the IP address, you will have to wait for the partition resizing and reboot.
+
 ### Installation with sshramdisk image
 
-build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console.  To use this method, write that image to a uSD card as above, and then:
+build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console.  Note that this image is much smaller and that you will need to fetch the sets over the network.  To use this method, write that image to a uSD card as above, and then:
 
  - Ensure that you have a lan with a DHCP server.
  - Connect an Ethernet cable from the RPI to the LAN.