On 04/24/2016 10:38 AM, Kamil Cholewiński wrote:
> execline is not exactly a shell. It's supposed to facilitate "DJB-style"
> command chaining, and focuses on little else.
>
> Suppose you have a bunch utilities that each do exactly one thing, and
> then 'execve(2)' the remainder of their arguments:
>
> setuser my_user program arg
> setgrp my_group program arg
>
> You could freely chain such commands to modify the execution environment
> for the final program:
>
> setuser my_user setgrp my_group program arg
>
> If your script does nothing else (as is the case 99% of the time when
> using daemontools[1] or runit[2]), /bin/sh is quite redundant.
>
> [1]: https://cr.yp.to/daemontools.html
> [2]: http://smarden.org/runit/
>
> For that intent and purpose, I would call it perfectly suckless.
Thanks for the explanation. I think I understand a little better now.
Received on Thu Apr 28 2016 - 19:58:47 CEST