Bug#813506: zipl-installer: set up re-IPL to boot newly installed Debian/Linux

[Philipp Kern <pkern@debian.org>]

On Tue, Feb 02, 2016 at 05:40:34PM +0100, Hendrik Brueckner wrote:
> --- a/debian/zipl-installer.postinst
> +++ b/debian/zipl-installer.postinst
> @@ -57,8 +57,5 @@ EOF
>  sed -e 's/^do_bootloader.*$/do_bootloader = yes/' < /target/etc/kernel-img.conf > /target/etc/kernel-img.conf.$$
>  mv /target/etc/kernel-img.conf.$$ /target/etc/kernel-img.conf
>  
> -mount -t proc none /target/proc || true
> -
> -log-output -t zipl-installer chroot /target /sbin/zipl
> -
> -umount /target/proc || true
> +# Run zipl in the installed target instance
> +in-target /sbin/zipl -V

I'm a bit sad that this loses the zipl-installer tagging in
/var/log/syslog because in-target does not support customized logging.
It will log everything as "in-target".

At least there's prior art here in grub-installer calling in-target
if $ROOT is /target. in-target does a bunch of stuff with policy-rc.d,
for instance. But I guess that should be safe then...

> diff --git a/finish-install.d/70chreipl b/finish-install.d/70chreipl
> new file mode 100755
> index 0000000..ff8bcb9
> --- /dev/null
> +++ b/finish-install.d/70chreipl
> @@ -0,0 +1,3 @@
> +#!/bin/sh -e
> +
> +in-target chreipl /boot || true

Did you test that /usr/sbin is in PATH? For zipl we specify /sbin
explicitly. (And yes, those might well be different execution
environments...)

Kind regards
Philipp Kern