Linked by Nathan Mace on Tue 19th Mar 2002 17:21 UTC
FreeBSD Most tech savvy geeks can work their way through a FreeBSD install, even if they have no prior UNIX experience. However installing an OS and configuring an OS are two totally different things. This article is targeted towards anyone who might be wondering about FreeBSD, but doesn't know what to do with it after they install it. This isn't then end-all be-all of FreeBSD howto's. Just some of the simple stuff. Update: Some of the readers of OSNews have emailed me concerning corrections that need to be made in this article. Dig in (third page) for more.
Permalink for comment
To read all comments associated with this story, please click here.
Nice article but a few corrections needed
by Anonymous on Wed 20th Mar 2002 13:05 UTC

This is certainly something that needed an article written about. Newbies very often show up after installing their new systems and wonder what to do next, and especially how to upgrade. Nice work.
However, slightly wrong information just adds to the general level of confusion and sometimes gets people in trouble, then they decide they hate FreeBSD because something didn't work for them.
The recommended way to build a new world and kernel is this:
To update from 4.0-RELEASE or later to the most current
4.x-STABLE
----------
make buildworld
make buildkernel KERNCONF=YOUR_KERNEL_HERE
make installkernel KERNCONF=YOUR_KERNEL_HERE
reboot (in single user)
make installworld
mergemaster
reboot
(Taken straight from /usr/src/UPDATING, which is required reading for upgraders.) Doing as you wrote will work most of the time but this way is supposed to work *all* of the time (and if you do it some other way and have trouble, people will just tell you to do it again this way).

The easiest and most effective way to upgrade ports is this:
cvsup [supfile]
portsdb -Uu
portupgrade -a

portsdb in this usage updates the ports INDEX file so that you don't have to wait for a new one to have portupgrade see that there are new ports. (It also takes a while; 10 min on a K7-1.33G and 1 hr on a P-166. Not to mention that you can't cut some of the ports out easily if you do this because make_index will complain about it.)
The -a flag to portupgrade means "all", it will just upgrade everything that needs it, keeping dependencies straight and doing no more than necessary. (Great utility, absolutely. Many thanks to Akinori MUSHA-san, the author of the portupgrade suite.)

It may also be useful to use the -s flag to cvsup (for both ports and sources), depending on whether you like to muck around with the files you download. See cvsup's man page for details.