Explore >> Select a destination
|
You are here 
|
blog.tmm.cx | ||
| | | | |
battlepenguin.com
|
|
| | | | | When going from Windows 3.1 to Windows 95, I favored installing things from scratch rather than trying to upgrade things in place. In my university d... | |
| | | | |
jasoneckert.github.io
|
|
| | | | | My personal website and blog | |
| | | | |
willhaley.com
|
|
| | | | | As my family's computers age into obsolescence I typically back up the disks, use shred to securely erase data from the disks, then donate or re-use the disks/computers. My current technique for backing up the Windows disks is to mount the primary (non-boot) Windows partition, convert it to a squashfs filesystem, then squirrel that backup image away somewhere for safe keeping. I like this technique because squashfs filesystems are highly compressed and read-only by default, which is exactly what I want for a Windows backup that I'll probably never look at again. | |
| | | | |
jreypo.io
|
|
| | | Welcome to the third post of my series about OpenStack. In the [first]{(% post_url 2014-04-29-deploying-openstack-with-kvm-and-vmware-nsx-part-1-nsx-overview-and-initial-setup %}) and second posts we saw in detail how to prepare the basic network infrastructure of our future OpenStack cloud using VMware NSX. In this third one we are going to install and configure the KVM compute host and the shared storage of the lab. | ||
