Linked by Eugenia Loli on Mon 28th Apr 2003 15:48 UTC
Original OSNews Interviews Today we feature an in-depth interview with three members of FreeBSD's Core (Wes Peters, Greg Lehey and M. Warner Losh) and also a major FreeBSD developer (Scott Long). It is a long read, but we touch a number of hot issues, from the Java port to corporate backing, the Linux competition, the 5.x branch and how it stacks up against the other Unices, UFS2, the possible XFree86 fork, SCO and its Unix IP situation, even re-unification of the BSDs. If you are into (any) Unix, this interview is a must read.
Permalink for comment
To read all comments associated with this story, please click here.
Snotty Comment
by Anonymous on Tue 29th Apr 2003 16:58 UTC

Nope, it's true. Why don't you go to java/jdk14 and do the 'make install'? You will find it out, which ports will not download. Because, you have to go website and agree the license, then download it. Drop the tarballs in the /usr/ports/distfiles/ and do the 'make install'.

Half the time I try that, something messes up, and I end up building from source anyway. Ports isn't all it's cracked up to be. It's nice, but it's far from 100% reliable. When I download a source distro, I do a make install and everything usually works, generally. Not so much with FreeBSD.

There was a distro of Tomcat that included -pthreads in it's build, which caused Apache to freak out. The -pthreads was in there by mistake for the FreeBSD build (there was also -dlinux), which again isn't any fault of the FreeBSD system, rather sloppy packaging.

So Linux source builds tend to go much more smoothly than FreeBSD builds, although that's more of an effect of usage than Linux versus FreeBSD.

I recently was in a situation where we had to upgrade from Java 1.1.8 on FreeBSD to something more, oh, say modern. Why would I run a Linux compatibility mode on a FreeBSD kernel to get 1.4.1 working when I could just run Linux and eliminate the compatibility factor?

That takes an entire layer of things that could go wrong out of the loop. And that is important when you've got developers writing buggy code and when things go wrong they might say "well it's the compatability layer".