"Laurent Bercot" <ska-supervision_at_skarnet.org> writes:
> That said, I'm not sure your goal is as valuable as you think it is.
> If you have a running system, by definition, it's running. It has
> booted,
> and you have access to its rootfs and all the tools on it; there is
> nothing to gain by doing something fragile such as exec'ing into
> another pid 1 and pivot_rooting. Unless I've missed something, the
> amount of space you'll need for your maintenance system will be the
> exact same whether you switch to it from your production system or from
> cold booting.
I would agree with you generally, but in this case the running system
has a readonly squashfs filesystem which can't be updated except by
flashing a complete new filesystem image on top of it. (I have tried
doing this on the running system just to see what would happen, but the
result was as about terminal as you might imagine it would be.) 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.
-dan
Received on Sun Nov 19 2023 - 01:31:43 CET