From owner-freebsd-hackers Mon Apr 27 20:07:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20784 for freebsd-hackers-outgoing; Mon, 27 Apr 1998 20:07:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20565 for ; Mon, 27 Apr 1998 20:06:31 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id WAA01841; Mon, 27 Apr 1998 22:04:58 -0400 (EDT) Date: Mon, 27 Apr 1998 22:04:58 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: Warner Losh cc: hackers@FreeBSD.ORG Subject: Re: ctm question In-Reply-To: <199804280246.UAA03021@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Apr 1998, Warner Losh wrote: > > OK. I have a ctm archive that was partially applied when the power > went away. It appears from the ctm_status file to have been applied, > but in reality it wasn't. This CTM file was huge (the recent 2.2.6 > mark going down), so there are boatloads of files impacted. Is there > some simple option to ctm that says "look, do the best you can, don't > touch those things that whose md5 doesn't match, but do touch those > that do" so that I have at least a hope of restoring my local CVS tree > w/o having to fetch the latest all snapshot. > > I looked in the manual, but didn't see anything. I'm doing a binary > search right now with -e options, but that is really painful... > > Thanks for any aid you might be able to render... Got just what you want, Warner ... here's a cut'n'paste copy of a post from about a month ago: cmtmd5 and ctmindex, an alternative to ctm(1) --------------------------------------------- see http://www.hclb.demon.co.uk/freebsd/ for fuller details and a zip file to download. Download ctmmd5 ctmmd5 and ctmindex are two programs which operate together to replace ctm(1). ctmindex takes a delta and creates an index file from it. The index file in then fed via stdin to ctmmd5 which tests the md5 checksum of the files listed in the index and applies any patches it can to them. ctmmd5 is much less fussy about broken source files than is ctm(1). It can also use any files it finds on a cdrom or elsewhere on your disks. If ctmmd5 fails to patch a file it will generate a shell script which can be used to ftp a replacement from one of the FreeBSD ftp sites. WHY USE CTNINDEX and CTMMD5? ctmindex and ctmmd5 come into their own if you have a source tree which ctm(1) refuses to touch. Once this happens it can often be extremely difficult and tedious to get the source tree into a state which ctm(1) will work on. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message