Bug#550584: Initial triggers patch and tracking of highest kernel

[Vagrant Cascadian <vagrant@debian.org>]

On Thu, Mar 10, 2011 at 01:10:41PM +0000, Hector Oron wrote:
> 2011/3/10 Hector Oron <hector.oron@gmail.com>:
> > 2011/3/10 Loïc Minier <lool@dooz.org>:
> 
> >>>  1. Chainload boot, at first boot load the usual kernel then call the
> >>> new one with kexec, if everything is fine then the user can replace
> >>> old kernel with new kernel, else the kexec call fails and leaves you
> >>> with old kernel.
> 
> >>  Sure, that's a nice approach; kexec doesn't work reliably on all
> >>  platforms though, but that would be an option for platforms which
> >>  support it.  There are various efforts to provide such an UI, petitboot
> >>  or kboot for instance.
> 
> More info about this, vagrant implemented a proof of concept for the
> Efika devices to kexec boot into other kernels via initramfs-tools.
>   < http://people.debian.org/~vagrant/efika/initramfs-tools/ >

though i haven't actually tested it on the efikamx, just on i386. i've heard
tell that kexec doesn't work reliably on the efikamx specifically, and arm in
general.

suppose i need to set up a build environment to build a kernel to actually test
it... or hope to see efikamx/sb kernels in debian soon? :)


live well,
  vagrant