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
Date:	Thu, 24 Jun 1999 12:47:54 -0400
From:	Phil Edwards <pedwards AT jaj DOT com>
Message-Id:	<199906241647.MAA19444@jaj.com>
To:	cygwin AT sourceware DOT cygnus DOT com, John DOT Wiersba AT medstat DOT com
Subject:	RE: cat broken

> > > Using the 5/23 cygwin1.dll, the following is broken:
> > > 	cat >file
> > > It echos the input typed from the terminal
> > 
> > Uh, that's what is supposed to happen... unless you mean that it ONLY
> > echos the input, and writes a zero-length file?
>
> No, "cat >file" should take input from stdin (the terminal) and write it to
> file, which in fact is what happens with the 1/15 cygwin1.dll.  However, the
> 5/23 dll echos the input from terminal back to the terminal.

Let me try again.  On any and every Unix,

   $ cat > file
   This is a test.
   ^D
   $ 

should echo to the screen as well as write to the file.  You will be hard
pressed to not get that stuff echoed on the screen.  I'm /hoping/ that your
problem is that cat is /only/ echoing to the screen and not /also/ writing
a file.  Check?


Now, the errors that you're seeing after replacing the DLL (those freaky
trace thingies) are indeed due to a mismatch between a binary and the DLL.
That's the only major problem with using the inst snapshots; it's harder
to keep things in sync (e.g., backing out replacements, or not getting a
new binary with a new DLL).  How you as an end user manage that is largely
a matter of taste -- copying directory structures and updating a copy, or
reinstalling original binaries from a distribution, or just living with
the nonfatal errors, etc, etc.


(If you reply to the list, please DON'T cc another copy to me.  Thanks!)
Phil


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

- Raw text -