Okay, so what's so great about FreeBSD?

Looking through your list, I want all of them to some degree or another. But they should not be mandatory. If you don't want a GUI you don't need a GUI.
 
To all your replies:

First, let me say thank you all for the intelligent and well-thought out responses.


MG said:
I actually don't know what's so great about FreeBSD. It just feels logical, I think.

@ MG: I definitely can relate to that. I have always had an annoying vague impression of a seemingly random and inconsistent directory structure with other OS's, even knowing very little about them.

drhowarddrfine said:
I didn't notice anyone saying this but, to be sure, FreeBSD is not Linux.

Understood. I'm sure that he (previously mentioned friend) is well aware of this fact, though it *was* an implication in the wording. I can see that this is the primary "pet peeve" for FreeBSD. You must admit that Linux and FreeBSD are much closer cousins than the others. And I don't think "all non-windows OS's are Linux", certainly.

oliverh said:

@Oliverh - Very cool, great article!


jemate18 said:
FreeBSD is one of the GREATEST OS for me...
...
5. Dedicated developers and volunteers..

@jemate18: Dedicated / knowledgeable community - This one seems like an important factor.


fronclynne said:
... my preference for FreeBSD comes down to its non-desktop nature.

Well, to be a bit of a difficult prick here: It seems that the "desktop" nature is really a thing of the choice in window manager, not the OS. If you wanted to, you could run a system entirely from command-line, but ... =)

But I do agree with you. It's one thing of which I have surely come to appreciate the value during my brief venture with Linux already - how much is you really learn by necessity after leaving the Windows "nest".


fronclynne said:
I explicily do not need/want

  • ...
  • dying moose/cat/garden-hose sounds when I start my computer desktop
  • a unified, themed desktop

LOL! Aha hahaa... Yeah... Good ol' Ubuntu.

So -
Reactions:
  • It does sound like FreeBSD has a much steeper learning curve, and requires a lot more knowledge to effectively operate. IE, never going to be a good machine for your mom & pop.
  • It seems that there is serious limitations on access to some applications.
  • It sounds like FreeBSD is *much* smaller in its share of operating systems across the globe than even many linux distributions, and therefore seems like it is going to be very limited in recognition by outside developers.
  • While the FreeBSD community (may) be relatively tiny, it also sounds like there is a stronger community, and perhaps the best quality of knowledge among users, that there is to be found.
  • It sounds like it excels in stability/speed/resource usage moreso than any other OS I've heard about.
  • It sounds like this is not going to be the choice for someone who needs a functional operating system tomorrow.
  • It does sound like this is the OS for someone who perhaps works at a computer, and has the time/inclination for tweaking / customizing.

On target, mostly?
 
fieldse said:
On target, mostly?
Mostly, there are also areas where Linux is nowhere near to FreeBSD sollutions, like sound for example.

On Linux you got ALSA and got problems with OSS apps, now you gos ALSA wich PulseAudio and have problems with PulseAudio, CPU usage, skipping sound, high CPU usage etc.

On FreeBSD you have live in kernel mixing of up to 256 OSS channels, so you can run arts, esound along with pulseaudio without ANY problems or slowdowns.

In short words FreeBSD's implementation is currently the best possible on ALL UNIX (and Linux) systems.
 
Hi:

You have all said good things about the OS. But i would like to express some things I really hate. Why? Well becausse saying what is bad will make it better.

Hardware support is not very good but almost everybody knows that given the M$ pressure to force that.

When the operating system is not properly rebooted it usually corrupts a partition(slice) and when the partition is corrupt it will be unable to fix it during boot unless you reboot in single user mode or if is not the root you forcedly unmount it. And that really sucks. Specially when you have to call the hosting company and request the operation because it can't be done remotely. I beleive the OS should automatically correct that during boot or at least be able to be configured like that. Why have a human do what a computer can do? There is no point.

Versions are dropped too quickly. That's exactly one of the things I hate most about linux. Too quick development is bad. For instance microsoft keeps and mantains operating system versions for at least 2 years (minimal). They bring new stuff but still mantain versions a loong time. That permits persons to learn the new OS and software companies to get their software supported a longer time without spending heavy cash into new debug/development cycle for a new OS. And updates are really very very easy in windows. So maintenace costs are really interesting compared to other operating systems. Something i beleive FreeBSD should learn.
 
