deleted by creator

The built-in rollback functionality doesn’t hurt either.

More than that I think it’s a prerequisite for doing this.

You could self-host a shared “source of truth” git repo that you access over ssh. That can be anything from a USB thumb drive, a small clean server or a container on your existing desktop with ssh access, to an entire Forgejo deployment. Then you only need the “secret zero” of an ssh key to get everything set up and syncable.

If fresh setup is more common, you probably have other parts like package installation and network configuration that you also want to automate. Enter configuration management like ansible or salt, image builders like packer or archiso, “immutable” solutions like Nix or rpm-ostree. Once you get there you typically manage that in git anyway and you could put your dotfiles repo as a submodule and copy them over as part of OS setup.

If it’s just for once in a blue moon, manual ad-hoc copying gets you pretty far.

No matter how you slice it I think you have to either frequently spend time syncing changes or just accept the drift and divergence between machines and the sources.

Wishful thinking and stretching the definition beyond meaningfulness with regards to your conclusion. Lies, damned lies, and statistics. Don’t delude each other.

Still, I’ve believed for a long time that the tipping point with an increasing trajectory is around 5% so pretty optimistic about recent trends.

It’s been continuously improving. There are devices that are a hassle but you’re a lot more likely to have things Just Working compared to a few years ago.

My understanding is that Ampere and others should run perfectly like any old x86 with a normal dist like vanilla Debian mostly due to a lot of hard work from individuals in the wider community.

Much of the time, dtb (device tree) and device drivers are what it comes down to.

For more estoric or finicky hardware, I think the dists with the best ARM support are Armbian, OpenWrt, and PostmarketOS.

Jeff Geerling has been reporting a lot about his experiments. https://www.jeffgeerling.com/

I wrote about getting Debian running on a device based on a popular Rockchip SoC last year. I assume the kernel situation has improved since trixie. https://blog.kumio.org/posts/2025/01/bananapim7-hvm.html

Try running it on something like an older Celeron, a RaspberryPi 3, a PinePhone, or a constrained VM. For me alt+tab can take seconds on GNOME but still be almost instant in Xfce on the same hardware.

I assume it’s from Wayland not performing as well on these platforms combined with fancy animated transitions being enabled by default on G.

It can be about not having to change hardware as much as about habits.

This community is funny.

From what I can tell this is is basically the spiritual evolution of Bazzite, by the same team and built with a similar approach. Yet look at how differently they are received.

Brand identity memes are truly impactful these days. Names and presentation seem to drive majority sentiment.

Remember Serverless? Servers all the way down.

INTERMEDIARY BUILD LAYERS WERE NOT SUPPOSED TO BE GIVEN NAMES

DAYS OF REBASING yet NO REAL WORLD USE FOUND for building on anything above fedora:atomic

Wanted to base your image on someone elses anyway to save some work? We had a tool for that, it was called “FORKING”

“Distroless is built on GNOME OS” “error: /Tree contains both /etc and /usr/etc” - Statements dreamed up by the utterly Deranged.

LOOK at what Devs have been demanding your Respect for all this time, with all the servers and window managers we built for them (These are REAL distros, done by REAL devs)

https://github.com/ublue-os/bazzite-firmware-nonfree/commits/bf835aec77e3af803acceffb789f8fb076fd779c/

https://github.com/ublue-os/akmods/commit/70af39999c681566bd1c66f23834daa37b996aaa

https://github.com/ublue-os/main/pull/771

“Hello I would like 1.8 pixels please”

They have played us for absolute fools.

On nginx, most of the upstream work on new features is in Nginx Plus, not benefitting free nginx. Several nginx devs have been disagreeing with the way this has been done and the way the project is being managed and left to work on forks. People who agree with the OP sentiment should look into freenginx and angie.

https://www.phoronix.com/news/Nginx-Forked-To-Freenginx

https://mailman.nginx.org/pipermail/nginx-devel/2024-February/K5IC6VYO2PB7N4HRP2FUQIBIBCGP4WAU.html

https://en.angie.software/angie/docs/

http://freenginx.org/

Your initial instinct was right, you do want to auto-apply security fixes.

unattended-upgrades does allow you to configure this somewhat.

