2018-03-03 05:39:35 UTC
USBstik, eg. TinyCore64 [or slax 64bit right now].
AFAIK, this should not be posssible without extra <mount-bind>
to make /dev ...etc. accessible to the <booted partition> ?!
Here's the <status> :--
***@slax:~# mount | grep sdb4
/dev/sdb4 on /sdb4 type ext3 (rw,relatime,data=ordered)
***@slax:~# chroot /sdb4/Slak which mozilla
and the chrooted mozilla does gmail!
***@slax:~# chroot /sdb4/Slak which pan
/usr/bin/pan <-- also runs 32bit in 64bit booted partition?!
...and writing THIS via 32bit pan!!
***@slax:~# chroot /sdb4/Slak ls -l /dev |wc -l
So `chroot /sdb4/Slak` has access to <all the /dev dirs>;
but I'm not using a modem, like originally; I've got WiFi
from slax. Does WiFi also I/O via /dev/* ?
***@slax:~# chroot /sdb4/Slak ls -l /proc |wc -l
***@slax:~# chroot /sdb4/Slak pstree
/proc is empty (not mounted ?)
That's WHY <chroot anything> should NOT be able to connect to
And what about, as expected, I can't chroot from this 64bit
booted installation, to most of my Slak13:32bit apps;
but I CAN to mozilla:gmail and pan: both 32bit apps ?
??? How does the WiFi <leak over> between the booted-installation
and the chrooted-installation ?