Hi all,
An update: current Chaos Calmer HEAD (i.e. latest commit) does correctly
follow symlinks on ar71xx but not x86_64.
That is jails work on ar71xx but not x86_64 with current Chaos Calmer
branch. (as described previously manually addingthe links on x86_64
allows the jails to work).
On 08/10/2015 06:01, Daniel Dickinson wrote:
> Hi again,
>
> It turns out the problem isn't Etienne's code, it is the fstools update
> in revision 47083.
>
> This causes symlinks to not be followed which breaks procd-jail even
> though the real issue is that procd-jail was in fact only working
Ok, I thought I had found the root cause but all I'm left with is that
symlinks aren't followed.
That is when procd-jail is installed and using procd_add_jail (or
manually executing ujail) on x86_64 using squashfs, on (for example)
/usr/sbin/ntpd (which is a symlink to /bin/busybox), then in
Hi all,
Reverting to 15.05 release fails to resolve the issue on x86_64 so I
suspect jails are simply broken on x86_64 due not following symlinks.
For some reason ar71xx does follow the symlinks and does not experience
this issue with the same commit.
Regards,
Daniel
On 2015-10-08 2:45
Hi again,
It turns out the problem isn't Etienne's code, it is the fstools update
in revision 47083.
This causes symlinks to not be followed which breaks procd-jail even
though the real issue is that procd-jail was in fact only working due to
broken behaviour.
Regards,
Daniel
On
Hi all,
In Chaos Calmer revision 46996 which bumps procd to latest git breaks
jails because Etienne's code fails to follow symlinks.
This is a major problem because especially for libraries symlinks are
what is reported int the ELF header (and for busybox 'binaries', or
other multicall
