Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)K
Posts
2
Comments
98
Joined
3 yr. ago

  • Can attest that Folder Sync is excellent. I use it all day (in the background) for two-way sync (notes) and backup of photos videos etc

    Though a small PSA on setting up:I once set up a new share on a new phone with two-way sync, and the app decided to sync the (newer) empty directory to the server (i.e. delete everything) instead of pulling the files from the server to the phone.Easy fix: Restore notes from backup (step 0: have backups in the first place), then do an initial 1-way sync from server to phone, then change the sync job to two-way.

  • LTS gang rise up ^^

  • Well today I learned.I didn't think "third party" like homebrew would be preferred over ostree-rpm, but makes sense that you shouldn't change too much from the tested main image.

    For anybody else, here's the exact caveats with rpm-ostree: https://docs.bazzite.gg/Installing_and_Managing_Software/rpm-ostree/#major-caveats-using-rpm-ostree

    Personally I mainly used it for fcitx5 language input method some years ago, but I see now that fcitx5 is included in Bazzite, and also that it should work as a flatpak or in distrobox, https://github.com/ublue-os/bazzite/issues/2996

  • Do you happen to dual boot to Windows when at school, and live 8 timezones from Britain? Linux by default stores the hardware clock in UTC (and concerts to local time on the fly), while Windows stores the hardware clock in local time.

  • Do you version your compose files in git? If so, how does that work with the dockGE workflow?

  • I highly recommend you use Proxmox as the base OS. Proxmox makes it easy to spin up virtual machines, and easy to back up and revert to backups. So you're free to play around and try stupid stuff. If you break something in your VM, just restore a backup.

    In addition to virtual machines, Proxmox also does "LXC containers" , which are system level containers. They are basically a very light weight virtual machine, with some caveats like running the same kernel as the host.

    Most self-hosting software is released as a docker-image. Docker is application level containers, meaning only the bare minimum to run the application is included. You don't enter a docker container to update packages, instead you pull down a new version of the image from the author.

    There are 3 ways to run docker on Proxmox:

    • Install docker inside a virtual machine (recommended).
    • Install docker inside a LXC Containers (not recommended because of various edge cases)
    • Install docker directly on the Proxmox host (not recommended for various reasons).
    • (There is ongoing work for running docker images directly in Proxmox, this is in beta/preview since Proxmox 9.1).

    The "overhead" of running docker inside a VM on the host is so negligible, you don't need to worry about it.

  • I had never heard of dockge before, but this sounds like the killer feature for me:

    File based structure - Dockge won't kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal docker compose commands

    Does that mean I can just point it at my existing docker compose files?My current layout is a folder for each service/stack , which contains docker-compose.yaml + data-folders etc for the service. docker-compose and related config files are versioned in git.I have portainer, but rarely use it , and won't let it manage the configuration, because that interfered with versioning the config in git.

  • For keyboard, if you're still having trouble, you can try connecting from the terminal with the command bluetoothctl . Terminal commands often tell you more details than GUIs about why things failed.

    Regarding distributions, you are on Bazzite, which is an immutable distribution, meaning the root file system is read-only. That makes it a bit different from "normal" distribution. The upshot is that most things should just work and the system is harder to break. The downside is that you sometimes have to jump through more hoops and do things differently from "normal" distributions when you want to do some deeper level tinkering.

    If you search for "How to do X in Bazzite" you might get fewer results because Bazzite is relatively new and niche (though growing quickly).If you search for "How to do X on Linux" you might find that the steps don't work because you're root filesystem is read-only.So sometimes you need to search for "How to do X on Silverblue" , because Bazzite is (sort of) based on Fedora Silverblue, which is the immutable version of Fedora distribution.

    If you want to install some software that you can't find in the app store (Flathub) or as AppImage, your next step is to look up the command rpm-ostree. It layers new software on top of your read-only root system. Changes from rpm-ostre take effect on the next reboot

  • The arch wiki is indeed excellent

    It can get very in-depth though, sometimes more so than you need when just starting out learning Linux. So try not to get overwhelmed by it, OP :)

    Also OP, since you're on Bazzite, you should know that that Bazzite is an immutable distribution, meaning your root file system is read-only. So some of the "advanced tinkering" with system files from arch wiki or random forum posts won't work the same way.

  • Improvements for Input devices (particularly stylus and drawing tablets, but any kind of input) is one of the 3 overarching "goals" of KDE at the moment

  • The article introduction is gold:

    In the unlikely case that you have very little RAM and a surplus of video RAM, you can use the latter as swap.

  • I'm using NixOS with KDE for HTPC, though I'm not sure I'd recommend it unless you're eager to learn Nix.

    The upshot is that it's super stable, and everything is declared and versioned in the git repo, including my lirc device codes and node-red automation flow for lirc and mqtt. (The HTPC shows up as a mqtt switch in home assistant for turning on and off, and the HTPC turns on or off the TV and amplifier through IR as the PC turns on or off)

    I mostly use Firefox and various streaming sites for video, and Spotify desktop client for music. A gyro mouse/keyboard is the main input device, plus wireless Xbox360 controllers for streaming games with Moonlight (from Flathub)

  • That's hilarious :D

    What It ISA real DOOM port - Uses the actual DOOM engine via doomgeneric, playing real levels with real game logic

    What it ISN'T:...A practical use of your PCB editor - This serves no purpose other than being delightfully absurd

  • Ugh indeed! Discord is an information black hole, where information enters never to be found again by search engines or even its members

    I can understand replacing IRC with Discord, but using Discord as a forum is madness

  • The other day i necrod a nearly 3 year old forumthread with some new information. A few hours later the person from 3 years ago came back and thanked me because the new information helped them. Sometimes nercomancy is good :)

  • That's awesome :) I hope they'll ship a more up-to-date nix than Ubuntu. The nix-bin deb package in the Ubuntu is so old it's better to install nix from the official installer or Determine Systems installer

  • Thanks for sharing! TIL about autofs. Now I'm curious to try NFS again.

    What's the failure mode if the NFS happens to be offline when PBS initiates a backup? Does PNS try to backup anyway? What if the NFS is offline while PBS boots?

    EDIT: What was the reason for bind mounting the NFS share via the host to the container, and NFS mounting from NAS to host?I did the NFS-mount directly in the PBS. (But I am running my PBS as a VM, so had to do it that way)

  • I run PBS as a virtual machine on Proxmox, with a dedicated physical harddrive passed through to PBS for the data.

    While this protects from software failures of my VMs, it does not protect from catastrophic hardware failure. In theory I should be able to take the dedicated harddrive out and put it in any other system running a fresh PBS, but I have not tested this.

    I tried running the same PBS with an external NFS share, but had speed and stability issue, mainly due to the hardware of the NFS host. And I wasn't aware of autofs at the time, so the NFS share stayed disconnected

  • In Danish and Norwegian the equivalent idiom is to "Swallow a camel" which sounds much funnier xD