Re: [rfc] replacing /boot/kernel.old with a unique directory name

On Sun Aug 14 11, Test Rat wrote:
> Test Rat <ttsestt_at_gmail.com> writes:
> 
> > Eduardo Morras <nec556_at_retena.com> writes:
> >
> >> At 22:06 13/08/2011, Steven Hartland wrote:
> >>>> i just had the following idea: how about instead of copying the
> >>>> current kernel
> >>>>to /boot/kernel.old and then installing the new one under /boot/kernel as the
> >>>> results of target installkernel, we create a unique directory name
> >>>> for the old
> >>>>kernel?
> >>>
> >>>The default size of / is likely your biggest problem.
> >>
> >> Don't know how much compresable is /boot/kernel.old but tar with -z 
> >> or -j may be a workaround. We can extract on demand and swap current
> >> /boot/kernel  with new /boot/kernel. Other way of do it is link
> >> /boot/kernel  to current kernel and update it, but i don't know
> >> (again) if it would work in single user mode.
> >
> > There is kgzldr that lets you boot compressed kernels. Try
> >
> >   $ gzip /boot/kernel/*
> >   $ reboot

the above works for me. just booted a compressed kernel.

> 
> Nevermind, I've confused it with gzip support in loader, it also
> has bzip2 support which for some reason doesn't work for me
> 
>   bzf_read: BZ2_bzDecompress returned -3