> > they are and they will have to be fixed before you can use the system
> > properly again.
> No, they won't.  If / gets whacked, and /usr is readonly, then a 60MB
> fsck takes far less time than a multi gigabyte fsck.
> Oh, and /usr won't corrupt on readonly file systems - there are no
> outstanding buffers.
>
> MORE, I can more easily work through a lost+found with 200 files
> than one with 2000 files.

trying to sum it up:

remove sysinst at all and put some docs about how to install system
normally (disklabel, newfs, tar/pax, installboot).

there is no "right way" and the way should be up to user.

and sysinst isn't much useful anyway.