Upgrade instructions are incorrect
Hi!
The upgrade instructions found in src/UPDATING and src/Makefile.inc1
are not quite correct. Suggesting to reboot with the new kernel and
non-matching userland is safer than opposite of course, but does not
always work nor guaranteed to work at all. Here's the safest version
I could think of; it ensures everything is installed using the tools
compatible with the currently running kernel. I'd like your comments
guys as you were touching these instructions in the past.
%%%
Index: UPDATING
===
RCS file: /home/ncvs/src/UPDATING,v
retrieving revision 1.208
diff -u -r1.208 UPDATING
--- UPDATING20 May 2002 13:06:24 - 1.208
+++ UPDATING22 May 2002 15:45:49 -
@@ -958,10 +958,10 @@
make buildkernel KERNCONF=YOUR_KERNEL_HERE
cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
make installkernel KERNCONF=YOUR_KERNEL_HERE
- reboot in single user [3]
+ shutdown in single user [3]
mergemaster -p [5]
- make installworld
mergemaster [4]
+ make installworld
[1]
reboot
@@ -985,14 +985,17 @@
your own device.hints to reflect your unique hardware
configuration.
- [3] From the bootblocks, boot -s, and then do
+ [3] Do not reboot with the new kernel as your installed
+ binaries may be incompatible with it. Instead, shutdown
+ or reboot with the old kernel in single user mode. If
+ rebooted, from the bootblocks, boot -s, and then do
fsck -p
mount -u /
mount -a
cd /usr/src
adjkerntz -i# if CMOS is wall time
Also, when doing a major release upgrade, it is required that
- you boot into single user mode to do the installworld.
+ you operate in single user mode to do the installworld.
[4] Note: This step is non-optional. Failure to do this step
can result in a significant reduction in the functionality of the
Index: Makefile
===
RCS file: /home/ncvs/src/Makefile,v
retrieving revision 1.256
diff -u -r1.256 Makefile
--- Makefile12 May 2002 16:00:43 - 1.256
+++ Makefile22 May 2002 15:45:49 -
@@ -48,10 +48,10 @@
# 2. `make buildworld'
# 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC).
# 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC).
-# 5. `reboot'(in single user mode: boot -s from the loader prompt).
+# 5. `shutdown' or `reboot' into single user mode with the old kernel.
# 6. `mergemaster -p'
-# 7. `make installworld'
-# 8. `mergemaster'
+# 7. `mergemaster'
+# 8. `make installworld'
# 9. `reboot'
#
# See src/UPDATING `COMMON ITEMS' for more complete information.
%%%
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software AG,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.512.251Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
msg38687/pgp0.pgp
Description: PGP signature
RE: Upgrade instructions are incorrect
On 22-May-2002 Ruslan Ermilov wrote: Hi! The upgrade instructions found in src/UPDATING and src/Makefile.inc1 are not quite correct. Suggesting to reboot with the new kernel and non-matching userland is safer than opposite of course, but does not always work nor guaranteed to work at all. Here's the safest version I could think of; it ensures everything is installed using the tools compatible with the currently running kernel. I'd like your comments guys as you were touching these instructions in the past. Wrong. If you are following the proper upgrade path, then your old binaries will always work with your new kernel. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Upgrade instructions are incorrect
On Wed, May 22, 2002 at 01:05:48PM -0400, John Baldwin wrote: Wrong. If you are following the proper upgrade path, then your old binaries will always work with your new kernel. Can I ask you what the proper upgrade path is? In /usr/src/UPDATING : To rebuild everything and install it on the current system. --- make world Build a new kernel, see above. In handbook: make buildworld make buildkernel make installkernel reboot into single use mode make installworld ... Although the world target still exists, you are strongly encouraged not to use it. I thing that are two different ways, aren't they? Which one is right? I'm naturally speaking about upgrading of the -current system, the way of upgrading from 4.X is similar in both documents. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Upgrade instructions are incorrect
This seems exactly backwards. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Upgrade instructions are incorrect
- Original Message - From: M. Warner Losh [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, May 22, 2002 2:04 PM Subject: Re: Upgrade instructions are incorrect This seems exactly backwards. Warner Unlike replying to something without including a shred of context, to half-a-dozen addresses including a mail list, to which all the other recipients are probably subscribed anyways. Brian K. White -- [EMAIL PROTECTED] -- http://www.aljex.com/bkw/ +[+++[-]-]+..+.+++.-.[+---]++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Upgrade instructions are incorrect
At 7:02 PM +0300 5/22/02, Ruslan Ermilov wrote: The upgrade instructions found in src/UPDATING and src/Makefile.inc1 are not quite correct. Suggesting to reboot with the new kernel and non-matching userland is safer than opposite of course, but does not always work nor guaranteed to work at all. If you only boot into single-user mode (so you're not running all the daemons), then what programs would not work? So far I have never run into any problems. I should admit I'm generally less than a month out-of-date when I do a new buildworld, so not all that much has changed. I know that programs like 'ps' or 'top' will produce the wrong results, of course, but I would not expect any catastrophic problems should happen. Much more important, to me, is to catch the cases where the new kernel does *not* work, and I definitely have run into those cases. When a problem like that happens, at the time I find out about the it, the only change I have made is to install the new kernel. At that point it is pretty easy to back out of the problem. If I do the installworld before booting up off a new kernel, then I would definitely be in trouble when I realize the new kernel does not work on my hardware. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Upgrade instructions are incorrect
On Wed, May 22, 2002 at 01:05:48PM -0400, John Baldwin wrote: On 22-May-2002 Ruslan Ermilov wrote: Hi! The upgrade instructions found in src/UPDATING and src/Makefile.inc1 are not quite correct. Suggesting to reboot with the new kernel and non-matching userland is safer than opposite of course, but does not always work nor guaranteed to work at all. Here's the safest version I could think of; it ensures everything is installed using the tools compatible with the currently running kernel. I'd like your comments guys as you were touching these instructions in the past. Wrong. If you are following the proper upgrade path, then your old binaries will always work with your new kernel. Grr, right, was smoking a crack. 4.0-R binaries work just fine with the 4.6-RC kernel, and the current technique has a nicety of verifying that the new kernel works before giving you a chance to shoot yourself in a foot. Sorry for the false alarm. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg38710/pgp0.pgp Description: PGP signature
