The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Brian Walden <tuhs@cuzuco.com>
To: <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] A portrait of cut(1)
Date: Tue, 14 Jan 2020 23:54:15 -0500 (EST)	[thread overview]
Message-ID: <202001150454.00F4sF9H013965@cuzuco.com> (raw)

Random832 <random832 at fastmail.com> writes:
>markus schnalke <meillo at marmaro.de> writes:
>> [2015-11-09 08:58] Doug McIlroy <doug at cs.dartmouth.edu>
>>> things like "cut" and "paste", whose exact provenance
>>> I can't recall.
>>
>> Thanks for reminding me that I wanted to share my portrait of
>> cut(1) with you. (I sent some questions to this list, a few
>> months ago, remember?) Now, here it is:
>>
>>      http://marmaro.de/docs/freiesmagazin/cut/cut.en.pdf
>
>Did you happen to find out what GWRL stands for, in the the comments at
>the top of early versions of cut.c and paste.c?
>
>/* cut : cut and paste columns of a table (projection of a relation) (GWRL) */
>/* Release 1.5; handles single backspaces as produced by nroff    */
>/* paste: concatenate corresponding lines of each file in parallel. Release 1.4 (GWRL) */
>/*        (-s option: serial concatenation like old (127's) paste command */
>
>For that matter, what's the "old (127's) paste command" it refers to?

I know this thread is almost 5 years old, I came across it searching for
something else But as no one could answer these questions back then, I can.

GWRL stands for Gottfried W. R. Luderer, the author of cut(1) and paste(1),
probably around 1978.  Those came either from PWB or USG, as he worked with,
or for, Berkley Tague. Thus they made their way into AT&T commercial UNIX,
first into System III and the into System V, and that's why they are missing
from early BSD releases as they didn't get into Research UNIX until the
8th Edition.  Also "127" was the internal department number for the Computer
Science Research group at Bell Labs where UNIX originated

Dr. Luderer co-authored this paper in the orginal 1978 BSTJ on UNIX --
https://www.tuhs.org/Archive/Documentation/Papers/BSTJ/bstj57-6-2201.pdf

I knew Dr. Luderer and he was even kind enough to arrange for me stay with his
relatives for a few days in Braunschweig, West Germany (correct county name for
the time) on my first trip to Europe many decades ago. But haven't had contact nor
even thought of him forever until I saw his initials. I also briefly worked for Berk
when he was the department head for 45263 in Whippany Bell Labs before moving to
Murray Hill.

And doing a quick search for him, it looks like he wrote and autobiograhy, which I
am now going to have to purchase
http://www.lulu.com/shop/gottfried-luderer/go-west-young-german/paperback/product-23385772.html?ppn=1

-Brian

             reply	other threads:[~2020-01-15  4:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15  4:54 Brian Walden [this message]
2020-01-15  8:02 ` markus schnalke
  -- strict thread matches above, loose matches on Subject: below --
2015-11-11 12:41 Norman Wilson
2015-11-09  1:39 [TUHS] PWB contributions Doug McIlroy
2015-11-09  2:12 ` Clement T. Cole
2015-11-09 13:58   ` Doug McIlroy
2015-11-10 20:26     ` [TUHS] A portrait of cut(1) (was: PWB contributions) markus schnalke
2015-11-11  0:16       ` [TUHS] A portrait of cut(1) Random832
2015-11-11 12:23         ` markus schnalke

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=202001150454.00F4sF9H013965@cuzuco.com \
    --to=tuhs@cuzuco.com \
    --cc=tuhs@minnie.tuhs.org \
    /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).