Building a server with FreeBSD 7

Building a Server with FreeBSD 7No Starch Press has released its eagerly awaited Building a Server with FreeBSD 7

This modular guide to building a FreeBSD server is has been written to make it easy for (new) users to choose the packages that they need, with step-by-step directions for installation and configuration.

The book’s modules cover topics like:

  • Running common FreeBSD admin commands and tasks.
  • Managing the FreeBSD ports collection.
  • Installing third-party apps like Apache, Courier-IMAP, SpamAssassin, CUPS, Cyrus SASL, MediaWiki, and WordPress.
  • Setting up MySQL, NTP, ISC DHCP, ISC BIND DNS, PHP, OpenLDAP, OpenSSH, OpenSSL, and OpenVPN.
  • Appendixes explain user management, backup/restore, and network protocols. Building a Server with FreeBSD 7 will have readers running their own server loaded with useful modules in no time, with a minimum of hassle.

The most difficult part of building a server with FreeBSD, the Unix-like operating system, is arguably software installation and configuration. Finding the software is easy enough; getting everything up and running is another thing entirely. The only option for many people has been to hire a consultant.Building a Server with FreeBSD 7 is for those of us who prefer to build our own server. If you’re a small business owner looking for a reliable email server, a curious Windows administrator, or if you just want to put that old computer in the closet to work, you’ll learn how to get things up and running quickly. Then, once you have a working system, you can experiment, extend, and customize as you please.

You’ll learn how to install FreeBSD, then how to install popular server applications with the ports collection. Each package is treated as an independent module, so you can dip into the book at any point to install just the packages you need, when you need them.

Check amazon for the cheapest copies

Innotek looking for FreeBSD devs

virtual box for freebsdInnotek, developer of the virtualisation software VirtualBox, which was recently acquired by Sun, is looking for developers to help porting this promising product to FreeBSD

Very basic porting work has been done on a voluntary basis by one of my colleagues. We actually hope some developers from the FreeBSD community will pick up where we left off and complete the port.

If interested, there is a developer’s mailing list, IRC channel and forums for any questions – check out the community page.

FreeBSD KDE’s 4.0.3 update in progress

Martin Wilke has posted an update today on the progress of the porting of KDE 4.0 to FreeBSD

Right now I have some free time to update KDE4. Today i’ve committed the 5 Basic Ports (kdelibs4/base4/pimlib/runtime/workspace) with the implementation of bsd.kde4.mk. This allows further use of USE_KDE4 (actually, kdelibs, kdebase and pimlibs) for KDE4-related builds. Now I have to work on the implementation of all other related ports.

FreeBSD 5.5, 6.1, and 6.2

On May 31st, FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 5.5 is the last remaining supported release from the FreeBSD 5.x stable branch, support for the FreeBSD 5.x stable branch will also cease at the same point. Users of any of these FreeBSD releases are strongly encouraged to upgrade to either FreeBSD 6.3 or FreeBSD 7.0 before that date.

Please note that the End of Life dates for FreeBSD 5.5 and FreeBSD 6.1 were announced in May 2006; and the End of Life for FreeBSD 6.2, which was originally announced as January 31, 2008, has been extended by four months in order to allow time for users to upgrade.

The FreeBSD Ports Management Team wishes to inform users that May 31st (the security team’s End-Of-Support date for FreeBSD 5.x) will also be the end of support for the Ports Collection on both 5.5-RELEASE and the 5-STABLE branch. Neither the infrastructure nor individual ports are guaranteed to work on these FreeBSD versions after that date. A CVS tag will be created for users who cannot upgrade for some reason; as of that commit, these users are advised to stop tracking the latest ports CVS repository and instead stay with the version as of that tag.

Source & more info (01-04-2008)