... but it would be too short! It is actually really easy, if you are using hardware RAID. On that note, for RAID 5, I definitely recommend hardware RAID, not software... I have seen the disastrous results of software RAID 5 when things go bad, and it is not pretty... you might as well not be using RAID. Besides, for SOHO or home use, a motherboard with decent RAID support is only $10 - $30 more expensive than a non-RAID equivalent.
In any event, with hardware RAID, since you set it up before the OS boots, it looks like like a regular drive to the OS. FreeBSD will know that it is a RAID, so the RAId will be (assuming that it is the first "drive" in the system) /dev/ar0 Treat /dev/ar0 the same way you would treat /dev/ad0 (for an IDE drive) and you'll be fine! Interestingly enough, you should also see the individual drives listed; I am not sure what happens if you try writing to one of them, particularly in a RAID 5 scenario.
However, I am not quite sure if my FreeBSD system is properly monitoring for drive failure, I never did test that...
I know what you mean about the expense, too! My desktop has two RAID 1 arrays (two 160 GB drives for the OS/apps, two 250 GB drives for data, both sets with the special RAID Edition Western Digital SATA II drives) and my new FreeBSD server has a RAID 1 array (two 80 GB drives) and a 500 GB drive for backups... all said and done (once you through in my IPCop router) I probably spent $800 on drives a few months ago when I set this all up. But I think the redundancy was well worth it, as well as the boost in read speed (write speed is a touch slower).
Personally, I don't trust RAID 5. Two failues guarantees data loss, without a hot spare. RAID 1 has a 50/50 chance of surviving a double drive failure, in case of failure. Rebuilds also seem a bit quicker and reliable, but I could be wrong.
Feel free to PM or email me if you want more information on the subject!
J.Ja