From owner-freebsd-stable Thu Aug 24 5:11: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id D485137B422 for ; Thu, 24 Aug 2000 05:10:54 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id IAA32736; Thu, 24 Aug 2000 08:01:08 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008241201.IAA32736@sanson.reyes.somos.net> From: "Francisco Reyes" To: "fingers" Cc: "FreeBSD Stable List" Date: Thu, 24 Aug 2000 08:08:52 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Aug 2000 10:11:03 +0200 (SAST), fingers wrote: >Hi > >> What was the reason for these daemons been set to not start? >> Wouldn't this "break" working machines? > >I don't know what percentage of installers are doing the same, That is the problem. Most likely nobody knows the percentage of people that use them vs the percentage that turns them off. >but the first thing I do is disable them and kill 'em dead. Perhaps this could be an installation flag. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message