On Wed, May 14, 2014 at 11:50 PM, Laurent Bercot <[email protected]> wrote: >
> power. The original daemontools utilities were lacking that, and I > simply hadn't noticed until I added myself to some group in > /etc/group and what I wanted to do didn't work because the processes > behind s6-setuidgid didn't pick it up. > > You can see it as a bugfix, not as an additional feature. > Maybe. I would guess that setuidgid does it on purpose. But it is harmless to have all the extra groups, I suppose. > > >> The documentation in http://skarnet.org/software/conf-compile.html >> suggests that conf-home should not be touched; but the default makes >> the existence of /package/... mandatory, which is somewhat unexpected >> and shocking when using statically compiled binaries. A few comments >> about this would make it easy to use in less standard setups. > > > I'm afraid I don't understand your point. What are you trying to do > that requires manually setting conf-home ? How does that relate to > using slashpackage and to using statically compiled binaries ? > We talked about this some time ago. If a binary is statically linked, I would expect it to work wherever I put it, since it doesn't matter whether any relevant libraries are there. I know now that this is not true, because the binary may use some hard-coded paths. It happened to me when I copied some binaries to /command in my initramfs (which doesn't include /package). The solution was echo "" >conf-home Thanks Jorge