halplus said:
When the operating system is not properly rebooted it usually corrupts a partition(slice) and when the partition is corrupt it will be unable to fix it during boot unless you reboot in single user mode or if is not the root you forcedly unmount it. And that really sucks. Specially when you have to call the hosting company and request the operation because it can't be done remotely. I beleive the OS should automatically correct that during boot or at least be able to be configured like that. Why have a human do what a computer can do? There is no point.

There are ways to mitigate this, and to make it so that only extreme errors require human intervention.

Have a look at gjournal(8) which can remove the need for fsck at boot.

Have a look at /etc/defaults/rc.conf for the fsck_y_enable option, which will auto-correct most errors during the automatic fsck at boot.

Have a look at /etc/defaults/rc.conf for the background_fsck option which will take a snapshot of the corrupt filesystem, and run the fsck on that snapshot in the background while the system continues booting.

There's also ZFS, which removes a lot of the above issues. In FreeBSD 8.0, it'll be bootable as well. If you have a problem in ZFS that requires manual intervention, it's usually due to hardware. :)

Versions are dropped too quickly. That's exactly one of the things I hate most about linux. Too quick development is bad. For instance microsoft keeps and mantains operating system versions for at least 2 years (minimal). They bring new stuff but still mantain versions a long time. That permits persons to learn the new OS and software companies to get their software supported a longer time without spending heavy cash into new debug/development cycle for a new OS. And updates are really very very easy in windows. So maintenace costs are really interesting compared to other operating systems. Something i beleive FreeBSD should learn.

Doing some research into this before complaining would be beneficial. :)

Start here. You'll find that everything you wrote above is already done. :)
 
fieldse said:
Reactions:
  • It does sound like FreeBSD has a much steeper learning curve, and requires a lot more knowledge to effectively operate. IE, never going to be a good machine for your mom & pop.

FreeBSD works best for those not afraid of a challenge, those who like to learn new things, and those who don't mind firing up a text editor to configure things. The return on investment for this is that you learn a lot more about how the OS works, and how to fix it when it breaks.

  • It sounds like FreeBSD is *much* smaller in its share of operating systems across the globe than even many linux distributions, and therefore seems like it is going to be very limited in recognition by outside developers.

It all depends on where you look. :) Baraccuda's spam filtering appliances all run FreeBSD under the hood. IronPort's spam filtering appliances all run FreeBSD under the hood. Juniper Networks routers all run FreeBSD under the hood. One of the big managed wireless providers uses FreeBSD under the hood as well, except I can't remember which one, now. There are a lot of devices out there running BSD (whether Free, Open, Net, or DFly).

In the server rooms, as well, there's a large number of FreeBSD boxes out there.

On the desktop, though, FreeBSD isn't known or used nearly as much as RedHat, SuSE, *buntu, Debian, etc.

  • It sounds like this is not going to be the choice for someone who needs a functional operating system tomorrow.
  • It does sound like this is the OS for someone who perhaps works at a computer, and has the time/inclination for tweaking / customizing.

Define "functional". :) You can have a fully functional KDE 4 desktop up and running in a couple of hours (install the base OS from CD, configure networking, pkg_add -r kde4, configure X, and you're done).

Alternatively, one can grab a PC-BSD install CD, and have a working X desktop up and running even quicker. Then you can either use the PC-BSD apps and never even know you are running FreeBSD. Or you can drop to a shell and muck around with the innards just like a normal FreeBSD install.
 
The thing that I like the best about FreeBSD is that it is both unified and liberal at the same time. Features that need to be standardized are just that (like pkg_add), but yet there's still tons of things to choose for yourself. Windows has the standardization but lacks the choice, and Linux has the choice but lacks the standardization (since there are so many distros and every one seems to have their own 'best way' of doing things). FreeBSD takes some time to get used to (even from a Linux background), but once you get the hang of it, you'll wonder how you survived without it. :)
 
I'm a difficult prick: just ask my exes.

fieldse said:
Well, to be a bit of a difficult prick here: It seems that the "desktop" nature is really a thing of the choice in window manager, not the OS. If you wanted to, you could run a system entirely from command-line, but ...
With FreeBSD, you can easily and quickly install KDE, Gnome, XFCE, or whatever you want.

With most of the Linux distros I've tried (excepting Slackware, Gentoo, and Arch) you have to de-install whatever the default tries to stick you with if you don't like it.

