Date: Sun, 14 Aug 2011 15:51:29 +0400 From: Test Rat <ttsestt@gmail.com> To: Eduardo Morras <nec556@retena.com> Cc: freebsd-current@freebsd.org Subject: Re: [rfc] replacing /boot/kernel.old with a unique directory name Message-ID: <86bovsyzwe.fsf@gmail.com> In-Reply-To: <86sjp4z0xa.fsf@gmail.com> (Test Rat's message of "Sun, 14 Aug 2011 15:29:21 %2B0400") References: <20110813195127.GA34295@freebsd.org> <CC816BA30D11428593A03EF5FF449295@multiplay.co.uk> <35403.3654126853$1313318383@news.gmane.org> <86sjp4z0xa.fsf@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86bovsyzwe.fsf>