Using plymouth to install updates at startup time

[Richard Hughes]

On 3 June 2012 15:08, Ray Strode <halfline at gmail.com> wrote:
> Oh right, the initrd already started it presumably.  Though, you'll
> want to make sure it still gets started on systems that don't have
> initrds too:

Hmm, I hadn't thought about this, thanks.

> Well, I had assumed there wouldn't be a reboot, but instead a
> systemctl isolate system-update.target

Nahh, Lennart wanted a full reboot so we can start afresh with new
library versions, directory locations and that kind of thing.

> If you're doing a full reboot, then's no reason to quit the running
> plymouth, so I'd say let's nix the updates mode idea.

Okay.

> You could hack it like some distros hack fsck by having the splash
> plugin look for and act on specific milestone markers,
> e.g. plymouth update --status=system-update-25%

Nahh, icky.

> You'll have to be careful on the systemd side to make sure it doesn't
> try to kill plymouth, or start a new plymouth during the shutdown
> part.

I'm not totally sure how to do that -- Lennart?

> plymouth change-mode --updates
> plymouth display-message --text="Preparing to install updates..."
> plymouth system-update --progress=0.0
> plymouth system-update --progress=0.23
> plymouth system-update --progress=0.52
> plymouth system-update --progress=1.0
> plymouth change-mode --shutdown
> plymouth display-message --text="Updates installed, rebooting..."

Yes, this makes more sense for me.

> Either way, we're going to need to write some code

Yup, that's expected, don't worry :)

Richard