Subject: likely dumb question
To: None <port-sun3@NetBSD.ORG>
From: Ken Wellsch <kcwellsc@math.uwaterloo.ca>
List: port-sun3
Date: 04/22/1996 12:25:58
I'm involved with the NetBSD port to the VAX line and brought one of my
Sun-3's home from storage to help out with the work (i.e. to give me access
to a QIC tape drive as I do not have very good Internet access - for bringing
large bin/src images and such home).

I am working with a Sun 3/140 (8Mb and VME si) and a couple of Micropolis
1558 drives (via MD21s).  I've been able to update my old image to what
is NetBSD-current level.

For security I then tried to install my one setup onto the second drive
(which I believe I formatted a year ago when I had access to a SunOS system).

I was pleased to see the nice increase in file space with the new fs stuff
(my older disk had a year old copy of netbsd and says 4.2/4.3 while the new
via dumpfs says 4.4).  After dump/restoring onto the new fs (root/usr) I
was impressed with the extra space I had.

Unfortunately I do not seem to be able to correctly label the new disk so
it can boot.  After adding "memcpy" to the sun3/stand/Makefile so the stand-
alone stuff would compile, I followed the read-me but without success.
The system monitor says "no label" and punts to ie().

I've ended up doing a "dd" of the original disk but that does not give me
access to the nice shiny new fs layout and such...  even after "fsck -c 3"
I didn't see any space change magic like the first transition via newfs/dump.

-- Ken Wellsch

P.S. I failed also to make a bootable installation tape - I suspect my
old 160 board does not gronk my QIC-150 or visa-versa (I get a short read
error when tapeboot tries to finish loading netbsd-rd).