qhwudbebd

3 ms·

1.
by qhwudbebd 1mo ago
I remember procps top --help did this. I hated the resulting clunky, inconsistent wording enough to add a local patch in my procps build recipe to rewrite it. Apparently I'm still carrying the patch, so the current version must still d
2.
by qhwudbebd 2mo ago
OpenRouter map this into their API in a slightly different way, making -pro and normal different model slugs, so you have openai/gpt-5.6-luna-pro vs openai/gpt-5.6-luna vs openai/gpt-5.6-sol[-pro], etc. This makes reasoning e
3.
by qhwudbebd 2mo ago
It seems even worse than that: when you're calling the model, you have this strange two-dimensional thing with reasoning effort (specified in a small handful of random strings like "medium", "xhigh", "max"
4.
by qhwudbebd 8mo ago
Yes, I was going to suggest nat64 encapsulating the customer's v4 network on the wireguard overlay, but their embedded device is presumably a little linux board, and mainline linux still lacks any siit/clat/nat64 in netfilter
5.
by qhwudbebd 9mo ago
My impression is that you (very reasonably) treat anything inside the VM as untrusted. If you want trusted rollback, presumably that implies that the VM can't have any ability to tamper with the snapshot? But maybe you have parts of th
6.
by qhwudbebd 9mo ago
AFAIK fly.io run firecracker and cloud-hypervisor VMs. This seems to have a copy-on-write filesystem underneath. Given their principled take on only trusting full-VM boundaries, I doubt they moved any of the storage stack into the untrusted
7.
by qhwudbebd 9mo ago
It claims London E1W for my IPv4 and IPv6 RIPE PI space, and the same location/postcode for my EE home broadband. Generic 'London data centre' postcode? Or the location of the nearest Cloudflare POP, maybe? (Whois on the PI b
8.
by qhwudbebd 10mo ago
I hack on various C projects on a linux/musl box, and I'm pretty sure I've seen musl's malloc() return 0, although possibly the only cases where I've triggered that fall into the 'unreasonably huge' catego
9.
by qhwudbebd 10mo ago
Quite apart from that, an EFI shell that's less awful than the standard UEFI one is an interesting project in its own right...
10.
by qhwudbebd 10mo ago
Whenever I think about writing a central privileged daemon to grant capabilities to other processes, I'm puzzled by the choice to remove the old version of CAP_SETPCAP in 2.6.24: "grant or remove new capabilities to/from an e
11.
by qhwudbebd 10mo ago
while wait && [[ $SECONDS -lt $1 ]]; do read -t $(($1 - SECONDS)) done <><(:) although if you're not too concerned about finishing early if a signal interrupts, probably { wait; read -t $1; }
12.
by qhwudbebd 11mo ago
This has prompted me to look at how the Tor Project's Arti reimplementation is going. They've got way further along than I realised: https://tpo.pages.torproject.net/core/arti/ https://gitlab.
13.
by qhwudbebd 1y ago
Reading and hacking on the Chez Scheme codebase is always a treat and rather inspiring, especially compared with more mainstream compilers and code generators. As well as Kent Dybvig, Andy Keep's contribution (nanopass) is super-impres
14.
by qhwudbebd 1y ago
And the N150 had mainline linux support from day one, whereas I'm not sure if there's proper support for pi5-family devices in a released mainline kernel even now, two years after the launch. They used to do an good-to-adequate jo
15.
by qhwudbebd 1y ago
This is certainly the reputation but I'm not sure they deserve it. They've always had the horrible closed-source bootloader with threadx running on the gpu, without a free alternative. At least up to pi4 they weren't bad at l
16.
by qhwudbebd 1y ago
UK perspective here: I've not claimed for $43, but I've used the small claims process to recover £65. They replied to the paperwork sent out by the court indicating they intended to defend it, so I paid the hearing fee to take it
17.
by qhwudbebd 1y ago
I came here to mention this too, but saw you'd beaten me to it. It's remarkable how bad non-free OSes are at maintaining basic infrastructure in their kernel and userspace compared to Linux and the BSDs isn't it? Basic bugs g
18.
by qhwudbebd 1y ago
I'm really surprised to hear that the slow restore times from tarsnap are still as big a problem now as they were a decade ago when I last used it. I absolutely loved the interface and the security model, and I was willing to pay at th
19.
by qhwudbebd 1y ago
I think it's pretty much policy by now that GitHub don't allow features to be disabled by users who dislike them. Those of us with public projects that don't or can't accept contributions through GH PRs (including niche
20.
by qhwudbebd 1y ago
Nice to see BSDs up and working on new RPi hardware. Is there even (mainline) linux support for RPi5 and CM5 nowadays? For what seemed like ages they were unsupported (no usable IO) and I avoided using any of the newer boards for projects a
21.
by qhwudbebd 1y ago
In case your first instinct (like mine) was to browse through the implementation, the javascript is at https://github.com/VSRemoter/LuxPDF/blob/main/script.js
22.
by qhwudbebd 1y ago
This is true for personal tax, but HMRC has been successfully bribed by Sage et al. not to support web-based returns for partnerships or companies.
23.
by qhwudbebd 1y ago
Another masterpiece of elegance: v1/images/generations supports only application/json requests, whereas v1/images/edits supports only multipart/form-data. (The keys expected by the two calls are otherwise entir
24.
by qhwudbebd 1y ago
I hope the images support in the responses API is more competently executed than the mess piling up in the v1/images/generations endpoint. To pick an example, we have a model parameter and a response_format parameter. The response
25.
by qhwudbebd 2y ago
Given serial access on an mt7981, you can usually use the UART recovery protocol to boot a bricked device entirely over serial, e.g. with https://github.com/981213/mtk_uartboot just run something like mtk_uartboot
26.
by qhwudbebd 2y ago
Thanks. I went to look at bcm2712-rpi-5-b.dts and bcm2712.dtsi in 6.12.x, as it's been a while since I last checked, but it looks like even 14 months after the RPi5, they've still got no further with upstreaming than serial suppor
27.
by qhwudbebd 2y ago
Do this and the RPi5 run (proper mainline) Linux yet, or are they still only usable on the fork hacked together in-house?
28.
by qhwudbebd 2y ago
Don't disagree for what it's worth. The non-_RB behaviour for streams is useful too and isn't available at all on Linux. Though it's nowhere near as annoying as Linux having the epoll() mess instead of kqueue().
29.
by qhwudbebd 2y ago
Indeed. SO_REUSEPORT_LB is the FreeBSD equivalent of SO_REUSEPORT on Linux. SO_REUSEPORT on FreeBSD means something different, as you say. If SO_REUSEPORT_LB exists, we're on FreeBSD and want to use it! :)
30.
by qhwudbebd 2y ago
Confusingly, on FreeBSD this option is SO_REUSEPORT_LB; SO_REUSEPORT is something different. So I find myself writing #if defined SO_REUSEPORT_LB setsockopt(fd, SOL_SOCKET, SO_REUSEPORT_LB, &(int) { 1 }, sizeof(int)); #e

More ›