From owner-ctm-announce Sat Mar 31 15:18: 1 2001 Delivered-To: ctm-announce@freebsd.org Received: from picnic.chuckr.org (picnic.chuckr.org [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id 10F4E37B719 for ; Sat, 31 Mar 2001 15:17:59 -0800 (PST) (envelope-from chuckr@picnic.chuckr.org) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.11.3/8.11.3) with ESMTP id f310IL672569 for ; Sat, 31 Mar 2001 19:18:21 -0500 (EST) (envelope-from chuckr@picnic.chuckr.org) Date: Sat, 31 Mar 2001 19:18:11 -0500 (EST) From: Chuck Robey To: ctm-announce@freebsd.org Subject: ctm ftp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ctm-announce@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been asking around for a temporary home for the ctm deltas, something the other sites can mirror from. The host I have access to, for ctm generation, is ready to go, but I need a place to stick the deltas, because I can't get local permission to allow ftp. That place must be willing to let me send them in some other way than the old method, ftp mirroring from the ctm generation site. Perhaps scp would be ok. This is a temporary need, because I expect to be able to work out *some* sort of arrangement with a site from FreeBSD.org, but I don't want to hold things up any more, I'm ready otherwise to begin test generation of ctm deltas. I've mailed off to some of the ftp sites that currently mirror ctm, but no answer yet. Anyone willing to allow me such access on a short term (probably less than 1 month) basis? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe ctm-announce" in the body of the message