From: "Dr. Volker Zell" <vzell@de.oracle.com>
To: John Wiersba <John.Wiersba@medstat.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: cat broken
Date: Thu, 24 Jun 1999 08:29:00 -0000 [thread overview]
Message-ID: <kvpv2l1uq3.fsf@vzell.de.oracle.com> (raw)
In-Reply-To: <03F4742D8225D21191EF00805FE62B990205E17C@AA-MSG-01>
>>>>> "John" == John Wiersba <John.Wiersba@medstat.com> writes:
John> I tried the 6/10 dll. It fixed the cat problem. But now I
John> frequently get the following error message: 0 0 [main]
John> D:\opt\cygwin\bin\bash.exe 1008 fhandler_base::fork_fixup:
John> /jrw/jrw/mdst/sh/d - Win32 error 6, handle 0x30
John> Is this caused by a mismatch in bash.exe (dated 12/1/98)
John> vs. cygwin1.dll? Do I have to install everything in the
John> 6/10 cygwin-inst*, too? That's more dangerous because it's
John> harder to back out.
I installed only the dll. My CYGWIN env liks like:
System: WinNT 4.0/SP3
Cygwin B20.1 with egcs-1.1.2
- cygwin1.dll - cygwin1-19990610.dll.gz
- everything mounted binary,
- CYGWIN = tty title binmode ntea nontsec
Ciao
Volker
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: "Dr. Volker Zell" <vzell@de.oracle.com>
To: John Wiersba <John.Wiersba@medstat.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: cat broken
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <kvpv2l1uq3.fsf@vzell.de.oracle.com> (raw)
Message-ID: <19990630221000.6nvbpOO92klNjLng6u88R0CNGub23z8a6C7jX2B8ahY@z> (raw)
In-Reply-To: <03F4742D8225D21191EF00805FE62B990205E17C@AA-MSG-01>
>>>>> "John" == John Wiersba <John.Wiersba@medstat.com> writes:
John> I tried the 6/10 dll. It fixed the cat problem. But now I
John> frequently get the following error message: 0 0 [main]
John> D:\opt\cygwin\bin\bash.exe 1008 fhandler_base::fork_fixup:
John> /jrw/jrw/mdst/sh/d - Win32 error 6, handle 0x30
John> Is this caused by a mismatch in bash.exe (dated 12/1/98)
John> vs. cygwin1.dll? Do I have to install everything in the
John> 6/10 cygwin-inst*, too? That's more dangerous because it's
John> harder to back out.
I installed only the dll. My CYGWIN env liks like:
System: WinNT 4.0/SP3
Cygwin B20.1 with egcs-1.1.2
- cygwin1.dll - cygwin1-19990610.dll.gz
- everything mounted binary,
- CYGWIN = tty title binmode ntea nontsec
Ciao
Volker
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-06-24 8:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-24 8:18 John Wiersba
1999-06-24 8:29 ` Dr. Volker Zell [this message]
1999-06-30 22:10 ` Dr. Volker Zell
1999-06-24 11:51 ` Chris Faylor
1999-06-30 22:10 ` Chris Faylor
1999-06-30 22:10 ` John Wiersba
-- strict thread matches above, loose matches on Subject: below --
1999-06-24 15:57 John Wiersba
1999-06-30 22:10 ` John Wiersba
1999-06-24 12:03 John Wiersba
1999-06-24 12:11 ` Chris Faylor
1999-06-30 22:10 ` Chris Faylor
1999-06-30 22:10 ` John Wiersba
1999-06-24 10:56 Earnie Boyd
1999-06-30 22:10 ` Earnie Boyd
1999-06-24 10:00 John Wiersba
1999-06-30 22:10 ` John Wiersba
1999-06-24 9:37 Phil Edwards
1999-06-30 22:10 ` Phil Edwards
1999-06-23 15:47 John Wiersba
1999-06-30 22:10 ` John Wiersba
1999-06-23 14:52 Phil Edwards
1999-06-30 22:10 ` Phil Edwards
1999-06-23 12:42 John Wiersba
1999-06-24 0:49 ` Dr. Volker Zell
1999-06-30 22:10 ` Dr. Volker Zell
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=kvpv2l1uq3.fsf@vzell.de.oracle.com \
--to=vzell@de.oracle.com \
--cc=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).