Re: Reboot - Versioned Kernel Installs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Friday, June 10, 2011 05:48:57 Vic Demuzere wrote:
> On Jun 10, 2011 12:43 PM, "Martti Kühne" <mysatyre@xxxxxxxxx> wrote:
> > On Fri, Jun 10, 2011 at 12:36 AM, C Anthony Risinger <anthony@xxxxxxx>
> 
> wrote:
> > <snip>
> > 
> > > what if we (optionally) stored the original images _inside_ the new
> > > one?  the new/bad kernel would boot, and via some bootloader entry eg.
> > > kernel param the new initcpio script would kexec the old kernel, with
> > > another (different) kernel param ... when the old kernel booted it
> > > would load the exact same initramfs image, except it would use an
> > > alternate tree, ie. instead of /init it would chroot to /previous and
> > > run /previous/init ...
> > 
> > eh, for the priority of known sources of error: an UPDATE image could
> > contain the NEW kernel in an alternate tree /new/init, because the OLD
> > kernel is KNOWN to boot that far...
> > 
> > Anything else would be insane.
> 
> Having multiple kernels is insane. I don't get why it's needed. There is a
> live cd to rescue your system if needed.
> 
> Vic

Another agreement from me here. Also, may I also add that a great deal of Arch 
users have /boot in a (tiny) partition to start with and can't really KEEP 
that much stuff in there? Keeping old kernels would definitely screw their 
systems up and keep them from upgrading with any ease.


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux