On February 24, 2016 6:11:36 PM EST, Swift Griggs <swiftgri...@gmail.com> wrote: > >When a Linux-binary runs, what does it "see" in terms of the root file >system? So, for example, if I run 'ldconfig', does it see Linux >libraries >in /emul/linux/lib or just "/lib" ? > >Also, how does this play out when I want to run Linux binaries from my >home directory? Ie.. if I wanted to run foobar.exe and it expects to >find >some shared lib in /usr/local/lib does that need to be relative or >absolute? > >What about 32 vs 64 bit binaries, is there any automatic translation or > >chrooting for /emul/linux vs /emul/linux32 ?
For linux emul, it's more like a leaky overlay than a chroot. Processes running as linux emul will generally look in /emul/linux first, and if the desired file/directory isn't found there it'll try /. There are other details, like whiteout entries, magic /../ escape prefixes, etc.. and I believe it's documented in a man page somewhere, but sorry, I don't remember off-hand which one. I'm assuming it's the same for 32-on-64, but I've never looked. Eric