A lot of the security fixes since spectre have focused on exploiting speculative execution (a key CPU performance feature) to cross security boundaries. Defeating speculative execution when switching from user to kernel space (for example) adds a lot of overhead.
The new kernel add controls so that machines that don’t need to worry about these exploits to disable the performance killing fixes.
It’s a few hundred lines of C across 7-8 files. It checks the password hash against a set of predefined ones and then calls a script if it matches.
It doesn’t need a lot of maintaining.
As does Arch.
The avalanche has started. It is too late for the pebbles to vote.
…except there’s no hardware to run it on. They’ve chosen an ISA profile that’s not been decided on for long enough.
I think people who dislike flatpaks or similar aren’t having “problems”. They work, but they’re using using a sledgehammer to drive a nail.
https://wiki.manjaro.org/index.php/Manjaro:A_Different_Kind_of_Beast
Although Manjaro is Arch-based and Arch compatible, it is not Arch.
Manjaro package repository
Stable branch - There is no solid rule indicating when Stable branch is snapped from testing. It can be anything from one to four weeks…
Testing branch - Testing branch is snapped from unstable at irregular intervals - …
Unstable branch - Unstable branch is synced several times daily from Arch stable
Manjaro Unstable is Arch Stable
I would expect Steam to report Steam OS as Steam OS.
They managed to differentiate Manjaro to it’s own entry after all. It’s Arch based too.
I’m quite impressed Arch comes out on top
Mone might even had been a Cyrix too. Honestly I struggle to remember. My dad bought straight Intels and I bought the clones (cheaper) I can’t remember which one I first started on, but both got it eventually.
Complete with cow-print box?
I think my lowest was a 33 MHz 486sx (maybe DX) with 8MB of RAM.
I wouldn’t want to try it today though.
When it was first developed it was too heavyweight and too customisable. The effort needed to theme it was huge and a lot of the popular themes were poor from a UX point of view.
Still E16 was usable, and then the development of E17 started about 24 years ago. People are still on E16 you say?
The Linux Unplugged podcast did something similar to an old Arch based server. Only one year out of date, but they had a similar experience.
Your problem isn’t Arch. It’s the fact that the Weyland experience is still under development and so not stable release to release.
This will be true on any distro.
If your solution is to freeze your distro in a certain point in time, don’t type pacman anymore.
Pretty sure that’s a Nazgul
…and some dude is feeding it!
Depends on two things
Tools like perf on Linux can get you access to your processors performance counters and you’ll be able to see how many “events” occur while a process is running.
What’s an event? Well they can be configured to monitor all sorts of things in the CPU. Instructions executed, Interrupts, page table misses, and on some loads / stores.
Memory systems on a CPU aren’t straightforward though. They contain multiple levels of cache, each of which reduces the number of accesses which go to the next layer. So depending on which level you measure, you’ll get different numbers.
So more like a charity status?
Agreed. The headline is terrible. Headline Case Doesn’t Help Either.