Post #2270212
2026-04-09 23:42 UTC
@resuna@ohai.social @mia@shrimptest.0x0.st I can't believe I'm still hearing this in 2026, to be honest. Will that misperception ever die?
You do not need to write your run scripts in execline. You never have, and you never will. You can write your run scripts in any scripting language you want. You can even make your run "scripts" compiled executables, if you like.
Most people use /bin/sh as the interpreter for their run scripts, and it's totally fine.
s6 (more accurately, s6-rc) uses execline internally because execline is better than sh for automated script generation, but you never have to see it. You can use s6 and pretend execline doesn't exist. You can even build s6 without execline, it's not recommended, but it's possible. I don't know what more I can do at this point.
Replies (1)
-
@resuna@ohai.social 2026-04-09 23:47
@ska@social.treehouse.systems @mia@shrimptest.0x0.st I am supporting a system that was built by other people, so I don't have the luxury of changing the scripting language it uses, and it uses execline. And right now I just Googled it and found the documentation on S6 and it goes on about how execline is a better scripting language than the shell and how horrible the source code to the Shell is and yes I agree Bournegol is insane. Which doesn't exactly read like execline is an internal tool and you don't have to actually touch it.