public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Alex <garbanzo@hooked.net>
To: gnu-win32@cygnus.com
Subject: Re: Output redirection, file creation, and libjpeg.a
Date: Mon, 13 Oct 1997 14:33:00 -0000	[thread overview]
Message-ID: <Pine.BSF.3.96.971013142504.624A-100000@zippy.dyn.ml.org> (raw)
In-Reply-To: <2.2.32.19971013160906.00951028@ma.ultranet.com>

I've seen a few threads so far on this list about the default mode for
opening pipes, and the arguments for and against each way.  Along those
lines, I've noticed that FreeBSD has a nice little interface to some of
the system configuration stuff sysctl({3|8}), sysctl(8) being a wrapper
of sorts. This got me to thinking, something like this could be really
useful for enabling or disabling certian debugging stuff.  I know that the
mount table is stored in the registry already, what about something like
this?  For instance, one could say type sysctl -c debug.sigchld=1, and it
would effect everything globally, and it would provide a more uniform way 
to check various options. Thoughts?

On Mon, 13 Oct 1997, Larry Hall wrote:

> Actually, regardless of how the file systems are mounted, if you are using
> the bash that came with the original b18, stdin, stdout, stderr, and pipes
> will be opened in text mode.  The later version of bash (2.0.1) compiled by
> Sergey does NOT set all these to text mode and therefore you won't get 
> carriage returns appended.  I am uncertain whether mounting file systems as
> binary using the original version of bash would remove the carriage returns
> from stdin, stdout, and stderr (probably not) but the problem would persist
> for pipes.  See Sergey's patches for the new bash (and patched cygwin DLL) - 
> http://www.lexa.ru/sos .

- alex

-
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-10-13 14:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-13  9:19 Larry Hall
1997-10-13 14:33 ` Alex [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-10-13 10:28 Earnie Boyd
1997-10-13  5:07 Earnie Boyd
1997-10-12 10:20 Victor Schneider

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=Pine.BSF.3.96.971013142504.624A-100000@zippy.dyn.ml.org \
    --to=garbanzo@hooked.net \
    --cc=gnu-win32@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).