🚀 go-pugleaf

In article <1992Dec15.155425.25217@convex.com> finger@convex.com (Jay Finger) writes:

| In article <1992Dec15.042513.23969@gandalf.ca> dperks@gandalf.ca (Dave Perks) writes:
| >Is it also possible that since the Intel 486 supports supervisor-mode write
| >protection, it is is used to allow something like copy-on-write?  If NeXT Step
| >was designed to use this then the kernel would require fairly major changes.
| 
| Yep, NeXTstep (and maybe Mach in general, somebody correct me if I'm wrong)
| uses copy-on-write all over the place.  The programmers' references
| mention copy-on-write in many places (at least the 2.x documentation does,
| but that's for a 680[34]0).

While I can't say anything about NeXT's implementation, I am posting
this article from a 386 (not a 486) running OSF/1, which is based on
Mach, and uses copy-on-write all over the place.
--
Michael Meissner	email: meissner@osf.org		phone: 617-621-8861
Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142

You are in a twisty little passage of standards, all conflicting.