From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: echo -n
Date: Thu, 23 Nov 2006 20:17:27 -0800 [thread overview]
Message-ID: <20A49DB2-5E13-40C5-93B9-D15D487D649B@orthanc.ca> (raw)
In-Reply-To: <3b8ca08e65a47af482e25d1b764043bd@plan9.bell-labs.com>
On Nov 21, 2006, at 5:32 PM, dmr@plan9.bell-labs.com wrote:
> 8th edition streams began to transmit them
> over pipes (or networks).
Since this thread started I've been nagged by the memory of UUCP's
'e' protocol. If my brain hasn't completely cached out, 'e' used the
ability of Datakit to preserve 0-length messages as an inband
delimiter, vs. the 't' protocols use of explicit protocol field
length counters. (Or was it 'x' that used null read/write ops ... ?)
--lyndon
next prev parent reply other threads:[~2006-11-24 4:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 19:06 [9fans] v9fs mounting in linux Paul Lalonde
2006-11-20 19:15 ` erik quanstrom
2006-11-20 22:35 ` Paul Lalonde
2006-11-21 0:27 ` ron minnich
2006-11-21 1:16 ` Paul Lalonde
2006-11-21 2:36 ` ron minnich
2006-11-21 2:42 ` Paul Lalonde
2006-11-21 2:49 ` ron minnich
2006-11-21 3:00 ` erik quanstrom
2006-11-21 3:17 ` [9fans] read of eof Michael Baldwin
2006-11-21 6:38 ` Bruce Ellis
2006-11-21 1:23 ` [9fans] Re: echo -n arisawa
2006-11-21 2:32 ` ron minnich
2006-11-21 17:36 ` Andrew Lynch
2006-11-21 17:35 ` andrey mirtchovski
2006-11-21 18:13 ` Axel Belinfante
2006-11-21 18:23 ` andrey mirtchovski
2006-11-21 18:31 ` Axel Belinfante
2006-11-21 18:53 ` Skip Tavakkolian
2006-11-22 1:32 ` dmr
2006-11-24 4:17 ` Lyndon Nerenberg [this message]
2006-11-24 16:24 ` Bruce Ellis
2006-11-21 9:01 Fco. J. Ballesteros
2006-11-21 15:23 ` Dave Lukes
2006-11-21 15:37 ` ron minnich
2006-11-21 15:54 ` erik quanstrom
2006-11-21 16:35 ` Brantley Coile
2006-11-21 16:49 ` Bakul Shah
2006-11-24 4:06 ` Lyndon Nerenberg
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=20A49DB2-5E13-40C5-93B9-D15D487D649B@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@cse.psu.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).