From owner-freebsd-current Mon Aug 19 21:33: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0EDF37B400 for ; Mon, 19 Aug 2002 21:32:58 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4BCA43E77 for ; Mon, 19 Aug 2002 21:32:58 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 7635AAE1C1; Mon, 19 Aug 2002 21:32:58 -0700 (PDT) Date: Mon, 19 Aug 2002 21:32:58 -0700 From: Alfred Perlstein To: current@freebsd.org Subject: -current data corruption Message-ID: <20020820043258.GI75574@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If anyone is interested both David O'Brien and I are experiencing what looks like data corruption under -current. On a dual SMP AMD 1.9ghz box I'm seeing the vim port somehow corrupt patched files. I really don't have the time or energy to backtrack -current to figure out when or why this started happening. At first I thought it had to deal with pipes, but afaik the vim port doesn't patch files, it just does this: /usr/bin/patch -d /vol/share/ports/editors/vim/work/vim61/ --forward --quiet -E -p0 < $i for each patchfile in the port. Please CC me, as I'm not subscribed to this list. -- -Alfred Perlstein [alfred@freebsd.org] [#bsdcode/efnet/irc.prison.net] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message