J R wrote:
We tend to refer to the parts we deal intimately with by name,
e.g. TSO, ISPF, HLASM, VTAM, TCP/IP, JES2, SDSF, etc., etc.
Unless we are looking at some component in particular, we tend
to refer to everything else non-specifically as "the system".
previous posts
http://www.garlic.com/~lynn/2006p.html#10 What part of z/OS is the OS?
http://www.garlic.com/~lynn/2006p.html#11 What part of z/OS is the OS?
in the past, kernels tended to refer to privilege/supervisor execution
and protected storage. lots of kernels have implemented protected
storage with virtual address spaces ... i.e. cp67 on 360/67. mvt used
360 storage protection.
as technology progressed there was a direction (like for fault
isolation) to provide greater granularity for both privileges and
storage protection/isolation.
so from a structuring standpoint, system services got a lot less
distinct with much greater levels of privileges and storage isolation.
a couple months ago there was talk by one of the vendors about moving
SSL processing into the kernel. the issue was that they were going to be
supporting SSL crypto hardware accelerator devices. In order to provide
support for potentially multiple different applications sharing a common
device ... SSL processing (used of a shared external device) became a
resource and protection management issue (typical requirement for system
services).
Discussion of some of the repercussions in the SSL security model that
were the result of the SSL crypto processing overhead ... as well as
some discussion as to how many of the requirements for SSL might be
addressed in other ways:
http://www.garlic.com/~lynn/2006p.html#7 SSL, Apache 2 and RSA key sizes
http://www.garlic.com/~lynn/2006p.html#8 SSL, Apache 2 and RSA key sizes
in the referenced discussion (about moving SSL support into the kernel)
there was also mention of repeated efforts trying to get tcp/ip protocol
stack out of the kernel in the secure, capability coyotos secure
operating system
http://www.coyotos.org/
coyotos heritage is eros
http://www.eros-os.org/
http://www.capros.org/
the eros/capros heritage is keyKOS
http://www.cis.upenn.edu/~KeyKOS/
http://www.cis.upenn.edu/~KeyKOS/#keylogic
keykos is the renamed gnosis by the key logic spin-off of tymshare after
MD bought tymshare. gnosis was a secure 370-based operating system
developed by tymshare. tymshare happened to have been one of the early
cp67/vm370 commercial time-sharing offerings in the late 60s and 70s
http://www.garlic.com/~lynn/subtopic.html#timeshare
disclaimer, i was brought in to do gnosis audit and evaluation as part
of the gnosis spin-off for key logic. misc. past posts mentioning
gnosis/keykos
http://www.garlic.com/~lynn/2000f.html#69 TSS ancient history, was X86
ultimate CISC? designs)
http://www.garlic.com/~lynn/2000g.html#22 No more innovation? Get serious
http://www.garlic.com/~lynn/2001b.html#73 7090 vs. 7094 etc.
http://www.garlic.com/~lynn/2001g.html#33 Did AT&T offer Unix to Digital
Equipment in the 70s?
http://www.garlic.com/~lynn/2001g.html#35 Did AT&T offer Unix to Digital
Equipment in the 70s?
http://www.garlic.com/~lynn/2001n.html#10 TSS/360
http://www.garlic.com/~lynn/2002f.html#59 Blade architectures
http://www.garlic.com/~lynn/2002g.html#0 Blade architectures
http://www.garlic.com/~lynn/2002g.html#4 markup vs wysiwyg (was: Re:
learning how to use a computer)
http://www.garlic.com/~lynn/2002h.html#43 IBM doing anything for 50th Anniv?
http://www.garlic.com/~lynn/2002i.html#63 Hercules and System/390 - do
we need it?
http://www.garlic.com/~lynn/2002j.html#75 30th b'day
http://www.garlic.com/~lynn/2003g.html#18 Multiple layers of virtual
address translation
http://www.garlic.com/~lynn/2003h.html#41 Segments, capabilities, buffer
overrun attacks
http://www.garlic.com/~lynn/2003i.html#15 two pi, four phase, 370 clone
http://www.garlic.com/~lynn/2003k.html#50 Slashdot: O'Reilly On The
Importance Of The Mainframe Heritage
http://www.garlic.com/~lynn/2003l.html#19 Secure OS Thoughts
http://www.garlic.com/~lynn/2003l.html#22 Secure OS Thoughts
http://www.garlic.com/~lynn/2003l.html#26 Secure OS Thoughts
http://www.garlic.com/~lynn/2003m.html#24 Intel iAPX 432
http://www.garlic.com/~lynn/2003m.html#54 Thoughts on Utility Computing?
http://www.garlic.com/~lynn/2004c.html#4 OS Partitioning and security
http://www.garlic.com/~lynn/2004e.html#27 NSF interest in Multics security
http://www.garlic.com/~lynn/2004m.html#29 Shipwrecks
http://www.garlic.com/~lynn/2004m.html#49 EAL5
http://www.garlic.com/~lynn/2004n.html#41 Multi-processor timing issue
http://www.garlic.com/~lynn/2004o.html#33 Integer types for 128-bit
addressing
http://www.garlic.com/~lynn/2004p.html#23 Systems software versus
applications software definitions
http://www.garlic.com/~lynn/2005.html#7 How do you say "gnus"?
http://www.garlic.com/~lynn/2005b.html#6 [Lit.] Buffer overruns
http://www.garlic.com/~lynn/2005b.html#7 [Lit.] Buffer overruns
http://www.garlic.com/~lynn/2005b.html#12 [Lit.] Buffer overruns
http://www.garlic.com/~lynn/2005c.html#67 intel's Vanderpool and
virtualization in general
http://www.garlic.com/~lynn/2005d.html#43 Secure design
http://www.garlic.com/~lynn/2005d.html#50 Secure design
http://www.garlic.com/~lynn/2005h.html#13 Today's mainframe--anything to
new?
http://www.garlic.com/~lynn/2005k.html#30 Public disclosure of
discovered vulnerabilities
http://www.garlic.com/~lynn/2005s.html#12 Flat Query
http://www.garlic.com/~lynn/2006k.html#37 PDP-1
http://www.garlic.com/~lynn/2006m.html#34 PDP-1
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
