The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Mary Ann Horton <mah@mhorton.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] fmt(1): history, POSIX, -t, -c
Date: Fri, 29 May 2020 10:14:10 -0700	[thread overview]
Message-ID: <0222efc8-e02f-7de8-dc94-9cba389c98a4@mhorton.net> (raw)
In-Reply-To: <CAC20D2NAtHPNLLJgGVaqgPnC8A_7sCXbs83DA7WAcKhWg=eb=g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]


On 5/29/20 6:39 AM, Clem Cole wrote:
>
>
> On Fri, May 29, 2020 at 1:11 AM Michael Stiller via TUHS 
> <tuhs@minnie.tuhs.org <mailto:tuhs@minnie.tuhs.org>> wrote:
>
>     It is also included in 2.9BSD, or was it backported:
>
> Just recompiled. I don't think this was one he had to make any changes 
> too. As Mary Ann and I said, Kurt wrote as part of the UCB Mail 
> package [which includes delivermail(8) - which was the moral parent to 
> sendmail(8)].
fmt was literally part of Mail - it compiled in the same source 
directory, and was considered user agent (UA) code. delivermail/sendmail 
was separate, also from Berkeley, but written primarily by Eric Allman, 
and was the mail transport agent (MTA). It's in 2.8BSD as well.
> The whole key is that Keith did not have a Vax at the Math department 
> (they had an 11/70 with max memory) and wanted all of the cool 
> programs that were being created on the Vax.   Remember, VM is 
> automatic overlays.   So first with the kernel, and then later with 
> user code, larger and larger programs were enabled and many of the 
> programs for the Vax migrated to the PDP-11, as people ran out of 
> address space (IIRC: one the first user programs that needed to use 
> overlays was ex/vi.  Again, as I recall the original wnj version by 
> then was such a mess, getting a new/cleaner code base was a large 
> impetus for Keith to start writing nvi).

ex/vi didn't use overlays (unless you count split I/D). It fit in 64 
bits by using ifdefs.  Less useful code, like supporting upper-case-only 
terminals, would be ifdeffed out on the pdp11.

     Mary Ann




[-- Attachment #2: Type: text/html, Size: 3359 bytes --]

  parent reply	other threads:[~2020-05-29 17:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 12:34 markus schnalke
2020-05-28 13:08 ` Rob Pike
2020-05-28 13:30 ` Clem Cole
2020-05-28 13:47   ` Clem Cole
2020-05-28 16:08     ` Mary Ann Horton
2020-05-28 18:00       ` Clem Cole
2020-05-28 18:35         ` Richard Salz
2020-05-28 18:51           ` Clem Cole
2020-05-29  0:18   ` Greg 'groggy' Lehey
2020-05-29  5:10     ` Michael Stiller via TUHS
2020-05-29  5:19       ` Greg 'groggy' Lehey
2020-05-29 13:39       ` Clem Cole
2020-05-29 15:43         ` Warner Losh
2020-05-29 16:12           ` Clem Cole
2020-05-29 17:14         ` Mary Ann Horton [this message]
2020-05-28 13:46 ` Clem Cole
2020-05-31 13:01   ` [TUHS] mh/hm, mmh (was: fmt(1): history, POSIX, -t, -c) markus schnalke
2020-05-31 14:53     ` Clem Cole
2020-05-31 16:25       ` Richard Salz
2020-05-31 16:50         ` Larry McVoy
2020-05-31 17:09       ` Ralph Corderoy
2020-05-31 17:25         ` Jon Steinhart
2020-05-31 17:28       ` [TUHS] mh/hm, mmh Mary Ann Horton
2020-05-31 18:56         ` Eric Allman
2020-05-31 19:49           ` Clem Cole
2020-05-31 21:31           ` Mary Ann Horton
2020-06-01  6:32             ` Caipenghui
2020-06-01  7:14             ` markus schnalke
2020-05-31 12:35 ` [TUHS] fmt(1): history, POSIX, -t, -c markus schnalke
2020-05-29  1:25 Doug McIlroy

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=0222efc8-e02f-7de8-dc94-9cba389c98a4@mhorton.net \
    --to=mah@mhorton.net \
    --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).