Explore >> Select a destination
|
You are here 
|
nagimov.me | ||
| | | | |
dustymabe.com
|
|
| | | | | Last time I walked through creating a sparse disk image using dd and cp --sparse=always. OK, we have a disk image. Now what? Normally it would suffice to just set up a loop device and then mount, but this disk image doesn't just contain a filesystem. It has 4 partitions each with their own filesystem. This means in order to mount one of the filesystems we have to take a few extra steps. | |
| | | | |
github.com
|
|
| | | | | This is a portable implementation of the FreeBSD kernel block-device encryption framework (with read/write support). Currently, GNU/Linux is supported but support may grow to other operating systems as well. - bijanebrahimi/portable-geli | |
| | | | |
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. | |
| | | | |
www.davidschlachter.com
|
|
| | | Compatibility of FreeBSD on a Lenovo Thinkpad T480, notes and fixes (HiDPI, Trackpad, camera, etc). | ||
