Re: Using execline in place of shell for s6/s6-rc setup: environment variables?

Which would require rc(1), but it is unfortunately "unmaintained" in Alpine. Following are static-compiled binaries for the 1.7.4 version: x86_64: x86: Attached are

Re: Using execline in place of shell for s6/s6-rc setup: environment variables?

:( On Sat, May 20, 2017 at 12:51:13PM +0800, Casper Ti. Vector wrote: > Attached are their checksums (plus that for the `alpine-s6rc-conf' > tarball) signed with my OpenPGP key. -- My current OpenPGP key: RSA4096/0x227E8CAAB7AA186C (expires: 2020.10.19) 7077 7781 B859 5166 AE07 0286 227E 8CAA

Using execline in place of shell for s6/s6-rc setup: environment variables?

Hello list, I am trying to determine whether is feasible and sane for me to try to port Slackware's init scripts that initialize such things as filesystems, kernel modules, network interfaces, etc. I would be trying to write these in execline as oneshot services to be started by s6-rc at the very

Re: Using execline in place of shell for s6/s6-rc setup: environment variables?

I am trying to determine whether is feasible and sane for me to try to port Slackware's init scripts that initialize such things as filesystems, kernel modules, network interfaces, etc. I would be trying to write these in execline as oneshot services to be started by s6-rc at the very