The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Sebastien F4GRX <f4grx@f4grx.net>
To: tuhs@tuhs.org
Subject: [TUHS] Re: (Amdahl UNIX) "Notes on Au Performance - or How to get the Pb out of Au"
Date: Wed, 19 Jul 2023 16:23:27 +0200	[thread overview]
Message-ID: <fc487c05-5f83-5c3b-2739-bb6173b014a9@f4grx.net> (raw)
In-Reply-To: <5baa2142-c350-679b-0660-8cc3f0e2104c@f4grx.net>

Hi again,

this remark actually applies to the other document about unix370 
feasability, oops!

However, That one is also interesting. I read in it at 6.1.4 "Login 
procedure optimization" about "combining (..) (init, getty and login) 
into one [program]". We can see this as the premices for the modern 
systemd :-)

Sebastien

Le 19/07/2023 à 15:50, Sebastien F4GRX a écrit :
> Hi,
>
> Thank you, this is a very interesting read. I will share this with 
> friends as soon as this is publicly available in the TUHS archives.
>
> We see premices of the Linux Copy-On-Write forking method!
>
> I also note that they decided to avoid a global kernel lock.
>
> Sebastien
>
> Le 19/07/2023 à 03:08, Tom Lyon a écrit :
>> This is perhaps the first significant document I wrote at Amdahl. 
>> Although undated, I believe this was written in August 1979, after I 
>> had attended a 2 week class at IBM Chicago about VM//370(CP) 
>> internals and performance.
>>
>> The paper makes reference to V7 UNIX being "on order", so this is 
>> when the V6 UNIX system was in use.  IIRC, V7 UNIX was released in 
>> Nov. of 1979.
>>
>> https://drive.google.com/file/d/1cB2eqTwmicj1AQOiULDZjED5Rq-_V4N4/view?usp=sharing 
>>
>>
>> Huge thanks to my friend Karl D. for hanging on to this for 44 years.

      reply	other threads:[~2023-07-19 14:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19  1:08 [TUHS] " Tom Lyon
2023-07-19 13:50 ` [TUHS] " Sebastien F4GRX
2023-07-19 14:23   ` Sebastien F4GRX [this message]

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=fc487c05-5f83-5c3b-2739-bb6173b014a9@f4grx.net \
    --to=f4grx@f4grx.net \
    --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).