The fix involves changing two settings from the command prompt. You need to run the command prompt as an administrator. You can do this by right-clicking and selecting run as administrator. Type in the following commands
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global rss=disabled

You will need to restart your machine afterwards. The difference is night and day. I wonder what the reasoning was for not having Vista set like this out of the box?

If you are unhappy with the changes you can restore the default settings with
netsh int tcp set global autotuninglevel=normal
netsh int tcp set global rss=enabled

Create RAID
mdadm --create /dev/md0 --level=5 --raid-devices=4 /dev/sd[bcde]1
mkfs.ext3 /dev/md0

Remove disk from RAID
mdadm --fail /dev/md0 /dev/sda1
mdadm --remove /dev/md0 /dev/sda1

Copy the partition structure (when replacing a failed drive)
sfdisk -d /dev/sda | sfdisk /dev/sdb
mdadm --zero-superblock /dev/sdb

Add a disk to a RAID array (to replace a removed failed drive)
mdadm --add /dev/md0 /dev/sdf1

Check RAID status
cat /proc/mdstat
mdadm --detail /dev/md0

Reassemble a group of RAID disks
mdadm --assemble /dev/md0 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1

Steps to emulate mdrun (which has been depreciated)
mdadm --examine --scan --config=partitions > /tmp/mdadm.conf
mdadm --assemble --scan --config=/tmp/mdadm.conf

Convert a RAID 1 array to RAID 5 (follow the steps to add a disk after running this command)
mdadm --create /dev/md0 --level=5 -n 2 /dev/sda1 /dev/sdb1

Add a disk to an existing RAID and resize the filesystem
mdadm --add /dev/md0 /dev/sdg1
mdadm --grow /dev/md0 -n 5
fsck.ext3 -f /dev/md0
resize2fs /dev/md0

Stop and remove the RAID device
mdadm --stop /dev/md0
mdadm --remove /dev/md0

Hardware RAID uses an add in card (PCI, PCI Express, PCI-X). The card has on-board memory and a processor to compute the RAID calculations. The RAID is stored in the controllers proprietary format and most likely you will need to use their drivers. The price is around $300-400 for a 4 port SATA card. The CPU load is basically non-existent with this setup.

Hardware/software RAID uses an add in card as well. However the card doesn’t contain memory or a RAID processor. It instead off-loads the RAID calculations to the CPU. The data is still in a proprietary RAID format and most likely you’ll need to use the card’s RAID drivers. These run around $100-150 for a 4 port card. Personally I think this form of RAID is pointless unless it is used for RAID 1 or 0 for reasons explained below.

Software RAID is proprietary to the software format. In linux you can move the drives easily between systems and linux distros provided the kernel support is the same. I’ve moved between Debian and Ubuntu without an issue. All the RAID calculations are performed by the CPU. However with today’s processors this will most likely not be an issue. The advantage to software RAID is the support as it is widely used.

No matter which implementation you choose make sure to test all possible scenarios before putting the RAID into production. Practice failing a drive, replacing it, and rebuilding the array. If you are going the software RAID route VMWare allows easy and fast testing. You can create multiple 1 GB drives which will rebuild much faster than 500GB real drives.

When starting the installer proceed until you reach the network configuration screen where it asks for the hostname. At this point you’ll want to switch to another virtual terminal (alt+f2). Run the following commands
modprobe raid1
modprobe dm_mod
mdrun

Mdrun might return command not found as it has been depreciated in later linux releases. Don’t worry we can use mdadm instead.
mdadm --examine --scan --config=partitions > /tmp/mdadm.conf
mdadm --assemble --scan --config=/tmp/mdadm.conf

Let’s verify that the RAID arrays were found and started.
cat /proc/mdstat

If you are using LVM we can now scan and activate the volumes.
lvscan
vgchange -a y

Now you can return to the installer with alt+f1. When you reach the partitioning stage select manual and assign the RAID / LVM volumes mount points.

This can be a problem if you have a shared CGI app like awstats as unless you make each user a copy the uid/gid will not match. Not to mention that the docroot on Fedora is /var/www so if you want to store your virtual hosts elsewhere your out of luck. Not to worry recompiling apache isn’t as hard as you might think.

Since we are modifying suexec there is always the potential that the modifications may cause a security hole. Proceed at your own risk!!

First we need to grab the httpd SRPM from FC5 updates
cd ~
wget http://mirrors.kernel.org/fedora/core/updates/5/SRPMS/httpd-2.2.2-1.3.src.rpm

Next we setup the RPM build area
fedora-buildrpmtree

Install the SRPM into the rpmbuild directory
rpm -ivh httpd-2.2.2-1.3.src.rpm

Grab the suexec no UID/GID check patch
cd rpmbuild/SOURCES
wget http://www.excalibur-partners.com/wp-content/uploads/2007/11/suexec_nocheck.patch

Modify the docroot
cd ~/rpmbuild/SPECS
vim httpd.spec
Line 192:
- --with-suexec-docroot=%{contentdir} \
+ --with-suexec-docroot=/ \

Modify the httpd.spec to include the patch
vim httpd.spec
Line 48:
Patch73: httpd-2.2.3-CVE-2007-3304.patch
+ Patch80: suexec_nocheck.patch
Line 131:
%patch73 -p1 -b .cve3304
+ %patch80 -p1 -b .nocheck

Now we can build the modified RPM
rpmbuild -ba httpd.spec

Instead of reinstalling apache I recommend just extracting and replacing the suexec file
cd ~/rpmbuild
rpm2cpio RPMS/`uname -p`/httpd-2.2.2-1.3.src.rpm | cpio -imVd ./usr/sbin/suexec
sudo cp -p /usr/sbin/suexec /usr/sbin/suexec.orig
sudo cp ./usr/sbin/suexec /usr/sbin/suexec
sudo chown root:apache /usr/sbin/suexec
sudo chmod 4510 /usr/sbin/suexec

To get started you need to have a folder to store the data for each virtual website. On my system I have a created a new user for each website following the pattern.
/home/*/public_html/

For example to add jsmith. Note that the /home/jsmith folder must have execute permissions and the public_html folder must have read permissions for apache.
useradd jsmith
cd /home/jsmith
mkdir public_html
chown jsmith:jsmith public_html
chmod 711 .
chmod 755 public_html

Lets open up the apache config and add the required sections.
vim /etc/httpd/conf/httpd.conf

Scroll down to the end of the file and you will see the virtual hosting section. The first thing we must do is let apahce know what IPs and ports it will be serving for virtual hosts. The * wild card is supported. The line below states that apache will server requests for port 80 on all incoming IPs.
NameVirtualHost *:80

Now we set the individual settings for each virtual host. If you are a hosting provider you probably will want a catchall host to display if the user goes to the server’s IP or hostname. To do this we use the _default_ attribute.
<VirtualHost _default_:80>
ServerAdmin email@domain.com
DocumentRoot /var/www/html
ServerName www.domain.com
</VirtualHost>

On the rest of your virtual hosts I recommend to fill in a ServerAlias. Lets say your site is http://www.jsmith.com/. Without a ServerAlias if a visitor points his/her browser to http://jsmith.com/ they will get the default host instead of http://www.jsmith.com/.
<VirtualHost *:80>
ServerAdmin email@jsmith.com
DocumentRoot /home/jsmith/public_html
ServerName www.jsmith.com
ServerAlias jsmith.com *.jsmith.com
</VirtualHost>

Make sure to verify the apache config first
apachectl configtest

If it comes back syntax OK you are ready to reload the config
service httpd reload

or start up the apache server if it is not already running.
service httpd start