The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: Split addressing (I/D) space (inspired by the death of the python... thread)
Date: Fri,  4 Aug 2023 17:40:50 -0400 (EDT)	[thread overview]
Message-ID: <20230804214050.BFD2A18C077@mercury.lcs.mit.edu> (raw)

    > From: Clem Cole

    > first two subsystems for the 11 that ran out of text space were indeed
    > vi and Pascal subsystems 

Those were at Berkeley. We've established that S-I&D were in V6 when it was
released in May, 1975 - so my question is 'what was Bell doing in 1975 that
needed more than 64KB?'

The kernel, yeah, it could definitely use S-I&D on a larger system
(especially when you remember that stock V6 didn't play any tricks with
overlays, and also dedicated one segment - the correct term, used in the 1972
-11/45 processor manual - to the user structure, and one to the I/O page,
limiting the non-S-I&D kernel to 48KB). But what user commands?


It happens that I have a complete dump of one of the MIT systems, so I had a
look to see what _we_ were running S-I&D on. Here's the list from /bin (for
some reason that machine doesn't have a /usr/bin):

  a68
  a86
  c86
  emacs
  lisp
  ndd
  send
  teco

The lisp wasn't a serious use; I think the only thing we ever used it for was
'doctor'. So, two editors, a couple of language tools, an email tool (not
sure why that one got it - maybe for creating large outgoing messages). (The
ndd is probably to allow the biggest possible buffers.)

Nothing in /etc, and in /lib, just lint1 and lint2 (lint, AFAICT, post-dates
V6). Not a lot.


So now I'm really curious what Bell was using S-I&D for. (If I weren't lazy,
I'd pull the V6 distro - which is only available as RK images, and individual
files, alas - and look in /bin and everywhere and see if I can find anything.
I suspect not, though.)

Anyone have any guesses/suggestions? Maybe some custom applications?

	Noel

             reply	other threads:[~2023-08-04 21:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 21:40 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-03 23:14 Steve Simon
2023-08-03 23:10 Noel Chiappa
2023-08-03 23:42 ` Warner Losh
2023-08-03 21:48 Noel Chiappa
2023-07-30 23:59 [TUHS] Re: Cool talk on Unix and Sendmail history, by Eric Allman Erik E. Fair
2023-08-01 10:58 ` Erik E. Fair
2023-08-02  0:37   ` Dave Horsfall
2023-08-02 14:52     ` Ron Natalie
2023-08-02 21:14       ` Grant Taylor via TUHS
2023-08-02 22:20         ` segaloco via TUHS
2023-08-02 23:49           ` Rich Salz
2023-08-03  0:51             ` [TUHS] Re: python Larry McVoy
2023-08-03  2:07               ` Clem Cole
2023-08-03 16:57                 ` [TUHS] Re: [TULSA] " Phil Budne
2023-08-03 17:00                   ` Rich Salz
2023-08-03 20:35                     ` [TUHS] Split addressing (I/D) space (inspired by the death of the python... thread) Will Senn
2023-08-03 21:05                       ` [TUHS] " Kenneth Goodwin
2023-08-03 21:10                         ` Ronald Natalie
2023-08-03 21:16                           ` Warner Losh
2023-08-03 21:24                             ` Ronald Natalie
2023-08-03 22:34                           ` Kenneth Goodwin
2023-08-03 21:05                       ` Ronald Natalie
2023-08-03 21:44                       ` Clem Cole
2023-08-03 22:08                         ` Will Senn
2023-08-03 22:54                           ` Clem Cole
2023-08-03 23:08                             ` Dave Horsfall
2023-08-03 23:15                             ` Clem Cole
2023-08-04  0:38                             ` John Cowan

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=20230804214050.BFD2A18C077@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@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).