on the edge

computers & technology, books & writing, civilisation & society, cars & stuff


Greg Black

gjb at gbch dot net
Home page
Blog front page


If you’re not living life on the edge, you’re taking up too much space.


FQE30 at speed



Syndication / Categories

  All
   Announce
   Arts
   Books
   Cars
   Family
   House
   Meta
   People
   Places
   Random
   Society
   Software
   Technology
   Writing



Worthy organisations

Amnesty International Australia — global defenders of human rights

global defenders of human rights


Médecins Sans Frontières — help us save lives around the world

Médecins Sans Frontières - help us save lives around the world


Electronic Frontiers Australia — protecting and promoting on-line civil liberties in Australia

Electronic Frontiers Australia



Blogroll

(Coming soon…)



Software resources


GNU Emacs


blosxom


The FreeBSD Project

Wed, 19 May 2004

Why publicfile?

Several people have asked me why I’m using publicfile rather than, say, apache. Several reasons come to mind:

  • Nearly everything I’ve ever wanted to publish on the Web has been static html, so publicfile has been entirely adequate.
  • When you don’t need the complexity of apache—regardless of your belief in its security—there’s no point in exposing yourself to needless risk.
  • My long-serving gateway box—bambi (a Celeron-366 with adequate memory)—died recently and its duties are being handled by a Pentium-100 that would be hard-pressed to run apache on top of its principal responsibilities.
  • Whether you like Dan Bernstein or not, his software is reliable (even if badly-written) and performs efficiently.

Notwithstanding the above, I will be changing to apache shortly, as I plan to provide some web-based services that will not be possible with publicfile—once I get time to setup felix (the Celeron-2200 box that’s sitting quietly in a corner) as my gateway.