From owner-freebsd-current@FreeBSD.ORG  Sun Aug 14 12:02:06 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1233)
	id AE640106567A; Sun, 14 Aug 2011 12:02:06 +0000 (UTC)
Date: Sun, 14 Aug 2011 12:02:06 +0000
From: Alexander Best <arundel@freebsd.org>
To: Test Rat <ttsestt@gmail.com>
Message-ID: <20110814120206.GA66085@freebsd.org>
References: <20110813195127.GA34295@freebsd.org>
	<CC816BA30D11428593A03EF5FF449295@multiplay.co.uk>
	<35403.3654126853$1313318383@news.gmane.org>
	<86sjp4z0xa.fsf@gmail.com> <86bovsyzwe.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <86bovsyzwe.fsf@gmail.com>
Cc: Eduardo Morras <nec556@retena.com>, freebsd-current@freebsd.org
Subject: Re: [rfc] replacing /boot/kernel.old with a unique directory name
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 12:02:06 -0000

On Sun Aug 14 11, Test Rat wrote:
> Test Rat <ttsestt@gmail.com> writes:
> 
> > Eduardo Morras <nec556@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