Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!uwm.edu!cs.utexas.edu!uunet!majipoor.cygnus.com!kithrup.com!sef From: sef@kithrup.com (Sean Eric Fagan) Subject: Re: "persistent object not clean" Organization: Kithrup Enterprises, Ltd. References: <1993Jul22.164535.20962@qualcomm.com> <22mvo9$7op@pdq.coe.montana.edu> Message-ID: <CALC9s.nH@kithrup.com> Date: Fri, 23 Jul 1993 00:05:36 GMT Lines: 10 In article <22mvo9$7op@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes: >I *think* (some VM guru interject here) that is might be the Copy On >Write problem recently fixed in FreeBSD (aka interim aka 0.1.5). Yes, this is it: I run 386bsd 0.1 + patchkit, so does a coworker. I grabbed the fix Nate is talking about, hand-merged the new copyout() and copyin() into my locore.s, and that seemed to fix the problem. As a further test, I gave the new locore.s to my coworker, who had noticed the problem with emacs-19, and, sure enough, the new kernel did not have the problem.