Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 7 Mar 2000 16:08:51 -0800
From:      Brooks Davis <brooks@one-eyed-alien.net>
To:        Warner Losh <imp@village.org>
Cc:        Nik Clayton <nik@FreeBSD.ORG>, current@FreeBSD.ORG
Subject:   Re: Alternative way to do -stable to -current upgrade
Message-ID:  <20000307160851.A27814@orion.ac.hmc.edu>
In-Reply-To: <200003072349.QAA97583@harmony.village.org>; from imp@village.org on Tue, Mar 07, 2000 at 04:49:06PM -0700
References:  <20000307114400.A27909@orion.ac.hmc.edu> <20000305202435.A39101@catkin.nothing-going-on.org> <20000307110109.A52023@catkin.nothing-going-on.org> <20000307101957.A5565@orion.ac.hmc.edu> <20000307191442.B19024@catkin.nothing-going-on.org> <20000307114400.A27909@orion.ac.hmc.edu> <200003072349.QAA97583@harmony.village.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 07, 2000 at 04:49:06PM -0700, Warner Losh wrote:
> In message <20000307114400.A27909@orion.ac.hmc.edu> Brooks Davis writes:
> : You don't need to update /dev though.  As long as you don't change
> : anything else, a 4.0 kernel will work just fine with a 3.x /dev and
> : userland (other then top and friends).  You can delay updating /dev
> : until later as the ata code will deal with wd devices as well as ad
> : devices.  
> 
> This is incorrect information.  If you ever have a dirty filesystem,
> the new fsck will not be able to fix that and you'll be unable to
> mount that filesystem w/o reboot, iirc.

I haddn't realized that.

> : I built my current laptop configuration by installing 3.3 from
> : CD, cvsuping to 4.0, installing a new kernel, and then building and
> : installing world.  I looked at UPDATING.  I think it's wrong.  It should
> : have you test a new kernel before rebuilding /dev.  You should do it,
> : but like the scsi disk renaming it isn't mandatory, at least for now.
> : I think the problem is that UPDATING is a bit to optomistic about
> : things.  If you have a system that works with the new ata driver it's
> : correct, but otherwise it's a good way to waste your system. :-(
> 
> Alternative, accurate, text welcome :-)

Here's a diff.  It requires one more reboot, but it avoids backing
yourself into a corner.  A crash between reboots is a little messy, but
if you only follow these directions that's not very likely.  The
directions are good, but just assume support is identical and I can
think of at least one case where that's not true (defective IDE
controlers).

-- Brooks

Index: UPDATING
===================================================================
RCS file: /home/ncvs/src/UPDATING,v
retrieving revision 1.71
diff -u -r1.71 UPDATING
--- UPDATING	2000/02/23 05:51:02	1.71
+++ UPDATING	2000/03/07 23:58:09
@@ -624,9 +624,11 @@
 	--------------------------------
 	cd /usr/src
 	make buildworld
+	<follow directions to build/install a kernel>
+	reboot
+	<if reboot fails, revert to working kernel and debug>
 	cd sbin/mknod
 	make install
-	<follow directions to build/install a kernel>
 	<follow rebuild disk /dev entries above>	[*]
 	reboot
 	<in single user>

-- 
Any statement of the form "X is the one, true Y" is FALSE.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




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