dezgeg

I don't think this is about core kernel semaphores but rather the SysV semaphore system calls?

Ah, but you see Xbox security updates won't be for your security. They will be for protecting the console's security against jailbreaks etc.

> Today I am filing: > 1. A payment dispute with the email payment processor for the 7/29 transaction of $451.15 > 2. A complaint with the FTC and California Attorney General (retention of payment without delivery) > 3. A small claims filing in San Francisco County for $451.15 plus costs

I wonder did their prompts include a fake location or have the models assumed that Silicon Valley is the center of the universe :)

System prompt for something like Claude Code should be identical, no?

The bottleneck was with the serial protocol between the drive and C64. It was done via bit banging in software due to some chip bug. The fastloaders replaced the protocol with something more amenable to bitbanging.

That is the reality for huge amount of ARM powered hardware, unless you fancy running vendor forks of kernel, u-boot, etc.

You can't if the firmware provided DTB doesn't follow any upstream Linux approved bindings and instead uses some vendor kernel specific bindings.

Have you actually tested the portability? MacOS ships an ancient bash version and neither mac or BSDs use GNU version of coreutils.

I'm also very doubtful performance of this would be faster than python, bash is very slow.

Quite safe in practice, even Nintendo games have had no issues. GTA 3 / Vice City decompilers did get sued though, but IIRC mainly because they did not comply with DMCA requests at all.

Yes, exact version of the original compiler is required.

Generally bit-for-bit equivalence to the original executable is expected. However I think for some cases where the original executable included debug info (eg. PS2 ELFs) then the unused-at-runtime sections need not match.

MIDI doesn't have RTS/CTS pins...

I have seen some pre-AI over-mocked codebases where the "tests" where essentially that (but harder to read than regex would have been)

Detect tests somehow (eg. in rust you could check for #[test]) and just skip the analysis for that function?

Even if it could, it would be ridiculously token inefficient to update huge amount of addresses instead when some small change is done to the middle of a binary

What does "long term memory" mean? It can write down notes from past/recent support requests? If so, that sounds like risk of one customer's data leaking to another.

That's defined in Makefile

Some stricter interpretations also require that maximum stack usage can be statically analyzed (ie. no recursion, no function pointers, no VLAs/alloca).

It requires a keyring service being installed (accessed over dbus) and if there isn't one it just silently doesn't store them anywhere. Pretty bad UX.

It only stores credentials in the keyring, so if you have no dbus keyring service running it just silently won't remember them.

But then you have to pay by the token instead of the subsidized subscription prices

Did you actively verify that your builds were bit-reproducible?

You don't need to do that for every write though. Only when the database file is created.

For home computers, essentially https://xkcd.com/1200/ applies.

Reminder that this was a student project.

In wsl, each distro you have runs in a container (with lot of permissions), you'd need to apply the modprobe change inside wsl "hypervisor" rootfs

Even worse, the actual struct page on Linux is 64 bytes, so 4x your example

Do they use it via mainline Linux kernel's ISNDN drivers though (and not something proprietary)?

GPL-3 dependencies are typically banned inside embedded device firmware. If a 3rd-party app uses those presumably it will be problem for the developer of the app, not Amazon.

Could there be mixup with FreeCell?

Switching between NFC vs NFD could be even sneakier.