From owner-freebsd-current Thu May 21 21:04:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20687 for freebsd-current-outgoing; Thu, 21 May 1998 21:04:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from imo30.mx.aol.com (imo30.mx.aol.com [198.81.17.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20635 for ; Thu, 21 May 1998 21:04:26 -0700 (PDT) (envelope-from StevenR362@aol.com) Received: from StevenR362@aol.com by imo30.mx.aol.com (IMOv14.1) id 4ZHMa02449; Fri, 22 May 1998 00:02:12 -0400 (EDT) From: StevenR362 Message-ID: <15cf01e2.3564f8c5@aol.com> Date: Fri, 22 May 1998 00:02:12 EDT To: jhay@mikom.csir.co.za, sepotvin@videotron.ca Cc: current@FreeBSD.ORG Mime-Version: 1.0 Subject: Re: softupdates Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: AOL 4.0 for Windows 95 sub 170 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In a message dated 5/21/98 4:36:49 PM Eastern Daylight Time, jhay@mikom.csir.co.za writes: << You are not alone. We have the same here on our SMP machine. I thought it was the SMP that was at fault, but now with your report, maybe it is that after all. I can do lots of "make buildworld"s and "make world"s with no problems, but "make release" kill it everytime. For now we are back to an async mount on the release partition. The machine does not have devfs, so it isn't that either. John -- John Hay -- John.Hay@mikom.csir.co.za >> This is pure conjecture, but doesn't a make release use the vn device? Maybe, softupdates interacts badly with vn accessed filesystems. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message