All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Søren Boll Overgaard" <boll+mlmmj@fork.dk>
To: mlmmj@mlmmj.org
Subject: Re: splitting configuration from the spool/queue
Date: Tue, 07 Sep 2004 09:37:40 +0000	[thread overview]
Message-ID: <20040907093740.GD70234@freesbee.wheel.dk> (raw)
In-Reply-To: <20040907083520.GA70234@freesbee.wheel.dk>

On Tue, Sep 07, 2004 at 11:34:00AM +0200, Mads Martin Joergensen wrote:
> > Well, making the symlinks from /var to /etc would break future
> > introductions of calls to chroot(), so symlinks, if used, should
> > probably be from /etc to /var, and not vice-versa.
> 
> If the symlinks go from /etc to /var, how can the config files be on a
> read-only mounted filesystem?

Obviously the system would need to be made read-write during configuration
changes. To my knowledge that's not unreasonable for /etc on a production 
server.

-- 
Søren O.                                           ,''`.
                                                   : :' :
GPG key id: 0x1EB2DE66                             `. `'
GPG signed mail preferred.                           `-

  parent reply	other threads:[~2004-09-07  9:37 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
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 [this message]
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=20040907093740.GD70234@freesbee.wheel.dk \
    --to=boll+mlmmj@fork.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.