I want to move my freebsd 8.2 installation from a dual-core AMD machine to a quad-core intel machine. Ideally I'd just like it to re-detect all the changed hardware and load whatever drivers it needs in order to boot. Both systems are basically SMP x64-machines, does freebsd care beyond that?
I realise it will break a lot of configs due to new nics etc, but as long as the machine boots I'll be ok.
Will it work, or is there a way to make it work?
Amazon web services recently introduced a free tier, where you basically get free stuff to try out AWS and run tiny sites and projects. Basically it's free as long as you remain below a certain limit of bandwidth, disk storage etc.
Since going over the limits can quickly become quite expensive (for a hobbyist) I would like some recommendations or suggestions about which AMI's I can run on the free tier, for the purpose of trying out Ruby on Rails and/or Django.
I recently installed freebsd 8 on a file server and created a raidz-pool from 4 drives. It works fine, except the filesystems are not mounted automatically on boot. zpool status and zfs list shows nothing wrong but I have to do a zpool export and import for the pool and filesystems to get mounted, and consequently for the shares to be accessible from the network.
This also happens on a vmware test system I have, also running freebsd 8 (x64 in both cases). After the manual import everything works fine.
I assume this is a small bug in freebsd 8 since it happens with two different installs, and I can work around it with a small script, but what's the (proper) way to solve it?
FreeNAS seems like a great product with a full checklist of features, even iSCSI. But how reliable is it? There are a few scary stories about lost data, for example here. Here is another example.
If you have used freeNAS for a longer period of time or even in a production setting, please share your experiences, good or bad. It would be great if you could also describe the setup, ie which hardware and features (software raid, zfs, iscsi etc) you are using.