/explore
|
You are here 
|
wittchen.io | ||
| | | | |
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. | |
| | | | |
nabijaczleweli.xyz
|
|
| | | | | 005a. A single-disk but slightly more cursed ZFS-on-root corollary | |
| | | | |
blog.stigok.com
|
|
| | | | | NOTE: If you mix up the disk names in the below commands the results may be fatal for your data. If you are not certain you are writing the correct drive pat... | |
| | | | |
www.kroah.com
|
|
| | | Note This post is based on a whitepaper I wrote at the beginning of 2016 to be used to help many different companies understand the Linux kernel release model and encourage them to start taking the LTS stable updates more often. I then used it as a basis of a presentation I gave at the Linux Recipes conference in September 2017 which can be seen here. With the recent craziness of Meltdown and Spectre , I've seen lots of things written about how Linux is released and how we handle handles security patches that are totally incorrect, so I figured it is time to dust off the text, update it in a few places, and publish this here for everyone to benefit from. | ||
