Two days are worth the years you’re gonna spend living with that system.

Because everything is labeled safe and unsafe, right?

Okay, but are you still going to audit 200 individual dependencies even once?

You presume incorrect

It’s not a fact that updates regularly break the system. I’ve been using Arch for like 20 years now and I can count the amount of times that’s happened to me on one hand. I can do the same for CentOS and other distros as well.

It also wasn’t what I was referring to when I said I broke my shit by a mistake so you’re sticking words in my mouth.

Recognizing your own mistakes is self-gaslighting now? FFS. And making a mistake sure is not “using a system in exactly the way it’s supposed to be used.”

Sometimes we make mistakes, it’s okay. If I wanted my OS to coddle me I wouldn’t be using Linux.

Don’t know what you’ve been using but I sure wouldn’t describe Arch as any of that. Once things are setup, I’ve extremely rarely run into issues that I didn’t cause myself.

Seems more like an opportunity to learn then if that’s the case. Fixing things has almost never taken me longer than a full reinstall.

Also, this whole meme misses out on the whole fun factor of getting everything setup exactly how you want and all the learning along the way. The Arch user is way more likely to fix any issues that come up in the future rather than just nuking the install and starting over Windows-style like this meme suggests.

Arch user rage bait and I guess I fell for it. I use arch btw.

ha, I thought this slide was literally about the OS/license

What kernel parameters should I use?

At least 3 times. 5 to make sure.

Linux users are in the (well constructed) tent camp in the local park that Mac users ride their electric scooters past while desperately trying to avoid eye contact.

Consumer friendly?

I’m flagging that AUR package and you can’t stop me.

I really need to get my screen sharing working. It’s been a miserable slog so far.

Running fstrim frequently, or even using mount -o discard, might negatively affect the lifetime of poor-quality SSD devices.

I guess it was recommending against frequent runs.

Yeah, the man page doesn’t really help me out.

   fstrim is used on a mounted filesystem to discard (or "trim")
   blocks which are not in use by the filesystem. This is useful for
   solid-state drives (SSDs) and thinly-provisioned storage.

   By default, fstrim will discard all unused blocks in the
   filesystem. Options may be used to modify this behavior based on
   range or size, as explained below.

   The mountpoint argument is the pathname of the directory where
   the filesystem is mounted and is required when -A, -a, --fstab,
   or --all are unspecified.

   Running fstrim frequently, or even using mount -o discard, might
   negatively affect the lifetime of poor-quality SSD devices. For
   most desktop and server systems a sufficient trimming frequency
   is once a week. Note that not all devices support a queued trim,
   so each trim command incurs a performance penalty on whatever
   else might be trying to use the disk at the time.

For instance, why would unused blocks not be discarded? And what does “discarded” even mean in this context? But it does recommend against using it for SSDs so I think I’ll skip it.

If that’s bacula, what’s tar?

Traceback (most recent call last):
  File "", line 1, in 
IsADirectoryError: [Errno 21] Is a directory: 'C:\Windows\System32'