No Xorg also ships with up to date distros like Debian, arch, Ubuntu, etc but several of them have switched to using Wayland by default. It is deprecated because it is no longer actively developed and only maintained by a small group of devs and even that because these devs work for companies like Red Hat, Oracle, etc who have a vested interest in fixing those bugs
Follow the blogs for Year of the Voice initiative from Home Assistant. There will be lots of pointers for the journey they’ve taken this year getting TTS and STT working for HA.
Debian Sid should be fine. I wouldn’t go with Stable − too old.
Personally, I’d go with the Flathub version of Steam and not pollute my main system with 32bit libraries Steam required for backwards compatibility. With the 32bit dependencies as Flatpak Runtimes, the main system stays clean.
Fedora Silverblue and Linux Mint Debian Edition are my goto distros atm. Have not had issues with either, they’ve been great out of the box. Fedora Silverblue requires relearning a few things however, being very container oriented.
i went cold turkey when i got that early, free upgrade from win7 to win 10. after a week of win 10 and unable to downgrade back to 7. Bam. i became full time linux at that moment.
That can be done, but as others mentioned, if you don’t have permissions/other attributes for the files it’s going to be a real PITA to get everything working. If I had to do that I’d just copy over the files, chown everything to root and then use package manager to reinstall everything, but even that will most likely need manual fixes and figuring out what to change and to what value will take quite a bit of time and complexity of it depends heavily on what you had running on the host, specially things under /var.
If even file owner is not preserved (it is not always root, espetially in /var), you likely lost files’ extanded attributes an, maybe, also permissions. Without them your system won’t work normally.
Then, contents of these directories must be consistent with other ones. E. g. /var contains a package manager data about packages you installed. If you installed/removed anything after creating a backup, information about this will be lost.
If you created the backup while system was working, some files (espetially under /var, again) could be changed during that process, and this also makes such backup unusable. Every sysadmin knows that to create a database backup by copying files, dbms must be stopped.
In future, think about restoration before planning a backup and test if this possible immediately after it is done.
I think the easiest way is to take them from the ‘experimental’ branch of debian’s own repository. But read about the consequences of enabling experimental, first.
Quoting the Debian FAQ:“project/experimental/: This directory contains packages and tools which are still being developed, and are still in the alpha testing stage. Users shouldn’t be using packages from here, because they can be dangerous and harmful even for the most experienced people.”
Yeah, you’re right. If you absolutely need the latest NVidia drivers, you kind of have to choose between the devil and the deep blue sea. You can pull it from some random place on the internet, or use whatever script NVidia provides you with and do it under your own responsibility… Or use experimental, but it may be not be tested or be incompatible with your kernel version. Neither option is recommended. I’ve had some success with experimental. Debian have high standards and at least it’s packaged and tied into the distribution at all. But there is no guarantee. (I’m not sure if you can mix that with the stable version of Debian, though. I use Debian Testing…) (Their Backports are a better option for Debian Stable.)
Maybe somebody else has an idea, I don’t know any better way to do it. The proper way is to wait until it’s tested and becomes available in Debian.
I don’t know when that’s going to happen. It usually takes quite some time with Debian. Probably some more months. You can have a look at the Package tracker
You can use distrobox to run ubuntu on fedora and fedora on ubuntu.
Imo the difference isn’t too big. If you know what you do, your system will look roughly the same on ubuntu and fedora. Same packages, same workflow etc.
If you keep the base packages constant, i.e. with a immutable distro, you can compare it much better, imo. The experience on Fedora silverblue and opensuse microos will be almost the same for the usual end user. Both are immutable systems, you install packages via flatpack, command line tools via distrobox. System keeps itself up to date. One is standard release, one is rolling.
Flatpak and distrobox offer sandboxing and reproducibility. Imo you want both on a regular install as well which almost make a traditional install like an immutable system, yet you are not as discouraged from installing packages onto the base layer.
If I’d be asked what the difference between fedora and ubuntu is, then I’d say the company behind it from which you get tech support. That’s mostly it.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.