Gentoo Archives: gentoo-amd64

From: Peter Humphrey <prh@××××××××××.uk>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] chroot howto?
Date: Wed, 13 Jul 2005 10:57:40
Message-Id: 42D4F315.1080408@gotadsl.co.uk
In Reply to: Re: [gentoo-amd64] chroot howto? by Barry.SCHWARTZ@chemoelectric.org
Barry.SCHWARTZ@×××××××××××××.org wrote:

>Peter Humphrey <prh@××××××××××.uk> wrote: > > >>I unpacked an x86 stage 3, and set up hosts, networks and users as >>instructed, but when I tried "linux32 chroot /mnt/gentoo32 /bin/bash" I >>got a permission-refused error on /bin/bash. (I tried both with and >>without --login; it made no difference.) >> >> > >Did you do this as root? > >
Yes, and as myself which gave a slightly different error msg.
>>So I unpacked a portage >>snapshot, rebooted from the installation CD and tried again. I could >>then chroot. I reasoned that /bin/bash could not be executed because >>there was no 32-bit kernel, so I emerged and compiled gentoo-sources in >>/mnt/gentoo32. After that I could chroot from the installed system. >> >> > >You don't need a 32-bit kernel. >
Hmm. Then I'll have to solve the problem above. Meanwhile I have the kernel so perhaps I'll keep it pro tem.
> For a few things it can be convenient >to have kernel sources present, but I don't remember what things those >are. Cross that bridge if you come to it. > >
Ok. < Snip useful scripts - thanks! >
>I maintain my chroot as practically another whole system. That's >wasteful but makes some things a lot easier -- even maintenance is >easier with all that waste, because you are letting portage 'think' >for you about what it needs to install. > >
Tha's more-or-less what I seem to be doing. -- Rgds Peter Humphrey Linux Counter 5290, Aug 93. -- gentoo-amd64@g.o mailing list