From owner-freebsd-stable Wed Apr 3 14:36:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtpout.mac.com (smtpout.mac.com [204.179.120.88]) by hub.freebsd.org (Postfix) with ESMTP id BF70037B43C; Wed, 3 Apr 2002 14:36:36 -0800 (PST) Received: from smtp-relay01.mac.com (server-source-si02 [10.13.10.6]) by smtpout.mac.com (8.12.1/8.10.2/1.0) with ESMTP id g33MaXN2023725; Wed, 3 Apr 2002 14:36:33 -0800 (PST) Received: from asmtp02.mac.com ([10.13.10.66]) by smtp-relay01.mac.com (Netscape Messaging Server 4.15 relay01 Jun 21 2001 23:53:48) with ESMTP id GU0K4W00.PH5; Wed, 3 Apr 2002 14:36:32 -0800 Received: from quinn ([65.96.80.20]) by asmtp02.mac.com (Netscape Messaging Server 4.15 asmtp02 Jun 21 2001 23:53:48) with ESMTP id GU0K4V00.L8L; Wed, 3 Apr 2002 14:36:31 -0800 Date: Wed, 3 Apr 2002 17:36:28 -0500 Subject: Re: Heads up, a bit: ephemeral port range changes Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v481) Cc: Mike Silbersack , stable@FreeBSD.ORG To: "Jacques A. Vidrine" From: Justin White In-Reply-To: <20020403221056.GB89405@madman.nectar.cc> Message-Id: <3D426F83-4753-11D6-9621-000393092F82@mac.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.481) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, April 3, 2002, at 05:10 , Jacques A. Vidrine wrote: > On Wed, Apr 03, 2002 at 10:00:27PM -0600, Mike Silbersack wrote: >> On Wed, 3 Apr 2002, Jacques A. Vidrine wrote: >> If this really is going to cause problems, >> it's better that we find out now rather than wait until >> 4.6-release. (I >> don't believe it will cause problems, in any case.) > > I disagree. Some people running -STABLE will be behind firewalls > which they don't administrate. After updating one day [1], they may > suddenly have network applications failing in strange ways. For some > people, it will be very hard to track down the problem. > > Why do you feel you must change this in the -STABLE branch? What > benefit is it to the users of -STABLE? > > I don't object outright to merging the change during 4.6-RELEASE code > slush, although I think that it is a gratuitous change for a minor > release bump. why wait for code slush? as long as the same notice that was in the original e-mail (about firewalls that specifically allow 1024-5000 and disallow others) is put into /usr/src/UPDATING, there should be no problems. no one will just "update one day" and not be able to find the problem. the problem (IF they have it) will be right there in /usr/src/UPDATING, with a solution. if you're tracking stable, current, or just updating releases, and not reading /usr/src/UPDATING, you should be. that's what it's there for. -Justin White justinfinity@mac.com http://justinfinity.2y.net/ AIM:just6979 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message