Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!uokmax!d.cs.okstate.edu!unx2.ucc.okstate.edu!minich From: minich@unx2.ucc.okstate.edu (Robert Minich) Newsgroups: comp.arch Subject: Re: Sun bogosities, including MMU thrashing Message-ID: <1991Jan27.003821.24814@unx2.ucc.okstate.edu> Date: 27 Jan 91 00:38:21 GMT References: Organization: Oklahoma State University Computer Center Lines: 15 suitti> [ ... describing a log based editor instead of a copy based one suitti> like, in different ways, vi or emacs ... ] Grandi> Precisely what I think is the best organization! Especially for Grandi> virtual memory. Another nice organization was used by the TSS/370 Grandi> editor, which used VSAM (then called another way) for (memory Grandi> mapped) files. With a log based editor, what happens if someone changes the file while you're editing it? Are the files locked while in use? -- |_ /| | Robert Minich | |\'o.O' | Oklahoma State University| "I'm not discouraging others from using |=(___)= | minich@d.cs.okstate.edu | their power of the pen, but mine will | U | - "Ackphtth" | continue to do the crossword." M. Ho