public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What to put in chroot mtab
Date: Fri, 01 Aug 2014 08:28:01 -0500	[thread overview]
Message-ID: <53DB95E1.5010709@gmail.com> (raw)
In-Reply-To: <6536155.f0GWtIUbSO@wstn>

Peter Humphrey wrote:
> On Friday 01 August 2014 14:07:08 I wrote:
>
>> I run a couple of chroots on this box to build packages for other boxes on
>> the LAN. So far, I haven't worked out what I should populate /etc/mtab with
>> in each chroot. Is it enough to "grep ext4 /etc/mtab >
>> /mnt/chroot/etc/mtab"? That catches all the physical partitions, but I
>> imagine I need to add some /proc, /sys and /dev entries as well, but is
>> there a simple formula for doing this?
> I meant to add that one chroot is 32-bit and the other is 64. The host is an 
> i5 running openrc.
>

It has been a good while since I used this.  So, make sure it makes
sense to you before trying this.  This may not work if something has
changed in the past several years.  Use with caution if at all. 

This is a little script, if you want to call it that, that I used to do
mine.  It also lists the command to use to do a 32 bit chroot from a 64
bit rig.  Here it is:

root@fireball / # cat /root/xx.chroot-mount-32bit


mount -o bind /dev /mnt/gentoo32/dev
mount -o bind /dev/pts /mnt/gentoo32/dev/pts
mount -o bind /dev/shm /mnt/gentoo32/dev/shm
mount -o bind /proc /mnt/gentoo32/proc
mount -o bind /proc/bus/usb /mnt/gentoo32/proc/bus/usb
mount -o bind /sys /mnt/gentoo32/sys
mkdir -p /mnt/gentoo32/usr/portage/
mount -o bind /usr/portage /mnt/gentoo32/usr/portage/


echo " mounting finished"

echo "run linux32 chroot /mnt/gentoo32 /bin/bash next"
root@fireball / #


You may have different mount points at the very least so edit to match
what you have.  Again, things could have changed and that no longer will
work.  It may not be a bad idea to let someone who has done this more
recently to give a thumbs up to that. 

That last command should be:

linux32 chroot /mnt/gentoo32 /bin/bash

Dale

:-)  :-) 


  reply	other threads:[~2014-08-01 13:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 13:07 [gentoo-user] What to put in chroot mtab Peter Humphrey
2014-08-01 13:12 ` Peter Humphrey
2014-08-01 13:28   ` Dale [this message]
2014-08-01 20:46     ` J. Roeleveld
2014-08-01 21:31       ` Canek Peláez Valdés
2014-08-01 21:33         ` Canek Peláez Valdés
2014-08-01 21:39           ` J. Roeleveld
2014-08-01 21:44             ` Canek Peláez Valdés
2014-08-01 21:46               ` Canek Peláez Valdés
2014-08-02  0:27                 ` J. Roeleveld
2014-08-02  0:21               ` J. Roeleveld
2014-08-02 10:08               ` Peter Humphrey
2014-08-01 23:39       ` Dale
2014-08-01 14:56   ` Peter Humphrey
2014-08-01 15:00   ` Canek Peláez Valdés
2014-08-01 15:07     ` Rich Freeman
2014-08-01 15:25       ` Peter Humphrey
2014-08-01 15:21     ` Peter Humphrey
2014-08-01 15:29       ` Canek Peláez Valdés
2014-08-01 16:50         ` Peter Humphrey
2014-08-02 18:28         ` Rich Freeman
2014-08-01 14:02 ` Rich Freeman
2014-08-01 19:32 ` Neil Bothwick
2014-08-01 20:40   ` J. Roeleveld
2014-08-02 10:38   ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53DB95E1.5010709@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox