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

Fix a dangling code fence

Browse source
This commit is contained in:
jultty 2025-10-10 05:32:45 -03:00
commit 3257331481
1 changed files with 5 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -90,15 +90,14 @@ I then checked out BusyBox's manual page to try and understand more:
> - TSTP: stop respawning until CONT > - TSTP: stop respawning until CONT
> - QUIT: re-exec another init > - QUIT: re-exec another init
> - USR1/TER, /USR2/INT: run halt/reboot/poweroff/Ctrl-Alt-Del script > - 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:
```inittab
::sysinit:/sbin/openrc sysinit ::sysinit:/sbin/openrc sysinit
::sysinit:/sbin/openrc boot ::sysinit:/sbin/openrc boot
::wait:/sbin/openrc default ::wait:/sbin/openrc default
```
Meaning, Alpine's init is BusyBox's init, which in turn calls on OpenRC to bring services up. Meaning, Alpine's init is BusyBox's init, which in turn calls on OpenRC to bring services up.