Subject: sysinst on mac68k is really bad!
To: None <port-mac68k@NetBSD.org>
From: Paul Sander <paul@wakawaka.com>
List: port-mac68k
Date: 06/20/2004 16:51:51
Hi folks,

I've just spent the bulk of my afternoon fighting with the new installation
kernel for NetBSD 1.6.2 on a Centris 650.  I've come across three show-
stoppers:

- After formatting the root partition, it's left in a state that can't
  be subsequently upgraded.  This happens after formatting it for the
  first time, then exiting.  The shell can't read the root filesystem,
  and neither can the installation program after exiting the shell
  (when choosing the upgrade option from the main menu).
- When installing from an ISO-9660 CD image, neither of the kernel
  install sets can be found because their names exceed the 8.3 limitation.
  In my case, the CD is produced using a version of Toast that does not
  support the Unix-style long names that the installer seems to expect.
  And there's no option to install a set that I can identify by hand, or
  override the name of the kernel install set.
- After completing a fresh install (less kernel), the installer complains
  that the new filesystem isn't readable, and it gives a nonsensical
  path that ends with the name of a timezone file.

There are also several major annoyances:

- Fresh install formats every partition, not just the root partition.
  This makes it impossible to do a fresh install without losing whatever
  might be on the other partitions.
- When choosing a directory on a CD to copy install sets from, I can't
  explore the filesystem on the CD.  That is to say, I must know beforehand
  what directory contains the sets and type it in, rather than do an ls/cd
  sequence before choosing a directory.
- When choosing install sets to install, I can't get a listing of the
  sets that are available.
- The names of the install sets are hard-coded in the installer, so if
  there are custom packages that also happen to be in gzipped tar format
  I can't install them at the same time.

So, back to the old tools I go.  How can I file bug reports for these
problems?

Thanks,

Paul