Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Jun 2006 11:18:37 -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:  <20060601151837.GA32439@xor.obsecurity.org>
In-Reply-To: <20060601084127.GS21998@submonkey.net>
References:  <200605311915.k4VJFKef060742@repoman.freebsd.org> <20060601012130.GA5066@xor.obsecurity.org> <20060601084127.GS21998@submonkey.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--ReaqsoxgOBHFXBhH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 line, b=
ut I
> > >   seem to remember that there was a period where /boot/kernel was sch=
g, 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, but I
> can't think of anything off the top of my head.

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.

Kris

--ReaqsoxgOBHFXBhH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFEfwVMWry0BWjoQKURAhmCAKDuAEa52r03wCtaeuiPPgyve3VnaQCgggqM
Ol5jlmVnyAmIlkDSxw2eiLw=
=1jyD
-----END PGP SIGNATURE-----

--ReaqsoxgOBHFXBhH--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060601151837.GA32439>