Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!uunet!spool.mu.edu!uwm.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 386BSD - what a pain to install!
Message-ID: <1992Sep30.035327.4082@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
References: <1992Sep27.020909.2692@cs.unca.edu> <1992Sep27.091749.2076@fcom.cc.utah.edu> <id.X7NT.904@ferranti.com>
Date: Wed, 30 Sep 92 03:53:27 GMT
Lines: 31
In article <id.X7NT.904@ferranti.com> peter@ferranti.com (peter da silva) writes:
>> This is generally accomplished (by Xenix, as an
>> example) by only running code in medium model, where you have unlimited text
>> (read only) pages per program, but only 64K (1 segment) of data (read/write)
>> pages.
>
>This is not true.
>
>We've been running Xenix-286 for years with multiple data and multiple code
>segments. We're talking applications with megabytes of both.
Sorry. Peter is right for SCO Xenix, of course... but then again, that
won't compile for all 286 Xenix's... the resultant code runs only on SCO.
>Of course, I wouldn't recommend segmented memory to anyone for *fun*!
I know a couple people I probably be willing to do this to... ;-).
Terry Lambert
terry@icarus.weber.edu
terry_lambert@novell.com
terry_lambert@ns.novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------