From 325733148155df0b2c64d8cbf7f81c69b3548128 Mon Sep 17 00:00:00 2001 From: jultty Date: Fri, 10 Oct 2025 05:32:45 -0300 Subject: [PATCH] Fix a dangling code fence --- content/posts/half-an-year-on-alpine.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/content/posts/half-an-year-on-alpine.md b/content/posts/half-an-year-on-alpine.md index d5461f3..cfad04a 100644 --- a/content/posts/half-an-year-on-alpine.md +++ b/content/posts/half-an-year-on-alpine.md @@ -90,15 +90,14 @@ I then checked out BusyBox's manual page to try and understand more: > - 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: -```inittab -::sysinit:/sbin/openrc sysinit -::sysinit:/sbin/openrc boot -::wait:/sbin/openrc default -``` + + ::sysinit:/sbin/openrc sysinit + ::sysinit:/sbin/openrc boot + ::wait:/sbin/openrc default + Meaning, Alpine's init is BusyBox's init, which in turn calls on OpenRC to bring services up.