I am testing the 1.6 BETA 2 to upgrade my VS 3100/m38 from 1.5.2.

I copied the install.ram.gz kernel to / because I didn't want to set up
netbooting if I could avoid it. When rebooting, it turns out that the
existing /boot program cannot boot this kernel. I extracted the new boot
from base.tgz, only to discover that it was identical to the one in
installation/netboot. I don't know if this was documented because I
didn't read any documentation beforehand (having done NetBSD
installations with sysinst and by hand so many times already).
Fortunately on the VAX you can replace /boot without re-running
installboot.

I selected the upgrade procedure.

 Welcome to sysinst, the NetBSD-1.6_BETA2 system installation tool.  This
 menu-driven tool is designed to help you install NetBSD to a hard disk, or
 upgrade an existing NetBSD system, with a minimum of work.  In the following
 menus, you may change the current selection by either typing the reference
 letter (a, b, c, ...).  Arrow keys may also work.  You activate the current
 selection from the menu by typing the enter key.

 If you booted from a floppy, you may now remove the disk.

 Thank you for using NetBSD!
 
               +-----------------------------------------------+
               | NetBSD-1.6_BETA2 Install System               |
               |                                               |
               | a: Install NetBSD to hard disk                |
               |>b: Upgrade NetBSD on a hard disk              |
               | c: Re-install sets or install additional sets |
               | d: Reboot the computer                        |
               | e: Utility menu                               |
               | x: Exit Install System                        |
               +-----------------------------------------------+

After fscking we get to this screen:

 The NetBSD distribution is broken into a collection of distribution sets.
 There are some basic sets that are needed by all installations and there are
 some other sets that are not needed by all installations.  You may choose to
 install all of them (Full installation) or you select from the optional
 distribution sets.
 
 




                          +--------------------------+
                          | Select your distribution |
                          |                          |
                          |>a: Full installation     |
                          | b: Custom installation   |
                          +--------------------------+

and from here on, the terminal seems to be in cooked mode instead of raw
mode.  This is very inconvenient and I expect a too big hurdle for
first-time installers. I limped along by using the letters from each
menu and then hitting return...

This problem has existed since some time, since I remember it from my
previous upgrade. It really should be fixed.

I deselected each X set:

 The following is the list of distribution sets that will be used.
 
 Distribution set   Use?
 ------------------ ----
 Kernel       :     Yes   +-----------------------------+
 Base         :     Yes   | Selection toggles inclusion |
 System (/etc):     Yes   |                             |
 Compiler     :     Yes   | a: Kernel (GENERIC)         |
 Games        :     Yes   | b: Base                     |
 Manuals      :     Yes   | c: System (/etc)            |
 Miscellaneous:     Yes   | d: Compiler Tools           |
 Text tools   :     Yes   | e: Games                    |
 X11 clients  :     No    | f: Online Manual Pages      |
 X11 fonts    :     No    | g: Miscellaneous            |
 X11 servers  :     No    | h: Text Processing Tools    |
 X11 contrib  :     No    | i: X11 base and clients     |
 X programming:     No    | j: X11 fonts                |
 X11 Misc.    :     No    | k: X11 servers              |
 k: X11 servers           | l: X contrib clients        |
 l: X contrib clients     | m: X11 programming          |
 m: X11 programming       |>n: X11 Misc.                |
                          | x: Exit                     |
                          +-----------------------------+

This window refreshed many times, then apeared to go on to the next one
before I even indicated OK:

 The following are the values you entered.  Are they OK?

 DNS Domain:             falu.nl
 Host Name:              xzan
 Primary Interface:      le0
 Host IP:                10.0.0.7
 Netmask:                0xffffff00
 IPv4 Nameserver:        10.0.0.5
 IPv4 Gateway:           10.0.0.5
 Media type:             <default>

Maybe that was because the last <return> was still in the stdin buffer.

After extracting the kernel, I saw this:

     
    







 The directory /mnt/usr/share/man/man8/arm32 has been renamed to /mnt/usr/share
 /man/man8/arm32.old because it was not empty.
 The directory /mnt/usr/share/man/man4/arm26 has been renamed to /mnt/usr/share
 /man/man4/arm26.old becaus+-----------------------+
 The directory /mnt/usr/sha| Hit enter to continue |n renamed to /mnt/usr/share
 /man/cat8/arm32.old becaus|                       |
 The directory /mnt/usr/sha|>a: ok                 |n renamed to /mnt/usr/share
 /man/cat4/arm26.old becaus+-----------------------+
 The directory /mnt/usr/share/lkm/vfs/module has been renamed to /mnt/usr/share
 /lkm/vfs/module.old because it was not empty.
 The directory /mnt/usr/share/lkm/vfs has been renamed to /mnt/usr/share/lkm/vf
 s.old because it was not empty.
 The directory /mnt/usr/share/lkm/syscall/test has been renamed to /mnt/usr/sha
 re/lkm/syscall/test.old because it was not empty.The directory  has been to i

It looks a bit strange. Then this:

     
 Cleanup of the existing install failed.  This may cause the extraction of the
 set to fail.
 





 
 
 
                           +-----------------------+
                           | Hit enter to continue |
                           |                       |
                           |>a: ok                 |
                           +-----------------------+
 
 
 
I had not chosen to see the extracted file names, since I know from
experience that on a VAX this is quite slow. 

The rest all went according to plan. I copied my old rc.conf file, and
even the ssh key generation only took a finite time. I should have
moved those keys beforehand to the new /etc but testing fresh generation
is not bad anyway.

-Olaf.
-- 
___ Olaf 'Rhialto' Seibert - rhialto@       -- Woe betide the one who feels
\X/ polderland.nl  -- remorse without sin - Tom Poes, "Het boze oog", 4444.