Date: Sat, 20 Apr 2002 09:45:51 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: "Bruce A. Mah" <bmah@FreeBSD.org> Cc: Hajimu UMEMOTO <ume@mahoroba.org>, Doug Barton <DougB@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: etc mfc Message-ID: <Pine.NEB.3.96L.1020420094500.91313D-100000@fledge.watson.org> In-Reply-To: <200204200727.g3K7ReLt046219@intruder.bmah.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 20 Apr 2002, Bruce A. Mah wrote: > I would strongly like to see the inetd_enable change backed out. > Ultimately, having inetd disabled by default is a Good Thing (TM), but > doing the change in the middle of the 4-STABLE train will cause (and is > causing) too much disruption. In my opinion, the badness outweighs the > goodness. > > In any case, I will make the necessary entries for the release notes. > (Apparently, I haven't yet documented this change for -CURRENT, either.) My recollection is that sysinstall will: (1) prompt to enable inetd during the install and if yes is selected (2) Prompt to edit inetd.conf If they are upgrading, then they will already have an enable line in rc.conf, so I'm not sure it makes the upgrade too bumpy, actually. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1020420094500.91313D-100000>