From: clemc@ccc.com (Clem cole)
Subject: [TUHS] SYSTEM V R1 HELP
Date: Sat, 23 Dec 2017 07:26:58 -0500 [thread overview]
Message-ID: <49F79F9D-9E03-40C9-9973-14D4A3069257@ccc.com> (raw)
In-Reply-To: <20171223002146.GS17720@mcvoy.com>
V1.
Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite.
> On Dec 22, 2017, at 7:21 PM, Larry McVoy <lm at mcvoy.com> wrote:
>
>> On Sat, Dec 23, 2017 at 11:19:30AM +1100, Dave Horsfall wrote:
>>> On Fri, 22 Dec 2017, Random832 wrote:
>>>
>>> I've got it. The problem is with putc (actually _flsbuf), and it is
>>> precisely *because* stderr is unbuffered.
>>>
>>> #define putc(x, p) (--(p)->_cnt >= 0 ? \
>>> ((int) (*(p)->_ptr++ = (unsigned char) (x))) : \
>>> _flsbuf((unsigned char) (x), (p)))
>>
>> [...]
>>
>> That, sir, is one brilliant piece of analysis; well done! Of course, in
>> hindsight it's bleedin' obvious :-)
>
> I'm curious as to which release of System V fixed this. The SVR4 was the
> release that gained (some) traction, was it busted until then?
next prev parent reply other threads:[~2017-12-23 12:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 22:12 William Corcoran
2017-12-21 22:30 ` Clem Cole
2017-12-22 0:34 ` William Corcoran
2017-12-22 1:51 ` William Corcoran
2017-12-22 1:54 ` William Corcoran
2017-12-22 2:55 ` Random832
2017-12-22 3:47 ` William Corcoran
2017-12-22 9:09 ` Random832
2017-12-22 12:42 ` William Corcoran
2017-12-22 23:48 ` William Corcoran
2017-12-23 0:19 ` Dave Horsfall
2017-12-23 0:21 ` Larry McVoy
2017-12-23 12:26 ` Clem cole [this message]
2017-12-22 15:04 ` Clem Cole
2017-12-22 1:55 ` Random832
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=49F79F9D-9E03-40C9-9973-14D4A3069257@ccc.com \
--to=clemc@ccc.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 NNTP newsgroup(s).