supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Daniel Barlow" <dan@telent.net>, supervision@list.skarnet.org
Subject: Re: restarting s6-svscan (as pid 1)
Date: Sun, 19 Nov 2023 01:46:23 +0000	[thread overview]
Message-ID: <em8e9139c6-3190-40fb-8d0d-d3f06a5b798d@648a1dd0.com> (raw)
In-Reply-To: <87wmue7fdc.fsf@telent.net>


 > I believe (have not yet tested) that I can relatively simply create 
the
>maintenance system on the fly by copying a subset of the root fs into a
>ramdisk, so it doesn't take any space until it's needed.

  The problem with that approach is that your maintenance system now
depends on your production system: after a rootfs change, you don't
have the guarantee that your maintenance system will be identical to
the previous one. Granted, the subset you want in your maintenance fs
is likely to be reasonably stable, but you never know; imagine your
system is linked against glibc, you copy libc.so.6, but one day one
of the coreutils grows a dependency to libpthread.so, and voilà, your
maintenance fs doesn't work anymore.

  You probably think the risk is small, and you're probably correct.
I just have a preference for simple solutions, and I believe that a
small, stable, statically-linked maintenance squashfs would be worth
the space it takes on your drive. :)

--
  Laurent


      reply	other threads:[~2023-11-19  1:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 22:20 dan
2023-11-17 22:38 ` adam
2023-11-17 22:45 ` Steve Litt
2023-11-18  0:58 ` Laurent Bercot
2023-11-19  0:31   ` Daniel Barlow
2023-11-19  1:46     ` Laurent Bercot [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=em8e9139c6-3190-40fb-8d0d-d3f06a5b798d@648a1dd0.com \
    --to=ska-supervision@skarnet.org \
    --cc=dan@telent.net \
    --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).