Can it run Firefox yet? The last time I tried reactOS, it BSODed just trying to launch Firefox... and don't even try using Windows drivers on it, it'll either hardlock, BSOD immediately, or during startup, regardless of whether you're in safe mode or not...
I’m pretty sure the idea that DST is for farmers is just a legend. Farmers can wake up whenever they need to based on where the sun is; it shouldn’t matter to them at all what the civil time is.
Farmers don't work in perfect isolation and do have to interact with other economic sectors that keep to clock hours. However, I don't think the misalignment between civil time and solar time has ever been so severe (nor would it be under year-round DST) to pose a serious problem for them.
Check your software SDR gain, use higher sampling rates and make sure NFC is enabled.
Otherwise, there might be some other nuances I'm not yet aware of, such as some phones not polling on unlock. I did test iPhone 15 Pro and Pixel 7 for initial POC. Others tested modern Samsungs/Xiaomis - worked as a charm.
Maybe he was significant to a lot of hackers. The death was also untimely, which reminds us to cherish the time we have. Many of us are in our 50s or 60s.
This is not really mysterious or anything, though, right? They allow bending of the rules for stuff that is not likely to devolve into a big stupid political flame war, because, like, pick your battles.
Also I’d expect there to be some annoying edge cases if they tried to ban that sort of discussion. I mean, Kilmer is not a tech person. But tech people die sometimes too. Arguably discussing their life as people is outside the scope of the site. Maybe we shouldn’t have had a conversation about how great a guy Mr. Moolenaar was and just discussed the technical aspects of his life’s work. But, come on, that’d not really be a human way of responding to somebody’s death, right?
If we’re going to have these sort of lightly rule breaking threads, then I don’t think it is necessary to ask the mods to adjudicate exactly who’s technical enough to warrant one. It’s a fuzzy spectrum anyway, we have tech people, tech policy people, STEM outreach people, tech YouTube influencers, celebrities that played beloved nerd characters.
atop freaks out if it isn't talking to the thing it thinks it's talking to... who would have thunked it... I feel like a lot of programs have that issue.
It's acceptable to freak out by crashing. It's even acceptable to crash via explicit assertion failure if the developers don't want to write proper error handling. It's not acceptable to crash via segmentation fault.
It's to an extent even acceptable to crash via segmentation fault (more specifically, doing whatever unsafe exploitable things may come of the source of the issue) if it takes the same amount of privileges to cause the crash as the thing crashing has.
And that's the important thing violated here, atop being rather reasonably ran by root to examine root processes, whereas the exploiter just needs the ability to host a thing on a specific port.
It can be difficult to prove that an out-of-bounds memory reference triggered by malformed input will always result in a segmentation fault instead of a read or write of an "interesting" memory location.
This depends. In this, I guess the issue is that there is some oob memory reference. But for example a null pointer deference resulting in a segmentation fault is not (necessarily) a security problem.
I'm not paying oracle for cloud services, I learned my lesson the hard way, they're still emailing me about random cloud stuff despite me telling them to stop contacting me.
reply