OK, I'm trying to get my pc532 back up and running after losing
its disk.  (The new one I bought to copy to before the old one
finally gave up also died.)

However, the install program seems to have a few defects in it (I
know you can't imagine how that could possibly happen either.)
Anyway, first, it appears to not know that it needs to do a
'mount /dev/md0 /' to get the root file system writable before it
tries to play with /etc/disktab.  It reports:

     mount_ffs: /dev/rd0 on /: No such file or directory

Looks like someone made a typo of 'rd0' instead of 'md0'.
That would avoid the error message:

     //install: cannot create /etc/disktab: read-only file system
     //install: cannot create /etc/disktab: read-only file system

which followed right after the mount error.  So, after manually
mounting the root filesystem, and rerunning the install script,
ignoring the mount_ffs error, I got:

      1730592, 1757808, 1785024, 1812240, 1839456, 1866672, 1893888, 1921104,
      1948320, 1975536, 2002752,
     exec: mount_ffs /dev/sd0a /mnt
     /dev/sd0a on /mnt type ffs (local, writes: sync 2 async 0)

     Populating filesystems with bootstrapping binaries and config files
     pax: not found
     /mnt/netbsd.gz: No such file or directory

     Creating an fstab...//install: cannot create /mnt/etc/fstab: directory nonexistent
      done.

Tar is in /usr/bin, but pax is nowhere to be found.  Also, I don't
see a netbsd.gz anywhere, so that could make the 'gzip -d
/mnt/netbsd.gz' a bit difficult to execute, even if pax did copy
everything onto the new filesystem.  I wonder how easy it is going
to be to bring up the PPP link...

This isn't supposed to be a complaint, more of a "if your looking
for something to do, or were looking into the pc532 install code
anyway" kind of message.  (Well, and to let me look into the archives
and see what might need looking at later, if I get to it.) Perhaps
I should have just filed a PR or 2 instead, but the setup isn't
quite far along enough to make that fun or easy...

Jon