jutty/blog
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Replace a code fence with blockquote

Browse source
This commit is contained in:
jultty 2025-10-08 13:23:20 -03:00
commit 4868c12b39
1 changed files with 9 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

16
content/posts/half-an-year-on-alpine.md
View file

@ -81,13 +81,15 @@ I could not find explicit information on whether this is the case with Alpine, b
I then checked out BusyBox's manual page to try and understand more: I then checked out BusyBox's manual page to try and understand more:
``` > Init is the first process started during boot. It never exits.
Init is the first process started during boot. It never exits. It > It (re)spawns children according to /etc/inittab.
(re)spawns children according to /etc/inittab. Signals: >
> Signals:
HUP: reload /etc/inittab TSTP: stop respawning until CONT QUIT: re- >
exec another init USR1/TER, /USR2/INT: run > - HUP: reload /etc/inittab
halt/reboot/poweroff/Ctrl-Alt-Del script > - TSTP: stop respawning until CONT
> - QUIT: re-exec another init
> - USR1/TER, /USR2/INT: run halt/reboot/poweroff/Ctrl-Alt-Del script
``` ```
I knew Alpine heavily leaned on BusyBox, but didn't realize it was to this extent. So, following this trail, there was Alpine's `/etc/inittab`, where I found this: I knew Alpine heavily leaned on BusyBox, but didn't realize it was to this extent. So, following this trail, there was Alpine's `/etc/inittab`, where I found this: