On Fri, Jun 02, 2006 at 03:02:52PM -0400, Kris Kennaway wrote: > 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 > > > > > > > > > > > > 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. > > > > > > 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. > > > > 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.
I'll mess about and try to reproduce it, thanks.
Ceri
--
That must be wonderful! I don't understand it at all.
-- Moliere
pgp5iMI8bSbNc.pgp
Description: PGP signature
