From owner-ctm-users@FreeBSD.ORG Mon Jan 28 19:30:53 2013 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4221E77E for ; Mon, 28 Jan 2013 19:30:53 +0000 (UTC) (envelope-from ike@blackskyresearch.net) Received: from rs149.luxsci.com (rs149.luxsci.com [64.49.224.181]) by mx1.freebsd.org (Postfix) with ESMTP id D9DD46E4 for ; Mon, 28 Jan 2013 19:30:52 +0000 (UTC) Received: from rs149.luxsci.com (localhost.localdomain [127.0.0.1]) by rs149.luxsci.com (8.14.4/8.13.8) with ESMTP id r0SJUoZC017033 for ; Mon, 28 Jan 2013 14:30:50 -0500 Received: (from root@localhost) by rs149.luxsci.com (8.14.4/8.13.8/Submit) id r0SJU2rv015491 for ctm-users@freebsd.org; Mon, 28 Jan 2013 19:30:02 GMT Received: (from sender 74627) (rs149.luxsci.com [127.0.0.1]) by LuxSci SP; Mon, 28 Jan 2013 19:30:02 +0000 From: "Isaac (.ike) Levy" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: CTM index on servers Date: Mon, 28 Jan 2013 14:29:39 -0500 To: ctm-users@freebsd.org X-Lux-Comment: Message r0SJTdBX014869 sent by user #74627 Message-Id: <1359401402-8482577.26305758.fr0SJTdBX014869@rs149.luxsci.com> X-Comment: LuxSci SP Message ID - 1359401402-8482577.26305758 X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 19:30:53 -0000 Hi Stephen, ctm-users, New to this list, coming from a lively thread on freebsd-stable@ For me and a lot of admins/users, fetching sources just got a lot harder = for a *lot* of admins/users. A page was raised to try to help cull = facts out of all the confusing details, here: https://wiki.freebsd.org/UsersFetchingSource At this point the page may be more confusing itself :) -- Enter: CTM I'm delighted to learn about ctm(1) usage, and quite interested in using = it to fetch REL and RELENG sources, and keep it up to date (to = redistribute internally across a cluster of servers). I know a *ton* of *BSD admins who love c[v]sup, but I don't know any who = use ctm(1) any more, so I'm sorry if my questions are naive. On Jan 28, 2013, at 1:53 PM, Stephen Montgomery-Smith wrote: >> On the FTP server, is there an index of which CTM delta files are on = the FTP server? I'd like to automate fetching just the new deltas... >>=20 >> If there was perhaps 1 file with a consistent name, I could fetch = that on a nightly basis and fetch the other CTM files. >=20 > I can easily put in something like this. Maybe the output of ls in = each directory? >=20 > If you have more ideas on this, sign up to the ctm-users mailing list, = and we can discuss exactly what is wanted. I'm very interested in seeing some kind of 'index' file put in place, a = simple file which lists the ctm delta (and xEmpty) files. This way, users could do something in a shell/cron job, like: fetch ftp://ftp.freebsd.org/pub/FreeBSD/development/CTM/src-9/index # # diff against the last ctm file, or a directory listing containing the = delta files # download/apply any ctm delta files which have not yet been applied -- It's an open question weather or not the entire CTM dir should have the = index, or the individual releases (or both?) e.g. /pub/FreeBSD/development/CTM/src-9/index - vs - /pub/FreeBSD/development/CTM/index (I assume it would be appropriate also to provide sig files for the = index, as well.) -- The index could be as simple as: $ echo "`date +%s`" ; find . -type f -name 'src*' | sort | sed = 's/.*\///' 1359382951 src-9.0400xEmpty.gz src-9.0401.gz src-9.0401.gz.sig src-9.0402.gz src-9.0402.gz.sig src-9.0403.gz src-9.0403.gz.sig $=20 Could get fancier as necessary later, (perhaps date modified for each = file, etc=85) -- With some sort of index, the ease-of-use functionality of c[v]sup could = be trivially replicated in sh(1). Even just as a prototype, this is a task I will enthusiastically do, = even if only for my own use- (I started something already which culls = FTP tarballs, a less than ideal solution). What do yall' think? Best, .ike