From: "Milan P. Stanic" <mps@rns-nis.co.yu>
Subject: Re: runit on the read-only file system
Date: Tue, 8 Jun 2004 15:04:56 +0200 [thread overview]
Message-ID: <20040608130456.GA17649@rns-nis.co.yu> (raw)
In-Reply-To: <20040606230951.GM8983@tinyvaio.nome.ca>
On Mon, Jun 07, 2004 at 08:09:53AM +0900, mike@mikebell.org wrote:
> Nope, not that I know of. I guess you /could/ just modify runsv to
> create directories at the end of broken symlinks, then point all the
> supervise symlinks to the non-existant subdirectories of a tmpfs mount.
> That would be a little more difficult up-front but would make things
> much easier in the long run, and since only root should have write
> access to make such a symlink I don't see any particular security
> implications as long as you make the directory safely.
I hacked runit to use /var/runit instead of /etc/runit and made script
which create /var hierarchy and symlinks during boot.
It is crude hack, but it works for now. So, I have runit on read-only
filesystem with /var mounted on tmpfs.
next prev parent reply other threads:[~2004-06-08 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 23:29 Milan P. Stanic
2004-06-06 2:15 ` mike
2004-06-06 21:46 ` Milan P. Stanic
2004-06-06 23:09 ` mike
2004-06-08 13:04 ` Milan P. Stanic [this message]
2004-06-07 15:05 ` Gerrit Pape
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=20040608130456.GA17649@rns-nis.co.yu \
--to=mps@rns-nis.co.yu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).