IAmLiterallyAB

They've changed the plans a bit, you can get 8GB even cheaper I think. I pay $30 a month after the autopay discount. Though mine is only 5GB

What secret state do you mean? All PRNGs have state right? Which you need to keep secret if you don't want the sequence to be predictable. Is there something more I'm missing?

Interesting, but there's one part I'm not sure I agree with.

> Pseudo-random number generators are useful for many purposes, but unbiased shuffling isn't one of them.

A properly seeded CSPRNG is perfectly fine at this. And if it's not, then all of our cryptography is pretty much screwed. This is why in modern kernels, /dev/random and /dev/urandom are the same (minus differences in behavior when the initialization isn't complete). As D.J. Bernstein put it, it's superstition to not trust CSPRNGs. https://www.mail-archive.com/cryptography@randombit.net/msg0... And if it's good enough for crypto, it's good enough for card shuffling.

FYI I am not a cryptographer

If you could reverse engineer the expected signal you could probably make your own gun

Oh, for sure what I said wouldn't work on a W^X system. I was just pointing out that one of the most widely used JIT software uses WX pages.

What OSes prohibit that? Linux doesn't (well, I think it can with SeLinux maybe?). OpenBSD might?

Found a similar big once. The API would correctly reject unauthenticated requests for exactly 10 minutes. Then, for exactly 1 minute, unauthenticated requests were allowed. The cycle repeated indefinitely. Would love to know what was going on on the backend...

I remember GTK themes used to break every couple releases. Is that not an API break?

Or you do what V8 does with WebAssembly and just use WX pages because doing it correctly is "too hard" to do without losing performance.

Just want to say, your blog has been a godsend for understanding the weird quirks of linking and ABI stuff. Thank you.

The docker daemon is running as root in that scenario. So anyone in the Docker group can trivially become root by starting a privileged container.

The hope is to eventually remove the in-kernel terminal emulator. See here https://dvdhrm.wordpress.com/2012/08/12/killing-off-config_v...

AntennaPod is my favorite podcast app. I use it for all my podcasts that have RSS feeds. Highly recommend

Ah, I guess I was mistaken

Somewhat misleading. Because these days, none of the network transparent primitives are used anymore. All the rendering happens server side, and bitmaps are sent over the wire. It's basically a crappy VNC. And at that point, just use RDP or VNC

NXP still sells those? Wow, e500 will never die huh

Clang 18 came out in March and GCC 14 isn't even out. So those are bleeding edge by just about any metric

> full constraint specifications

Is that a technical term? (if so, can you explain further)

I've made SLEIGH specs for two architectures. In my experience, it can describe 95% of the semantics well enough for decompilation (it gets weird when your ISA has quirks). Not as comprehensive as SAIL appears to be

Also, SLEIGH compiles to an XML format which is what Ghidra actually uses

SAIL reminds me of SLEIGH, the language Ghidra uses to describe ISA semantics. Cool stuff

Mandatory CSD was always a bad idea imo and this is yet another reason

Oh neat, had this guy as a professor for "Linux Kernel Programming". Good to see he's still doing cool stuff

Because you used bytes mode, not alphanumeric mode

That commit has nothing at all to do with task cancellation.

Ugh. We're forever pinned on 3.8.1 since they broke task cancellation in 3.8.3. The handling of that is frustrating, we won't be using aio http for new projects.

https://github.com/aio-libs/aiohttp/issues/6719

Am I wrong? Just noticed the downvote. That is my understanding of the old AIO kernel API anyway. The original io_uring paper describes some of the deficiencies of AIO. And the fact that the API is broken on non-O_DIRECT regular file descriptions is well known.

The old aio API is very inefficient and has awful quirks, such as not working on regular files opened without O_DIRECT. Not surprised no one used it

> GCC 14

Do you have a reference for significant module changes in GCC 14? I see nothing on the changes page for 14

> And generally, libc is vehemently opposed to the existence of smart compilers

Yes, as far as I'm aware none of the major libcs on Linux support LTO

Even those get most of their info from /proc and /sys rather than special syscalls

I'm having trouble distinguishing the differences between the bright end of the gradient. Maybe it should use a different color space. This site explains it well: https://joshdata.github.io/color-scales/

"Unfortunately math in “RGB space” isn’s perceptually valid. Dividing the green component in half doesn’t make a color half as green. Adding 50 to all of components makes the color brighter by uneven amounts depending on which color you start with. That’s because the sensitivity of human color perception is uneven across the gamut of colors we can see, and the definition of RGB used by computer monitors doesn’t follow human perceptual sensitivity."

Tangently related, does anyone have experience with AsciiDoc? I've used reStructuredText before, but AsciiDoc is tempting, it looks cleaner.