Linux Setup Notes

Posts

Rawhide + KDE Plasma/Gear/Builder Stack Git!

There used to be a "Kinoite-nightly" image at https://gitlab.com/fedora/ostree/ci-test/-/pipelines that combined Kinoite Rawhide and KDE Git versions of Plasma and Gear based on COPR repos maintained by solopasha. However those COPR repos had not been updated in months and so the "nightly" version stopped being produced. Recently KDE developer silverhadch produced a nightly build of KDE Git versions of Plasma, Gear and a full developer stack based on Universal Blue's base image (no small amount of work to make that happen!). Recently he has migrated the base to the same base I'm using (quay.io/fedora-ostree-desktops/base-atomic:rawhide). His repo can be found at: https://github.com/silverhadch/fedora-plasma-canary I like using a Rawhide base (bleeding edge + bleeding edge!) and the "stock" Fedora base without the choices made by Universal Blue (i.e., Bazaar vs. Discover). I forked silverhadch's repo and layered on some additional packag...

Debian set up (using SpiralLinux as installer)

https://github.com/SpiralLinux/SpiralLinux-project (for Btrfs/Snapper set up) Disk creation: 1. Select Manual Partitioning in Calamares 2. Create the partition table (if starting fresh): ◦ Select your disk (e.g., /dev/vda) ◦ Create a new GPT partition table 3. Create EFI System Partition: ◦ Size: 1024 MiB (1 GB as requested, instead of 300M) ◦ File system: FAT32 ◦ Mount point: /boot/efi ◦ Flags: Set the boot and esp flags 4. Create Root Partition: ◦ Size: Remaining space (~79 GB) ◦ File system: Btrfs (since your setup shows multiple subvolumes) ◦ Mount point: / ◦ No flags needed 5. Configure Btrfs Subvolumes (if Calamares supports it): After creating the Btrfs partition, you'll need to set up subvolumes for: • @ → / • @home → /home • @root → /root • @tmp → /tmp • @log → /var/log • @snapshots → /.snapshots Install packages: sudo apt install -y...

KDE's Own Distro

For installation details see the Installation section https://community.kde.org/KDE_Linux#Installation and https://kde.org/linux/install/ Install homebrew: (do oh-my-zsh and powerlevel10k first so .zshrc modification by brew survives) /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" Install distrobox: curl -s https://raw.githubusercontent.com/89luca89/distrobox/main/install | sh -s -- --prefix ~/.local echo 'export PATH="$PATH:~/.local/bin"' >> ~/.bashrc echo 'export PATH="$PATH:~/.local/bin"' >> ~/.zshrc OneDrive: brew install onedrive # type onedrive to register/connect with your MSft OneDrive account brew services start onedrive-cli onedrive --force --skip-dot-files --skip-dir venv --sync NOW ON MY Kinoite IMAGE, so just initiate normally and then: mkdir -p ~/.config/systemd/user/onedrive.service.d cat > ~/.config/systemd/user/onedrive.service.d/override.conf <...

Raspberry Pi WOL via cable

Headless Raspberry Pi set up: https://www.youtube.com/watch?v=9fEnvDgxwbI curl -fsSL https://pkgs.tailscale.com/stable/debian/trixie.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null echo 'deb [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg] https://pkgs.tailscale.com/stable/debian trixie main' | sudo tee /etc/apt/sources.list.d/tailscale.list sudo tailscale up --ssh sudo pacman -S wakeonlan Making Wake-on-LAN (WOL) Persistent on Arch Linux By default, the ethtool setting for Wake-on-LAN does not persist across reboots on most Linux systems. To make Wake-on: g permanent for your network interface ( enp69s0 ), you have several reliable options: 1. Using a systemd Service Create a custom systemd service that sets WOL after the network interface is up: Create the service file /etc/systemd/system/wol@.service with the following content: text [Unit] Description=Enable Wake-on-LAN for %i Requires=network.target Afte...

Using rclone to integrate Google Drive in Arch

sudo pacman -S rclone rclone config # will need to set up secret key and client ID follow instructions mkdir ~/GoogleDrive rclone mount gdrive: ~/GoogleDrive --vfs-cache-mode writes --daemon # can also use following to run in background (nohup): nohup rclone mount gdrive: ~/GoogleDrive --vfs-cache-mode writes --allow-non-empty --dir-cache-time 1000h --poll-interval 15s systemctl --user edit --force --full rclone-mount.service add: [Unit] Description=RClone Mount Google Drive After=network-online.target [Service] Type=notify ExecStart=/usr/bin/rclone mount gdrive: %h/GoogleDrive --vfs-cache-mode writes --vfs-cache-max-age 1h ExecStop=/bin/fusermount -u %h/GoogleDrive Restart=on-failure RestartSec=5 [Install] WantedBy=default.target Enable: systemctl --user enable --now rclone-mount.service

Getting rtcwake working on Bluefin

#!/bin/bash # User systemd setup for auto suspend/wake on Bluefin #Please run these two commands manually: #1. First, create the sudo rule: echo "$( whoami ) ALL=(ALL) NOPASSWD: /usr/bin/rtcwake" | sudo tee /etc/sudoers.d/rtcwake-nopasswd #bash #2. Then set the correct permissions: sudo chmod 440 /etc/sudoers.d/rtcwake-nopasswd #bash #After you've run those commands, we can test if passwordless sudo works: sudo rtcwake -m show #❯ sudo rtcwake -m show #alarm: off # Create user service directory mkdir -p ~/.config/systemd/user # Create helper script for suspend + rtcwake mkdir -p ~/bin cat > ~/bin/rtc-suspend.sh << 'EOF' #!/bin/bash # Helper script to suspend and set RTC wake time # Usage: rtc-suspend.sh "wake_time_description" if [ $# -ne 1 ]; then echo "Usage: $0 'wake_time_description'" echo "Example: $0 '15:00 today'" exit 1 fi wake_time="$1" wake_timestamp=$(date -d ...