public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Earnie Boyd" <earnie_boyd@hotmail.com>
To: gnu-win32@cygnus.com, marcus@bighorn.dr.lucent.com
Subject: Re: Bug in od, cat, etc reading binary files
Date: Fri, 26 Sep 1997 11:34:00 -0000	[thread overview]
Message-ID: <19970926183330.261.qmail@hotmail.com> (raw)

>From: marcus@bighorn.dr.lucent.com
>Date: Fri, 26 Sep 1997 09:41:22 -0600
>To: gnu-win32@cygnus.com
>Subject: Re: Bug in od, cat, etc reading binary files
>
>> >It seems to me that if one wants to port software into the NT 
environment
>> >then one has no choice but to run the normal way NT programs do 
(without
>> 
>> A. We are not porting to NT, we are porting to the cygwin32 API
>> B. Most Un*x tools expect Binary IO, mounting without -b will break 
many configure scripts
>
>I have to agree with the original poster on this.  What good is the 
cygwin32
>API on NT if it is not compatible with the rest of NT?  If you are 
going to
>only use programs running in the cygwin32 world, then why not just run 
Linux
>instead and get better performance and better compatibility?  If you're
>running NT, it seems that you likely need it to run some other things 
that
>only run on NT, so if cygwin32 is to be useful, it should also be able 
to
>deal with files produced by or intended for these other programs.
>
>Sure, it may be a royal pain to have to deal with the compatibility 
problems,
>and that's probably where a lot of the ugliness of NT comes from, but I 
think
>that that's the reality of the NT world.  If you don't want to be 
compatible
>with the rest of the NT world, why try to run on NT in the first place?
>
>marcus hall
>-

Marcus

The cygwin32 isn't for compatibility with NT it is to provide a 
mechanism for which those things that aren't can be ported to the win32 
environment.  Because of this the cygwin32 layer must try to be 
compatible to both worlds (which it does, nicely).  The problem isn't 
cygwin32 it is the lack of tools ported without modification for binary 
versus text that is the problem.  Therefore remaining in the binary 
format is not an alternative it becomes necessary.

-        \\||//
---o0O0--Earnie--0O0o----
-earnie_boyd@hotmail.com-
------ooo0O--O0ooo-------


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1997-09-26 11:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-26 11:34 Earnie Boyd [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-09-30  7:14 Larry Hall
1997-09-30  5:02 Earnie Boyd
1997-09-29 18:48 Earnie Boyd
1997-09-29  7:41 marcus
1997-09-29 18:31 ` Pete Jordan
1997-09-29  7:09 marcus
1997-09-29 13:04 ` Mikey
1997-09-29 18:33 ` justin.
1997-09-27 10:03 Larry Hall
1997-09-26  8:42 marcus
1997-09-25  1:22 Eric Mills
1997-09-25  6:23 ` Mikey
1997-09-22 10:29 Earnie Boyd
1997-09-22  8:15 Larry Hall
1997-09-22  1:30 Eric De Mund
1997-09-08 14:23 Joe Peterson

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=19970926183330.261.qmail@hotmail.com \
    --to=earnie_boyd@hotmail.com \
    --cc=gnu-win32@cygnus.com \
    --cc=marcus@bighorn.dr.lucent.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).