I'm not going to argue "better/worse" here, but I know which I prefer.
 
nobody mentioned beastie!! i use it cause it does what i need, run a www server at work, and a development www server at home.
 
I'll start with the down-sides:
1)No wireless drivers for my laptop
2)Network appears slower on 7.2/i386 than it should (though I'm trying to look into what's causing this; but FreeBSD is the only OS I'm having problems with)
3)FreeBSD is ignored by third party application developers (not FreeBSD's fault, but it's a PITA to deal with)


As far as what I like about FreeBSD, it's the polar opposite of Solaris, Vista and (to some degree) Ubuntu in terms of system requirements. I'm running GNOME, a media player, xchat and 5 firefox tabs and yet according to the system monitor all of that only uses 212 megs. My desktop has 2 gigs of ram and I can run a 768 meg Vista virtual machine in VirtualBox and still have ~800 megs left over if I need it.

There aren't any other systems I'm aware of that gives me so much functionality at such little cost.

I have convenient access to the source code for the entire system in /usr/src. Getting the source tree for an entire Linux system is an incredible PITA (ironic given the "free software" mindset of Linux's GNU advocates).

Performance; file operations appear (I say 'appear' b/c I have done no benchmarks) faster under FreeBSD than under Linux.

So, FreeBSD provides a modern desktop experience for very little cost in terms of system resources -that's what brings me back to it.
 
If you will be running *nix desktop(s) AND file servers, with FreeBSD you can comfortably run both. Linux and FreeBSD are sufficiently different that if possible, if you have to manage remote or local file servers *and* run a *nix desktop, it is nice to do both on the same OS.

From a daily usage perspective this shows up mostly in file system hierarchy differences with FreeBSD arguably being far more logical.

Sure, you can use Linux for both. Or Windows. The arguments for or against either are stated already or easily discovered.

But at least you can configure your desktop under FreeBSD; yes, there are the odd driver issues to be aware of but being aware of these before you invest in hardware will save you any grief. Yes, there are a few common apps which either aren't available on FreeBSD or need to be run in Linux mode. But for someone heading down a systems admin path it is likely there are no show stoppers preventing adopting FreeBSD for your desktop OS.

For a file server / application server / database server perspective, I would pick FreeBSD without any hesitiation except for one area:

If you are destined to become a "control panel" user (i.e. to help automate the reselling of shared or other types of internet hosting), think carefully about this. While the scene is changing rapidly of late, many control panel vendors provide either no, or substandard, support for FreeBSD. I do believe this will change. I started down this road when there were few choices and in our case we ended up writing our own code to do the job.

But I would still head down that path again, and I have decent experience with Linux and FreeBSD to make that informed choice. The sorts of issues you commonly run into with specialized internet hosting are a) attacks (pf is a superior firewall to the common Linux solutions) and b) security issues. Jails is a useful tool in this regard. From my perspective the FreeBSD ports system is also superior to the package management solutions on other OS's. I also don't much like the "backporting" which goes on in certain key Linux distributions rather than releasing say OpenSSH as version 5.2 they'll take as patches key changes, maybe all - who knows - and apply them to OpenSSH 4.x. It feels untidy to me, and FreeBSD tends to be a daemon (pun intended) for tidyness.

With FreeBSD 8 offering native Xen guest OS compatibility I expect we'll see more virtual server providers offering FreeBSD and thus more FreeBSD users overall.

No, you wouldn't typically plop down FreeBSD desktops in front of your parents (unless you are live-in technical support) or for a whole school district full of kids (Phoenix can speak to that one) but you would put a FreeBSD file server(s) / router(s) / db server(s) in the shop / basement / school district / parents house to manage a whole swack of Linux desktops for less technical users.

Bottom line: it is a high quality operating system that you won't go wrong with if you are adept at learning new things, and any knowledge you gain will still be eminently useful on other *nix OS's.
 
mwatkins said:
No, you wouldn't plop down FreeBSD desktops in front of your parents (unless you are live-in technical support)

