Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!decwrl!sun!guy
From: guy@sun.uucp (Guy Harris)
Newsgroups: net.arch,net.micro.16k,net.micro.68k
Subject: Re: 24 bit vs. 32 bit address space
Message-ID: <2146@sun.uucp>
Date: Tue, 30-Apr-85 01:23:32 EDT
Article-I.D.: sun.2146
Posted: Tue Apr 30 01:23:32 1985
Date-Received: Thu, 2-May-85 07:06:56 EDT
References: <983@watdcsu.UUCP> <2385@nsc.UUCP> <730@amdcad.UUCP> <523@inset.UUCP> <5351@utzoo.UUCP> <100@daisy.UUCP>
Organization: Sun Microsystems, Inc.
Lines: 14
Xref: linus net.arch:941 net.micro.16k:298 net.micro.68k:674

> Mr. Spencer asks "Incidentally, how do you implement a pipe or a terminal as
> a segment?"  Well, I'm just a dumb application programmer but our O.S.,
> running on the iAPX286, implements real, honest-to-goodness Unix pipes
> and devices.

But does it implement them *as segments*?  I.e., do you "write" to a pipe or
terminal by storing data into a segment in the exact same way you'd write
data in a file by storing it in a segment?  Furthermore, do you "read" from
a pipe or terminal by fetching data from a segment?  Multics did file I/O by
fetching from or storing into a segment, but I/O to devices was done by
calling various device driver entry points.

	Guy Harris