From: ace3@quads.uchicago.edu (AA Acero (Tony)) Subject: Using the 8514a Xserver w x11v2.0 Date: Mon, 21 Sep 1992 04:09:41 GMT
The following is Kevin Martin's reply to my questions regarding
setting up his 8514a Xserver to work with X386 v 2.0; I hope users of
his excellent 8514a server will find it helpful in setting it up under
v. 2.0.
>
>
>> After playing around with the fonts some more I have more problems to
>> report.
>>
>> First, the server as it is now does not support the Speedo, Type1 and
>> BitstreamType1 fonts that are part of the distribution. It is not
>> completely clear to me but it seems the support is in the base x11v2.0
>> distribution and the server must be recompiled under this source tree
>> for the support to be added.
>
>You are correct on both accounts. The Speedo, Type1 and BitstreamType1
>fonts are not currently supported in Xlinux.8514. To get this support,
>someone (me if I ever get a break - not likely) will have to port my
>changes to XFree86. I welcome anyone who has the time/expertise to do
>this.
>
>> Second, the fonts are being distributed in a compressed format --
>> apparently this format is directly supported by the new servers. I
>> not only had to uncompress the fonts, but I also had to edit the
>> fonts.dir file to get the server to recognize the ~/fonts/misc/ and
>> ~/fonts/75dpi/ fonts. (I didn't catch this step yesterday because I
>> accidentally untarred the old fonts directory over the x11v2.0
>> distrubition, and everything started working (because the old
>> fonts.dir had overwritten the new)).
>
>Thanks for this info. I'll pass it along to others. If you have any
>other problems with the X11v2.0 release and Xlinux.8514, please keep
>me informed so that I can relay this info. Actually, why don't you
>send this info directly to the X11 channel and c.o.l? Maybe this will
>head off some questions/problems.
>
>I hope the xfm problems go away when you repartition you HD. If this
>is the case, can we chalk this up to a problem in the extended partition
>code? I'm not convinced of this since the program crashed on an X
>function although this might have been the end result of a problem that
>lies elsewhere.
>
>Thanks,
>Kevin
>___
>Kevin E. Martin University of North Carolina at Chapel Hill
>martin@cs.unc.edu Department of Computer Science
tony acero