On 8/14/11 3:27 AM, Eduardo Morras wrote: > At 22:06 13/08/2011, Steven Hartland wrote: >> ----- Original Message ----- From: "Alexander Best" >> <arundel_at_freebsd.org> >> >>> 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. What would make more sense to me for thsi would be a kernel name that was recognised by teh final boot stages as being an exeprimental kernel and moved to the new location only on successful boot.. Once you have successfully booted it, then you delete the kernel[-1] and do the replacement that "make installkernel" now does. > >> Regards >> Steve > > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe_at_freebsd.org" >Received on Sun Aug 14 2011 - 17:24:29 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:16 UTC