Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!sri-spam!ames!oliveb!felix!ccicpg!turnkey!jack
From: jack@turnkey.CTS.COM (jack)
Newsgroups: comp.unix.xenix
Subject: Re: 386 Unix/Memory Models
Message-ID: <140@turnkey.UUCP>
Date: Mon, 5-Oct-87 18:51:38 EDT
Article-I.D.: turnkey.140
Posted: Mon Oct  5 18:51:38 1987
Date-Received: Sat, 10-Oct-87 11:05:48 EDT
References: <143@conexch.UUCP>
Organization: Turnkey Computer Consultants, Costa Mesa, CA
Lines: 19
Summary: No more segment headaches

In article <143@conexch.UUCP>, enped@conexch.UUCP (Eric Pederson) writes:
> I guess the question on my mind now is this:  since the 386 has such a large
> address space, and since it *can* support segments over 64K, will we benefit
> with Unix 386?  What I'm really asking is this: will we get to do away with
> the memory model foolishness that we have had to deal with in 286 *NIXes
> for so long?

Yes, Eric, in SCO Xenix 386 you still have segments (presumably for downward 
compatability) but they are now 4 Gigabyes. Also, there is only one memory
model, large (all segment registers, and hence pointers are now 32 bits wide).
So there will be no more need to fool with makefiles to determine
which memory library to call for. I assume this will also be the case with
packages such as 386/ix from Interactive or Microport's release (whenever it
becomes available).

-- 
Jack F. Vogel
Turnkey Computer Consultants, Costa Mesa, CA
UUCP: ...!uunet!ccicpg!turnkey!jack 
Internet: jack@turnkey.CTS.COM