Date: Fri, 22 Dec 1995 10:24:27 +0000 (GMT) From: Paul Richards <p.richards@elsevier.co.uk> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: jkh@time.cdrom.com, andreas@knobel.gun.de, graichen@omega.physik.fu-berlin.de, current@FreeBSD.org Subject: Re: pcnfsd.. Message-ID: <199512221024.KAA13494@cadair.elsevier.co.uk> In-Reply-To: <199512220806.AAA06934@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Dec 22, 95 00:06:01 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Satoshi Asami who said > > And the X ports have no clue where the heck that tree is. > That's not important in this case. As long as the package knows to install a startup file in the ports_startup_file directory and there's a hook in sysconfig to go look in this directory, there can be a script in that directory for the X package that'll start it and known anything that needs to be known about it. All we're saying, for example is the line in /etc/rc that starts apache should become a startup script say /usr/local/etc/ports/startup/apache, or something better named :-) And that instead of lots of special case lines for each port in /etc/rc or sysconfig you have one hook that trawls through that directory running startup scripts. None of the other ports know where the heck that tree is either. I think you're mixing up the idea of config files and startup files, X config files will still end up in the X tree which is something we should be a bit more forcefull about with the X folks because it's a badly broken concept. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512221024.KAA13494>