If ambient noise is a concern, I’d go with an SSD. If money is tight, an HDD will give you the best value.

My server is in an otherwise quiet home office/sitting room, so I went with an 8TB SSD (870 QVO). Spinning disks make a fair bit of noise just waking up, let alone the actual file operations.

You should be able to layer the xdg-desktop-portal-gnome package, which will also pull any dependencies.

To answer your general question though, yes I believe you can easily install at least minimal versions of each DE with little impact to rpm-ostree performance. They don’t need to be separate images, though that’s possible too by rebasing and pinning. I would just layer the necessary packages to load a GNOME environment (start with rpm-ostree install gnome-shell). This way everything stays up to date with the active image. For example, I’m running GDM under Kinoite simply because I was having unresolvable issues with SDDM and LightDM.

Pinning separate images would require you to rebase with each image update and then unpin/pin the old/new images…too much work.

NUC 8i5, 32GB, 500GB NVMe (host), 8TB SSD (data), Akasa Turing fanless case, running Proxmox:

• samba
• syncthing
• pihole
• radicale
• jellyfin
• minidnla

I also have a Pi 4 running LibreElec for Kodi on the home theater. Nothing fancy yet and it more than meets our current needs. Most maintenance done over SSH.

Would like to eventually get a proper web and email server going (yes, I know).

Haha, oh I know and I’m all for trying things for the fun of it! Just wondered if there was a practical benefit of such a setup.

Interesting endeavor…any practical benefits? I would think that even a slow USB 2.0 drive would provide better performance than a cloud-based file system.

Craigslist is still superior in the PNW, at least in my experience.

I’ve enjoyed seeing some of these blasts from the past, but I admit it’s not as nice when the VM host window is captured as well. Just something to consider… I appreciate it all the same.

Completely anecdotal, but I generally find more success with servers outside of North America. Definitely helps with reddit and imgur.

A gecko is a lizard, so it’s in keeping with SUSE’s chameleon theme. Maybe a little too similar for corporate.

I think Komodo Linux, or KomodOS are good options too, but I can’t recall if they were already used for a distro.

Off the top of my head…

• Gecko or GeckOS
• LizOS
• ReptilOS
• ChamelOS
• KomodOS

Me too! I can’t recall now why I parted with it, but I wish I hadn’t. Would love to see what it could do today.

If that’s one of those old 10" netbooks, I had good experiences running dwm and xmonad on mine back in the day (had an Acer and later an MSI Wind U120(?)). Typically ran all my apps maximized, one per desktop. Firefox did okay, but this was around 2010-2012. Mostly stuck with terminal apps and it was more than snappy enough.

Some screenshots from days past…

See my follow-up post elsewhere here. Sounds like you might not have an always-online device to keep others always synced, and/or the devices you’re using to add entries aren’t online when you do. Might consider using a designated device for database modifications.

That used to happen to us before we started using SyncThing (and before we had data plans on our phones).

By the time we migrated to it, we had a home server running 24/7 and this ensured that at least one device in the chain was always online, had the latest version of the database, and pushed it to other devices as they came online. Our phones also have data plans now, so things generally sync in realtime which helps avoid issues.

If you don’t have at least one always-online device, I think the next easiest way to avoid sync conflicts is to modify the database from one designated device. That way even if a conflict does arise, you’ll know which device is always correct.

For resolving the conflicts, I would open both databases, sort by modified, and review the latest changes in each.

KeePass, and more specifically the KeePassXC (desktop) and KeePassDX (Android) ports.

My wife and I have shared a single KeePass database for about 15 years now and I couldn’t imagine switching to anything else.

My reasons have remained the same over the years:

• Free and open source
• Offline (but supports cloud sync)
• Lightweight
• Cross platform
• Supports autofill

I would never entrust the management of my credentials to a 3rd party online service. They’re an easy target (it’s only a matter of when, not if they are breached), and they could go out of business at any time.

We don’t use cloud storage for anything these days, but we keep the KP database (and many other things) synced across more than 7 devices using SyncThing, another amazing FOSS project.

It’s probably just familiarity bias, but I really like the classic 3D design elements of the '90s desktops. I was a big fan of the Windows classic shell, NeXTSTEP and Openbox UIs. And even though I think both GNOME and KDE look fantastic today, I would still happily use a CDE-style UI if I could do so consistently.

Felt like a pirate on the high seas! Those were the days…

I haven’t experienced that personally but Reddit’s Imgur has also cracked down on VPNs and many hosted pics and gifs will not load, depending on your selected server.

Yep, that’s the one. We use KeePassDX on mobile and KeePassXC on the desktop.

My wife and I share a KeePass database for all of our credentials, including the keys to our digital kingdom. I document our LAN design, server setup, and general maintenance notes, which are synced between all of our devices via SyncThing.

I add notes and quick instructions to the important credentials, like “See Proxmox.md to start this service”, or “This password decrypts our file server drive…to do this, open a terminal and paste the following…”

She is comfortable pasting commands into a terminal already, so if anything ever happens to me I am confident she or my son will at least be able to access our data and move it to a more user-friendly format.

Edit: Had way too many words lol