This doesn’t mean it’s a bad format or that it shouldn’t be used. In fact, it should still be the default unless you need something it doesn’t support or really need to reduce file size.

I rather disagree. I’ve switched to lossless WebP for all my needs. There are practically no drawbacks and I get a smaller file.

What you have in title of the post, body of the post and in this screenshot all disagree with each other.

Use backtics to quote code fragments. Tripple backtics to block quote. You should be able to edit your post.

Well, that’s kind of his personality though.

Yes. Linus is known to overreact and use colourful language.

So does it wait until it has found all the matches to run the command as a giant batch instead of running it as it finds matches?

Indeed. If possible, it is typically what you want (as opposed to find ... -exec ... {} \; which runs command for each found file) since it will run faster. You want find ... -exec ... {} \; if the command you’re executing can run on single file only or you’re dealing with legacy system without -exec ... {} + support.

But I need x on directory, because that’s required to enter/read the directory. If I understand properly.

That’s why bacon listed find ${path} -type d exec chmod 750 {}; as first command. See also my reply.

X applies to directories and executable files. Presumably, OP wants to clear the executable bits from any files and +X won’t do that.

I’ve Pulse 14 with plain Debian installation and so far didn’t notice any issues. Though admittedly, I’m not a heavy laptop user. Your mileage may vary I guess.

You cannot write setuid scripts. It must be a binary.

Which is why I haven’t wrote ‘EOF character’, ‘EOT’ or ‘EOT character’. Neither have I claimed that \x4 character is interpreted by the shell as end of file.

Edit: Actually, I did say ‘EOF character’ originally (though I still haven’t claimed that it sends EOF character to the program). I’ve updated the comment to clear things up more.

Having to type sudo already acts as a molly-guard. Whatever OP wants to do I won’t stop them, but they are doing something strange.

If you go with adding a passphrase to the drive keep in mind that if it’s a unique one you may end up forgetting it since you won’t normally be using it. Even if you set it to the same passphrase as root partition, if you ever change passphrase for root you might forget to change home passphrase.

I would probably just make a physical copy of the key file. It’s just 32 bytes (no, larger key file doesn’t make things any more secure) so you can hexdump -C it and copy the key on a piece of paper.