• 0 Posts
  • 13 Comments
Joined 3 years ago
cake
Cake day: June 8th, 2023

help-circle

  • dist-upgrade must die.

    I spent like three hours I didn’t have the other day trying to bring a Debian Unstable system up to date, it decided to stop every few packages to tell me it failed because the t64 libraries conflict with the regular ones and nobody taught apt how to figure that shit out for me and install the right ones.

    Even Ubuntu is like “oh hey there’s a new release, you’re available for three hours straight to, every two to fifty minutes, explain to a TUI dialog that you don’t have an opinion, right? Oh also can you resolve this merge conflict on this config file we think you edited, but you didn’t, by being shown the diff once and then opening nano?”

    This is not an acceptable way for this to go.




  • I think it’s a pretty good translation of the word; “Republicans” ostensibly would support a “republic”, which is governed supposedly for the common good by mechanisms which are not really explained or examined and definitely distinct from just letting people do whatever they agree on like under one of those gross dirty democracies. “Common harmony” captures the same good-vibes/no-plan energy.

    Of course, what they’ve got now aren’t even actual republicans, because, like their favorite model of Rome, republics love to become empires.






  • It looks like they ginned them up from relevant specs they stuffed in and and the model’s latent knowledge of QEMU VirtIO and the absurd GPU-managed system architecture that is the Pi.

    The models have seen several IP stacks before, plus many copies of the Linux, BSD, etc. source trees.

    It’s not actually hard to write a network stack, just tedious.

    At some point in the USB keyboard/mouse code the model has loudly proclaimed PRINTF NOT ALLOWED, in the style it does when overcompensating after its obvious mistakes are pointed out to it for the third time. So I suspect that part might be implemented by brute force.

    Unfortunately, the talking horse’s OS hasn’t bothered with syscalls and lacks any notion of memory protection, and has a terrible userspace API which e.g. puts waiting for a ping response entirely in kernel.

     * Programs call kernel functions directly - no syscalls needed.
     * Win3.1 style!
    

    Usually people don’t manage to produce an entire operating system without knowing why this is a bad idea.