From owner-freebsd-hackers  Fri Sep 22 06:49:47 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id GAA01628
          for hackers-outgoing; Fri, 22 Sep 1995 06:49:47 -0700
Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id GAA01607
          ; Fri, 22 Sep 1995 06:49:40 -0700
Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA20435
  (5.67a/IDA-1.5); Fri, 22 Sep 1995 08:36:22 -0500
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id IAA20502; Fri, 22 Sep 1995 08:35:51 -0500
From: peter@taronga.com (Peter da Silva)
Message-Id: <199509221335.IAA20502@bonkers.taronga.com>
Subject: Re: ports startup scripts
To: gryphon@healer.com (Coranth Gryphon)
Date: Fri, 22 Sep 1995 08:35:50 -0500 (CDT)
Cc: hackers@freebsd.org, peter@taronga.com, ports@freebsd.org
In-Reply-To: <199509220427.AAA02389@healer.com> from "Coranth Gryphon" at Sep 22, 95 00:27:36 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 847       
Sender: owner-hackers@freebsd.org
Precedence: bulk

> Crontab entries, yes. Package data, I could go either way with.

Package data could equally well go in /usr/local. It really doesn't belong in
/var.

> Aren't "at" jobs single shot, therefore volotile?

I have seen people running "at" jobs that re-triggered themselves, to get
the effect of variable-period rescheduling too complex for cron. You could
do as well with a cron-run daemon that read a more complex schedule file.

I'll buy "at" in var. I think /etc/dumpdates might go in /var as well.

> > 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.

/usr/local/ghostscript/3.0/Fontmap?

System V uses "/etc/default" for per-package config files. They're not really
templates, they're things like /etc/csh.login.

/etc/default/ghostscript/Fontmap?