From owner-freebsd-bugs Tue Apr 18 11:30: 4 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1402537B52E for ; Tue, 18 Apr 2000 11:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA90983; Tue, 18 Apr 2000 11:30:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 18 Apr 2000 11:30:01 -0700 (PDT) Message-Id: <200004181830.LAA90983@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ed Hudson Subject: Re: kern/13532: bad vm mfs interaction Reply-To: Ed Hudson Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/13532; it has been noted by GNATS. From: Ed Hudson To: freebsd-gnats-submit@FreeBSD.org, proett@nas.nasa.gov Cc: Subject: Re: kern/13532: bad vm mfs interaction Date: Tue, 18 Apr 2000 11:28:51 -0700 i've just tried this old bug on a 4.0-RELEASE system, with no crashes. when i last tried this (3.3-RELEASE), it hosed my system strait away. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message