

I wasn’t trying to give a positive side, I was just explaining why Microsoft wants the feature
I wasn’t trying to give a positive side, I was just explaining why Microsoft wants the feature
If the executable binary has to be signed with a key, similar to the module signing key, Microsoft could sign their binaries
This, along with secureboot, would prevent the owner of the machine from running eBPF programs Microsoft doesn’t want you to run, even with root
The Ubuntu security team only supports the ~2,000 packages in “main”
Things like ffmpeg are in “universe” and only get security updates if you subscribe to Ubuntu Pro
Debian’s security team has always been significantly more responsive than Ubuntu. It’s regularly had CVE fixes in older versions of Debian that newer versions of Ubuntu don’t bother to pull into universe
FWIW, if you decide to go with KDE and manage to delete your panel, it’s
😉
My job is literally to make Linux distros using Yocto for various boards. I’m constantly writing new build scripts or updating build scripts, debugging the kernel/systemd/glibc and whatever libraries are on the system.
All of my work and personal desktops run some version of Fedora Atomic or a uBlue variant right now.
With distrobox/toybox/brew and using podman/docker/KVM+qemu, even as a tinkerer, it’s great
And “the specific resource ID” is almost certainly for localization of the text
SSDs make hibernate even more powerful
That’s why things like suspend-then-hibernate are popular now
If you’re seriously wanting to compile optimized software for those devices, you would want to investigate “cross compiling”
git was created because a proprietary VCS was being a dick
I was reasonably certain, but left it open in case OP knew of some edge case where flags that are intended to be machine independent caused bugs on different architectures
-O2 vs -O3 adds
-fgcse-after-reload -fipa-cp-clone -floop-interchange -floop-unroll-and-jam -fpeel-loops -fpredictive-commoning -fsplit-loops -fsplit-paths -ftree-loop-distribution -ftree-partial-pre -funswitch-loops -fvect-cost-model=dynamic -fversion-loops-for-strides
I don’t think any of these optimizations require more modern hardware?
For historical info - Oracle bought OpenOffice and started to close it down, so all the developers that worked on it forked it into LibreOffice
Oracle has since given OpenOffice to an open source group, Apache, but the main development still happens on LibreOffice
If your speedometer/tachometer is a screen instead of dials, it’s extremely likely it’s running Linux, too
So still somewhat useful in the auto space
Both GNU and GrapheneOS have staunch requirements and will accept no compromises.
This is a situation where their requirements don’t align, so they’ll never reach an agreement.
GrapheneOS, for example, is also strictly against making the Fairphone line of phones a little more secure because it doesn’t meet all of their security requirements
In this case GNU won’t certify GrapheneOS as fully open because it includes binaries that aren’t open
The FSF is more along your line of improving the situation where they can
I’d used Linux a bit out of curiosity in the Windows XP era
Windows Vista came out and was completely unusable on the computers I or anyone around me owned. It was also harder to configure than Linux and the new UI looked worse than the Linux UIs at the time
So I switched and haven’t been back to Windows since
The summary here and in the paper isn’t very helpful to check what CVEs are relevant
The kernels referenced aren’t supported, and it says the issues were reported upstream
Checking some of the references of the paper, it says
By the time we posted this writeup, all the distros have patched this vulnerability.
Do you know what CVEs users should check against?
It’s a strange suggestion after very recently working closely with openSUSE to ensure Leap can use the same binaries as SLE, though
Well, a.out doesn’t make much sense these days.
Gotta move to .elf
deleted by creator