Jean-Paul Calderone wrote:
> On Wed, 11 Feb 2009 09:31:56 -0600, Nick Craig-Wood
> wrote:
> >r0g wrote:
> >> I'm writing a linux remastering script in python where I need to chroot
> >> into a folder, run some system commands and then come out and do some
> >> tidying up, un-mounting proc &
On Wed, 11 Feb 2009 09:31:56 -0600, Nick Craig-Wood wrote:
r0g wrote:
I'm writing a linux remastering script in python where I need to chroot
into a folder, run some system commands and then come out and do some
tidying up, un-mounting proc & sys etc.
I got in there with os.chroot() and I
r0g wrote:
> I'm writing a linux remastering script in python where I need to chroot
> into a folder, run some system commands and then come out and do some
> tidying up, un-mounting proc & sys etc.
>
> I got in there with os.chroot() and I tried using that to get back out
> but that didn't
Dennis Lee Bieber schrieb:
> That's the whole purpose of chroot()... As far as the process is
> concerned, the chroot() path is now the top of the file system, so there
> is no where above it you can get to...
Yes, you can get with some hacks.
> chroot() is meant for cases where one may be
I'm writing a linux remastering script in python where I need to chroot
into a folder, run some system commands and then come out and do some
tidying up, un-mounting proc & sys etc.
I got in there with os.chroot() and I tried using that to get back out
but that didn't work so... is my script trapp
