Xref: utzoo comp.unix.microport:3047 comp.unix.questions:12486 comp.unix.wizards:15261
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!xanth!nic.MR.NET!shamash!com50!bungia!cimcor!mike
From: mike@cimcorMN.ORG (Michael Grenier)
Newsgroups: comp.unix.microport,comp.unix.questions,comp.unix.wizards
Subject: Re: C bug causes double panic
Message-ID: <784@cimcorMN.ORG>
Date: 28 Mar 89 13:45:41 GMT
References: <18250@gatech.edu>
Organization: Grenier & friends, Forest Lake, MN
Lines: 21

From article <18250@gatech.edu>, by ken@gatech.edu (Ken Seefried iii):
> In article <9989@ihlpb.ATT.COM> gregg@ihlpb.ATT.COM (Wonderly) writes:
>>Multics comes to mind...  64K segments, 4 access levels, transfer
>>gates...

> I thought about that, but it is my understanding (which surely could
> be wrong) that multics is based on dynamicly allocated, variable size
> segments of potentially large size.  Certainly, the 80286 doesn't fit
> this criteria with its fixed size, 64K segments.  Also, doesn't


Huh,
    The 80286 doesn't have fixed 64K segments. You set the length of
the segment in the segment descriptor for that segment. From a user
level on this Microport box, you can allocate a segment of any size
 <= 64K using the brk() system call. Of course, its the 64K max segment
size that is the real pain.


    -Mike Grenier
     mike@cimcor.mn.org