Rebuilding s6

Rebuilding s6

[Ian Macdonald via supervision]

Hi,

I have just started investigating s6. I installed all the
programs and, using the s6-linux-init quickstart page, appeared to have
things working.

The first few scripts I converted from svinit ( virtualfs and remount
rw) compiled and run as expected but the first script using a program
on /usr/sbin would not compile, insisting there was no such file.

I thought this may be a problem with paths and symlinks ( in LFS /bin
and /sbin are symlinks to /usr/{s}bin) so I decided to rebuild s6,s6-rc
and s6-linux-init with the --enable-absolute-paths option. 

Now the quickstart recipe can't work because there is no
/etc/s6-linux-init directory which I assume the s6-linux-init install
should have created. There were numerous install warnings about
programs not being updated.

Is there a trick to re installing the s6 programs or have I just made
an obvious mistake?

Re: Rebuilding s6

[Laurent Bercot]

>Is there a trick to re installing the s6 programs or have I just made
>an obvious mistake?

  Generally speaking, --enable-absolute-paths is a bad idea, except in
very specific situations. Things will likely work better without
that option; I suggest you rebuild the packages again without it.

  The step you're missing is probably running s6-linux-init-maker again,
after rebuilding/reinstalling the packages.

  Be aware that the default PATH set by s6-linux-init-maker is
/usr/bin:/bin, and that's what all the services will inherit. If you
have a service that needs a binary in /usr/sbin, make sure to update
the PATH in the run script for the service.
  Alternatively, if your whole infrastructure relies on binaries in
/usr/sbin, you might find it easier to adjust the default PATH for the
supervision tree, via the -p option to s6-linux-init-maker.

  HTH, and good luck,

--
  Laurent