From owner-freebsd-current Wed Jun 30 3: 7:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 6D48F14D47 for ; Wed, 30 Jun 1999 03:07:49 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10zHH9-0000rH-00; Wed, 30 Jun 1999 12:07:31 +0200 From: Sheldon Hearn To: Doug Cc: current@freebsd.org Subject: Re: HEADS UP! Inetd wrapping OFF by default In-reply-to: Your message of "Wed, 30 Jun 1999 00:41:54 MST." <3779CA42.40534D6C@gorean.org> Date: Wed, 30 Jun 1999 12:07:31 +0200 Message-ID: <3302.930737251@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 30 Jun 1999 00:41:54 MST, Doug wrote: > > This is a situation in which we can't make _everyone_ happy. For the > > particular case you've provided, anyone who upgrades from 2.2 to 3.3 > > without reading the release notes will get what's coming to him. > > That's always true, but traditionally it's been a primary goal of the > project to make these kinds of changes as minimal as possible. Okay, so let's say we've got Joe Bloggs upgrading from 2.2.8 to 3.3 . He doesn't read the release notes, so he doesn't notice that inetd now wraps by default. The impact on him is: 1) Inetd makes unnecessary calls to hosts_access(). 2) Previously unwrapped internal services are suddenly and mysteriously wrapped. The first is a performance issue and isn't a big deal, given that Joe didn't read the release notes. The second _is_ an issue. However, it's got to be an issue for _someone_; either for Joe or for the guy who's upgrading from 3.2-RELEASE to 3.3-RELEASE. To me, it just doesn't make sense to pander to the people who've lagged behind STABLE. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message