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.
What are these numbers exactly and why are there two of them?
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.
I like Taler, but it’s specifically designed to not give anonymity to sellers. In order to verify that you got a valid token (meaning it was issued by an accredited bank and was not already spent) you need to deposit it with the bank.
Now if you get money from a friend you trust has given you a valid token, then that’s not an issue. You can just use it to pay for stuff and nobody will know how you got that token. A seller however will want to verify the token immediately or they might end up giving stuff away for free.
I guess for donations it could work since you’re not giving anything in return and so can’t be scammed, but it’s obviously a bit of a problem since you could be sitting on worthless tokens. You don’t know what funds you have until you try to spend them, and people will probably get pretty annoyed with you if most of your tokens end up being fake. Not sure how one might protect themselves against this sort of spam.
You think FairEmail is too cluttered but like K9? 🤔
K9 is the most insane mail client, it’s got hundreds of settings! I was so happy to ditch K9 when I found FairEmail.
As I said, every file read from disk, be it an executable, image or whatever gets cached in RAM automatically and always.
Having said that, if you read a file using read(2) (or like any API that uses read() internally, which is most), then you end up with two copies of the file in RAM, the version your OS put in the disk cache, and the copy you created in your process’s memory. You can avoid this second copy by using mmap(2). In this case the copy of the file in the disk cache gets mapped into your process’s memory, so the RAM is shared between your copy and the disk cache copy.
You can also give hints to the disk cache subsystem in the kernel using fadvise(2). Don’t though unless you know what you’re doing.
FTL and Into the Breach have native versions that have never given me any issue.
Does that stuff still happen? I didn’t try this but I had kinda hoped this stuff got fixed with the introduction of systemd.
This doesn’t explain what a disk cache (afaik often refered to as page cache) is, so here goes: When any modern OS reads a file from the disk, it (or the parts of it that are actually read) gets copied to RAM. These “pages” only get thrown out (“dropped”) when RAM is needed for something else, usually starting with the one that hasn’t been accessed for the longest time.
You can see the effect of this by opening a program (or large file), closing it, and opening it again. The second time it will start faster because nothing needs to get read from disk.
Since the pages in RAM are identical to the sectors on disk (unless the file has been modified in RAM by writing to it), they can be dropped immediately and the RAM can be used for something else if needed. The downside being obviously that the dropped file needs to be read again from disk when it is needed the next time.
They’re a sucker who’s gonna get fleeced. If they answer that they know the game is rigged (as most of them will), but that they totally understand how this works, they’re a super sucker who’ll get double fleeced.
Unsuccessfully.