Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<03F4742D8225D21191EF00805FE62B990205E16A@AA-MSG-01>
From:	John Wiersba <John DOT Wiersba AT medstat DOT com>
To:	"'Christopher Faylor'" <cygwin AT sourceware DOT cygnus DOT com>,
	"'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	RE: question (latest "stable" dll?) + bugs: vim, bash, gcc, cp,
	find, less, zip, ls
Date:	Tue, 22 Jun 1999 16:56:41 -0400
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2448.0)

Christopher,

I took my cygwin1.dll from ftp://sourceware.cygnus.com/pub/cygwin/snapshots/
which doesn't show any mount.exe.  I was looking for the dll closest in date
to the 3/28 date mentioned in the referenced email.  So, after I exited all
cygwin processes and switched in the 5/23 cygwin1.dll and restarted a bash
shell, my mounts were screwed up.  I couldn't even find mount.exe because my
cygwin directory wasn't mounted (i.e. / wasn't mounted properly).  After
some amount of playing around in the registry, I got my cygwin directory
mounted properly, so from that point on I was able to use the old (i.e.
1/16) version of mount to remount my other directories.  If I read your
email correctly, you're saying that there is a newer version of mount.exe
which I could use.  For obvious reasons, I didn't want to download/install
cygwin-inst-XXX (where the new mount.exe is located?) until I had verified
that cygwin1.dll worked ok.  

Eventually, I'll probably unpack the bash source and see if I can diagnose
the "cd /; cd x/y" bug.  I agree it does sound like a bash bug.  For now I
have an ugly work around: I defined a bash function which hooks the cd
command and checks if I'm in the root and referencing a relative path which
exists under the root (knowing that . is the first entry in my CDPATH) and
prepends a / to the path before calling the real cd command.

-- John

> -----Original Message-----
> From: Christopher Faylor [mailto:cygwin AT sourceware DOT cygnus DOT com]
> Sent: Tuesday, June 22, 1999 4:42 PM
> To: John Wiersba
> Cc: 'cygwin AT sourceware DOT cygnus DOT com'
> Subject: Re: question (latest "stable" dll?) + bugs: vim, 
> bash, gcc, cp,
> find, less, zip, ls
> 
> 
> On Tue, Jun 22, 1999 at 02:56:38PM -0400, John Wiersba wrote:
> >Since no one has yet suggested a "stable" release of 
> cygwin1.dll after 1/16,
> >I tried the 5/23 release (it was the earliest one I could 
> find after the
> >3/28 date mentioned below).  It seems to be relatively 
> stable so far (i.e.
> >I've used it for several minutes so far!).  I did have to twiddle the
> >registry settings for mounts (not unexpected, after the 
> comment about mounts
> >below).
> 
> What does "twiddle the registry settings" mean, exactly?  
> Does that mean that
> you didn't use the newer "mount" program which is associated 
> with the DLL?
> 
> AFAIK, there should be no need for any manual invervention in 
> switching from
> an older DLL to a newer.  The new DLL should read the older 
> mount settings
> and copy them to the appropriate place in the registry.
> 
> >2) It does not however seem to fix the "cd /; cd 
> relativepath/dir" problem
> >(apparently going out to the LAN).  Note that cd does 
> eventually work -- it
> >just hangs for several seconds before figuring things out. 
> >
> >=> Additional information: it doesn't hang when CDPATH is 
> unset.  It does
> >hang when CDPATH=.
> 
> So, in other words, this is probably  bash bug.  Is anyone 
> willing to debug
> this and offer a fix?
> 
> cgf
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -