Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!cs.utexas.edu!tamsun.tamu.edu!bloom-beacon.mit.edu!ai-lab!life.ai.mit.edu!mycroft
From: mycroft@trinity.gnu.ai.mit.edu (Charles Hannum)
Newsgroups: comp.os.386bsd.questions
Subject: Re: vm error: vm_object_dealloc: persistent object [????] not clean.?
Date: 15 Aug 1993 18:55:25 GMT
Organization: MIT Artificial Intelligence Lab
Lines: 13
Message-ID: <MYCROFT.93Aug15145525@trinity.gnu.ai.mit.edu>
References: <1993Aug13.141037.27182@husc14.harvard.edu> <24h660$hnv@pdq.coe.montana.edu>
<g89r4222.745426655@kudu> <24lr13$4fn@pdq.coe.montana.edu>
NNTP-Posting-Host: trinity.gnu.ai.mit.edu
In-reply-to: nate@bsd.coe.montana.edu's message of 15 Aug 1993 17:16:19 GMT
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.
This is a very twisted way of putting it. FreeBSD is very different
from 386BSD, though not as much so as NetBSD.
Like NetBSD, FreeBSD is not completely `binary compatible' with
386BSD. Programs which use the DB library (namely, anything which
does getpwuid() or getpwnam()) need to be, at the least, relinked.