Yeah, it has been slowly growing on me 😜. But I would like to explore all other options before I fully commit.

You’ve already discovered the best editor. There’s no need to explore more. ;)

If it was compromised account trying to sneak code into the kernel, the attacker wouldn’t rewrite history since that would be obviously flagged when Linus tries to merge the pull request; as demonstrated by Linus in fact noticing the rewritten history. There was virtually no chance that this was an attack.

find -type f -exec chmod 644 -- {} +
find -type d -exec chmod 755 -- {} +

will only affect regular files and directories. There are other type of files (specifically block and character devices, named pipes and sockets) which those two commands would leave unaffected. In practice, I suspect you don’t have any of those to worry about so you can use -find f.

Switch to a non-buggy browser.

Yes. I’m just keeping the symbols file in home directory so that I don’t have to edit the system files. To change backspace you’d have something like the following I believe:

    key <BKSP> {    [ BackSpace, Delete ] };

Also, nano may not always be installed.

mcedit, gedit, pico. For majority of people lack of any simple non-vi-based text editor is a corner case not worth worrying about. Definitely not enough of a problem to start ‘How to learn Emacs’ tutorial with ‘Learn Vim’.

src/* will skip hidden files. You want rsync -avAXUNH src/ dst which copies contents of src into dst. Notice the trailing slash in src/. Without the slash, src is copied into dst so you end up with a src directory in dst. The AXUNH enables preserving more things. You might also add --delete if you’re updating the copy.

PS. I should also mention how I end up with -avAXUNH. Simple:

$ man rsync |grep ' -. *preserve'
       --hard-links, -H         preserve hard links
       --perms, -p              preserve permissions
       --executability, -E      preserve executability
       --acls, -A               preserve ACLs (implies --perms)
       --xattrs, -X             preserve extended attributes
       --owner, -o              preserve owner (super-user only)
       --group, -g              preserve group
       --times, -t              preserve modification times
       --atimes, -U             preserve access (use) times
       --crtimes, -N            preserve create times (newness)

and then include all that. a covers some of those options and those don’t have to be set explicitly:

$ man rsync |grep ' -a ' |head -n1
       --archive, -a            archive mode is -rlptgoD (no -A,-X,-U,-N,-H)

You could pass $1 and $got through $(realpath -P -- ...) to make sure all the path are in canonical form. Though now that I’m thinking about it, stat is probably a better option anyway:

want=/path/to/target/dir
pattern=$(stat -c^%d:%i: -- "$want")
find "$HOME" -type l -exec stat -Lc%d:%i:%n {} + | grep "$pattern"

Everything you’re describing is further speculation and unfalsifiable statements for events which already have a simpler explanation. That’s a tell-tale sign of a conspiracy theory.

Google buying the company as some kind of plot to get spies into Google requires more assumptions than Google buying the company for the technology (as it has done with plethora of other companies). If Google is somehow complicit in it, they could just hire those people directly. And if it’s all covert operation, Israel is capable of training and coaching their spies to pass Google’s interviews. Google interviews aren’t trivial, but it’s also not some super-elite company which hires only the top 0.01% of software engineers.

If you want to convince me otherwise, you need to demonstrate why your explanation is more likely than the obvious one.

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.

This is too simplistic example to give any meaningful answer. What’s Type? What’s value? If it’s i32 and 42 than they both compile to the exact same thing. But if Type is Drop than the second will call the destructor on each iteration. (I’ve also written previously about similar example with BorrowedBuf^1^).