Most newer distros inexplicably cause your NIC to have what Icall "random" non-standard name conventions because of systemd. This is a big problem for many people and especially those running servers. Imagine that you have a static IPconfigured for ens33 but then the hard disk is moved to a newer system, the NIC could be anything from ens33 to enp0s1, meaning that manual intervention is required to go and update the NIC config file (eg. /etc/network/interfa........

I messed up the bootloader by accident on a standard Centos 6.3 install because I turned the /dev/vda1 boot partition into an mdadm raid 1. This was all done correctly aside from one point Ididn't realize was an issue metadata=00.90 is the only thing that will allow you to boot (otherwise grub won't work and you won't boot). So the next step is rescue mode from a CD right? The problem you will find is that grub does not detect your hard drives, this is Ibelieve is be........

Mount Linux ext2 file systemNormally in Linux you could mount ext2 or ext3 etc... like this: mount -t ext2 /dev/hda1 /mnt/hda1/ In FreeBSD the difference is of course the disk naming conventions (hda1 would be known a /dev/ad0s1): To mount ext2 in FreeBSD just type: mount -t ext2[b:68c16c60bf]fs[/b:68c16c60bf] /dev/ad0s1 /mnt/ad0s1........