mirror of
https://github.com/kuhyx/testsAndMisc.git
synced 2026-11-10 22:47:02 +01:00
Krzysztof kuhy Rudnicki
4f2b0ccdf7
Two levels of pure taxonomy carrying no information, and a 2-directory
cap leaves no room for them. Categories now sit directly under
linux_configuration/: features, fixes, utils, misc, fresh-install,
installers, diagnostics, gaming, boot_recovery, periodic_background, lib,
meta, tests. A script's own lib/ and tests/ are exempt from the cap, so
those stay put.
Depth violations 248 -> 139; roughly 40 of the remainder are inside
digital_wellbeing and hosts, deferred until the guard-lib repoint.
The moves are the easy half. What breaks is every path that counted
levels, and three classes of it had to be found by resolving paths rather
than reading diffs:
- 52 relative `source` lines for lib/common.sh and lib/android.sh. The
correct prefix differs per file: 40 were ../../ and 12 were ../../../,
so a blanket replace would have fixed one set and broken the other.
- REPO_ROOT in 7 fixes/lib/tests harnesses and setup_syncyomi_guard.sh,
each walking up four levels from a directory now two levels shallower.
This caused a real regression -- the fixes suite went red with
"log_warn: command not found" -- caught by running it and comparing
against the pre-move baseline worktree.
- conftest.py's sys.path entries, which took the pytest gate down with
14 collection errors, and the `# shellcheck source=` directives, which
took shellcheck down with SC1091.
16 symlinks in $HOME broke, including the entire i3blocks bar. All
repointed, and cpu_monitor/memory/disk/time/volume were run to confirm
they emit real output rather than merely resolving.
Verified: 1798 tests pass at 100% coverage, 8 of 9 lib/tests suites pass
(the ninth needs the coverage jail, identically at baseline), pre-commit
is clean, and the two untracked secret configs are still ignored after
their gitignore paths changed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PJrqKERAo5QUeEHWS5Asgp
|
||
|---|---|---|
| .. | ||
| README.md | ||
| start-player2.sh | ||
Dual Steam Accounts (same PC, two monitors)
Runs a second Steam instance as player2 on HDMI-0, alongside your main session on DP-0.
Both accounts play simultaneously with full GPU acceleration — no VT switching needed.
One-time setup (fresh install)
1. Create the player2 user:
sudo useradd -m -G audio,video,input -s /bin/bash player2
sudo passwd player2
2. Install dependencies:
sudo pacman -S xorg-xhost
3. Add passwordless sudoers rule (allows launching Steam as player2 without a prompt):
echo "kuhy ALL=(player2) NOPASSWD: /usr/bin/steam" | sudo tee /etc/sudoers.d/player2-steam
sudo chmod 440 /etc/sudoers.d/player2-steam
4. Symlink the script into PATH:
sudo ln -sf ~/testsAndMisc/linux_configuration/gaming/start-player2.sh /usr/local/bin/start-player2
5. Start the getty on tty2 (needed if LightDM autologin is configured, otherwise tty2 has no login prompt):
sudo systemctl enable getty@tty2
Usage
start-player2
A Steam window opens as player2. Drag it to HDMI-0 and log into the second account.
Click whichever monitor you want to control — no switching needed.
To stop: close the Steam window or pkill -u player2 -f steam.
How it works
- Steam is launched as
player2viasudo -H -u player2 steamonDISPLAY=:0(your main X session). - Because
player2has a separate home directory (~/.local/share/Steam/), the two Steam instances don't conflict — different PID locks, different configs, different accounts. xhost +local:grants local users access to your X display.- Full GPU acceleration since there is no nesting — both instances hit the hardware directly.
Monitor layout
| Output | Resolution | Session |
|---|---|---|
| DP-0 | 3840×2160 | kuhy (main) |
| HDMI-0 | 2560×1440 | player2 |