freemint-discuss

[Freemint-discuss] Chroot Troubles

[Mark D. <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

Re: [Freemint-discuss] Chroot Troubles

[Mark D. <mdu...@at...>]

Thank you sir, that explains everything.

Thanks,
Mark


On 02/19/2018 06:08 AM, Adam Klobukowski wrote:
> IIRC chroot is done in MiNTlib, without kernel involvement. So, it
> depends on how each binary was compiled.
> 
> AdamK
> 
> 
> 
> -- 
> Semper Fidelis
> 
> Adam Klobukowski
> ada...@gm... <mailto:ada...@gm...>

Re: [Freemint-discuss] Chroot Troubles

[Thorsten O. <ad...@th...>]

On Montag, 19. Februar 2018 18:57:52 CET Mark Duckworth wrote:
> IIRC chroot is done in MiNTlib, without kernel involvement. So, it

> > depends on how each binary was compiled.

That's not true. The only thing mintlib does is to implement the chroot() 
posix function, by directing it to the Dchroot() MiNT call.

Re: [Freemint-discuss] Chroot Troubles

[Adam K. <ada...@gm...>]

2018-02-20 17:20 GMT+01:00 Thorsten Otto <ad...@th...>:

> On Montag, 19. Februar 2018 18:57:52 CET Mark Duckworth wrote:
> > IIRC chroot is done in MiNTlib, without kernel involvement. So, it
>
> > > depends on how each binary was compiled.
>
> That's not true. The only thing mintlib does is to implement the chroot()
> posix function, by directing it to the Dchroot() MiNT call.
>
>
It used to be true a long time ago it seems. It also seems that Dchroot()
seems to be very incomplete.

-- 
Semper Fidelis

Adam Klobukowski
ada...@gm...

Re: [Freemint-discuss] Chroot Troubles

[Thorsten O. <ad...@th...>]

On Dienstag, 20. Februar 2018 19:29:06 CET Adam Klobukowski wrote:
> It used to be true a long time ago it seems

I don't think so. If you look at git log -p unix/chroot.c, the last change 
there is from 2001. And even that patch didn't change much, there is nothing 
that indicates that mintlib manages the root directory itself. Wouldn't make 
much sense anyway, since every program would still be able to get out of the 
jail by using the GEMDOS calls directly.

>It also seems that Dchroot() seems to be very incomplete.

Thats more likely the problem. For example, when chrooted, pathnames with 
drive letters shouldn't be allowed (except maybe u:).


PS.: pls send discussions to the list, otherwise ppl. wonder what we are 
talking about ;)

Re: [Freemint-discuss] Chroot Troubles

[Adam K. <ada...@gm...>]

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...