From mboxrd@z Thu Jan  1 00:00:00 1970
From: schily@schily.net (Joerg Schilling)
Date: Tue, 10 Jan 2017 17:20:49 +0100
Subject: [TUHS] the guy who brought up SVr4 on Sun machines
In-Reply-To: <79091EE2-D7F8-4BE2-9422-47C365780367@berwynlodge.com>
References: <79091EE2-D7F8-4BE2-9422-47C365780367@berwynlodge.com>
Message-ID: <587509e1.gGhkbfCz1YmUYkqT%schily@schily.net>

Berny Goodheart <berny at berwynlodge.com> wrote:

> Here???s the breakdown of SVR4 kernel lineage as I recall it. I am pretty sure this is correct. But I am sure many of you will put me right if I am wrong ;)
>
> From BSD:
> TCP/IP			<=== NO, Svr4 uses a STREAMS based TCP/IP stack
> C Shell
> Sockets			<=== NO, BSD has sockets in kernel, SVr4 in
					userland
> Process groups and job Control
> Some signals
> FFS in UFS guise		<=== NO, rather taken from SunOS-4
> Multi groups/file ownership
> Some system calls
> COFF				<=== NO, COFF was from SysV and deprecated in Svr4
>
> From SunOS:
> vnodes
> VFS
> VM
> mmap
> LWP and kernel threads
> /proc				<=== NO, /proc did not exist in SunOS-4
> Dynamic linking extensions
> NFS
> RPC
> XDR
>
> From SVR3:
> .so libs			<=== What should this be?
					I am not even sure whether SVr4 included
					backwards compatibility for the SVr3
					"installed" shared libraries.

> revamped signals and trampoline code +++++sigset() was not in SVr2, I believe 
						it was not available in svr3 as 
						well and rather invented for 
						Svr4
> VFSSW				<=== NO, this is from SunOS-4
> RFS
> STREAMS and TLI		<=== SVr3 did not have STREAMS
> IPC (Shared memory, Message queues, semaphores) <=== Already in SunOS-4

Jörg

-- 
 EMail:joerg at schily.net                  (home) Jörg Schilling D-13353 Berlin
       joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/