What is the most duct-tape thing you've done to Linux?
What is the most duct-tape thing you've done to Linux?
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're viewing a single thread.
Building a custom Buildroot Linux for a Pentium 2 laptop that can fit on a CD so I could back up a 2.5" IDE drive to a USB drive, probably.
On another note, last night, I had to get a Google TV set up on my dorm Wi-Fi, which requires me to either go through a portal to set it up or to go into my account and add the device's MAC address. The TV (which was brand new and doing OOBE stuff) wouldn't let me go to settings to get the MAC address without a network connection. Even more infuriating, there was a button in the Google Home app that said "Show MAC address", but when I pushed it, it would say "Can't get MAC address." What I ended up doing to get around that crap was setting up my Debian Thinkpad (which I am writing from now) to share its internet connection over ethernet to finish the setup process so I could get to settings and get the MAC address.
On one hand, a funny experience, but on the other hand, I'm simultaneously both mad at Google and my dorm internet provider.
The Pixel watch has this problem too. However, it randomizes the MAC per network, so that strategy won't even work. I've tried to get it from the debug log but failed I've resigned that it won't be getting connected to the school network
Open a bug report with the school network admkn. This is default android behavior and a privacy issue to boot
Android is fine because you're able to use a web browser to get an auth key. You have to register devices where you can't do that, and it seems to be impossible in the case of the pixel watch
Edit: Also, they're not concerned about privacy. They want to know who every device belongs to
That never works for me on Android systems. It probably needs some shitty Google service.
You have a right to privacy. Its your school. They work for you.
The iPhone does that too, but has a way to disable it on a per-network basis.