Debian vs. FreeBSD as a Web Serving Platform, Part 1

Debian vs. FreeBSD as a Web Serving Platform, Part 1

Posted Feb 24, 2005 17:36 UTC (Thu) by tzafrir (subscriber, #11501)
In reply to: Debian vs. FreeBSD as a Web Serving Platform, Part 1 by vonbrand
Parent article: Debian vs. FreeBSD as a Web Serving Platform, Part 1

Again, in the context where it was written:

> This is in sharp contrast with FreeBSD where
> only the base system, often referred to as
> kernel and userland, is kept in a constant
> state (with the only exception being security
> updates), while the included applications,
> or ports in FreeBSD's language, are
> continuously updated. This being so, a system
> administrator can choose to keep upgrading all
> important ports to their current stable
> versions and take advantage of any new
> features in them. This is a very pleasant
> aspect of FreeBSD - instead of an endless
> wait one might endure before a new stable
> Debian release, the administrator running
> FreeBSD can upgrade all installed ports to
> their latest versions at any time, independently
> on the base system.

Basically either use Stable+backports or Unstable to get basicalyl the same effect.

BTW: I'd like to see some comparison of the apache configuration in both distros. The Debian mainjtainers of the package bothered doing the extra work to automate as many tasks as possible. e.g.: almost all modules are disabled in the default apache config. There is an extra utility to "enable" modules (and virtual hosts, for apache2).

---

(Log in to post comments)