From owner-freebsd-stable Fri Mar 20 18:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02303 for freebsd-stable-outgoing; Fri, 20 Mar 1998 18:52:09 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02255 for ; Fri, 20 Mar 1998 18:52:00 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from baloon.mimi.com (sjx-ca126-11.ix.netcom.com [207.92.177.203]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id SAA29628; Fri, 20 Mar 1998 18:51:53 -0800 (PST) Received: (from asami@localhost) by baloon.mimi.com (8.8.8/8.8.8) id SAA01341; Fri, 20 Mar 1998 18:51:47 -0800 (PST) (envelope-from asami) Date: Fri, 20 Mar 1998 18:51:47 -0800 (PST) Message-Id: <199803210251.SAA01341@baloon.mimi.com> To: mvh@netcom.com CC: john@www.cas.unt.edu, freebsd-stable@FreeBSD.ORG In-reply-to: <199803200615.WAA20223@netcom1.netcom.com> (mvh@netcom.com) Subject: Re: 'Code Freeze' From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk * One more pet peeve - can the binaries for the ports be left on * cdrom.com at least until the next release? I've lent CDs to people * who aren't up to going -stable yet, and a remarkable number of the * ports can't be built because the binaries can't be fetched. This is news to me. I've been trying very hard to keep the distfiles for at least one release prior to the current one up there for ftp. For those that have the same filename and different checksum, there is little we can do about, but I'm confident something like 98% (to grab an arbtrary number out of think air) of the distfiles on ftp.freebsd.org are correct. Please let me know which one if there are any that's missing. Satoshi P.S. Did you tell your friends that they can mount the CDROM as "/cdrom" and have the distfiles fetched from there? :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message