XFree86 install fails

[Harold L Hunt II]

Chris,

The mount information is pretty much the only information that Cygwin 
stores in the registry, and unfortunately it is not cleared when you 
uninstall Cygwin/XFree86.  At least, I don't recall that it is cleared. 
 I will probably add something about this to the FAQ, eventually.

Harold

Chris plonski wrote:

>Thanks!  This did the trick!  I just have a question now, where is this
>mount information stored?  I started out by deleting any previous cygwin
>directory trees.  Does cygwin use the windows registry to save previous
>configurations?
>
>On Wed, 2002-10-16 at 18:39, Harold Hunt wrote:
>  
>
>>Chris,
>>
>>You need to run ``mount'' from a Cygwin bash prompt and check the location
>>of your fonts mount.  For example, here is what I get:
>>
>>Administrator@HUNTHARO ~
>>$ mount
>>C:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system
>>(binmo
>>de)
>>C:\cygwin\bin on /usr/bin type system (binmode)
>>C:\cygwin\lib on /usr/lib type system (binmode)
>>c:\PalmDev on /PalmDev type system (textmode)
>>C:\cygwin on / type system (binmode)
>>c: on /cygdrive/c type user (binmode,noumount)
>>w: on /cygdrive/w type user (binmode,noumount)
>>y: on /cygdrive/y type user (binmode,noumount)
>>z: on /cygdrive/z type user (binmode,noumount)
>>
>>
>>My guess is that at some point you had Cygwin/XFree86 installed to a
>>different drive that is no longer available.  You can unmount your current
>>mount for /usr/X11R6/lib/X11/fonts and either 1) remount it if your default
>>mount is not binary mode, or 2) leave out that mount if your default mount
>>is binary mode.
>>
>>Harold
>>
>>    
>>
>>>-----Original Message-----
>>>From: cygwin-xfree-owner@cygwin.com
>>>[mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Chris Plonski
>>>Sent: Wednesday, October 16, 2002 5:47 PM
>>>To: cygwin-xfree@cygwin.com
>>>Subject: XFree86 install fails
>>>
>>>
>>>I have seen this on multiple Win2k SP3 machines.  I cannot
>>>perform a new install of the XFree86 package.  The setup proceeds
>>>as normal till it gets to the fonts.  It will freeze unpacking
>>>the first font package, and I have to cancel.  I have tried to
>>>manually running bunzip2 on any of the fonts packages, and it
>>>fails with aas follows:
>>>
>>>$ bunzip2 XFree86-fenc-4.2.0-2.tar.bz2
>>>
>>>bunzip2: I/O or other error, bailing out.  Possible reason follows.
>>>bunzip2: Invalid argument
>>>        Input file = XFree86-fenc-4.2.0-2.tar.bz2, output file =
>>>XFree86-fenc-4.
>>>2.0-2.tar
>>>bunzip2: Deleting output file XFree86-fenc-4.2.0-2.tar, if it exists.
>>>
>>>Using a win utility to extract out the .tar file and issuing a
>>>tar -xvf command does as follows:
>>>$ tar -xvf XFree86-fenc-4.2.0-2.tar
>>>usr/X11R6/lib/X11/fonts/
>>>tar: usr/X11R6/lib/X11/fonts: Cannot mkdir: No such file or directory
>>>usr/X11R6/lib/X11/fonts/encodings/
>>>tar: usr/X11R6/lib/X11/fonts/encodings: Cannot mkdir: No such
>>>file or directory
>>>
>>>I attempted to simply issue a mkdir command as follows, and it
>>>fails doing that too!
>>>
>>>$ mkdir /usr/X11R6/lib/X11/fonts
>>>mkdir: cannot create directory `/usr/X11R6/lib/X11/fonts': No
>>>such file or directory
>>>
>>>What's up?
>>>      
>>>
>
>
>  
>