On 30/06/14 20:56, Filipe Brandenburger wrote:
> On Mon, Jun 30, 2014 at 12:28 PM, Kay Sievers <k...@vrfy.org> wrote:
>> We should find out when we need to create /lib64 --> $libdir, grr ... :)
>
> Consider the case where you're running Fedora but use debootstrap to
> create a Debian tree and systemd-nspawn to run a process in it.
> $libdir will make sense in Fedora, not in Debian...
In practice, a debootstrap'd 64-bit Debian tree will have to contain its
own /lib64 basically forever, because the generic x86-64 Linux ABI says
it must (even though Debian does not otherwise use lib64 any more);
libc6_*_amd64.deb contains the directory and the ld-linux-x86-64.so
symlink. As long as you don't actively break an existing /lib64 in the
container, everything should be OK?
On current Debian unstable, the only thing in /lib64 is:
lrwxrwxrwx 1 root root 32 Jun 23 22:30 ld-linux-x86-64.so.2 ->
/lib/x86_64-linux-gnu/ld-2.19.so
S
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
