Snarwin

https://www.merriam-webster.com/dictionary/gimp

(offensive) : a disabled person

“Title II” in this context refers to Subchapter II of 47 U.S.C. Chapter 5. 47 U.S.C. is the Communications Act of 1934, the act of Congress that established the FCC, and Chapter 5 is the part that deals with “Wire and Radio Communications.”

If you want to know what this law empowers the FCC to do, you can read the statute yourself. Or, if that’s too difficult, you can also use your access to the internet to look up more accessible sources, such as Wikipedia’s “Common carrier” article.

As long as you copy from the device file (/dev/whatever), you will get “the raw bits”, regardless of whether you use dd, cp, or even cat.

As someone who occasionally dabbles in music production on Linux, I love that Pipewire lets me run JACK and Pulseaudio apps side-by-side without having to jump through hoops.

On my distro (debian) I can use systemctl --user restart pipewire.service.

This website explains the process: https://git-send-email.io/

You could try the solution suggested in this reddit thread, and use systemctl to start and stop wireguard instead of wg-quick.

For me, Crunchbang was a great introduction to the possibilities of customizing your Linux experience. No giant, monolithic desktop environment, just a handful of programs that you could (and were encouraged to) tweak or replace to your heart’s content.

I still run a Crunchbang-inspired setup on my vanilla Debian install—openbox, tint2, conky, nitrogen, gmrun, Win+Letter hotkeys for frequently-used apps, etc. While I’ve outgrown the need for a preconfigured distro myself, I’m glad to see these projects still providing an on-ramp for users looking to dip their toes into the deeper end of the Linux pool.

The first step after you untar is always “open the README and look for build instructions.”

Personally my only gripe with systemd is that the systemctl and journalctl commands are cryptic and unintuitive. Every time I have to use one (which thankfully isn’t often), I have to spend 5 minutes reading man pages to remind myself whether -u is “user” or “unit”, what the difference is between a “unit” and a “service”, etc.

I imagine this is what non-developers feel like when they’re forced to use git—having a whole pile of unfamiliar vocabulary and syntax thrown in your face when you’re just trying to do one simple thing.

Same thing happened to me. Borked my Windows install and didn’t have a recovery disc, so I just wiped the whole thing and went Linux-only. Never looked back since. :)

Sometimes, all you need is a little push to get you out of your comfort zone.