From: "Morten K. Poulsen" <morten@afdelingp.dk>
To: mlmmj@mlmmj.org
Subject: Re: splitting configuration from the spool/queue
Date: Tue, 07 Sep 2004 10:00:19 +0000 [thread overview]
Message-ID: <20040907100019.GD1623@mopo.tv2.local> (raw)
In-Reply-To: <20040907083520.GA70234@freesbee.wheel.dk>
On Tue, Sep 07, 2004 at 11:54:20AM +0200, Søren Boll Overgaard wrote:
> > What I meant is: if the symlinks are in /etc pointing to the actual
> > files below /var/.../control holding the data, then the config files are
> > not on the read-only file system, are they?
> >
> > But that's only a problem in the case of chroot environments of course.
>
> I think we agree, even if the terminology is a little fuzzy :)
>
> If the actual files are in /etc and symlinks are made from /var/.. to /etc,
> then problems will arise if chroot'ing is introduced. This is easily fixed
> though, as one can just make the links hard
No, you can not make hard links across partitions, and you can not make
only some part of a partition read-only.
So:
- All files in /var, symlinks in /etc, chroot
- Some files in /var, some in /etc, symlinks in /var, NO chroot
Morten
--
Morten K. Poulsen <morten@afdelingp.dk>
http://www.afdelingp.dk/
next prev parent reply other threads:[~2004-09-07 10:00 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
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 [this message]
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=20040907100019.GD1623@mopo.tv2.local \
--to=morten@afdelingp.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.