Linux

48338 readers

441 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 3 months ago* (last edited 3 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] 48 points 3 months ago (2 children)

This certainly isn't of the same caliber as some of these other comments, but I found it to be fitting to the topic.

Last year I was having problems getting the game stellaris working on arch. (I use bazzite now, btw) My solution was the following:

download the game via steam.
switch it to use proton
switch it back to linux version
use the terminal to make the entire game folder read-only, so that steam couldn't touch the game anymore and screw it up.
add the exicutable to PATH
start the game via terminal

If any one of those step was left out, it didn't work. I'm no linux expert, so I didn't have the skills to actuality find the real problem.

[–] [email protected] 19 points 3 months ago (1 children)

I... What? Why does that work? How did you figure this out?

[–] [email protected] 7 points 3 months ago

Blind trial and error, mostly. Making the game folder read-only was the real "duct-tape" part, it occued to me to do that after steam kept "updating" the game and breaking my solution.

[–] [email protected] 17 points 3 months ago (1 children)

Even when Proton doesn't work, it still somehow works.

Magic.

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

Indeed. Proton for the win yet again.