3 out of the top 4 most reliable hosting companies run, yes, FreeBSD.
Check Netcraft’s report for full details.
I built a 1.3TB freeNAS box a while back. I used 4 x 250GB drives in one array, and 3 x 120GB drives in the 2nd array, with an old 80GB for the freeNAS OS.
The case and IDE controller card was purchased for the project, but the PSU, mobo etc, and all the drives were stuff I had laying around.
It’s an old Gigabyte board with an AMD Athlon XP 2600+ running at 1919 MHz, plus 1.5GB of RAM (which is stupid over-powered for a freeNAS box, but hey, it was left over stuff). On the upside, the system is *never* sweating for CPU power. It’s got a built in 10/100 NIC. There’s a video card in there, but only because the thing won’t boot w/out a video card in the slot.
The OS is freeNAS 0.684b, which I’m pretty happy with. This thread isn’t about setting it up, but that’s not really hard to do. If this board would have booted off USB (which I just could NOT get it to do) the freeNAS OS would have been running of a 64MB USB flash drive I had lying about. Since the thing wouldn’t boot of USB, I threw in an 80GB drive and ran the OS off that.
Roughly 34MB of the drive is in use, lol….
Anyway. I stuffed 1.3TB of drives in there, and then created 2 separate RAID 5 arrays. The reason for that is that freeNAS can use different size drives in one array, but it’ll pick the smallest to set the stripe size with, and you end up with 7 x 120GB drives instead of 3 120’s and 4 250’s (because it pretends the 250’s are 120’s, which is a huge waste).
The third beta release of m0n0wall 1.3, a FreeBSD-based firewall, is now available for download.
From the changelog:
added voucher support to captive portal (mwiget); wireless LAN improvements; allow dashes in alias names; added hidden option to disable auto-generation of PPTP rules on WAN; fixed ATA hard disk spin down feature; ipfilter TCP window scaling bug fix; synced with changes from 1.23 branch; increased mfsroot size to 14 MB (from 13 MB); updated base system to FreeBSD 6.2-RELEASE-p6; updated PHP to 4.4.7, ipsec-tools to 0.6.7, isc-dhcpd to 3.0.5, Dnsmasq to 2.39; added kernel patch for fragment bug in ipfilter; modified kernel patch to handle ipnat+dummynet in ip_input….
Check the changelog for full details
Have you ever wasted too much time online? Right, so posting this on my blog imparts some selection bias to the answers to that question. But have you really wasted time to the point of not getting work done, or letting other things fall by the wayside?
We’re going to block some sites that sing their siren song to us, calling like the blue light inside the bug zapper. I’ll use four that friends have suggested.
Now, it’s simply no good to just cut off your access to these sites. The goal here is to get you back to work, not to make it so that you have to go find a way around an all-encompassing block to get your fix. So, we’re going to block access to problem sites during parts of the day when you think you ought not be accessing them.
This can now be easily done with pfSense
To implement this we need to break down the problem into two parts:
1. What do we want to block?
2. When do we want to block it?
Read the complete howto here.
Have you seen the “FreeNAS, how it works” video?
FreeNAS Week – day 1: System and Skill Requirements
FreeNAS Week – day 2: Installation HowTo
FreeNAS Week – day 3: Basic Configuration
FreeNAS Week – day 4: Configuring Disks
FreeNAS Week – day 5: Windows Shares
FreeNAS Week – day 6: Setting up FTP access in FreeNAS
FreeNAS is an open source operating system exclusively built to serve the purposes of implementing a small Network Attached Storage (NAS for short) device. NAS devices allow for centralization of data, data backup, and collaboration. The beautiful part, besides it’s being free, is the ease in setting it all up.
At TTU we have begun using a FreeNAS server for organizing all of our files that are commonly used throughout our department. One of the issues that kept coming up within our department was versioning control (people using different versions of the same document). We were also struggling to keep all of our files that we commonly shared in one central location. It was not uncommon for one person to go on vacation and inadvertently lock us out of accessing documents that we all needed access. FreeNAS allows one central location for all of these solutions. FreeNAS’s features really shine in its versatility. With FreeNAS, one can connect to the NAS as a shared network drive, an ftp server, and many other useful methods that meet a wide variety of operating systems needs. With FreeNAS we can insure proper backup either by using a hardware RAID or the built in software RAID.
As one can already see the possibilities for education are pretty varied and wide. It for one can offer life to legacy hardware by turning older machines with lower power processors into centers for data management. A NAS does not need the heavy computing power that many other services need. FreeNAS can also be fun from a usb drive or compact flash drive further reducing its footprint. FreeNAS offers efficiency and access to files from either work, home, or abroad. It offers a method for sharing files that would other wise have to be handed off physically or broken into chunks and sent through email. It also gives schools the opportunity to centralize their documentation and backup. When combined with backup software one can greatly decrease the likelihood of data loss due to hardware failure. It also offers integration with LDAP and local user authentication and restriction control. All in all the software provides another free and easy to configure alternative to expensive projects.
This is a review by rschapman. Bold by me.
Are you bored at work and wish you could listen to the hundreds or thousands of mp3’s or ogg’s that you have ripped to your hard drive at home? Maybe you want to create an internet radio station and live out your fantasy of being a DJ.
Whatever your reason, I’m going to show you how to very easily and freely create a kick ass streaming audio site using Linux or *BSD that you can listen to from any computer. I say again, any system – Windows, Mac, Linux, whatever – will be able to listen. Sound cool?
Read Rich Morgan’s howto here