The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Questions about the history of cut(1)
Date: Mon, 1 Jun 2015 10:14:53 -0400	[thread overview]
Message-ID: <CAC20D2N95V=iXNFhK2z4rgcikGaX9fA4XE7W5-hRTUH9Z2+vfQ@mail.gmail.com> (raw)
In-Reply-To: <556B88A4.3080605@mhorton.net>

+1

Similarly, I can not find any PWB 2.0 info, but I agree that if CB UNIX had
it, that is a strong indication that it was part of PWB 2.0.

On Sun, May 31, 2015 at 6:18 PM, Mary Ann Horton <mah at mhorton.net> wrote:

> CB UNIX paralleled USG/PWB versions, so that's a strong hint that PWB 2
> had cut/paste.  My recollection is also that it did, but I don't have any
> doc or source to confirm that.
>
>
> On 05/31/2015 11:06 AM, markus schnalke wrote:
>
>> Thanks a lot for all your responses. They helped and encouraged me.
>>
>> [2015-05-18 11:06] Clem Cole <clemc at ccc.com>
>>
>>> I thought it came from USG, as it was definitely in PWB 3.0 [which was
>>> "rebranded" as System III post break-up], I think it may have been in
>>> PWB 2.0.
>>>    Mashey might remember.   I'll check any doc I have at home tonight,
>>> but do
>>> not think I still have PWB 2.0 bits anywhere.  I think Warren has a TAR
>>> image
>>> from Henry of the PWB 1.0 which to check.
>>>
>>
>> This is what I found out so far:
>>
>> 1) cut was part of System III. The sources are online:
>> http://minnie.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/cmd/cut.c
>> In consequence, cut was part of PWB 3.0, as well, because that's
>> the same.
>>
>> 2) These sources of (presumely) PWB 1.0 show no signs of cut:
>> http://minnie.tuhs.org/Archive/PDP-11/Distributions/usdl/
>>
>> 3) I couldn't find any sources or useful documentation about PWB 2.0.
>>
>> 4) I've discovered that cut was present in CB Unix 2.1 (which I
>> haven't even known it existed. ;-) ). I found scanned man pages,
>> which date November 1979:
>>
>> ftp://sunsite.icm.edu.pl/pub/unix/UnixArchive/PDP-11/Distributions/other/CB_Unix/cbunix_man1_02.pdf
>> (cut is on PDF page 57)
>> Unfortunately, I wasn't able to find sources or, actually, much
>> useful information at all on CB Unix.
>>
>>
>> Possibly, you can help me a further step from this point on.
>>
>> I think, interesting would be sources or docs about PWB 2.0 and
>> CB Unix and the relation i.e. code transfer between PWB and CB Unix.
>>
>>
>> meillo
>> _______________________________________________
>> TUHS mailing list
>> TUHS at minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/tuhs
>>
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150601/906339bb/attachment.html>


  reply	other threads:[~2015-06-01 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 10:36 Doug McIlroy
2015-05-18 11:49 ` John Cowan
2015-05-18 14:04 ` markus schnalke
2015-05-18 15:01   ` Andy Kosela
2015-05-18 15:20     ` Clem Cole
2015-05-18 15:06 ` Clem Cole
2015-05-31 18:06   ` markus schnalke
2015-05-31 22:18     ` Mary Ann Horton
2015-06-01 14:14       ` Clem Cole [this message]
2015-06-02 17:31         ` markus schnalke
2015-05-18 15:13 ` random832
  -- strict thread matches above, loose matches on Subject: below --
2015-05-17 18:00 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='CAC20D2N95V=iXNFhK2z4rgcikGaX9fA4XE7W5-hRTUH9Z2+vfQ@mail.gmail.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).