On Tue, 11 Nov 1997 16:14:56 +0100 (MET),
   User ZOMBIE <zombie@il.fontys.nl> writes:

>Fatal server error:
>could not open default font 'fixed'
>X connection to :0.0 broken (explicit kill or server shutdown).

Sorry. I got the options to use xfs the wrong way around the first time.
Grab the latest etc.tar.gz and xservers.tar.gz and install them,
(or untar them by hand, if that's easier for you.) 

The README.pmax file in /usr/X11R6/bin has an explanation of where
this problem comes from and how to use xfs as a workaround.
I posted a copy of it to port-pmax eaerlier today.


>As for sysinst, because I had to use a hybrid installation (1.3 didn't
>netboot correctly) I've had some trouble using it. I tried to install
>13alpha with sysinst to a second harddrive I temporarily added to the
>DECstation. I ran from the station on it's 1.3 kernel, but I encountered
>trouble all along the path.
>
>1:	sysinst didn't disklabel the second harddisk correctly.
>	(actually the label was correctly written, but when it tried to
>	newfs rz2d, the /usr partition, newfs freaked out)
>
>This marked the end of the attempt to install a new BSD on the second disk.
>I then untarred the base and etc with a copy of the fstab to the second disk
>(manually re-labeled) and told sysinst to upgrade.

Could you email a copy of the error message, please?  And the name you
used for a disklabel?  Had you tried to use that same disklabel name
in an earlier run of sysinst?  That might be related...



>2:	The upgrade went a little further. It got busy on the disk,
>	switching from time to space saving along the way, but the program
>	cored when it reached the package-selection menu.

I'm guessing you were using an 80x24 console. There was a bug in
sysinst; it was trying to paint a menu bigger than 80x24.  That's been
fixed in the latest diskimage (and also in the latest sysinst) thanks
to Simon Burge.

>Feedback please. Why is X producing errors it shouldn't? Why does it only
>complain about the font-path when the misc and 75dpi fontsdirectories are
>included (with only Speedo it only reports a Fatal error because it can't
>FIND 'fixed', as opposed to the usual three lines of about errors setting 
>the default path)?


The README.pmax tries to explain this.  In brief, it's due to a change
in standard font names and aliases that the X consortium made between
R5 and R6.  The R6 font directories shipped with all NetBSD ports
don't have quite the same names for fonts as the R5 server expects.