There's always the option of fixing the port and learning about the software you're working with too...That's one of my favorite parts about FreeBSD, there are few barriers to getting into the code or makefiles if your install is source based.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
I'm not sure what you're talking about...I'm a FreeBSD user, I compile everything, and it doesn't spew things all over the file system. Unlike linux, man hier is essentially enforced.
I use it all the time. I also use Linux variants.
FreeBSD is really a powerful, well-documented system that brings a lot of stuff to the table that's not possible, not production ready, or simply broken in Linux.
Off the top of my head: standardized networking commands, ZFS (in kernel), GEOM framework, devd, pf firewall is huge, RAID trim support, lagg (link aggregation/hot failover) and CARP (common address redundancy protocol...share IP for multiple servers).
Maybe Linux could use FreeBSD's devd...at least it's documented...
Works great...we even have non-udevd based automount, with custom mount flags...does that still require hacking and a recompile?
How's pulseaudio working out for you?
God forbid I have someone come over for dinner and they're unable to login to my infrastructure switches and peruse the configs!
You're possibly thinking about the classic corewars game?
It seems like the "gadgets" would be just as vulnerable to network profiling and detection.
This could be great for p2p 802.11 links of some kind as well...I wonder if having the beam coherent would have any effect on things like rain and fog effects...