From owner-freebsd-current Mon Aug 3 19:27:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16265 for freebsd-current-outgoing; Mon, 3 Aug 1998 19:27:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA16258 for ; Mon, 3 Aug 1998 19:27:34 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z3Wou-0006T0-00; Mon, 3 Aug 1998 20:27:24 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id UAA00389; Mon, 3 Aug 1998 20:27:14 -0600 (MDT) Message-Id: <199808040227.UAA00389@harmony.village.org> To: Chuck Robey Subject: Re: CTM checksum errors? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Aug 1998 20:54:17 EDT." References: Date: Mon, 03 Aug 1998 20:27:14 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : Maybe someone did you a "favor" and used cvsup on it? That would sure : do it. That is not possible. I've been trying to get my CVS tree updated via CVSUP (well a copy of it) and can't get the socks option to work with it at all. :-(. One good thing about all of this, however. I think I may have found a way to get a reproducible crash with soft updates: ctm -b /part/with/soft/updates/CVS * where the current directory has ctm cvs-cur.1800A.gz through cvs-cur.4522.gz.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message