Date: Mon, 26 Jun 1995 18:36:37 +0100 (BST) From: Paul Richards <paul@freebsd.netcraft.co.uk> To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Cc: dzerkel@feephi.phofarm.com, jkh@freebsd.org, hackers@freebsd.org Subject: Re: Announcing 2.0.5-950622-SNAP Message-ID: <199506261736.SAA00989@freebsd.netcraft.co.uk> In-Reply-To: <199506260959.CAA03484@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 26, 95 02:59:40 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Rodney W. Grimes who said > > > > > > Well, this has been simplified to a great extent by /etc/sysconfig. > > > It's my intention that ALL of the mutable files in /etc eventually > > > collapse to just /etc/sysconfig, and there's never any reason at all > > > for the user to modify the others. > > > > Well, I regularly turn of lpd... but that's in rc, so I guess a flag > > for that would help. > A knob flag will be added... along with an args variable since lpd > also takes options and arguments that some sites need to set. > > > How would we handle things that currently I put > > into rc.local (httpd)? > > Wouldn't, httpd is not part of the base system and should in no way > be handled by the base system. Umm, yeah, but how do I specify I want to start httpd if I don't put it in rc.local ? The problem is not that there is site specific stuff in rc.local but that that there is generic stuff in there which shouldn't be. That file should be empty and nothing more than a hook out from rc that I can use to start and set local stuff. It would then not need to be touched or even looked at by an upgrade procedure. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506261736.SAA00989>