After getting this blog online, I was able to hook it to my twitter account, supposedly. The entire purpose of getting a http://rootbsd.net virtual machine, IP, domain name and trying to understand how computers work was so that I could post things in more than 140 characters.
I was quite suprised at the quality of the how-to I found on http://forums.freebsd.org for setting up WordPress, with the exception of using mysql 5.6 for the installation, all seemed to be well. https://forums.freebsd.org/showthread.php?t=30268
Now, and only now, do I realize the folly of all this though. One of the crutches I’ve been heavily leaning on was ZFS, The Bacon Of Filesystems:
From IRC: <brueffer> ZFS must be the bacon of file systems. "everything's better with ZFS" – #zfs
— Peter Wemm (@karinjiri) July 4, 2013
I use it for snap shotting my file systems before doing any kind of buildworld or port upgrades. That has given me numerous changes to rollback before any serious damage has occured, at least until now. I only NOW realize that my VM is a small, UFS limited thing without the safety net of BACON. I LOVE BACON. It makes EVERYTHING better. Seriously.
How do you even do backups reliably on UFS? With ZFS you set a snap shot via “zfs snapshot -r zroot” and you’re done. (apply “bam” noise here)
If you have an issue with the current state of affairs, no worry, zfs rollback and you’re done. DUN.
I guess I need to learn more about backups in this non-bacon world.
One response to “Getting super social with Bacon”
UFS supports a fairly limited version of snapshots, so you could make and read-only mount the snapshot, then make your backup from that, same way you would if you were actually making a backup of ZFS (say, with Bacula)
see mksnap_ffs(8)