Bug#751012: [flash-kernel] Flash-kernel should fail with exit 0 under debrootstrap
On Mon, 2014-06-09 at 17:54 +0200, Bastien ROUCARIES wrote:
> On Mon, Jun 9, 2014 at 5:21 PM, Karsten Merker <merker@debian.org> wrote:
> > On Mon, Jun 09, 2014 at 03:48:11PM +0000, bastien ROUCARIES wrote:
> >
> >> Package: flash-kernel
> >> Severity: important
> >>
> >> Flash-kernel should detect it run under debrootstrap and fail gracefully/
> >>
> >> Install message:
> >>
> >> Processing triggers for libc-bin (2.18-7) ...
> >> Processing triggers for initramfs-tools (0.115) ...
> >> update-initramfs: Generating /boot/initrd.img-3.14-1-kirkwood
> >> /bin/df: Warning: cannot read table of mounted file systems: No such file or directory
> >> warning: failed to read mtab
> >> ^Cdpkg: error processing package initramfs-tools (--configure):
> >> subprocess installed post-installation script was interrupted
> >> Errors were encountered while processing:
> >> initramfs-tools
> >> E: Sub-process /usr/bin/dpkg returned an error code (1)
> >
> > Hello,
> >
> > I am trying to understand which problem exactly you have
> > encountered, but I am a bit confused: you have filed a bug
> > against flash-kernel but in the log you have provided, it is not
> > flash-kernel that shows an error message, but initramfs-tools. I
> > also cannot see in which context that has happened and how it
> > relates to debootstrap - by default debootstrap does neither
> > install a kernel image nor flash-kernel. From your log, it looks
> > like you have manually interrupted the update-initramfs process,
> > resulting in the error message above:
>
> No I have not interupted.
What is the ^C in the output from? Was it produced verbatim by the
process?
> I have installed te kirkwood kernel and flash-kernel on my chroot.
Out of interest, why?
> The problem is that flash-kernel is run by initramfs/post-update.d/flash-kernel
>
> I have added an exit 0 at the beginning of this file and everything is ok
>
> The best think is to exit 0 if we are under a debootstrap.
If you want to install flash-kernel in a chroot/debootstrap etc then you
should set FK_MACHINE=none in the environment or write none to
$chroot/etc/flash-kernel/machine, either of which will cause
flash-kernel to become a nop.
Alternatively if you want f-k to behave as if it was installing on a
particular piece of h/w you can use the appropriate DB Machine name,
although YMMV if that machine requires writing to specific partitions
etc.
Ian.
Reply to: