-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
I have fond memories of playing it as a comedy game back when the Radeon RX 480 came out
There was a bug with the shaders in this game, so all the walls and many floors were rainbows 😂
All of the security features mentioned in the article even started from work done by GrapheneOS - they’re simply upstreamed now
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
My assumption is baseball
AAA is the best you can get in minor leagues before you move to the major leagues
without any distro or configuration caveats.
In those cases, they generally have the Ubuntu version that’s supported in the specs section
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
If an attacker gets access to your system, they will be able to ensure you can’t get rid of their access
It will persist across operating system installs
However, this requires them to get access first
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?
eSIM requires proprietary google services to activate, so if you’re planning on messing with ROMs I find physical to be easier
It’s a strange suggestion after very recently working closely with openSUSE to ensure Leap can use the same binaries as SLE, though
It doesn’t have to, but GrapheneOS is designed around security first, privacy second, and usability third
If you install Fennec browser on it and open, e.g., https://www.learningcontainer.com/download/sample-pdf-file-for-testing/?wpdmdl=1566&refresh=6697dcd62a0141721228502
The PDF will display inside Firefox
The default web browser on GrapheneOS, Vanadium, doesn’t parse PDF’s (they’re an incredibly insecure format) and passes them off to a sandboxed, hardened app specifically for that usecase
This allows rejecting more permissions than doing it in the same process
Apple’s using Qualcomm modems, and the complaint seems to be around the modem
It looks like an alternative to LocalSend rather than Syncthing
For the Steam Folders, you can use Flatseal to declare other folders any Flatpak you install is allowed to access
Thanks! That sounds like exactly what I’d want to run mpd. I’ll check it out
For virtualization, I’m all good since I went with uBlue instead of Silverblue for now - the developer images come with lxc/lxd/qemu/libvirt :)
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