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.
That’s not even a bad idea then.
One of my machines has a boot partition that’s a bit too small, on an otherwise LVM setup.
I’d recommend a Linux installer on a memory stick, instead. It’s bound to have less network lag.
Nah, it’ll be fine.
I might have a large enough USB SSD laying around some where. I could probably use that instead.
Does your FS support online resizing? EXT4 doesn’t, so you’d have to use an installer stick.
Be super careful about partition sizes. I once tried to shrink my FS to an exact size, then shrink the LV to the same size - it ended up corrupting my FS. After that time, I started undersizing the FS, then resizing LV, finally expanding the FS again.
Have backups.
Yeah. I mainly use btrfs; it supports online growing and shrinking.
I know. I have done plenty of same device partition resizing. I know the pit falls, and for safety shrink the FS to below what the LV is going to be.
Thanks for the reminder. I’ve been meaning to set up snapshot backups for this machine using rsnapshot as an experiment. I mainly use Dirvish
I use rsync with a custom shell script to manage the number of incremental copies. You’ll probably prefer something less janky.
That sounds pretty much like what Dirvish and rsnapshot do. Both wrap rsync.