Is this honestly how simplistically you see the world? You think that is analogous to what people are saying? Amazing.
Carney already told Trump to pound sand on the “Board of Peace”.
My distro is based on MUSL. I seem to remember finding something that would not build on it but I do not recall what that is. In addition to the thousands of packages I am using, I have compiled hundreds of applications. Compatibility is very high.
Certainly it is clear the “most applications” work with MUSL.
That is, the source code does.
gcompat is when you want to run something that is already a binary that wants to call into Glibc. I try to avoid that so I cannot comment much.
There is the odd time I have had a binary built for Glibc that I could not avoid. For example, bootstrapping .NET or the version of vcpkg that the Ladybird browser uses in its build system. To be honest, in those cases, I just reach for Distrobox and drop into a distro that has Glibc natively, like Arch. Or I might use a RHEL Distrobox for a commercial binary meant to target that distro.
Clearly running a binary without one of the dependencies it was built against is a problem no matter what library you are taking about. But if we are just asking what works on MUSL, I would say almost everything.
They already have the refineries they need for Venezuelan oil. They are processing Canadian oil now.
This frees the US up from relying on a northern neighbour that won’t do what they are told.
Canada better get started diversifying.
Almost everything you care about should be in /home so back that up. Many people keep it on a separate partition or drive to make changing distros (or reinstalling the existing one) easier.
Most of your system config is in /etc so you may want to make a copy of that too.
But the proper process on Linux is not to re-install. It should not be necessary.
On top of this, part of the reasons to use containers is that you can create and destroy them at will while leaving your host tidy and stable. I use Distrobox quite a bit for this reason.
If you install a kernel from the Arch repos, DKMS will build the kernel module for you automatically as well as the initial RAM disk and boot entries. Kernel upgrades take a little longer but you do not have to do anything manually.
It will work with custom kernels too but, if you do build your own kernel, you have to make sure a couple of options are selected.
Distrobox changed the way I use Linux. I cannot imagine going back.
First, you are exactly right that it allows you to separate app repo from the rest of what you live about a distro.
I use an Arch Distrobox with every machine. Using Chimera Linux that uses MUSL, Clang, libc++, and BSD userland? Install anything from the Arch repos or AUR in seconds.
But it is not just package repo size. Using an app that targets RHEL? Install it from a RHEL Distrobox.
Doing dev for a project whose users are Ubuntu people? Build it in an Ubuntu Distrobox.
Want to try something and do not want it to mess up your system? Do it in a Distrobox.
Need some software for a class that will just be cluttering up your system after? Make a Distrobox for that class.
I have a .NET Distrobox. I have a Java Distrobox. Just not having to update the IDE and frameworks all the time is a huge win.
Mature application that I use every day that I do not want to change or break on me? Install from a Debian Distrobox.
Rapidly developing app where I want the latest for features and fixes? Install from an Arch Distrobox.
Tools you like that only Mint offers? Install a Mint Distrobox.
Distrobox is the greatest.
The Debian safety net is not to use third-party repos at all.
It has nothing to do with Rust. Permissive licenses are more popular with new projects. Rust is more popular with new projects.
The stats show that people are more likely to be attacked by a shark on days when they had ice cream. Eating ice cream does not make you more likely to be attacked by a shark. They are just both things that happen at the beach.
I love Haiku but this is a reasonable question
Santa lives in Canada. You can send him mail and he will reply.
https://www.canadapost-postescanada.ca/cpc/en/our-company/write-letter-to-santa.page
LeFantome
0 post score0 comment score
I hope they do not take their foot too far off the gas before completing their Wayland transition.
Once KDE, GNOME, COSMIC, Budgie, and Cinnamon are all Wayland, 90% of all Linux desktops will be Wayland. With XFCE, it could be 95%.
I am looking forward to essentially all Linux desktop users being on Wayland so we can stop acting like it is not already the norm or even pretending that it is not going to happen. I am looking forward to putting it behind us and we are so close.
At the same time, I have a lot of respect for conservative desktops like Cinnamon and XFCE that, while acknowledging that Wayland is the future, are taking great pains to minimize disruption for their current users and even to allow users to keep X11 as a fully supported platform. I am all for that.
I do not expect Cinnamon to maintain X11 as an option very long after they switch to Wayland as the default. First while many distros ship Cinnamon, it is really a product of the Mint project and Mint is very much a Linux Desktop. Second, Mint does not have the resources as they point out in this article. Of course, I could be wrong.
XFCE will probably keep X11 around much longer. First, XFCE is very popular in non-Linux settings. But mostly I say this because xfwm4 itself takes very little dev effort and it is the only XFCE component really tied to x11. Xorg is essentially in features freeze. As long as XLibre does not break everything, xfwm4 will just continue to work. The other components of XFCE work fine in both environments already. The goal of xfwl4 (the XFCE Wayland compositor) is to mirror the xfwm4 experience. And xfwl4 is deferring to other components to define behaviour (eg. xfsession and xfdesktop). So, it should be easy to keep the overall XFCE experience in sync on both display servers without much wasted effort.