You could try this https://feddit.online/post/1359926#comment_6688858

Doesn’t sound like this is screen blanking as it happens during use but to rule it out you could temporarily disable that with xset -dpms and xset s off on X11. https://wiki.archlinux.org/title/Display_Power_Management_Signaling#Xorg

Right, there’s the immutable root aspect. Guessing the other answer you got fills in the missing piece there and that Silverblue perhaps mounts the system flatpaks on a different r/w filesystem than the read-only /. Check output of mount to see.

At the end of the day it’s up to you if you prefer to keep the system clean and run flatpak unprivileged, or centralize updates under root.

The one catch I can think of with flatpak --user is that it obviously won’t work if /home is mounted with noexec, which is otherwise a good security measure (and IMO not doing that defeats a lot of the security wins of immutable distros). Unless you apply the same mounting strategy to the flatpak xdg user dirs, which is certainly an option but not something everyone will bother with. But then again maybe that’s exactly what you want anyway to make your Flatpak installations smoothly portable across distros.

BunDGiE LiNuxXx 🤪

There are some bug fixes that are relevant for installs and base images. For example, security update in GPG is probably not a big deal for you but might be for someone building and pushing things from these.
Kernel, firmware and microcode updates might only affect a small minority of users depending on hardware.

Internet should work if i disable the vpn app though, so idk what’s wrong there.

I don’t suppose you enabled the kill-switch feature?

https://mullvad.net/en/help/using-mullvad-vpn-app#temporarily-blocked-internet

No errors or output from the add?

I don’t see anything wrong in what you are doing assuming you have permissions but if it’s just for your user you can flatpak --user to install in your homedir instead of system-wide.

Also convenient for distro-hoppers as you can just share or copy the flatpak dirs between home directories so you don’t even have to redownload for every reinstall.

I adored Budgie precisely because it was still on X11 🥲

Anyway, for a relatively simple and clean holistic GNOME-that’s-not-GNOME, it’s a very polished desktop. Worth checking out for your F&F.

The need to think about and deal with snaps is the reason I don’t recommend Ubuntu to noobs in general. It’s confusing and unnecessary and adds to the frustration of being forced to make judgement calls about things you don’t want to understand just to do your thing (we have enough of that as it is). And if you do decide against snaps, it’s a bit of an uphill battle and it’s easy to start feeling that the OS, like what they came from, is antagonistic. Canonical decided to isolate and take control of part of the Ubuntu ecosystem with snaps and that has made the distro a bit more niche compared to before.

For better or worse Ubuntu is also known to be on the edge with new developments on the desktop. Switching to new shiny desktop environments between major versions, being very early on Wayland-first, etc. Having to learn new OS UI after an upgrade is not ideal if you are not an enthusiast.

Other than that, Ubuntu can be a fine distro, both for server and desktop. If you either accept the particularities like snaps or know how to work around them, it can be a very good experience and it’s well-maintained in general. But it’s less of a no-brainer and more situational if it’s appropriate or not.

Like Alpine or Gentoo: Great distros but for different reasons not anything I would recommend a non-technical Linux virgin to replace their Windows or macOS with.

Good first distros for beginners:

• Linux Mint Debian Edition
• EndeavourOS
• Debian
• Pop! OS
• Fedora Workstation

Not Good first distros but still getting picked up by people who don’t know:

• Manjaro
• Ubuntu
• Omarchy
• Zorin
• Garuda

Everyone: If you’ve only used one of the latter, try another distro before you believe “Desktop Linux is not ready” or “Linux is not for me”.

Specifically on Steam: Which hardware you run on can affect on which distro it runs out of the box on and if you need to fiddle with drivers and firmware or not to get things running smoothly. There is also some difference between installation methods (some people swear by the flatpak version and others swear off it).

Maybe also check the health of your SSD and that your firmware/BIOS are up to date.

In this case they are apparently fine with a personal computer being used

Where? Looks ambiguous. From all we know this is a work computer provided by the employer. It’s more likely to be an oversight or deprioritized/neglected.

which makes RDP actually a slightly more secure solution

I do not see how that folllows.

If both the company and employee are indeed fine with the RDP, it should be no problem to get that confimed from IT in writing.