![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Or a tui file manager like ncdu
Or a tui file manager like ncdu
If you’re scared to do rm -rf
, do something else that lets you inspect the entire batch of deletions first. Such as:
find .git ! -type d -print0 | xargs -0 -n1 echo rm -fv
This will print out all the rm -fv
commands that would be run. It’s basically rm -rf --dry-run
, but rm
doesn’t have that common option. Once you’ve verified that that’s what you want to do, run it again without echo
to do the actual deletion. If you’re scared of having that in your history, either use a full path for .git, or prepend a space to the non-echo version of the command to make it avoid showing up in your shell history (assuming you have ignorespace in your HISTCONTROL env var)
I use this xargs echo
pattern a lot when I’m crafting commands that are potentially destructive or change lots of things.
If there is a redundant block then it will auto recover and just report what happened. Redundancy can be set up with multiple disks or by having a single disk write blocks to multiple places by setting the “copies” property to more than 1.
zfs is made for data integrity. I wouldn’t use anything else for my backups. If a file is corrupted, it will tell you which file when it encounters a checksum error while reading the file.
Dude, you’re so not paranoid. This stuff has happened to me. I had a Wordpress blog that was hacked and the exploit was stored in the DB so even after reloading the OS I still was infected because I hadn’t sanitized my database. Luckily it was just Google search viagra spam, and it was a valuable lesson.
As many have pointed out, you don’t know that there is not a back door in your software.
One way to defend against such an unknown is to have a method of quickly reinstalling your system, so if you ever suspect you have been compromised you can reload your OS from scratch and reconfigure it with minimal fuss. This is one reason I recommend folks learn one of the configuration management systems like ansible or puppet, and use those to configure your Linux servers. Having config management also helps you recover anfter unexpected hardware failures.
Defense is done in layers. No one layer will protect you 100%. Build up several layers that you trust and understand.
This makes sense. When you use a copy-on-write block device, it is doing things below the level of the filesystem, so you have to use cow-aware tools to get an accurate view of your used disk space. For example, if you have two files that are 100% deduplicated at the cow-block level, they would show up as different inodes on the filesystem and would appear as using twice the space in the filesystem as they do on the block device. Same would go for snapshots and compressed blocks.
The back door is not in the source code though, so it’s not reproducible from source.
If the second internal ssd is there when windows boots, it will leave a trace. IMHO booting off the external drive is the best option if you want it to leave no trace on the windows partitions.
Also, it’s possible any booted device will leave a trace in the bios or uefi boot logs, which your corporation may have configured to ship to their audit logs or something similar.
Some things cannot be replaced. Spez destroyed something wonderful. There’s no going back.