Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!math.ohio-state.edu!uwm.edu!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: VM complaints in syslog Date: 20 Jul 1993 18:39:54 GMT Organization: Montana State University Lines: 22 Distribution: world Message-ID: <22he5q$qa1@pdq.coe.montana.edu> References: <21rn1r$15h@cleese.apana.org.au> <221gj7$tt@pdq.coe.montana.edu> <224hsl$79n@cville-srv.wam.umd.edu> NNTP-Posting-Host: bsd.coe.montana.edu In article <224hsl$79n@cville-srv.wam.umd.edu> ima@wam.umd.edu (Linda Tamara Bresler) writes: >i have gotten the unclean persistent objects as well ( is this a disease? ) >without using emacs. i do use ncsa telnet for the mac to connect to charon >(the 386bsd host) everyday. it seems the problem is not unique to emacs. This may not be the problem, but I've replied to a couple folks in private email about this. It appears that in 386BSD there is a bug that will allow read-only (executables) to be written to, which *can* cause executables to be corrupted. This can cause the VM errors mentioned above. A fix has been proposed, and is being tested. It *will* be in interim/FreeBSD when it is released. Nate -- nate@bsd.coe.montana.edu | In the middle of it ........ again. nate@cs.montana.edu | Running/supporting one of many freely available work #: (406) 994-4836 | Operating Systems for [34]86 machines. home #: (406) 586-0579 | (based on Net/2, name changes all the time :-)