Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Sep 2001 17:45:41 +0100
From:      ian j hart <ianjhart@ntlworld.com>
To:        "Russell P. Sutherland" <russ@quist.ca>
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: Upgrading from the source
Message-ID:  <3BB4A935.9E1A685D@ntlworld.com>
References:  <20010927173151.B10009@quist.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
"Russell P. Sutherland" wrote:
> 
> I've attempting to update several FreeBSD 4.2 and 4.3 systems
> remotely to 4.4, by first cvsup'ing the current sources and then
> building the sources. I believe that the install should
> be done from the console in single user mode. (All based on
> the "make world" section of Chapter 19, The Cutting Edge
> from the FreeBSD Handbook)
> 
> A few questions...
> 
> 1. Does make buildworld also build the kernel or
>    does one need to perform a make buildkernel
>    as well
> 
> 2. Do the make installworld, installkernel operations
>    need to be done in single-user mode? I'm thinking
>    of a lightly used system
> 
> 3. Given a neo-phyte at the helm, is the pre-building from
>    source method easier that the upgrade option with the
>    FreeBSD 4.4 CD.
> 
> --
> Quist Consulting                Email: russ@quist.ca
> 219 Donlea Drive                Voice: +1.416.696.7600
> Toronto ON  M4G 2N1             Cell:  +1.416.803.0080
> CANADA                          WWW:   http://www.quist.ca
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message

Remote updates can bite, take care. Always read /usr/src/UPDATING
and the stable list first. eg some net cards now need miibus.

(I'm assuming that you don't have serial console access to these
boxes.) 

As other folk have said the official instructions
(from /usr/src/UPDATING) are

make buildworld
make buildkernel KERNCONF=YOUR_KERNEL_HERE
make installkernel KERNCONF=YOUR_KERNEL_HERE
reboot  (in single user)
make installworld
mergemaster
reboot

If you are remote you don't have any way to select single
user mode and start the network services. hacks > /dev/null :)

You have a number of choices depending on how remote these
boxes are.

Go to the machine and work from the console (safe).
Go to the machine and configure a serial console (complex)
Skip the reboot step and cross your fingers (mostly safe)
Reboot multi-user and cross fingers and toes (not recomended)

If you decide to reboot you should be aware that having
a new kernel with an old world can break network services.

If the boxes really are remote then get a local box with
identical hardware and practice the remote install on that box.

Another useful tip. If these boxes are on your LAN then you don't
need to build the software on each system. Build kernel and world
on one machine and nfs export (ro) /usr/src and /usr/obj. Run
installkernel installworld and mergemaster from the nfs mounted
/usr/src. There are gotcha's with this of course. The mount points
should be the same, as should the contents of /etc/make.conf. Don't
set any special CPU options.

Don't reboot if you do this. Having mount_nfs fail on you is
stressful - I speak from experience. This is what I do, and I've
yet to have any major problems - pilot error excepted :).

HTH

-- 
ian j hart

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BB4A935.9E1A685D>