Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!agate!headwall.Stanford.EDU!kithrup.com!sef From: sef@kithrup.com (Sean Eric Fagan) Subject: Re: vm error: vm_object_dealloc: persistent object [????] not clean.? Organization: Kithrup Enterprises, Ltd. References: <1993Aug13.141037.27182@husc14.harvard.edu> <24h660$hnv@pdq.coe.montana.edu> <g89r4222.745426655@kudu> <24lr13$4fn@pdq.coe.montana.edu> Message-ID: <CBtD9n.FLH@kithrup.com> Date: Sun, 15 Aug 1993 18:41:32 GMT Lines: 14 In article <24lr13$4fn@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes: >>Is there a fix available for 386bsd0.1+pk0.2.4? >Yes, it's called FreeBSD. There will be an upgrade path from the patchkit >to FreeBSD. (The next patchkit has a name. ;-) I've got a version of locore that fixes the problem (hand-patched from the netbsd and freebsd stuff); if freebsd isn't out by next weekend, I'll post my locore. (I've made it available to a few people with the understanding that it is completely unsupported, if it crashes your machine you got what you asked for :).) The main people I've run across who needed this are people who are using emacs-19.