Date: Sun, 14 Aug 2011 15:29:21 +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: <86sjp4z0xa.fsf@gmail.com> In-Reply-To: <35403.3654126853$1313318383@news.gmane.org> (Eduardo Morras's message of "Sun, 14 Aug 2011 12:27:21 %2B0200") References: <20110813195127.GA34295@freebsd.org> <CC816BA30D11428593A03EF5FF449295@multiplay.co.uk> <35403.3654126853$1313318383@news.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86sjp4z0xa.fsf>