On 2015-06-19 19:19, Les Aker wrote:
Looks like s6-linux-init 0.0.1.0 pulls s6 in as a build-time
dependency. Not a huge issue, but might be worth updating the docs to
clarify that until the next release removes that? I've learned to
trust your docs and build tools enough that I spent a while
Looks like s6-linux-init 0.0.1.0 pulls s6 in as a build-time
dependency. Not a huge issue, but might be worth updating the docs to
clarify that until the next release removes that? I've learned to
trust your docs and build tools enough that I spent a while hunting
for what I was doing wrong :)
On 18/06/2015 05:12, Guillermo wrote:
I did a quick run and found out that in generated execline scripts
except the stage 1 init, the shebang line starts with #!execlineb.
Yes (unless you use slashpackage).
And on the machines where I tested, it's not a problem as long as
execlineb is in the
Hi,
2015-06-17 17:27 GMT-03:00 Laurent Bercot:
s6-linux-init-0.0.1.0 is out.
It is a new package that, for now, only contains one program,
and more documentation than source code. :)
Its goal is to automate the creation of stage 1 (/sbin/init) binaries
for people who want to run
Hello,
s6-linux-init-0.0.1.0 is out.
It is a new package that, for now, only contains one program,
and more documentation than source code. :)
Its goal is to automate the creation of stage 1 (/sbin/init) binaries
for people who want to run s6-svscan as process 1.
Unfortunately, it has to
