From: Jorge Almeida <jalmeida@math.ist.utl.pt>
To: Gerrit Pape <pape@smarden.org>
Cc: supervision@list.skarnet.org
Subject: Re: aborting at stage 1?
Date: Tue, 19 Jun 2007 20:02:02 +0100 (WEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706191952230.3196@jmaa.math.ist.utl.pt> (raw)
In-Reply-To: <20070619183202.24886.qmail@f2f18f9094771c.315fe32.mid.smarden.org>
On Tue, 19 Jun 2007, Gerrit Pape wrote:
>
> Hi,
>
> if something goes wrong in stage 1, the /etc/runit/1 script should exit
> 100. runit will then skip stage 2, and enter stage 3, see runit(8).
> Possibly some things in stage 3 won't work if the root fs is mounted
> read-only, but finally /etc/runit/3 will exit, and runit will either
> halt or reboot after looking at /etc/runit/reboot. For read-only
> filesystems, runit supports /etc/runit/reboot being a symlink, even a
> dangling one, which can point into a ramdisk mount point. This applies
I suppose one can even do without the ramdisk by mounting an appropriate
"static" file over /etc/runit/reboot, with -o remount.
A thing that doesn't seem to play well with a pure-runit approach is
udevd. Maybe a solution would be to create a few static devices (the
ones needed for a particular system) and then run udevd as a stage 2
service, to take care of things like pen drives and such. (Just some
thoughts...)
> HTH, Gerrit.
>
>
Thanks,
Jorge
prev parent reply other threads:[~2007-06-19 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 12:20 Jorge Almeida
2007-04-28 16:57 ` Vincent Danen
2007-04-28 19:34 ` Jorge Almeida
2007-04-29 0:22 ` Mike Buland
2007-04-29 23:12 ` Vincent Danen
2007-04-30 10:06 ` Jorge Almeida
2007-06-19 18:32 ` Gerrit Pape
2007-06-19 19:02 ` Jorge Almeida [this message]
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=Pine.LNX.4.64.0706191952230.3196@jmaa.math.ist.utl.pt \
--to=jalmeida@math.ist.utl.pt \
--cc=pape@smarden.org \
--cc=supervision@list.skarnet.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 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).