What I get out of self hosting services: Full control of my data and something to tinker with when the fancy strikes.

Graphs? Monitors? Failover? I get enough of that shit at work. If it’s down then whatever: I’ll fix it when the inconvenience is too great to ignore. External users? I only invite people who understand that this is my hobby, not my job.

Calibre is an ebook library manager with a reader built-in. Koreader is purely reader software, and it works particularly well on touch and eink screens.

You nailed it. For me, the human-written stories were interesting because it’s not immediately apparent where they’re going. The prose evokes images and emotion, and I want to put the pieces together to identify the theme.

The AI stories blurt out the theme almost immediately, and then my attention wanes because there’s nothing left in the text except for a base retelling of events.

Why hew so closely to the “immutable paradigm” as if it’s a rule? I have a few packages layered on my system to achieve results that flatpak + toolbox cannot. Never had a problem with updates.

Can I leave all my drives connected, plug in a seperate SSD through USB, boot into Nobara live and install on that drive without it affecting my mint install?

Yes. Just double-check every part of the install process so you don’t write to the wrong device.

Also, if I do that will it put the EFI file on the seperate SSD?

Probably yes (depends on the options you pick during the install process). The external drive will get its own boot partition with appropriate EFI files. Then to boot from it, you would select the external drive in your UEFI.

I use rEFInd as my EFI bootloader: It lets me chain load other boot options (external drives) without touching my motherboard UEFI settings. I leave it installed to my main boot partition, but it scans for other bootable partitions at startup. Then it auto-populates a selector list of my main install, or whatever other external devices are plugged in. It can chain load GRUB, other EFI bootloaders, Windows, etc from these devices, so you don’t have to worry about compatibility with whatever bootloader the OS expects to use.

You said you don’t want the page to load. Do you even care if the browser opens?

What about overriding the default browser application that the terminal tries to use? Maybe there’s some env variable to override the xdg browser default, and you could point it to a script that exits instantly.

I agree with the person who suggested linking to Wikipedia articles.

For example, it’s not much help to learn that PCIe stands for Peripheral Component Interconnect Express, because nobody calls it that. As an outsider, now I’m wondering what a component interconnect is. It’s much more useful to link to a page that gives context about how PCIe is actually used.

There’s always decksight: https://www.crowdsupply.com/shade-technik/decksight

Based on your systemd output, it looks like the system is taking a long while to decrypt your drive. Is it a spinning disk, or an SSD?

I’m not sure if the PC repair shop specifically checked your drive, but it might be worth swapping out for another. Or maybe run some speed tests and/or diagnostics to see if there’s something funky going on.

You could also try an unencrypted install to see if the problem persists.

Looks like you’ve already had some help fixing your system. I’d recommend reading the arch wiki pages on encryption. Even if you’re not running arch, the wiki is a good source of up-to-date information, and contains many practical tips.

This section about setting up your /etc/crypttab to unlock a non-root filesystem at boot might be useful. Even if you don’t want to unlock at boot, it explains how crypttab works: https://wiki.archlinux.org/title/Dm-crypt/System_configuration#crypttab.

There’s another useful section if you want to decrypt on demand after boot: https://wiki.archlinux.org/title/Dm-crypt/System_configuration#Mounting_on_demand

Lastly, if you’re experimenting with fstab entries for a non-root device, consider setting nofail so that if you screw anything up the system still boots. This section is somewhat relevant: https://wiki.archlinux.org/title/Fstab#External_devices

Basically, you need both a crypttab entry and an fstab entry to open and then mount the device.

I set up a very straightforward Godot dev environment yesterday using toolbox which is built on top of rootless Podman.

• Create a new fedora toolbox
• Enter toolbox
• Install DotNet dependencies, git, etc with dnf
• Install Godot binary from release page
• Turns out there were other dependencies I needed
• Godot wanted a few Wayland libs on the container, so I installed Weston (maybe overkill)
• Godot wanted libxrandr so I added that too
• Godot just works ™

The nice thing about toolbox is that it uses my native host Wayland compositor. So whatever I have running in the toolbox can be interacted normally through sway (my host WM).

You can either distribute a container image with your given toolbox configured, or just document the setup steps.

You can host docker volumes over NFS, but the actual container images need to exist on a filesystem that supports overlay (which NFS does not) unless you want things to be slow as shit. And I really do mean miserably slow. A container image shared over NFS will take forever to spin up because it has to duplicate the entire container filesystem instead of using overlays, and then it’ll blow up your disk usage by copying all these files around instead of overlaying them. It’s truly unusable.

From that same discussion thread:

We plan on supporting any token/nft/coin for tipping, awards, curating, less captchas, etc. Each subplebbit owner should be able to create their own tokens or nfts to monetize their effort and incentivize their users to participate. Avatars will also be curated NFTs.

The protocol does not use blockchain for data, but the web service itself looks like it would use crypto and NFT to manage aspects of user identity, spam prevention, and monetary incentive.

There used to be a similar bug in the Roku jellyfin app.

If you can recreate the subtitle issue using test file 5 from this repo, it might be worth submitting a bug report. https://github.com/ietf-wg-cellar/matroska-test-files

Programmable condoms which make the user look like a bad dragon dildo.

I once had a directory in /tmp called etc which contained subdirectories for something I was migrating.

I thought that I was in /tmp when I ran rm -rf etc… I was actually in /

Look up the GPU on these charts to find out what codecs it will support: https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new

NVENC support will tell you what codecs your GPU can generate for client devices, and NVDEC support determines the codecs your GPU can read.

Then compare it with the list of codecs that your Intel can handle natively.

If you want to move your containers to a different location, look into configuring docker’s data-root: https://stackoverflow.com/questions/24309526/how-to-change-the-docker-image-installation-directory

You copy /var/lib/docker to a new location and update /etc/docker/daemon.json

I will say: Moving data-root to an NFS mount isn’t going to work well. I’ve tried it, and docker containers rely on filesystem features to run their overlays. On an NFS, this feature isn’t present, so your services will duplicate the container’s entire filesystem. This will tank your performance and is basically unusable for anything but trivial examples. Docker data-root basically needs to be a “physical” disk.

I’ve had no issues using NFS shares mounted as docker volumes. It’s just the data-root where it’ll fail.

If you’re doing it from scratch, I’d recommend starting with a filesystem that has parity checks and filesystem scrubs built in: eg BTRFS or ZFS.

The benefit of something like BRTFS is that you can always add disks down the line and turn it into a RAID cluster with a couple commands.

Yep, the problem was that docker started before the NFS mount. Adding the dependency to my systemd docker unit did the trick!