It is relevant when the CIA is co-opting the protest and trying to turn it into an insurrection.
Iranians that want progress will need to kick out foreign provocateurs the next time they protest or they'll be inviting people with an even worse human rights record.
The CIA has enough money, no need to donate your computing power.
Maybe it's some kind of knitting implement.
Afaik the free drivers can't control the clocks so the the card runs at low clock the whole time and is really slow. Not sure about features but I think it runs most games fine in terms of that.
Ah right! I always put a new ROM immediately.
There might be ways around this with an overlay fs.
This doesn't have anything to do with rooting? It's just a new filesystem.
LGPL says the user needs to be able to replace the LGPL'ed code with their own modified version. You can't do that on an iPhone. I think that's the issue there.
Also the SDL devs are themselves game developers/porters (I think that came out of Loki games), so it's not so hard to understand why they would relicense their stuff, it basically makes their own life easier also.
It's so commercial game devs can ship it on iOS and consoles. I think Apple makes it impossible to comply with the LGPL. Probably same thing for Sony, XBox and Nintendo.
I'm not too mad even though I'm a GPL fanboy. If it helps SDL adoption among game devs then that will help portability and Linux support in the long run. It will also help games run better on Linux: plenty of games that don't use SDL have annoying issues with my tiling WM for example.
With SDL 2, they even thought about the future compatibility issues due to static linking: Even if a game statically links SDL, you can still override the static copy with your own dynamic library. The static SDL will forward all function calls to the user supplied SDL.
It's an unmaintained mail app, so yes this means nobody's going to fix any security bugs if they are found.
I've seen hot takes about this on Reddit where people bring up these points:
To the first point I want to look at the evidence, which clearly suggests malware and shit like never make it into any Linux distro. This probably has less to do with security audits and expertise and such, but rather the desire of the packagers to actually package useful and legit software. It acts more like a general heuristic spam filter that throws out sketchy shit as part of the assessment of any software being useful and trustworthy by culturally aware people. These people can't be tricked like a shitty spam filter would.
To the second point I think some bleeding-edgelords undervalue stability and ignore the amount of work this actually causes everyday. Updating too often creates more work in many cases, though updating very rarely clearly also causes problems. There's probably a middle ground here.
Plus this whole argument is arguably kinda tangential to the actual point: There are rolling release distros that are only days or weeks behind upstream, and they still don't suffer that spam problem where random strangers are allowed to basically upload any crapware without human supervision.
First of all, this is probably a bad sign for the health of your drive, you should look at the dmesg output and SMART diagnostics of the drive. There's a package called smartmontools or something like that. Also make a backup now if you haven't yet.
If it's just the filesystem that's borked try fsck like that other person said.
Unsuccessfully.