I have installed Linux (Ubuntu distro) on my Android tablet, a Nexus 7 (no SD card at all), in a so-called CHroot install.
I am a Linux beginner, so my understanding is quite limited.
When in Linux (using a terminal emulator on the SSH service, logged in as root), I list the contents of the top level "/" directory and can see 18 directories, including: bin proc sys mnt srv home srv ..... and others
When using the Android app "ES File Explorer" (aka FX), I can only see 13 folders. There is some overlap, but some directories are unique to the FX view, and some are missing.
For example, the folder '/vendor' is visible in FX, but not on the linux terminal. Also, the folder /mnt shows different contents when I check it in FX versus the linux terminal.
I created a new test directory on the linux terminal, but cannot "see' it when I use FX.
I should note that my Android tablet has been rooted (verified), and I have turned on the Root option inside ES File Explorer, which allows me to successfully browse the "/" directory and subdirectories.
Why do I see a different directory structure when I view it via linux terminal versus the Android File Explorer?
Hours later: Having read up more on Linux Deploy, it seems to me that use of the "chroot" feature is part of the explanation - the root level and tree structure for the Linux environment is located at a lower level somewhere within the Android 'main system's tree structure - a "virtual" root so to speak.
However, that still means I should be able to "see" it using FX, shouldn't it? And how do I know where this virtual root is located within the Android tree?