Linux

48129 readers

427 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

283

What is the most duct-tape thing you've done to Linux? (lemm.ee)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

190 comments fedilink hide all child comments

tell me the most ass over backward shit you do to keep your system chugging?
here's mine:
sway struggles with my dual monitors, when my screen powers off and back on it causes sway to crash.
system service 'switch-to-tty1.service'

[Unit]
Description=Switch to tty1 on resume
After=suspend.target

[Service]
Type=simple
ExecStart=/usr/local/bin/switch-to-tty1.sh

[Install]
WantedBy=suspend.target

'switch-to-tty1.service' executes '/usr/local/bin/switch-to-tty1.sh' and send user to tty1

#!/bin/bash
# Switch to tty1
chvt 1

.bashrc login from tty1 then kicks user to tty2 and logs out tty1.

if [[ "$(tty)" == "/dev/tty1" ]]; then
    chvt 2
    logout
fi

also tty2 is blocked from keyboard inputs (Alt+Ctrl+F2) so its a somewhat secure lock-screen which on sway lock-screen aren't great.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 99 points 2 months ago* (last edited 2 months ago) (4 children)

My control key was broken, but I found that when I used an app and held down the space bar key, the CPU would get abnormally hot.

So I wrote an Emacs interrupt to interpret a rapid CPU rise as "press the control button".

Unfortunately the dev pushed an update that broke space bar heating, which broke my workflow. I opened a bug report about it, though...

[–] [email protected] 81 points 2 months ago (1 children)

https://xkcd.com/1172/

[–] [email protected] 10 points 2 months ago (1 children)

How the fuck....

[–] [email protected] 19 points 2 months ago

Other way around.

[–] [email protected] 34 points 2 months ago (2 children)

That's horrifying.

[–] [email protected] 44 points 2 months ago

Hey, my setup works for me! Just add an option to enable CPU overheating in the next update!

[–] [email protected] 8 points 2 months ago

Just think how many children are holding down spacebar to keep warm in the winter. We need to keep this feature around.

[–] [email protected] 6 points 2 months ago

This is an absolute winner IMHO. I’m imagining all the hotkeys that are accidentally activated when a CPU-intensive task spins up.

[–] [email protected] 5 points 2 months ago (1 children)

Wow...

[–] [email protected] 22 points 2 months ago

It's not real, it's an xkcd joke