vx — systems engineer
I write software meant to outlast the machine it runs on.
POSIX-compliant systems, minimal init stacks, and the kind of code that's still readable in ten years — because it was written to a standard, not a moment.
Standards over shortcuts
POSIX interfaces over vendor extensions. If a program only runs on one platform, that's a design decision worth questioning.
One job, done predictably
An init that only manages processes. A service manager that only manages services. Scope creep is usually the first sign something's about to become unreliable.
Small enough to understand fully
Code you can hold in your head beats code you have to trust. If I can't explain why a line is there, it doesn't stay.
Work
4suite
github.com/vx9k/4suiteA self-contained C boot stack: init, rc, logger, and user, each with its own scope and its own README.
Minimal PID 1 init. Its only job is managing processes — by default it hands off to 4rc, configurable in config.h. If it crashes, the kernel panics, same as any init would.
Inspired by rofl0r's minimal init gist.
The service manager that starts under 4init. Early — the project's own README calls it a service manager that "larps as being functional," which is a more honest status line than most projects give you.
Not started yet. Part of the suite's intended scope.
Not started yet. Part of the suite's intended scope.
Stack
I'd rather ship something small that I fully understand than something large I'm still discovering the edges of.