Subject: port-mac68k/29049: mac68k sysinst for 2.0 doesn't work for the install case. It works for the upgrade case
To: None <port-mac68k-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: None <edoneel@sdf.lonestar.org>
List: netbsd-bugs
Date: 01/23/2005 11:02:00
>Number:         29049
>Category:       port-mac68k
>Synopsis:       mac68k sysinst for 2.0 doesn't work for the install case.  It works for the upgrade case
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-mac68k-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jan 23 11:02:00 +0000 2005
>Originator:     Bruce ONeel
>Release:        2.0
>Organization:
None what so ever
>Environment:
NetBSD 2.0 (GENERICSBC) mac68k
>Description:
The sysinst install for Mac68k doesn't do a few necessary steps.

- After one has chosen to partition the disk one is asked, shall we continue, nothing has been written yet.  If you say yes then very very quickly you end up on the extract verbosity question.  What seems to happen (these systems are too fast, the screen flashes the messages too fast) is that the disklabel command is done, but, the newfs is not.  Newfs on my 040 takes a good 30 seconds.  Since the newfs wasn't done then the new root system is not mounted at /targetroot and the extract of sets is just about to fail.

If at the extract verbosity menu one types ^Z and types

newfs /dev/sd0a 

mount /dev/sd0a /targetroot

and then fg to get back into sysinst then one can continue with the untaring of the sets.

Sadly all isn't completely well.

- on reboot things go badly because /etc/fstab wasn't written.  One must manually create it.

If you already have say 1.6.2 on the system then the upgrade step works fine.
>How-To-Repeat:
Boot the install kernel for mac68k and try the install path and not the upgrade path.
>Fix:
See above.  My *guess* is that newfs isn't running for some bizzare reasons.