siege wrote: dalecosp: Thanks for the reply as well. I always come across FreeBSD but never really had a good grasp on what it truely was(as im sure i stiull have much to learn about that).
It actually traces its roots back to the "Berkeley System Distributions" of the 1970's, 80's, during which time the UNIX divergence between "SysV" (AT&T's continued development) and "BSD" (U. California/Berkeley's development path) became apparent. So, it differs from Linux in a few ways which might not be noticeable at first, until you start trying to figure out where certain files are supposed to be placed, how to get software to run at startup, etc. For the most part, people who are competent with Linux have little issues with BSD's, and vice versa; sometimes people come from FreeBSD from Linux with amazement at some of the features I've told you about, and sometimes they leave because FreeBSD doesn't always support new hardware or new programs as quickly as the Linux world does (the speed of Linux development, especially in the early years, was simply amazing, and it's not changed much AFAICT).
I have been plaing around with my Mac os X terminal a bit. I use it to FTP and to print directories. The biggest advantage I can see (jjust by what i have used so far) with having a GUI(app really) run an FTP are, drag and drop and automatically switch from passive to active, binary to... well you see! Im not that intimitated by Linux but I see the differences between that and DOS. I really have the need to have this box run Apache , PHP and MySQL and that is why i thought about Linux.
Well, in using the OS X terminal, you are actually using a little piece of FreeBSD: Apple brought in a bunch of people a few years ago (Jordan K. Hubbard, a chief architect and founder of the FreeBSD Project, was one), and put together the "Mach" kernel (developed by Carnegie-Mellon Univ. as a replacement for the BSD kernel, never used by BSD, adapted by Apple) and the "userland" from FreeBSD 4.X (possibly the most 'successful' FreeBSD series to date), to create OS X. In retrospect, it seems a very smart use of "free software" to make a bunch of $$$ for Apple, and I'm guessing that one of the factors in choosing to be BSDish instead of Linuxy was from the legal department after they compared the GPL to the BSD license, but that's quite another story.
As far as installation goes, the FreeBSD magic for MySQL, as an example, is simply:
$ cd /usr/ports/databases/mysql51-server
$ make install clean
after which the tarball is automatically downloaded, extracted, configured, compiled, installed, registered in the package database, and the compile directory is then removed while you're playing WoW, drinking your morning coffee, or e-mailing Mrs. Siege (or a candidate for same ๐ ) Not pretty, to be sure, but not bad for typing a few keystrokes, either. And, although there are ways to install it with a GUI, nobody in BSDland much cares to, because we like coffee and the Mrs. ๐
Does this effect performance? GNOME or KDE desktop configurations?
Fedora and debian seem to be in the race right now... with honorble mention to FreeBSD. I have to research hardward support.
I love hearing everyones 2ยข, so dont hold back
The choice of desktops certainly can affect performance; so much so, that many, maybe even most server administrators don't run their server systems with any desktop environment at all. There are certainly some security advantages to using the "less is more" philosophy, as well. Even if you keep Apache, PHP, and friends "up to date", your X system must be kept up to date as well, or a vulnerability might be exploited if/when they exist.
As for how performance is affected, GNOME and KDE are known as being rather "heavyweight" --- lots of features, require lots of resources. XFCE is a little less so, so it should take up less of a memory footprint, less CPU time, etc. With any Linux, if you decided that your server needed a graphical environment to run browser-based FTP, or whatever, you should also be able to install a really lightweight environment (Fluxbox, or Blackbox, or ??, I guess even "TWM"), and only use GUI apps when necessary. The question is whether you're going to be sitting at the box doing other work, in which case, I'd contend it's not really a "server" anyway, although it might be a great environment for development (it's what I do with FreeBSD, sometimes --- really, my box is a true "jack of all trades") and could maybe be called a "workstation/server".