Linked by Tony Bourke on Thu 29th Apr 2004 19:08 UTC
OpenBSD OpenBSD is a name synonymous with security, having earned the respect and adoration of security-concious sysadmins everywhere. OpenBSD is used in data centers all over the world, is the basis for several security products (from OpenBSD's site), and is even the basis for Microsoft's Services For Unix.
Permalink for comment
To read all comments associated with this story, please click here.
coolvibe
by TonyB on Sat 1st May 2004 08:34 UTC

If you read the article, you'd see that I used the ports version of PostgreSQL, but it died with the same error as my own compiled version. ;)

Also, the OpenBSD ports collection does not include MySQL 4.0, nor does the packages. It only includes MySQl 3.x. Perhaps 3.5 has added MySQL 4.0, I haven't checked since it was released only a few hours ago.

I prefer to compile by source for many applications, especially when comparing performance between various operating systems. I can keep the software version the same, and the build environment the same. When switching from one operating system to another, it's a great way.

Generally I don't have any problems with compiling by source on x86 systems. For non-x86, such as SPARC64, there are some pieces that don't work with basic source, and in that case I'll fall back to ports or packages. Sometimes it fixes the issue, sometimes it doesn't.

Another reason to use ports is with applications that are particularly cumbersome and/or time consuming to compile. An example would be KDE or Gnome. If it's something simple like tcsh, I'll happily use a package.

But for MySQL, PostgreSQL, Apache, OpenSSH, etc. I prefer compiling from source whenever I can. Packages and Ports are convienient and can solve problems (but not always), but aren't a total replacement. That'd be rather silly if it was.