decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
noooo! | 179 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
noooo!
Authored by: Wol on Thursday, September 20 2012 @ 06:47 PM EDT
I expect you're thinking of Intel segmented memory.

If memory serves me right, each segment/offset pair on Primes guaranteed a
unique memory location - you couldn't have multiple pointers to the same
location.

The OS was below o4000, each user had their own user space at about o6000, and I
think o7000 and above was reserved for something else.

I never really understood all this stuff, but one of the things that stands out
from what I remember is that snapping a dynamic link was very fast, and coupled
with that a call into the operating system was EQUALLY as fast!

One of the big problems with linux and speed is that a user/kernel-space context
switch is relatively very expensive. With Primos it cost almost nothing.

And if (as I suspect it did) you could compile your kernel such that it insisted
on its writeable memory being in the o6000 address range, then security is
moderately easy to achieve - seeing as each user has their own separate 6000
range this code can't stomp over other users OR the kernel.

Okay, I'm sure other people here will tell me there were horrendous flaws in
Primos that let you break in (I gather security was actually pretty poor, thanks
to various bugs and/or design features), but the basic architecture design was
pretty good.

Cheers,
Wol

[ Reply to This | Parent | # ]

  • noooo! - Authored by: greed on Tuesday, September 25 2012 @ 06:25 PM EDT
Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )