Path: csiph.com!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: ted@loft.tnolan.com (Ted Nolan ) Newsgroups: comp.os.linux.misc,alt.folklore.computers Subject: Re: Hmmm ... Downloaded Xenix - But It's *41* Floppies Worth Date: 26 Aug 2025 21:12:05 GMT Organization: loft Lines: 35 Message-ID: References: <108kqnu$615d$1@dont-email.me> <108l56v$77t$2@gal.iecc.com> X-Trace: individual.net XCaJcnaob8sg8ydjLhbgVwvIeQ7JbfKxeVPjC1ONW65HJOV+qi X-Orig-Path: not-for-mail Cancel-Lock: sha1:AN5TSESE024Rr777HKxTp3uHB9s= sha256:S8zJsk5Fx7noMspak0pnv4mLsjJL+QbTUg9aHgJa1bc= X-Newsreader: trn 4.0-test76 (Apr 2, 2001) Xref: csiph.com comp.os.linux.misc:72358 alt.folklore.computers:231630 In article <108l56v$77t$2@gal.iecc.com>, John Levine wrote: >According to Ted Nolan : >>>That also depends on one's definition of "proper MMU". The 286 had a >>>segmented MMU, but lacked a paged MMU. Paging was not added until the >>>386. And there are some that define "proper MMU" as "paged MMU". >> >>I don't know the MMU details for the 286, but my undestanding (formed >>at the time) is that it was "proper" in that it could actually protect >>running programs from each other. > >It could, but if your programs used more than one segment for code >or data, the switching was extremely slow and painful. Since the >segments were of variable size, that meant operating systems had >to do free space compaction that paging systems don't need. > >> PC-IX and I presume Xenix worked >>on the 8088/8086 by having the C compiler emit code which stayed >>in a segment -- so programs wouldn't interfere with each other > >There was 286 Xenix that used multiple segments in protected mode. >I never used it. > >>What the 286 couldn't do was virtual memory, which the 386 could. > >Sure it could. The system could mark segments as nonresident and >take a fault and swap them in as needed. I wouldn't call that >very good virtual memory, but it's definitely virtual memory. > Thanks! It ain't the things you don't know, but the things you know that ain't so... -- columbiaclosings.com What's not in Columbia anymore..