I picked this one up while collecting information on how to install FreeBSD for desktop use at home. As I found it is certainly possible. If the default install of PC-BSD with its full KDE4 installation is too bloated for you, consider reading this. It was originally written for and published on kompasmedia.nl.
The site has been down for a longer period of time and I would hate for this guide that is so easy to follow for newer users interested in the subject to get lost. It was linked on freebsdnews. If you're new to trying FreeBSD on your desktop - enjoy.
Saying that FreeBSD is an excellent choice to build a server upon would be stating the blatantly obvious. Sadly though, FreeBSD as a desktop OS is a much less common sight. This is a shame, particularly for developers who could have a desktop that closely mimics the configuration of FreeBSD servers in a remote datacenter. Very useful if you need to test things locally!
Since FreeBSD is a UNIX-like OS like Linux, just about all the software you can get for Linux is also available for FreeBSD. Significant exceptions are parts that are very closely linked to the OS kernel. Hardware support differs between OS'es so make sure you check the Hardware Notes that accompany every FreeBSD release to make sure your system is compatible.
To ensure long-term productivity using FreeBSD it would be very wise to use the integrated software management tools. They prevent a lot of problems with dependencies between software packages when it's time to upgrade parts of your system.
FreeBSD allows you to go about package management in two ways: binary packages and ports. Binary packages are completely pre-built installable versions of software. Ports, on the other hand, make use of the original source code of the software to build a tailor-made version of the package completely optimized for your particular system.
Binary packages have one major advantage: speed. They're really easy and fast to install. Ports are much more flexible though, and they usually are closer to the bleeding edge of development. Many ports present you with a configuration menu prior to installation. Using this you can customize the way the software gets built. Binary packages don't allow this flexibility and come with a generic default configuration set.
Best of both worlds
Fortunately you don't have to commit to either one of the mechanisms. For example, setting up a working base system is really fast when you use packages. You can then upgrade your system to the absolute bleeding edge using ports from a terminal session that runs in the background while you get on with some real work.
This article assumes we're building a system completely based on ports, even if installing them takes more time. For a desktop system having the very latest software can be a major improvement. First we'll pull in some tools to make life a little easier on our bare FreeBSD system (install the 'Developer' set without the ports collection).
#portsnap fetchThese commands fetch the current ports collection and store it in /usr/ports. In theory this is enough to get started using ports. However, the use of the ports collection becomes a whole lot easier thanks to tools like portupgrade, a collection of useful tools to automate much of the ports management.
To prevent a lengthy build of the Ruby programming language we'll cheat just this once and get a working portupgrade toolkit from binary packages:
#pkg_add -r portupgrade
Now that portupgrade is present on the system we only need three commands to install a complete GNOME desktop environment on the system. Like so:
#portinstall -rR xorg
#portinstall -rR gnome2
#portinstall -rR gdm
The 'gnome2' and 'xorg' ports are metaports. A metaport doesn't contain any software itself, it only points towards all the parts needed to assemble a larger collection. A desktop environment like GNOME consists of hundreds of components. Each of these is installed separately. The main advantage of this is the fact that each component can be upgraded or replaced individually without needing to replace the whole desktop environment. The above three commands take hours on a fast systems and may take days on older hardware. Do make sure you have the time for such an operation.
If this takes too long, you can also fetch part of your software from binary packages using the 'P' option with portupgrade. The above commands would change to:
#portinstall -rRP xorg
Any component that is available as a binary package in the correct version will now use the package instead of build from source code.
If your system is part of a group of systems that will all get the same configuration, you can use portupgrade to generate binary packages for the other systems so that they won't have to repeat the lengthy build process.
It's not uncommon to find a single system that builds packages from ports for use on the actual production systems. This prevents a surplus of development packages on your production systems. They may be needed to be able to build your software, but they're not required for running it. Automatically building packages, which get stored in /usr/local/ports/packages/All, works with the 'p' option to portupgrade:
#portinstall -rRp xorg
#portinstall -rRp gnome2
#portinstall -rRp gdm
When all ports are done installing, it's time for some configuring. Our goal is a system that boots into a graphical login screen and from there into the GNOME desktop environment.
The days of hand-crafted X11 configurations are long gone. On almost any system you'll only need a single command, as root:
This provides you with a new config file in /root. The above command returns information you can use to test your new config file. If everything goes well (ctrl-alt-backspace shuts down the X11 test session), you should move the file to /etc/X11/xorg.conf.
Now /etc/rc.conf needs a few finishing touches to fully support the GNOME desktop environment:
gdm_enable = "YES"
dbus_enable= " YES"
hal_enable = "YES"
If all went as it should, you'll reboot into a graphical environment that has quite a bit of software ready for you to use.
Stay current using ports
The ports collection is an excellent way to keep the software on your FreeBSD workstation fresh. Maintaining a current ports tree became a snap with the introduction of the portsnap tool.
Apart from the first time using portsnap is practically always the same. You can update your ports tree with:
portsnap fetch && portsnap update
Then you should check if the new ports collection has any upgrades available to software already on your system:
pkg_version -v | grep '<'
This gives you a list of packages for which a newer version is available in the ports tree:
This command not only upgrades your software but also checks all dependencies. The 'p' in the command line makes portupgrade build binary packages of your upgrades. Most of the time this isn't needed and you can freely leave the 'p' off your command line.
Date posted: 20 August 2010, with thanks. First published 17 November 2008 on http://www.kompasmedia.nl/en/linuxunix/freebsd-als-desktop-os.html.