A bit of history. The first universal packaging format was snap by Canonical and used to be called Click apps and it was made for the Ubuntu mobile OS and later to the Ubuntu desktop. Red Hat in response to that created the FlatPak format. The AppImages are community effort. As you can see since both snap and FlatPak are developed and supported by a company they are more widely available and easier to search, install and update them. There are multiple tools for AppImages as well, which can search, install an update, however they are not pre installed or can be installed from the repo on most distro. There are dielstros which ship AppImage support by default with App Store for example Nitrux. You can use AppMan or bauh for managing AppImages. The AppMan has command line interface and bauh is a graphical application. Bauh can also manage snap and FlatPak.
As others have said, there’s Vanilla and Endless, but both use GNOME.
Is there a reason why it has to be Debian? With an immutable distro, you won’t be using traditional package managers anyway (like apt), all have the same stability factor, and with the same systemd + KDE, it’s more or less the same experience regardless of which distro you go for.
One of the key usage patterns of an immutable distro is using a container to install your extra packages. So you could go for a Fedora-based immutable KDE distro like Kinoite, and set up a Debian container where you can use apt and other Debian tools.
Depends on the use case. I played around with it a lot and came to the conclusion that I don't like flatpaks and the base system is not flexible enough for me.
I use it as a self-updating desktop for my parents tho,. For that it's absolutely perfect.
I was just going to post the same thing. I actually split downloading duties with a friend of mine when we both had 1 (or maybe 2?) hr / day on our ISPs.
We even used coloured floppies to colour code the package sets.
You’ll have ask the question of how important is this data, then before you start run drive diagnostic tool to see if all are functioning as expected, I’d suggest moving directories aposed to chopping anything up as to maintain some form of redundancy if a drive were to fail. It’ll be a long process. Hope it goes well
I personally (and professionally) use Debian/Ubuntu based most of the time. I’ve tried Fedora several times over the last few years, but it just never sit right with me, especially the package manager and how much it sticks to GNOME stuff, even with its KDE spin.
I’ve been trying to get into RHEL based out of curiosity.
Not anything to do with the LDAC codec but why does wireless headphones on windows suck. On linux (even a wm) I just turn on my headphones and it works, on windows every time I have to remove the device and add it back again
Bluetooth drivers and the firmware on devices suck. Modern Windows with Intel Bluetooth seems to work as long as your devices don’t do weird shit. Broadcom chips are often problematic as hell, sometimes requiring a reboot to work after disconnecting a device.
Linux Bluetooth audio was a struggle for years. Pipewire made it Just Work for me. It’s still relatively new, but I don’t have any complaints, unlike in the Pulse+BlueZ days.
I just wish they would use another name for it, it’s linux here no need to copy windows slang! Or use another color! (I hope they’ll update it to make it a customizable color)
Fun fact: The Windows BSOD colour was as easy as adding a couple of lines to a .INI file for a long time. Then, as they tend to do, they made it more difficult, but it was still possible. Third party tools were written to do the work.
Very recent MS Windows I have no idea about. My search-fu is failing me.
Anyway, my point is that the "two lines in a config file" method would be nice.
Knowing systemd though, it'll be "send some kind of message into a /proc pseudo-file", or a sub-sub-sub-command of one of the many systemd* commands which ultimately does the same thing.
As its name suggests, LogoFAIL involves logos, specifically those of the hardware seller that are displayed on the device screen early in the boot process, while the UEFI is still running.
Do people actually use LXD in production? All hosting services I’ve seen use LXC and not LXD for containers, as do UIs like Proxmox and Unraid, and you don’t have to use Snap for LXC.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.