I succeeded in doing this once long ago. Then while in the Linux vm I wiped the VM’s partition table, which wiped the physical disk partition table, including windows. Do not recommend.
I succeeded in doing this once long ago. Then while in the Linux vm I wiped the VM’s partition table, which wiped the physical disk partition table, including windows. Do not recommend.
Professional CMake: A Practical Guide by Craig Scott is an excellent guide to modern cmake usage. Well worth the $30 if you need to build, maintain, or modify a CMake project.
Ah, yes, I live on “St Mary’ ; DROP TABLE street”
Consider how well Lotus Notes handles your form>…>messaging pipeline. Why aren’t we still using an evolution of that? There’s always a shiny new technology that promises to fix all of the problems of the previous ones.
Get a BeagleBoard! https://www.beagleboard.org/boards/beaglev-ahead
Edit: or a Star64! https://pine64.com/product-category/star64/
Isn’t this basically how lisp works?
Yes a back up is possible. Don’t back up partitions, back up the whole device. All 150+g at once.
Whenever you try to mount the device or the filesystems, make sure to mount it read-only so that no changes are written to the device.
Also, shrinking 84g of data into 32g is definitely not possible. Just changing the fdisk partition table doesn’t shrink or relocate the data. You need a filesystem-aware resizing tool to shrink the filesystem before shrinking the partition.
Hopefully you can just change the partition table back to the original values and get a clean fsck.
Real programmers curl unverified shell scripts into bash.
Do you find a beer gut sexy? How about Dad Bod?