It’s trivial. Use Linux Mint or Debian, enable non-free repositories if required, and that’s pretty much it.

I’ve never had issues with Nvidia drivers. Your mileage may vary.

It is a product of its time. If the same research was made 30 years ago, I bet there would be a stark difference to results today. LTO wasn’t as feasible. Compilers were less capable of removing redundant checks. Branch prediction in x86 processors was still a hot new thing. And on top of it all, there was less knowledge about language development.

Who cares what anyone on r/macos thinks.

If everything else fails, there’s always an option of defining your own keymap and enabling it in initrc.

Admittedly, I’m probably not the best person to ask for recommendation of a noob-friendly distro, but I feel people are overthinking this. If someone produces a list which includes distros I’ve never heard of, I think they spent too much time on ‘Top 10 Noob Friendly Distros in 2025’ websites.

If you really care about my recommendation, just start with Mint.

PS. I should also add, this isn’t criticism of you or any other new user who does search online for recommendation. This is more a comment on state of the Internet where there are so many websites which seem to pad their list with obscure distros where really all such articles should give recommendation for one of the same three distributions. Which three I don’t exactly know.

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)

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.

Why do you think it would affect performance?

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?’