Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3F0B73A8.9090501@msu.edu> Date: Tue, 08 Jul 2003 21:45:12 -0400 From: Harold L Hunt II User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin-xfree AT cygwin DOT com CC: Gerald Pekmezi , cygwin AT cygwin DOT com Subject: Re: CYGWIN_ROOT Question -- Attn: XFree86-fnts maintainer References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Igor, Thanks for the fix. This was indeed my fault and the fix is elegant. I have uploaded 4.2.0-3 versions of all of the fonts packages, which will fix the problem, but will annoy those that have already downloaded them... Harold Igor Pechtchanski wrote: > Gerald, > > Well, this is not a bug in setup.exe, but it looks like a bug in the > postinstall scripts for the XFree86-f??? packages. Basically, the scripts > re-mount /usr/X11R6/lib/X11/fonts to force a binary mount. They use > `cygpath -w` to find the Windows path of the fonts directory. > Unfortunately, they do it *before* unmounting the old one, so if you > change the Cygwin installation root between the runs of the scripts, they > will still refer to the old directory. > > The fix (for the postinstall scripts) is to unmount the directory *first*, > and then run `cygpath -w`. The corrected postinstall scripts would each > look like this: > > #!/bin/sh > > FONTDIR=/usr/X11R6/lib/X11/fonts > umount -u $FONTDIR 2>/dev/null > WFONTDIR=`cygpath -w $FONTDIR` > mount -bfs $WFONTDIR $FONTDIR 2>/dev/null || mount -bfu $WFONTDIR $FONTDIR > > The same changes as a patch (for XFree86-fnts.sh) are below. > > Hopefully this makes its way into the fonts package. Until it does, you > could simply "umount -u /usr/X11R6/lib/X11/fonts", and re-install all of > the XFree86-f??? packages that you need using setup.exe. > Igor > ============================================================================== > --- XFree86-fnts.sh-orig 2002-04-28 02:11:37.000000000 -0400 > +++ XFree86-fnts.sh 2003-07-02 19:16:29.000000000 -0400 > @@ -1,6 +1,6 @@ > #!/bin/sh > > FONTDIR=/usr/X11R6/lib/X11/fonts > -WFONTDIR=`cygpath -w $FONTDIR` > umount -u $FONTDIR 2>/dev/null > +WFONTDIR=`cygpath -w $FONTDIR` > mount -bfs $WFONTDIR $FONTDIR 2>/dev/null || mount -bfu $WFONTDIR $FONTDIR > ============================================================================== > > On Wed, 2 Jul 2003, Gerald Pekmezi wrote: > > >>Thanks for the reply >> >>I have come to believe this is an X problem after all and will add a post >>there. >>It seems that during my cygwin installation everything was installed in D: >>(D:\usr, D:\bin etc), except for usr\X11R6\lib\X11\fonts. which was instead >>installed as C:\cygwin\usr\X11R6\lib\X11\fonts . When I restore the latter >>XWin will run however it refuses to do so if >>C:\cygwin\usr\X11R6\lib\X11\fonts does not exist. I did add the font >>directory to D:\usr\X11R6\lib\X11\, but it did not make a difference. >>Possible bug in cygwin setup.exe? >> >>"Larry Hall" wrote in message news:3F02E9F7 DOT 6010505 AT cygwin DOT com... >> >>>Gerald Pekmezi wrote: >>> >>> >>>>Thanks in advance for helping. >>>> >>>>I originally had Linux RH9 installed on the second partition of my >>>>primary (and at the time only) harddrive. I have since dedicated a >>>>secondary hard drive to Linux, and figured I would completely >>>>dedicate the partition to Cygwin (D:\). However I have begun to >>>>suspect that setting CYGWIN_ROOT to D:\ is not sufficient (XWin >>>>refuses to run, I don't think its an X problem, but if it is I guess >>>>this post will be moved). >>>>My question is whether there is a quick fix to this or whether it is >>>>more trouble than it is worth. >>> >>>Hm. Now that's a good one. Perhaps my memory is failing me but in all >>>the years I've been using Cygwin, I don't ever recall CYGWIN_ROOT being >>>officially used. Perhaps you should back up and start over with: >>> >>> >>>and >>> > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/