From owner-freebsd-hackers Wed Feb 1 13:35:42 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA07640 for hackers-outgoing; Wed, 1 Feb 1995 13:35:42 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA07631 for ; Wed, 1 Feb 1995 13:35:34 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA19717; Wed, 1 Feb 1995 16:35:23 -0500 Date: Wed, 1 Feb 1995 16:35:23 -0500 From: Garrett Wollman Message-Id: <9502012135.AA19717@halloran-eldar.lcs.mit.edu> To: Poul-Henning Kamp Cc: hackers@FreeBSD.org Subject: SUP must die, CTM for president !! In-Reply-To: <199502010755.XAA19507@ref.tfs.com> References: <29186.791616495@time.cdrom.com> <199502010755.XAA19507@ref.tfs.com> Sender: hackers-owner@FreeBSD.org Precedence: bulk < said: > But for src-current: > It is stupid. Look at it: We run sup-scan every 8 hours, then > we download individual sets of files to each user based on timestamps. > That's not particular smart. We have probably all been hit by the > zero byte file with the right timestamp havn't we ? It works great for me, and I've never had any problems with it that weren't my fault. As I expressed in another message, I think the problem is that there are simply too many people running -current, who aren't prepared to deal with bleeding-edge phenomena. > On top of that: CTM transfers only the changes, not the entire file > each time a line is touched. Sometimes you want the entire file to be transferred. > CTM uses md5, so it will detect if people have corrupt files. Like in this case. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant