SINIT(8)

πŸ“¦ version 1.1, in nixos 26.05, nixpkgs unstable

✨ 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