|
From: Adam K. <ada...@gm...> - 2018-02-27 22:44:49
|
IIRC chroot is done in MiNTlib, without kernel involvement. So, it depends on how each binary was compiled. AdamK 2018-02-17 4:38 GMT+01:00 Mark Duckworth <mdu...@at...>: > Hello all, > > Once upon a time I was told that chroot in mint works fine. I decided > to try it and on the surface it looks good but when I dig deeper there > is issues. Here it is demonstrated. Current kernel, coreutils chroot > binary. > > Create a bootstrap under /root/bootstrap Not much under there, just > coreutils, rpm and a few other things. > > root@bf3:/root>chroot /root/bootstrap /bin/bash > bash-2.05a# pwd > /e/root/bootstrap > bash-2.05a# ls > bin etc sbin usr var > bash-2.05a# > > Ok so bash doesn't find anything which means bash is respecting the > chroot. We did change directories but pwd can see it is not in a new root. > > bash-2.05a# ls > bin etc sbin usr var > bash-2.05a# pwd > / > bash-2.05a# > > Ok but we can go to / and the chroot is adhered to. Maybe we can > proceed. What is under /var > > bash-2.05a# ls > adm catman log > bash-2.05a# > > Ok so proceed. > > bash-2.05a# rpm -qa > automake-1.11.1-1 > info-4.0-2 > cpio-2.4.2-3 > procps-ng-3.3.2-1 > bzip2-1.0.2-1 > > .... > > and so on. The rpm database is the one from outside the chroot. Any > ideas? > > Thanks, > > Mark > > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Freemint-discuss mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemint-discuss > -- Semper Fidelis Adam Klobukowski ada...@gm... |