From: Christian Laursen <xi@borderworlds.dk>
To: mlmmj@mlmmj.org
Subject: Re: splitting configuration from the spool/queue
Date: Tue, 07 Sep 2004 08:51:41 +0000 [thread overview]
Message-ID: <86n002o40y.fsf@borg.borderworlds.dk> (raw)
In-Reply-To: <20040907083520.GA70234@freesbee.wheel.dk>
Søren Boll Overgaard <boll+mlmmj@fork.dk> writes:
> Is there any particular reason why the list configuration is situated in the
> same directory structure as the list queue and archive? According to the FHS[1],
> list configuration should be somewhere under /etc while the queue and archive
> should be somewhere under /var. This would have the added benefit that list
> configuration could be stored on a read-only file system for added security.
Personally I find it convenient to have everything related to a list located
under the same directory.
I don't see a problem in adding optional support for having the control dir
located in a seperate location but the current directory layout should continue
to be the default to avoid breaking existing configurations.
--
Christian Laursen
next prev parent reply other threads:[~2004-09-07 8:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 8:35 splitting configuration from the spool/queue Søren Boll Overgaard
2004-09-07 8:45 ` Morten K. Poulsen
2004-09-07 8:51 ` Christian Laursen [this message]
2004-09-07 9:08 ` Mads Martin Joergensen
2004-09-07 9:09 ` Søren Boll Overgaard
2004-09-07 9:19 ` Mads Martin Joergensen
2004-09-07 9:34 ` Mads Martin Joergensen
2004-09-07 9:37 ` Søren Boll Overgaard
2004-09-07 9:38 ` Søren Boll Overgaard
2004-09-07 9:45 ` Mads Martin Joergensen
2004-09-07 9:54 ` Søren Boll Overgaard
2004-09-07 10:00 ` Morten K. Poulsen
2004-09-07 10:14 ` Søren Boll Overgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86n002o40y.fsf@borg.borderworlds.dk \
--to=xi@borderworlds.dk \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.