What others wrote except don’t use dd. Use rsync or make a backup with tar. dd will waste time reading unallocated regions of the disk.

I meant what’s the link to use since the same Lemmy post can be viewed through different instances and on each it has a different URL. It’s a bit user-hostile that the link gets you out of your instance (unless you’re on the same instance as author of the post).

Yeah, my bad. I should have linked to the previous post: https://discuss.tchncs.de/post/32637183 (not entirely sure what’s the etiquette for linking to posts on Lemmy is).

Yeah, it’s a bit philosophical.

• In graphical applications, Ctrl+M, Ctrl+J and Return/Enter are all different things.
• In a terminal in raw mode, Ctrl+M and Return/Enter are the same thing but Ctrl+J is something different. You can for example run bind -x '"\C-j":"echo a"' in bash and Ctrl+J will do something different.
• In a terminal in canonical mode, they are all the same thing. There probably are some stty options which can change that though.

Yes. So is Ctrl+J actually. Ctrl+J corresponds to line feed (LF) and Ctrl+M corresponds to carriage return (CR) ASCII characters. They are typically treated the same way.

Yes, I agree. But the dispute is what ‘sends EOF’ actually means. The article I respond to claims Ctrl+D doesn’t send EOF but is like Enter except that new line character is not sent. This is, in some sense true, but as I explain also misleading.

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"

You want readlink -f rather than ls -l. ++OK, actually not exactly. readlink won’t print path to the symlink so it’s not as straightforward.++

Also, you want + in find ... -exec ... + rather than ;.

At this point I feel committed to making readlink work. ;) Here’s the script you want:

#!/bin/sh

want=$1
shift
readlink -f -- "$@" | while read got; do
	if [ "$got" = "$want" ]; then
		echo "$1"
	fi
	shift
done

and execute it as:

find ~ -type l -exec /bin/sh /path/to/the/script /path/to/target/dir {} +

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.

Tuxedo

I used Claws Mail at some point in the past. Now notmuch+Emacs.

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.

Nothing you wrote contradicts the observation that it’s easier to apply for a job and get it than to construct a full blown company which needs to be acquired. If there are already 99 ‘spies’ at Google, there’s hardly need for such elaborate schemes.

Why do you think it would affect performance?

It’s easier to get operatives to apply for a job and get hired than build a company which ends up being bought. This sounds like conspiracy theory to me. Any large US corporation likely has operatives of various countries working for it.

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

The thread linked by the OP is Jarkko Sakkinen (kernel maintainer) seemingly saying “show your work, your patch is full of nonsense” in a patch submitted for review to the Linux kernel.

That’s not what he’s saying. He’s saying: ‘You’re using terms which aren’t that familiar to everyone. Could you explain them?’

If you have an SVG image you can either embed it directly on the website, or link it using img tag. Whatever the case, there’s no need to export it to PNG.

And yes, that will likely result in a smaller website and furthermore images which can scale smoothly.

Another interesting part is that HTML5 supports embedding SVG. That is, you can put SVG code directly in your HTML5 document and it’s going to render correctly. You can also style it through your website’s CSS file and manipulate the elements via JavaScript.

Though as others pointed out, it’s technically not HTML but XML. For example, you have to close all the elements and quote all the attribute values. But when you embed it inside a HTML document, those rules get relaxed to adhere with HTML. (I.e., you cannot write <circle r=5> in SVG (it must be <circle r="5" />) but you can when you embed it in HTML).

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.