Date: Fri, 2 Jun 2006 15:02:52 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Ceri Davies <ceri@submonkey.net>, Kris Kennaway <kris@obsecurity.org>, src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/sysinstall installUpgrade.c Message-ID: <20060602190252.GA69363@xor.obsecurity.org> In-Reply-To: <20060602094051.GF23618@submonkey.net> References: <200605311915.k4VJFKef060742@repoman.freebsd.org> <20060601012130.GA5066@xor.obsecurity.org> <20060601084127.GS21998@submonkey.net> <20060601151837.GA32439@xor.obsecurity.org> <20060602094051.GF23618@submonkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 02, 2006 at 10:40:52AM +0100, Ceri Davies wrote: > On Thu, Jun 01, 2006 at 11:18:37AM -0400, Kris Kennaway wrote: > > On Thu, Jun 01, 2006 at 09:41:27AM +0100, Ceri Davies wrote: > > > On Wed, May 31, 2006 at 09:21:30PM -0400, Kris Kennaway wrote: > > > > On Wed, May 31, 2006 at 07:15:20PM +0000, Ceri Davies wrote: > > > > > ceri 2006-05-31 19:15:20 UTC > > > > >=20 > > > > > FreeBSD src repository > > > > >=20 > > > > > Modified files: > > > > > usr.sbin/sysinstall installUpgrade.c=20 > > > > > Log: > > > > > Update the location of the kernel for upgrades. > > > > > =20 > > > > > I considered leaving /boot/kernel out of the chflags noschg lin= e, but I > > > > > seem to remember that there was a period where /boot/kernel was= schg, so > > > > > have left it in for safety's sake. > > > >=20 > > > > Does this explain the user report I have that a binary upgrade from > > > > 6.0 to 6.1 did not update the kernel? > > >=20 > > > No, I don't think so. This is more to do with saving the old one for > > > saftey's sake; there's nothing in here that should have prevented his > > > old kernel from being committed to block limbo. > > >=20 > > > I'll dig around and see if I can see how that might have happened, bu= t I > > > can't think of anything off the top of my head. > >=20 > > Never mind, it was user error (they were trying to use an 6.0 CD to > > update to 6.1 by changing the release name). This is actually fairly > > common, so I wonder if a bit of text could be added saying not to do > > this. >=20 > Hmm. It's been a while since I tried that, but I remember that worked > (so long as you pointed it at the internets). What you're asking for is > that we check that the release name set in options matches the bits on > the CD if we're extracting from CD, right? I think he was using the CD to do an FTP install and manually changing the release name from 6.0 to 6.1. This tends to fail since the old release doesn't know all of the special steps that need to be done to update to the new version. In this case it didn't replace the kernel, maybe because it didn't know it was supposed to first chflags noschg it. Kris --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEgItcWry0BWjoQKURAnikAKD3laP6ElYIARTvq+fmQknwRhRoFACcDER4 Gt9XnRIChmPNusC8GtORq/8= =HPaV -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060602190252.GA69363>