🚀 go-pugleaf

In article <KHB.90Feb8175209@chiba.Eng.Sun.COM> Keith Bierman writes:
>In article <5672@blake.acs.washington.edu> Mark Crispin writes:
>   Now, I may accept the claim that file/memory mapping will be less
>   useful on Unix, because it won't be standard on every Unix system (and
>It is part of the published feature list for V.4. So it will at least
>be on all UI derived platforms, and one strongly suspects that this is
>a feature that OSF will have no choice but to offer.

We put it into AIX some years ago.  I'm not sure the interface is the same;
in AIX it's a funny kind of shmat() but the semantics are quite obvious.  It
was in response to requests from data base types who found it to be useful for
implementing multiple simultaneous data base users, since it gets rid of a
whole layer of buffering and hence synchronization problems.  AIX also lets
you map a file copy-on-write and then commit the changes back atomically.
-- 
John R. Levine, Segue Software, POB 349, Cambridge MA 02238, +1 617 864 9650
johnl@esegue.segue.boston.ma.us, {ima|lotus|spdcc}!esegue!johnl
"Now, we are all jelly doughnuts."