From: Peter Humphrey <prh@gotadsl.co.uk>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] chroot howto?
Date: Wed, 13 Jul 2005 11:55:17 +0100 [thread overview]
Message-ID: <42D4F315.1080408@gotadsl.co.uk> (raw)
In-Reply-To: <20050713100551.GA8904@crud.crud.mn.org>
Barry.SCHWARTZ@chemoelectric.org wrote:
>Peter Humphrey <prh@gotadsl.co.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@gentoo.org mailing list
prev parent reply other threads:[~2005-07-13 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 9:03 [gentoo-amd64] chroot howto? Peter Humphrey
2005-07-13 10:05 ` Barry.SCHWARTZ
2005-07-13 10:55 ` Peter Humphrey [this message]
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=42D4F315.1080408@gotadsl.co.uk \
--to=prh@gotadsl.co.uk \
--cc=gentoo-amd64@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