The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: MichaelDavidson@pacbell.net (Michael Davidson)
Subject: [TUHS] New V7 port available
Date: Thu, 04 Oct 2007 22:10:38 -0700	[thread overview]
Message-ID: <4705C74E.7040509@pacbell.net> (raw)
In-Reply-To: <200710050428.l954SSiq007732@cuzuco.com>

tuhs at cuzuco.com wrote:
> 8086 lacks the required protected mode. don't remember how xenix over
> came this problem when it was first released. no one even has to think
> about this problem today
>   
Xenix for the 8086 only supported "small model" user programs of up to 
64k text + 64k data
and used the segment registers to point to the appropriate text and data 
segments in physical
memory. User programs were not supposed to ever look at or change the 
contents of their
segment registers - if they did then chaos was likely to ensue.

And, of course, there was no protection so a rogue process could access 
all of physical
memory including the memory used by the kernel.

It's quite amazing that it worked as well as it did.

md



  parent reply	other threads:[~2007-10-05  5:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05  4:28 tuhs
2007-10-05  4:44 ` John Cowan
2007-10-05  5:11   ` M. Warner Losh
2007-10-05  6:11     ` Andrew Warkentin
2007-10-05  5:10 ` Michael Davidson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-04 17:51 Robert Nordier
2007-10-04 18:10 ` Jochen Kunz
2007-10-04 23:01   ` Pat Villani
2007-10-05 19:23     ` Robert Nordier
2007-10-04 18:44 ` Michael Kerpan
2007-10-05 19:05   ` Robert Nordier
2007-10-05 21:10     ` Michael Kerpan

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=4705C74E.7040509@pacbell.net \
    --to=michaeldavidson@pacbell.net \
    /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).