Fucking monolithic OS

[littlefox@gotosocial-dev.svc.0x0a.network]

stuck-I/O zombies should be recoverable.

[littlefox@gotosocial-dev.svc.0x0a.network]

maybe I should just pull all the disks :blobhaj_thinking:

Can't be stuck if no disks

[littlefox@gotosocial-dev.svc.0x0a.network]

(I can't reboot, the affected system is Karl .. our router. And Dani is working)

[airtower@fedi.sillykittens.net]

@littlefox Just run everything from initramfs!

(Probably actually doable for a router, but I suspect it does some more stuff… )

[littlefox@gotosocial-dev.svc.0x0a.network]

I hate Linux.

It's the best OS we have rn, but it's .. not good

[littlefox@gotosocial-dev.svc.0x0a.network]

Wanna know how I deadlocked it?

I copied data onto it.

[airtower@fedi.sillykittens.net]

@littlefox What.

[littlefox@gotosocial-dev.svc.0x0a.network]

I wish I had some clones and could just develop LF OS full time ..

[littlefox@gotosocial-dev.svc.0x0a.network]

(this didn't work btw)

[anthropy@mastodon.derg.nz]

@littlefox mood, but it's difficult with kernel level modules to just punt them out, even for userspace processes handling zombies can be a pain because there's no way for them to receive signals, and at kernel level they're basically equal to the kernel itself, so avoiding a reboot there is difficult without writing elaborate hacky kernel level circuitry to handle those situations

[littlefox@gotosocial-dev.svc.0x0a.network]

@anthropy and that's the reason for my complaint

Just stop having that much shit in the kernel /o\

[anthropy@mastodon.derg.nz]

@littlefox but FUSE is slow