I get so very tired of this line. This grandpa has no issues at all with FreeBSD desktops (I've been using them since the 4.x days) and I need no technical support from the young'uns. It helps, I suppose, that I've used BSD for over 25 years, but it just is not that hard.

And no, I'm not a programmer any more.
 
Irony-in-action quote of the day:

DrJ said:
I get so very tired of this line. This grandpa has no issues at all with FreeBSD desktops (I've been using them since the 4.x days) and I need no technical support from the young'uns. It helps, I suppose, that I've used BSD for over 25 years, but it just is not that hard.

Ya think?

At any rate, I stand by my line.

I'm no whipper-snapper either - closing in on 30 years in the IT industry in one form or another. My kids are not yet at the point where I need to worry or look forward to be called gramps.

I too run BSD on the desktop (although lately I cheat by accessing my dwm workspaces via XMing on Windows - its a handy environment for the work I am doing these days). I know it is not that "hard".

But aside from my own friends who came out of the Unix industry (I worked for Data General myself) who may now be "grandpas", I don't know any personally that would enjoy the mental challenge of adopting an entirely foreign (to them) OS that requires some assembly. Nor do I know any gramps or grannies that I would plunk down a BSD desktop unless I knew they had someone to step in when things inevitably go wrong or they want to know why the latest bridge or bowling tournament software they bought doesn't work.

That isn't so much a comment on BSD or X but on the availability of a helping-hand - be it from a neighbour or from some geek-on-the-go for hire - who will have some Unix experience. The odds do not favour this.

I'm loathe to recommend Windows too but at least there is more likely to be someone who might ride to the rescue for poor ol' gramps. I don't need any more people to support, thus I want gramps to run something that someone near him can support. In this case grandma will look after many of his needs. ;)

Whatever is recommended to these folks has to at least:

a) reliably boot
b) provide some means of rescue if it doesn't, often by someone who will be brought in to do the job for free or for hire, by gramps or grandma who may live in other locations
c) auto-update in some sane manner with security as a prime objective. The net is a dangerous place.
d) run the software they are likely to want/need and deal with the files their buddies will be mailing to them. A typical active gramps might serve as a volunteer somewhere, get meeting minutes or spreadsheets (usually in MS formats), lots of pics from the kids and friends. If they are like mine, they'll be big football fans and watch their alma mater over the internet using a variety of tools, some of which are custom to their school of choice. Granny is keen on doing basic DTP work, churning out cards and function menus and awards and photoshopping her pic collection and playing a number of games to keep mental acuity up; meanwhile gramps is still running FirstChoice in a DOS window because it is the only application he can get his mind around aside from some limited ability with the browser.

You can do most of these things, perhaps all of these things by virtualizing Windows (oh boy, something else to break for poor granny and gramps); and I can do these things too.

But they can't, and the vast majority of elderly folks are going to fall in that grouping as well as 40 and 50 year olds, most of which are barely able to manage their Windows boxen.

Thus unless someone like you or I are willing to configure and manage this setup over the years, I would not recommend a BSD desktop nor even a Linux desktop. Maybe an Ubuntu or PC BSD might change my mind sooner or later, but the ready availability of a helping hand is going to be an issue for *nix on the desktop of the non-professional / non-geek user for some time.
 
mwatkins said:
But aside from my own friends who came out of the Unix industry ... , I don't know any personally that would enjoy the mental challenge of adopting an entirely foreign (to them) OS that requires some assembly.

But this is not age-related -- it deals with technical interests. Scientists or engineers from my era could do it too if they so chose. Some use "alternative" operating systems; most don't want to for the usual reasons, but it that is their choice.

And while computers are much more part of the lives of the younger generation these days, that does not equate with an interest in computers or software guts. My daughter and son-in-law would need support to move from their Macs (and I set up their networking).

If they are like mine, they'll be big football fans and watch their alma mater over the internet ... Granny is keen on doing basic DTP work, churning out cards and function menus and awards and photoshopping her pic collection and playing a number of games to keep mental acuity up ...

Being a grandparent does not mean that one is not working and using computers as a tool in that capacity. Heck, *my* father, who is in his late 80s, still is active in doing new things on the computer (mainly in sophisticated image processing).

I'll stop here and not pull the thread further off topic.
 
halplus said:
And updates are really very very easy in windows. So maintenace costs are really interesting compared to other operating systems. Something i beleive FreeBSD should learn.

