what if systemd had some kind of integration with queues?
like a unit type to limit concurrency like ninja.build pools but one could associate a service to more than one pool
and it binds to a posix queue and each message behaves like a socket activated unit
like each incoming message would work like a socket connection
if the pool is full the service stays as a job, if the service fails the message can be requeued
TL;DR: pool and queue units
Back when I was poking around with filesystem fuzzing stuff years back, I noticed something odd:
An EXT filesystem can tell the Linux OS how it should behave "if" the filesystem is corrupt, including triggering a kernel panic. In a world where USB thumb drives exist, this seems... not ideal.
Let's see what happens if we plug such a mass storage device into a fully patched Chromebook in 2024...
Oh.