I’ve used Manjaro for a while and my system broke twice in that time just by updating my system (And with “broke” I mean it didn’t boot anymore). Then I switched to EndeavourOS and I haven’t had that issue once. Been using that for over 2 years now.
What I’m missing from wayland, it’s not really something from wayland itself. Examples are several needed electron based applications, which some will refuse to properly work (for meetings, desktop sharing, etc), wine, gtk4 applications not respecting GDK_DPI_SCALE (not sure if already addressed) when not using gnome (wayfire being used as compositor), no proper support for conky (or eventually equivalent wayland functionality) yet, and several nuances with waybar, and some other tools. Major issue is my work dependency over some non floss electron binary blobs, like teams, slack, and so on, which particularly for desktop sharing and meetings don’t yet work properly, no matter the electron options one can use for them, and some floss I use like signal, freetube, jitsi. Wine has a horrible hack, which I might live with, but it’s horrible…
So I’ll have to wait further for non wayland stuff to truly support wayland, and it has taken ages for that to happen, :(
I haven’t tried labwc, andit sounds interesting, though I don’t like openbox configs, and I really love fluxbox ways, which are also text files, but I never got used to openbox configs, perhaps just because I got way too familiar with fluxbox, which is what I use with Xorg (fluxbox + picom + tint2 + conky).
GTK does not use env vars for configuration, those are for development. There are some GSettings that control scaling like org.gnome.desktop.interface text-scaling-factor.
The env var works fine on Xorg though. And yeap, several applications need to catch up. That’s what I meant when I said it’s not wayland fault itself. However it’s been years things have been trying to catch up. Every now and then I try, but a couple of months back I couldn’t routinely use wayland, given all missing functionality plus additional nuances… The hard part is that if not using gnome, or plasma for that matter, getting things working take a lot of time, just to find out some things, I depend on for work, don’t work yet. At any rate, I still pay attention as well, to forums like this, to see if there’s some news that might trigger another retrial…
It is part of their kernel. And there are a few different schedulers at play, you have the CPU one as well as the I/O one. Arch Linux has various different kernels (such as the zen one) that use different CPU schedulers (with lots of options in the AUR as well) and there are various settings you can tweak for different I/O ones.
I general you should go through the Improving performance wiki page on the details for these and even more performance tweaks you can do.
There is also pages for tuning things for better battery life for laptops as well that you may also find interesting.
Faster here has many different meanings. The tests in that benchmark are more batch processing tasks. But that is not the only measure of speed. Zen I believe is more tuned for desktop use and keeping the system in a more snappy state which comes at the cost of some raw throughout performance. There is forever a tradeoff between latency and throughput, optimising for one is generally done at the expense of the other and both are optimising for performance, just different kinds.
I only mentioned zen as one of the official alternative kernels that is worth a look at though, making no claims as to if it the best for anyones particular workloads.
This is why it is best to do your own benchmarks for the stuff you care about and pick the best solution for your situation.
Arch wiki to the rescue. I swear the forms of arch Linux must just be riddled with references to the wiki. Eventually I’ll learn that it just knows. Thanks for the response.
Aren’t you sorta trusting whoever wrote any package you install with root? I mean, you should have that attitude anyhow as packages have a huge attack surface so privilege escalation bugs are way more common than remote execution but still, flatpak and snap at least offer a bit of a sandbox which might improve…
Depends on your distro and what’s available in the repo. With default repos you’re more trusting the distro developer to vet packages.
I trust debian for that. It’s been a while since I used Ubuntu so I don’t remember how their repos are set up but the debian team is notoriously conservative with their repos.
The track record has been very good as far as i know with thousands of packages over the years so I doubt if there is a real problem to be solved here.
APT is not good at managing dependency hell. This is a common problem for all package managers that don’t typically bundle dependencies. You can get 30000 open source packages from trusted sources having a maintainer working on each to all share the same dependencies for an OS release. That’s what Debian does. However it’s a lot of work and that works increases significantly when you try to do it for a piece of software across OS releases.
Read - it’s difficult for LibreOffice or Mozilla to ship a new version of their software that works on several Debian or Ubuntu releases. It’s also difficult for maintainers to do that.
You could of course include dependencies in debs, but then you’re increasing the security attack surface of the OS, because there’s no sandbox around those bundled dependencies. Bundling dependencies requires sandboxing to be safe. Otherwise whenever there’s a security hole in one library in package X, package X might patch it, but the same library might exist in another 50 packages on the system unpatched.
This is a solved problem. It was done in Android, iOS, BlackBerry 10 and probably others. All OSes that had to deal with more than 30000 packages, open source or proprietary, from trusted or untrusted sources. Bundle non-system dependencies and confine in a sandbox. Snap’s been doing this ever since it was called Click. Flatpak didn’t have the sandbox part for a while if I’m not mistaken. I’m not sure what its current sandbox state is.
There are other issues with APT/deb but managing dependencies without sandboxing is probably the most fundamental one since dependency management is one their fundamental purposes.
Windows 10 is a lot more than just a skin for Windows 7. Just like all the Linux packages dependencies, All the individual libraries for Windows update. How things work changes all the time when security vulnerabilities are found.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.