Date: Thu, 1 Jun 2006 09:41:27 +0100 From: Ceri Davies <ceri@submonkey.net> To: Kris Kennaway <kris@obsecurity.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/sysinstall installUpgrade.c Message-ID: <20060601084127.GS21998@submonkey.net> In-Reply-To: <20060601012130.GA5066@xor.obsecurity.org> References: <200605311915.k4VJFKef060742@repoman.freebsd.org> <20060601012130.GA5066@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
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
> >
> > FreeBSD src repository
> >
> > Modified files:
> > usr.sbin/sysinstall installUpgrade.c
> > Log:
> > Update the location of the kernel for upgrades.
> >
> > I considered leaving /boot/kernel out of the chflags noschg line, but I
> > seem to remember that there was a period where /boot/kernel was schg, so
> > have left it in for safety's sake.
>
> Does this explain the user report I have that a binary upgrade from
> 6.0 to 6.1 did not update the kernel?
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.
I'll dig around and see if I can see how that might have happened, but I
can't think of anything off the top of my head.
Ceri
--
That must be wonderful! I don't understand it at all.
-- Moliere
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)
iD8DBQFEfqg3ocfcwTS3JF8RAvDUAKCFVTufOwFesAX6OrLfwV1SpNSlSwCghrO9
awMSMURGwUIeJggKw7eYYlU=
=GMLj
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060601084127.GS21998>