No description
Find a file
2026-06-19 14:02:15 +02:00
backup-scripts Add backup-scripts/appdata-backup-quintus.sh/README.md 2026-06-19 14:02:15 +02:00
check-mkv.sh Upload files to "check-mkv.sh" 2026-06-02 22:51:47 +02:00
sanitize_filenames.sh Upload files to "sanitize_filenames.sh" 2026-06-04 17:25:41 +02:00
show-arm-progress.sh Upload files to "show-arm-progress.sh" 2026-06-04 17:07:27 +02:00
start-screen-scripts Upload files to "start-screen-scripts" 2025-07-19 23:57:38 +02:00
sync-scripts Update sync-scripts/sync-music-to-cl-mbp-035.sh 2026-06-15 16:37:12 +02:00
tools Update tools/cpu-temperature-alarm.sh 2025-09-07 16:35:06 +02:00
transcode-via-amd-gpu.sh Upload files to "transcode-via-amd-gpu.sh" 2026-06-04 17:52:41 +02:00
podman-guide.sh Add podman-guide.sh 2025-07-18 15:35:30 +02:00
README.md Update README.md 2026-06-08 21:50:35 +02:00

linux script collection - aus dem hause wiotte

A collection of shell scripts for Linux. Mostly small, single-purpose tools I use day to day.

Layout

  • Standalone scripts live in the repo root — one .sh file, self-contained.
  • More involved scripts get their own folder named after the script, with a dedicated README.md explaining usage, dependencies, and options.
.
├── some-script.sh
├── another-script.sh
└── bigger-tool/
    ├── bigger-tool.sh
    └── README.md

If a script has its own folder, check the README inside it for details.

Usage

chmod +x some-script.sh
./some-script.sh

Read the top of each script (or its folder README) before running — some expect specific arguments or environment.

Platform

Written for and tested on Linux. A few scripts happen to also work on macOS, but that's coincidence rather than intent — no guarantees, and macOS-specific behaviour isn't maintained. If a script is OS-specific, most of the time its noted inside comments of the script or inside the script-README.