On Tue, Feb 07, 2017 at 03:08:58PM -0500, Rich Freeman wrote
> I suspect sticking something like this before the chroot command might
> do the trick:
> unshare -p -f --mount-proc -m -i -u
>
> That will create a new PID, mount, IPC, and UTS namespace for the
> chroot. If you do the mounts after t
On Tue, Feb 07, 2017 at 03:34:46PM -0500, Mike Gilbert wrote
> On Tue, Feb 7, 2017 at 3:08 PM, Rich Freeman wrote:
> > I suspect sticking something like this before the chroot command might
> > do the trick:
> > unshare -p -f --mount-proc -m -i -u
> >
> > That will create a new PID, mount, IPC, an
On Tue, Feb 07, 2017 at 03:08:58PM -0500, Rich Freeman wrote
>
> Did setting up those mounts actually work? They should have.
>
> As far as unmounting goes, the handbook instructions recursively set
> up some mounts so you need to unmount stuff like /dev/pts before
> umounting /dev (and there mi
On Tue, Feb 7, 2017 at 3:08 PM, Rich Freeman wrote:
> I suspect sticking something like this before the chroot command might
> do the trick:
> unshare -p -f --mount-proc -m -i -u
>
> That will create a new PID, mount, IPC, and UTS namespace for the
> chroot.
Using unshare may require another kern
On Tue, Feb 7, 2017 at 2:54 PM, Walter Dnes wrote:
>
> Any idea how to gracefully handle the missing /dev problem? I tried
> mounting /dev, /proc, and /sys, similar to the chroot process in the
> Gentoo install instructions. But I couldn't unmount afterwards, short
> of rebooting. If it's not
On Tue, Feb 07, 2017 at 10:25:10AM -0500, Mike Gilbert wrote
> You probably have the CONFIG_IA32_EMULATION kernel option disabled.
Thanks again. It's a large step in the right direction. Now it's...
===
[i660][root][~]
On Mon, Feb 6, 2017 at 10:40 PM, Walter Dnes wrote:
>
> What I'd like to do is a 32-bit CentOS chroot inside my 64-bit Gentoo
> desktop host. I'm looking at rsync'ing the / directory from inside the
> CentOS VM file system to a directory on the 64-bit host, and then chroot
> into the copy on th
On Tue, Feb 07, 2017 at 10:25:10AM -0500, Mike Gilbert wrote
> You probably have the CONFIG_IA32_EMULATION kernel option disabled.
[i660][root][~] grep CONFIG_IA32_EMULATION /usr/src/linux/.config
# CONFIG_IA32_EMULATION is not set
Thanks, you're right. I've just done "emerge --sync" and now
On Tue, Feb 7, 2017 at 10:13 AM, Walter Dnes wrote:
> On Tue, Feb 07, 2017 at 08:24:40AM +, J. Roeleveld wrote
>
>> I used to do this to build packages for my old 32bit netbook.
>>
>> To start a 32bit chroot:
>> # linux32 chroot /bin/bash
>
> I transferred over the CentOS system. It fails
On 07/02/2017 17:13, Walter Dnes wrote:
> On Tue, Feb 07, 2017 at 08:24:40AM +, J. Roeleveld wrote
>
>> I used to do this to build packages for my old 32bit netbook.
>>
>> To start a 32bit chroot:
>> # linux32 chroot /bin/bash
>
> I transferred over the CentOS system. It fails on my syste
On Tue, Feb 07, 2017 at 08:24:40AM +, J. Roeleveld wrote
> I used to do this to build packages for my old 32bit netbook.
>
> To start a 32bit chroot:
> # linux32 chroot /bin/bash
I transferred over the CentOS system. It fails on my system with
"Exec format error"
[i660][root][~] chroot
On February 7, 2017 4:40:56 AM GMT+01:00, Walter Dnes
wrote:
> Right now, I'm using a 32-bit CentOS QEMU VM to build Pale Moon for
>older machines. There's the usual processing overhead of a VM, plus it
>has to have it's own virtual disks with safety margin of space, plus 5
>gigabytes of swap s
Right now, I'm using a 32-bit CentOS QEMU VM to build Pale Moon for
older machines. There's the usual processing overhead of a VM, plus it
has to have it's own virtual disks with safety margin of space, plus 5
gigabytes of swap space inside the VM.
What I'd like to do is a 32-bit CentOS chroo
13 matches
Mail list logo
