From: John Wiersba <John.Wiersba@medstat.com>
To: "'Christopher Faylor'" <cygwin@sourceware.cygnus.com>,
"'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: RE: question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, find, less, zip, ls
Date: Tue, 22 Jun 1999 13:57:00 -0000 [thread overview]
Message-ID: <03F4742D8225D21191EF00805FE62B990205E16A@AA-MSG-01> (raw)
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@sourceware.cygnus.com ]
> Sent: Tuesday, June 22, 1999 4:42 PM
> To: John Wiersba
> Cc: 'cygwin@sourceware.cygnus.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@sourceware.cygnus.com
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: John Wiersba <John.Wiersba@medstat.com>
To: "'Christopher Faylor'" <cygwin@sourceware.cygnus.com>,
"'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: RE: question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, find, less, zip, ls
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <03F4742D8225D21191EF00805FE62B990205E16A@AA-MSG-01> (raw)
Message-ID: <19990630221000.2EZDjESxud0ZySMGwbp65GDF9zrqxkU3Go1CPIgYlkw@z> (raw)
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@sourceware.cygnus.com ]
> Sent: Tuesday, June 22, 1999 4:42 PM
> To: John Wiersba
> Cc: 'cygwin@sourceware.cygnus.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@sourceware.cygnus.com
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-06-22 13:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 13:57 John Wiersba [this message]
1999-06-22 14:07 ` DJ Delorie
1999-06-30 22:10 ` DJ Delorie
1999-06-30 22:10 ` John Wiersba
-- strict thread matches above, loose matches on Subject: below --
1999-06-23 6:19 Lincoln, W. Terry
1999-06-30 22:10 ` Lincoln, W. Terry
1999-06-22 12:09 Lincoln, W. Terry
1999-06-30 22:10 ` Lincoln, W. Terry
1999-06-22 11:57 John Wiersba
1999-06-22 13:41 ` Christopher Faylor
1999-06-30 22:10 ` Christopher Faylor
1999-06-30 22:10 ` John Wiersba
1999-06-21 15:59 Phil Edwards
1999-06-21 16:32 ` Brendan Simon
1999-06-30 22:10 ` Brendan Simon
1999-06-22 11:00 ` itz
1999-06-30 22:10 ` itz
1999-06-30 22:10 ` Phil Edwards
1999-06-21 15:40 John Wiersba
1999-06-30 22:10 ` John Wiersba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03F4742D8225D21191EF00805FE62B990205E16A@AA-MSG-01 \
--to=john.wiersba@medstat.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).