Date: Fri, 22 Sep 1995 00:27:36 -0400 From: Coranth Gryphon <gryphon@healer.com> To: hackers@freebsd.org, peter@taronga.com, ports@freebsd.org Subject: Re: ports startup scripts Message-ID: <199509220427.AAA02389@healer.com>
next in thread | raw e-mail | index | archive | help
From: peter@taronga.com (Peter da Silva)
> Satoshi Asami <asami@cs.berkeley.edu> wrote:
> >(1) /etc/rc.d
> > - Ports shouldn't touch anything in the root filesystem
> > + Central location, easy to maintain
> > + Per-machine configuration possible even if /usr/local is NFS shared
> + Complete system configuration backed up by tarring /etc.
> Though for that last, /var/db/pkg, /var/at/jobs, and /var/cron/tabs should
> also be in /etc.
> aside: /var/db/pkg and so on are a problem. Just about everything else
> in /var can safely be considered "volatile", you don't lose system
Crontab entries, yes. Package data, I could go either way with.
Aren't "at" jobs single shot, therefore volotile?
> - Other ports configuration scripts are in /usr/local/{etc,lib}
>
> >(2) /usr/local/etc/rc.d
> This is a problem anyway, since there are other per-machine config files
> in /usr/local.
That's part of the complaint. They shouldn't be.
> I like /etc/rc.d for all sorts of reasons that you've all already seen.
Agreed, but if we go with run levels "/etc/rc.#/..."
-coranth
------------------------------------------+------------------------+
Coranth Gryphon <gryphon@healer.com> | "Faith Manages." |
| - Satai Delenn |
Phone: 603-598-3440 Fax: 603-598-3430 +------------------------+
USMail: 11 Carver St, Nashua, NH 03060
Disclaimer: All these words are yours, except Europa...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509220427.AAA02389>