From: culliton@srg.af.mil (Tom Culliton x2278)
To: byron@archone.tamu.edu, rc@archone.tamu.edu
Subject: Re: redirection bug
Date: Wed, 12 Feb 1992 10:37:54 -0600 [thread overview]
Message-ID: <9202121137.aa04813@ceres.srg.af.mil> (raw)
>> Here's the patch to the extra-fork redirection bug that Chris just
>> mentioned:
>>
>> (this patch comprises all the changes made to walk.c since rc-1.3beta,
>> but fortunately there is just one other minor change in addition to this
>> one:)
I'm confused. Do you mean that this is a patch for Chris's bug plus
one other minor thing or that there is one other minor patch to 1.3beta
beside this? (maybe the patch for builtin.c?) In any case 1.3beta has
held up quite well to substantial abuse aside from the oddness with
SIGINT I noted earlier.
As a side note I've collected several hints for other SCO Unix users if
anyone is intrested, everything from patches to system include files to
small rc functions that improve speed substantially. For example,
fn true { return 0 }
is a big win vs. firing up the Bourne shell every time through a loop
with "while (true)".
Tom
next reply other threads:[~1992-02-12 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-02-12 16:37 Tom Culliton x2278 [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-03-20 19:27 Byron Rakitzis
1992-03-20 17:57 schwartz
1992-03-20 19:17 ` Brendan Kehoe
1992-02-12 4:38 Byron Rakitzis
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=9202121137.aa04813@ceres.srg.af.mil \
--to=culliton@srg.af.mil \
--cc=byron@archone.tamu.edu \
--cc=rc@archone.tamu.edu \
/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 NNTP newsgroup(s).