|
The one you're more versed in, in the end.
You have quality software for both, and it's more the time you need to resolve issues that count.
I'm a pro-linux, nad I'd even say that openBsd would be better as a shared web hosting server.
BSD is way more responsive than Linux under high load, and it's development model is "stability first, features after" where often Linux looks like a sand castle to me.
There are great ideas, but if you don't know exactly what to do, you could undermine your system. I think about the low latency patches, for instances. They are great for a desktop machine, bu not recommended for servers.
So in the end, if you have an MCSE and experience in Windows server, go that way.
If you feel more acquainted with Bsd or linux go that way.
Anyway, it's going to be hard work, configuring DNS, IP routing, BGP routing, setting up multiples connections to prevent your server being cut out of the net when 1 fiber goes out, load balancing, fail over preventing and securing your server.
I'd recommend you to have 2 machines, if possible close about the software you run on them.
1 at your disposal, at home or in your desk, to test and fsck it up, and the other, online, where you applies the solutions you have experienced on your test server.
It's the safest way to go.
__________________
Listen to the ducky: "This is awesome!!!"
|
OK You two 