I'm still learning the ins and outs, but so far, Microsoft definitely seems easier to update if you don't have Internet access. It might be a nuisance to find the service packs at their site, but you can download on any operating system, burn to disk and sneaker net to your Windows box if it's not connected to the Internet to update. Haven't seen a good equivalent on FreeBSD other than reinstalling a new release on DVD from scratch. I think that would mean rebuilding and recustomizing everything you've installed or changed since the last version of FreeBSD was installed, which could mean a lot of work. If there are good sneaker net solutions for updating a FreeBSD system, I would love to hear them.

The other negative, I just can't seem to get used to the ports/packages system. I've read nothing but good about it, but I'm just not partial to the system. I tried Slackware before trying FreeBSD and it's much more lenient on what it allows you to install. Personally, I'd rather be able to install something that doesn't work, than not be able to install something that does, but that's just my preference. There were something I was trying to install packages for on FreeBSD and it was complaining I needed Python before I could install. They were C/C++ programs that don't need Python to run, so I'm mystified as to why it would be a prerequisite. Maybe it's needed to compile, but I've built the same applications without it. Also, the ports makefiles may be great for the end user, but I haven't seen an easy way for a programmer to automate creation of them. I can automate creation of a SlackBuild script or a mingwport script. If I need to build a lot of programs not in ports, it seems rather time consuming to build and rebuild makefiles until they're just right, when I really just want to get the software built and installed once as quickly as possible and have a way to remove if needed later.

On the plus side, I really prefer the FreeBSD licensing over Microsoft and other Open Source operating systems.

The thing that really sold me on FreeBSD for my laptop was when it was able to play a DVD full screen. It worked fine in Windows ME on the same machine, but I've tried 3 variants of Linux and not one could do the same. I wanted an up-to-date operating system, but one that would still run well on low resources. Both Windows and Linux can't give you both. FreeBSD delivers.
 
DrJ said:
But this is not age-related -- it deals with technical interests.

I buy that.

And I also am selling the point that, demographically speaking, there are few 70 and 80 year olds that had any significant computer experience when they were working and what they have had access to in their retirement has mostly been MS Dos and MS Windows. I suppose I could have qualified my remark and said "I wouldn't normally put a technical desktop in front of granny or grampa" and added "unless they are part of the select group of 0.001% if all septo and octo generians with a suitable level of technical aptitude and interest".

Sure, there are a great many retirees who are now also computer users, hobbyists and more. That changes the context as far as I'm concerned - these are not so much granny or gramps but at least are *possible* technical desktop users, yet demographically speaking I bet I'm on solid ground as assuming this group is largely still not likely to be technical desktop users.
 
mwatkins said:
Irony-in-action quote of the day:



[...]

But they can't, and the vast majority of elderly folks are going to fall in that grouping as well as 40 and 50 year olds, most of which are barely able to manage their Windows boxen.

[...]

That's just wild guess. You don't have any numbers, only the widespread assumption of elderly people barely able to think anymore. I do know many people, even 60 years old, able to cope with Apple, Windows and sometimes Linux and I'm not talking of using a browser or mail, they do really advanced stuff. Maybe exceptions, but then where is the proof to your saying?
 
oliverh said:
That's just wild guess. You don't have any numbers, only the widespread assumption of elderly people barely able to think anymore.

Ah, but that's not the assumption that I am making. The point I'm making relies on observation of computer users in general, a large percentage of which each year run unsecured, infected, exploited because they do not know any better and are not interested - until something untoward happens to them - in changing that status.

True, I did note that users over a certain age have had less exposure computers during their working career than say the current crop of 20 and 30 somethings.

I'm also making an assumption about user tendencies in general, but that is an informed opinion. Having been involved in IT for more than 25 years now, in various roles and levels of responsibility ranging from the bottom rung to the strategic end of the ladder, I have much more than assumptions to go on when it comes to sizing up users or our industry.

We can also extrapolate the experiences witnessed here on forums.freebsd.org and others -- even self acknowledged geeks with some Linux experience, but apparently precious little systems management or X knowledge, frequently get tripped up once they walk away from their self-contained X / desktop package world.

There are a lot of moving parts in an X / graphical desktop environment sitting on *nix. Very few people, as compared to the population at large, will make that journey on their own. There is no supposition involved in making that assertion.

FreeBSD is my OS of choice but I still would not place it on my mother's computer (75, weak computer skills) or my wife's mother's computer (about the same age, fairly strong computer skills but not "system management" skills). My father in law - a geo engineer - nope. First Choice on DOS is his preferred environment. I would not even put a more GUI friendly *nix on their machines because then I'd become the sole support avenue instead of sharing the load with the other rellies, all but one of which in my extended family are Windows users. The amateur astronomer enjoys Linux. Sometimes.

