Date: Sun, 11 Jan 2009 22:40:07 -0800 From: "Kevin Oberman" <oberman@es.net> To: Andrei Kolu <antik@bsd.ee> Cc: Mike Lempriere <mike@vintners.net>, freebsd-stable@FreeBSD.ORG, freebsd@byshenk.net Subject: Re: mergemaster broken -- take 2 Message-ID: <20090112064007.8463E1CC0B@ptavv.es.net> In-Reply-To: Your message of "Mon, 12 Jan 2009 08:22:40 %2B0200." <496AE1AF.9060104@bsd.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1231742407_89602P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Mon, 12 Jan 2009 08:22:40 +0200 > From: Andrei Kolu <antik@bsd.ee> > Sender: owner-freebsd-stable@freebsd.org > > Mike Lempriere wrote: > > Thanks everyone for the advice -- I got it working this time just > > fine. Works much better when one follows the directions accurately > > instead of by memory -- the bottom line is that this time I remembered > > to jot down the commands before heading downtown to the machine rack > > room where there's no browser access... I started over and followed > > UPDATING: > > cd /usr/obj > > rm -R * > > cd /usr/src > > rm -R * > > cvsup -g -L 2 -h cvsup10.freebsd.org |& tee /root/cvsup-090108.out > > make buildworld |& tee /root/make-buildworld-090108.out > > make kernel KERNCONF=GENERIC |& tee /root/make-kernel-090108.out > > users > > ps ax | more > > shutdown -r now > You can go into single user without rebooting just by issuing command: > > # shutdown now > > NOTE: Network access will be shut down also, so you should be on your > console then. Did you even bother reading Oliver's explanation as to why it's a very bad idea. The official upgrade procedure can be modified if you know EXACTLY what you are doing, but it is unwise to suggest that you can go ahead without adequate knowledge of the risks. Please don't suggest skipping the reboot. Feel free to do so yourself, but don't expect much sympathy when an upgrade blows up and a system is down for several hours while you clean up the mess. > >> It _is_ necessary. If you don't reboot, you're still running > >> the old kernel which might not be able to support new binaries > >> and libraries that installworld will install on your system. > >> > >> For example, there may be new syscalls that the new binaries > >> will try to use, but the old kernel doesn't know about them. > >> It doesn't happen often, so you can get away without rebooting > >> most of the time. But it's risky, especially when updating > >> across major versions. So the recommendation is to always > >> reboot after installing the new kernel and before performing > >> the "installworld". > >> > >> It's also important that "installworld" is the last step > >> (except for mergemaster), because this is the point of no > >> return. As long as you still have the old userland (world), > >> you can still boot the old kernel and everything is fine. > >> You can start all over froms cratch, if necessary. > >> But as soon as you have started "installworld", your system > >> will not be able to work with the old kernel anymore. > >> > >> And remember: Always make a backup before you start to > >> update. And verify that the backup works. Better safe > >> than sorry. > >> > >> Best regards > >> Oliver > >> > >> > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > --==_Exmh_1231742407_89602P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFJauXHkn3rs5h7N1ERAgbHAJwNL12u4Thb6KBsdXs8Ay1KSTjQtgCdH+of O10gVZ2J6mJR5UEzhzRiksA= =Ok7x -----END PGP SIGNATURE----- --==_Exmh_1231742407_89602P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090112064007.8463E1CC0B>