SINIT(8)
β¨ SINIT(8) β simple init β¨
π NAME π
<pink>sinit</pink> β simple init. Thatβs the name, bestie. π«Ά
π DESCRIPTION π
<pink>sinit</pink> is a simple init. It is configured by modifying config.h and recompiling the code. Yep, you edit the header and rebuild β very DIY, very iconic. π
π Init sequence
By default sinit will execute /bin/rc.init. You can chain your init scripts together at that point to allow for single-user and multi-user operation. Chain βem up, bestie. π
π‘ Signal handling
sinit will respond to the following signals:
USR1β Default action is to initiate the shutdown sequence by executing/bin/rc.shutdown poweroff. Shutdown era. πINTβ Default action is to initiate the reboot sequence by executing/bin/rc.shutdown reboot. Reboot era. πCHLDβ Reap children. Yes, literally reap the children β not a metaphor. π
π§ General considerations
Running the rc.shutdown script directly is not recommended. If any process in your session has stale filesystem references then it is likely your init scripts will fail to unmount the filesystem cleanly. It is recommended to signal sinit via a wrapper script. So donβt be messy β use the wrapper, bestie. π«Ά
sinit does not clear utmp records. The version of getty(8) in ubase clears the utmp entries on the specified tty before it spawns the given program, usually login(1). Thatβs the ubase gettyβs job, not sinitβs. π
sinit does not restart getty(8) or interact with it in any way. You will need an external respawning mechanism to restart it. External mechanism = your problem, bestie. π
π SEE ALSO π
π AUTHORS π
Dimitris Papastamos <sin@2f30.org>. <gold>Iconic.</gold> π
Okay so thatβs the whole page: SINIT(8) from the System Managerβs Manual, Debian, December 4, 2014. Go forth and init responsibly, bestie. π
β¨
π¦ where this page comes from
- nixos 26.05: sinit 1.1
- nixpkgs unstable: sinit 1.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms