The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Ruizendaal <pnr@planet.nl>
To: Thomas Paulsen <thomas.paulsen@firemail.de>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] 8th Edition timeline
Date: Wed, 8 Apr 2020 22:13:29 +0200	[thread overview]
Message-ID: <0A39F8F1-C1C3-408F-9715-1D8B9C19A00C@planet.nl> (raw)
In-Reply-To: <b86ac02f64adfbc237a01135f76a305d@firemail.de>

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

On Apr 8, 2020, at 8:58 PM, Thomas Paulsen <thomas.paulsen@firemail.de> wrote:
> 
>> As was suggested on the list, I’ve reached out to Peter Weinberger to better
>> understand the time line of the File System Switch and the 8th edition network
> f>ile system. 
> 
> 'Introduced with System V Release 3.0, the File System Switch (FSS) architecture introduced a framework under which multiple different filesystem types could coexist in parallel.'
> https://www.oreilly.com/library/view/unix-filesystems-evolution/9780471456759/chap07-sec003.html <https://www.oreilly.com/library/view/unix-filesystems-evolution/9780471456759/chap07-sec003.html>

Thanks for that link!

The SysV R3 source floats around on the web. Its FSS is very different from what is in 8th edition.

In 8th edition the switch has 11 entries (i.e. a file system is an object with 11 virtual methods).
https://github.com/Alhadis/Research-Unix-v8/blob/master/v8/usr/sys/h/conf.h
I have never really studied R3 but at quick inspection the FSS there has 27 (!) entries and seems to be more a sys call switch.

In 10th edition it is still 11 entries, although some refactoring has taken place. Also later work from Research keeps it concise: the 9P protocol from Plan 9 has 14 messages.




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

  reply	other threads:[~2020-04-08 20:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 12:27 Paul Ruizendaal
2020-03-29 14:04 ` arnold
2020-03-29 18:12   ` Paul Ruizendaal
2020-03-29 21:48     ` Rob Pike
2020-03-30  7:43       ` Paul Ruizendaal
2020-03-30  9:06         ` Rob Pike
2020-04-04 12:56           ` emanuel stiebler
2020-04-04 19:57             ` Noel Hunt
2020-04-04 21:32               ` Rob Pike
2020-04-04 22:39                 ` Noel Hunt
2020-04-05  1:38                 ` aksr
2020-04-05 13:17                 ` emanuel stiebler
2020-03-30 13:26         ` Clem Cole
2020-03-30 13:38           ` reed
2020-03-30 14:41             ` Clem Cole
2020-03-30 15:06               ` [TUHS] Sytek (was Re: 8th Edition timeline) Jon Forrest
2020-03-30 16:02           ` [TUHS] 8th Edition timeline Paul Ruizendaal
2020-03-30 19:31             ` Clem Cole
2020-03-31  2:44               ` Paul Ruizendaal
2020-04-08 18:50     ` Paul Ruizendaal
2020-04-08 18:58       ` Thomas Paulsen
2020-04-08 20:13         ` Paul Ruizendaal [this message]
2020-03-30  6:25   ` Paul Ruizendaal

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=0A39F8F1-C1C3-408F-9715-1D8B9C19A00C@planet.nl \
    --to=pnr@planet.nl \
    --cc=thomas.paulsen@firemail.de \
    --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).