On Sun, 18 Jul 1999, Julian Gilbey wrote:
> > On Sun, Jul 18, 1999 at 02:45:04AM +0100, Julian Gilbey wrote:
> > > Do you know of any conffiles which are not configuration files? The
> > > concept of a conffile which is not a configuration file is bizarre.
> >
> > /etc/init.d/* and /etc/cron.d/*
On Sun, Jul 18, 1999 at 12:19:28PM -0500, Steve Greenland wrote:
> the /etc/init.d startup scripts as configuration files in any purest
> sense; they are more acurately described as "scripts subject to local
> modification" (which I personally would prefer be modified to store the
> configuration d
On 19-Jul-99, 04:25 (CDT), Julian Gilbey <[EMAIL PROTECTED]> wrote:
> One other question about the proposal. Is it necessary for multiple
> packages which share a configuration file for one of them to specify
> it as a conffile? Maybe it is a configuration file which by nature
> cannot be a conf
> On 18-Jul-99, 14:43 (CDT), Julian Gilbey <[EMAIL PROTECTED]> wrote:
> > > I'm against saying that "every conffile is a configuration file" simply
> > > because I don't want to lock out some other legitimate use of the
> > > conffile mechanism.
> >
> > The very nature of the conffile mechanism s
On 18-Jul-99, 14:43 (CDT), Julian Gilbey <[EMAIL PROTECTED]> wrote:
> > I'm against saying that "every conffile is a configuration file" simply
> > because I don't want to lock out some other legitimate use of the
> > conffile mechanism.
>
> The very nature of the conffile mechanism seems to be t
> if that behavior is useful. Examples? Well, I don't really think of
> the /etc/init.d startup scripts as configuration files in any purest
> sense; they are more acurately described as "scripts subject to local
> modification" (which I personally would prefer be modified to store the
> configurat
> On Sun, Jul 18, 1999 at 02:45:04AM +0100, Julian Gilbey wrote:
> > Do you know of any conffiles which are not configuration files? The
> > concept of a conffile which is not a configuration file is bizarre.
>
> /etc/init.d/* and /etc/cron.d/* are not really configuration files for
> the program
On 17-Jul-99, 20:45 (CDT), Julian Gilbey <[EMAIL PROTECTED]> wrote:
> > Note that a script that embeds configuration information (such as most
> > of the files in `/etc/init.d' and `/etc/cron.{hourly,weekly,monthly}')
> > is de-facto a configuration file and should be treated as suc
On Sun, Jul 18, 1999 at 02:45:04AM +0100, Julian Gilbey wrote:
> Do you know of any conffiles which are not configuration files? The
> concept of a conffile which is not a configuration file is bizarre.
/etc/init.d/* and /etc/cron.d/* are not really configuration files for
the programs in the pac
A few questions on the wording of this, but once those are clarified,
I will second the proposal.
> 4.7.1. Definitions
> --
>
> configuration file
> A file that affects the operation of program, or provides site-
> or host-specific information, or otherwis
I second this proposal.
--
see shy jo
package: debian-policy
version: 3.0.0.0
The configuration files section has long needed correction
and clarification. I propose we replace the existing section
(currently 4.7) with the following text. (I don't think I've
made any substantiative changes to actual policy, but I may
have shaded some
12 matches
Mail list logo
