This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: startx fails with: could not open default font 'fixed'
- To: cygwin-xfree at sourceware dot cygnus dot com
- Subject: RE: startx fails with: could not open default font 'fixed'
- From: "Karr, David" <david dot karr at cacheflow dot com>
- Date: Tue, 11 Sep 2001 15:10:08 -0700
I understand now. So, unless I'm misunderstanding something again, the ONLY
way to install this correctly is to install it on a binary mount, correct?
Suhaib's response gave me the impression I could also manually gunzip and
untar, but if I can install it by changing to binary, installing, and then
changing back to text, I could accept that. I don't want to leave it in
binary mode, however. Will it still work if I change it back to text
afterwards?
Is there any way to fix the install process so this doesn't become a
problem? If not, wouldn't it be a good idea to put code in the install
script that aborts with an error if you try to install on a text mount
(assuming there's no way that can work)?
-----Original Message-----
From: Harold Hunt [mailto:huntharo@msu.edu]
Sent: Tuesday, September 11, 2001 3:00 PM
To: Karr, David; cygwin-xfree@sourceware.cygnus.com
Subject: RE: startx fails with: could not open default font 'fixed'
David,
> First of all, the FAQ entry seems slightly wrong. The paragraph on point
> "1" begins thusly:
>
> Using Xinstall.sh to install Cygwin/XFree86 on a text-mode Cygwin mount
> rather than binary-mode mount. You will
> need to change your default Cygwin mount mode to binary-mode and rerun
> the Xinstall.sh script ...
Remember to read the sentence right before that:
There are two known ways of installing the fonts that causes the end of line
characters to be incorrect: Using Xinstall.sh to install Cygwin/XFree86 on a
text-mode Cygwin mount rather than binary-mode mount.
> If I understand this correctly, the first sentence should have "text-mode"
> and "binary-mode" reversed.
Nope. You didn't read everything in the question/answer.
> Now, on the alternative idea of "manually ungziping and untarring", what
> exactly do I ungzip and untar, and where do I put it? The FAQ
> entry refers
> to using a non-Cygwin-aware unpacker, like "Winzip", which I
> don't presently
> have
Oh man. Now I know that you aren't reading everything. Question/Answer 6.3
specifically says NOT to use Winzip.
You really have to read more carefully.
Harold