FOR WHAT? To distract folks from the Epstein files? For some fucking power move? Because he can?! I don’t know.
Oil (but also the other reasons you listed)
Ironically the current Iranian government is indirectly the US and UK’s fault (they overthrew the democratically elected government in 1953 because they wanted oil, which was later itself overthrown in 1979 and replaced with the current theocratic dictatorship)
i've been keeping this a secret for half a year, but i can finally come clean now.
i spent months editing the entire star wars movie. at first i made subtle changes (colour correction, fake shot/reverse shot scenes, etc.), but as the movie went on, my edits got more and more absurd (extra powerpoint transition wipes, doom door open/close sound effects, etc.).
i can't upload the full thing for obvious reasons, but here's one of my favourite parts: the death star scene. spoilers for a movie that came out nearly four decades ago
@maddy On x86 you can have a separate -march and -mtune. -march defines what microarchitecture to build for, so you should build for the lowest common denominator (in terms of extensions) or stuff might not work. -mtune defines what microarchitecture to optimize for, but won’t use instructions that are unavailable on the target instruction set.
I build with -march=haswell -mtune=skylake -maes -mabm to optimize for skylake (which my gentoo machine uses (actually coffee lake refresh but that’s the same microarchitecture)) but so the binaries would still be usable on haswell if I wanted to (-maes is because -march=haswell doesn’t include AES-NI because i3-4000M doesn’t have it for some reason (every other haswell i3 does), -mabm is because resolve-march-native outputted it on skylake and it seems to be present on haswell too)
If some packages built with -march=znver3 fail on raptorlake, it means it’s using some extension not present on raptorlake and you should find out which one and specifically disable it or just build with -march=x86-64-v3 -mtune=znver3.
(On other architectures it may be different. There’s 3 different flags (-march, -mtune, and -mcpu) and what they do is completely inconsistent between architectures)
@crowbriarhexe @maddy I have another Baytrail laptop/tablet thing (Toshiba Satellite Click Mini) with the same 32-bit UEFI and audio problems. I installed postmarketOS on it (the generic-x86_64 port supports 32-bit UEFI) and it’s the most broken x86_64 device I’ve used:
I’m afraid of breaking my installation and not being able to recover it since there’s no boot menu and it’s booting from eMMC which I can’t just take out and mount elsewhere. I couldn’t obtain a dump of the boot firmware either since it’s on a 1.8V flash chip and I only have a 3.3V programmer.