Date: Mon, 15 Oct 2001 17:33:27 -0400 From: Louis LeBlanc <leblanc+freebsd@acadia.ne.mediaone.net> To: freebsd-questions@freebsd.org Subject: Re: Upgrading to 4.4 Message-ID: <20011015173327.E4944@acadia.ne.mediaone.net> In-Reply-To: <20011015222132.B36840@drex.staff.izr.com> References: <Pine.OSF.3.95.1011015143523.11638F-100000@isua5.iastate.edu> <20011015154852.D4944@acadia.ne.mediaone.net> <20011015222132.B36840@drex.staff.izr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/15/01 10:21 PM, Mark Drayton sat at the `puter and typed: > Louis LeBlanc (leblanc+freebsd@acadia.ne.mediaone.net) wrote: > > On 10/15/01 02:37 PM, legg@iastate.edu sat at the `puter and typed: > > > [upgrading using cvsup] > > > > You don't have to be a developer to use cvsup. Just cvsup to > > RELENG_4_4_0_RELEASE, then use the following: > > cd /usr/src > > make buildworld && make install > > > > Which will upgrade your userland. Once this is done, you should do > > this: > > > > mergemaster -ia > > > > which will merge config/startup/etc. files from the upgraded source to > > the installed versions. Then reboot. > > > > Next, you will want to rebuild your kernel. If you have a custom > > kernel, use that, otherwise use GENERIC. > > > > cd /usr/src make buildkernel KERNEL=GENERIC && make installkernel > > KERNEL=GENERIC > > > > Of course if you do use GENERIC, you can leave out the KERNEL > > parameters. Once this is done, reboot. > > > > Now, you are running 4.4 release. And not one line of code had to be > > touched :) > > Sorry to be finicky, but this is potentially a very dangerous way of > upgrading. IMHO the safest way is follows: > > make buildworld > make buildkernel > make installkernel > (reboot) > make installworld > mergemaster > (reboot) Actually, you really should installworld before building the kernel. I have never had trouble with this, and this follows the suggestions I have seen on this list in the last 2 or 3 months. That is how I upgraded from 4.3 to 4.4 with not a single hitch, hangup, or hesitation. > You should build a new kernel then reboot to ensure the new kernel > works. It's easy to recover from a broken kernel but not from a system > that won't work because the world is too new for the kernel (which could > happen if you install world before kernel). That is what my suggestion does. If you use the command: make buildworld && make installworld The second part will only happen if the first succeeds. You can continue that to: make buildworld && make installworld && reboot with the same effect. If the build fails, the install won't happen. If the install fails, there will be no reboot. You ever sit and watch the screen while buildworld went on? Talk about a cure for insomnia. > When you know the new kernel is okay you can get on with installing the > new world and mergemastering. And how would you tell if your kernel is ok other than a successful build and a reboot? Like I said, the '&&' says if that one succeeded, to this. Mergemaster may be required to boot the new kernel if there are some new config or default files. Better to do that before rebooting the kernel. Cheers, Lou -- Louis LeBlanc leblanc@acadia.ne.mediaone.net Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://acadia.ne.mediaone.net ԿԬ Time is an illusion perpetrated by the manufacturers of space. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011015173327.E4944>