Date: Wed, 31 May 2006 17:05:28 -0400 From: Joe <dev@freedomcircle.net> To: Kris Kennaway <kris@obsecurity.org> Cc: questions@FreeBSD.org Subject: Re: pkg_upgrade? Message-ID: <447E0518.50803@freedomcircle.net> In-Reply-To: <20060531150245.GA64716@xor.obsecurity.org> References: <447B86F3.6070500@freedomcircle.net> <20060530002535.GA94917@xor.obsecurity.org> <447CB067.1080309@freedomcircle.net> <20060530213344.GA34025@xor.obsecurity.org> <447CC3C8.9020300@freedomcircle.net> <20060530222808.GA34725@xor.obsecurity.org> <447CDF69.4030704@freedomcircle.net> <20060531004426.GA36958@xor.obsecurity.org> <447D834A.90000@freedomcircle.net> <20060531150245.GA64716@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > Anyway, retry the binary upgrade as you say. The binary upgrade started from the 6.0-RELEASE CD-ROM didn't work, but using 6.1-RELEASE floppies was successful. I peaked at the debug screen and saw how it gets done: The GENERIC .ko's get put into a separate directory, then there's an 'rm -rf /boot/kernel' and then the GENERIC directory is moved to /boot/kernel. I presume that doing it from sysinstall in a running 6.0 system, the 'rm -rf' fails in spite of the force flag. You'd think the 6.0 CD ought not to have that problem, but I'm not sure if it fetched the .ko's from 6.1 even though it got everything else from 6.1. Thanks for your help. Joe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?447E0518.50803>