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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
