Date: Thu, 24 Aug 2000 08:11:25 -0400 From: "Francisco Reyes" <fran@reyes.somos.net> To: "Nik Clayton" <nik@freebsd.org> Cc: "FreeBSD Stable List" <freebsd-stable@freebsd.org> Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Message-ID: <200008241203.IAA32744@sanson.reyes.somos.net> In-Reply-To: <20000824101352.A48334@canyon.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 24 Aug 2000 10:13:52 +0100, Nik Clayton wrote: >> What was the reason for these daemons been set to not start? > >Now, if you have an empty /etc/rc.conf then (in theory) no network services >are running. This also means that if you want to find out what services are >started at boot time you only have to look in /etc/rc.conf, rather than >having to look at /etc/defaults/rc.conf as well. Then shouldn't we add the current programs which get started to /etc/rc.conf? >> Wouldn't this "break" working machines? > >Only if you (1) Are running -current, and (2) don't read the mailing lists >and the diffs mergemaster shows you. > >If both (1) and (2) are true then you shouldn't be running -current anyway. I know this is currently in "current", but won't this eventually make it to stable? 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008241203.IAA32744>