Ensuring there are sufficient support options is a key part of systems management I'm sure you'll agree.
 
It does what I want it to do, without having to do 300 other things. You can install just the minimal stuff to run, or you can install everything including the source code to build the kernel & the environment. This is very nice when customizing an install for whatever reason.

Jails are amazing. I keep my different servers separated but on one host & have no problems.

the Ports/Packages are sweet. building the apps from source or installing the package depending on how big it is & everything makes installing applications very easy & you don't have to surf all over the internet to get the applications. But you can also install from source without using ports, if you really want to.

The ability to only need to be familiar with one OS to be able to have desktop, server, firewall, etc... functionality run well.

The community/documentation is awesome. The online manual(s), man pages, mailing lists, forums, etc... are very helpful & centralized. There isn't a bunch of misinformation floating around, and everyone's (at least most people) are peaceful and willing to help, not flame & troll. Most other OS's/computer information I use a google search instead of searching specific docs or forums, but when there's something with FreeBSD I'm researching, I know where to look, and it saves a lot of time!

That's what's so great about FreeBSD!
 
Perhaps one of the best things about FreeBSD is the Handbook. It covers everything that a new user should learn. Much better than documentation for Linux that I have seen.

I started using FreeBSD around a year ago, and I have learned much more about the internals and other stuff than I have from using M$ Windows. You can say that it's fully customizable. When something goes wrong, check the logs. Much more informative than the error messages that pop up in Windows.

The Ports is something that nearly every FreeBSD user uses. Contains all the software that's needed. It's also separate from the base system, so they're still usable after an upgrade.
 
Here are the things I really enjoy about FreeBSD (these may or may not be part of other systems):

1. Multi-year uptimes. I had an active FreeBSD server online for over 812 days. It was forced offline due to an extended, scheduled power outage. I can't think of a time where one of my FreeBSD servers crashed that wasn't related to hardware. (and for the record, the server mentioned managed mail, web sites, NAT, firewall, DNS, spam scanning, virus scanning, network monitoring, FTP, SSH, squid proxy, file services and more.. every day).

2. Swapping hard drives. New hardware? Ok .. pull a hard drive from the old server, pop it in the new server .. do some minor system reconfig (usually just the network interfaces) and your back up and running. No messy reinstalls, data migrations or other non-sense.

3. PF. I *love* PF. Great firewall, very logical, very easy to manage.

4. Logical layout. I really enjoy having everything on the system so organized and logical. I really enjoy the confidence of knowing how the system operates (I still find myself scratching my head on basic bootup issues with Linux, Windows, and Mac OS X when they occur)

5. Consistency. I can install a port (application) and have a high degree of confidence on knowing where it installed files.

6. Ports. Ports are wonderful. Port auditing, port management, port upgrading, etc. Its great. I believe all of my servers run all their software from the ports system which makes management very centralized.

7. Documentation. I have found so many resources on FreeBSD that I can grok. It seems like other systems either have documentation that is too easy or way too complex. For some reason FreeBSD docs (handbook, books about FreeBSD, blogs, various online resources, etc) just seem to generally resonate with me.

8. Reboots. There is just so much you can do without having to reboot (ie I think everything except possibly setting up a software RAID and loading a new kernel .. and maybe those too).

9. Minimal downtime. I find with FreeBSD, I'm able to address issues very quickly and keep availability very high. For example, the server mentioned in #1 above I *think* had total downtime of *maybe* 8 hours over the course of 5 years... thats 99.99% availability (5 hours of that was the scheduled downtime during the power outage). This is through hardware upgrades, hard drive upgrades, software updates and system updates.

10. Enjoyment. I just enjoy using FreeBSD. Out of all the operating systems I currently use (various flavors of windows, mac os x, linux, solaris), FreeBSD is the only one I really *enjoy* using.
 
A simple example just to put my 2c into the tread. ;) It took me the whole day to set up apache+php+cgi+mysql+mrtg on Solaris (had to get through the perl and cc incompatibilities hell), but I'm sure I can get all these up'n'running under FreeBSD in a 30 mins or so, using nice and beautiful ports system.

@cerulean: ditto what you've said. High five, man. :)
 
Back
Top