Explore >> Select a destination
|
You are here 
|
blog.fritzhardy.com | ||
| | | | |
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. | |
| | | | |
willhaley.com
|
|
| | | | | I have XP installed on a drive with a configuration like this. (In reality, each partition was 10x larger, but I'm using smaller numbers for this example). [ ~2GB FAT32 | E: (/dev/sda1) ] [ ~6GB NTFS | C: (/dev/sda2) ] [ ~2GB NTFS | F: (/dev/sda3) ] It may look unusual that C: is not the first partition, but a setup like this is not entirely unsual for an OEM hard drive. E: is a recovery/utility partition, C: is the partition with XP installed, and F: is an extra partition for backup. | |
| | | | |
willhaley.com
|
|
| | | | | I have an old Dell desktop that seems to crawl to a stop whenever some intense disk I/O takes place. I also happen to have a spare SSD. That SSD would give this machine a nice performance boost. The current IDE drive in the Dell has the exact same amount of space as the SSD. Unfortunately, this Dell has no SATA support and the SSD has a SATA interface. Not to worry. For ~$35 and a couple of hours this upgrade can be complete and my machine can stop grinding to a halt on intense disk I/O. | |
| | | | |
vadosware.io
|
|
| | | Professional (software) yak shaving, writ large. No part of the software stack is left unshaven. | ||
