public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Ebden <peter.ebden@ac.co.nz>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] 64-bit chrooting?
Date: Sun, 13 Aug 2006 13:13:08 +1200	[thread overview]
Message-ID: <44DE7CA4.4080605@ac.co.nz> (raw)

[-- Attachment #1: Type: text/plain, Size: 456 bytes --]

Hi,

I'm trying to build a uclibc system using the Gentoo tarballs on my
amd64 machine. When I try to chroot into it ("linux32 chroot /mnt/gentoo
/bin/bash") I show up as "I have no name@localhost" with a user id of
2^32 or so. There's no change if I don't use linux32 for the chroot.

I can't find anything on the web about this problem. Is this approach
possible with a uclibc chroot? Or do I have to build it from a 32-bit
system?

Thanks,

Peter Ebden

[-- Attachment #2: Type: text/html, Size: 749 bytes --]

             reply	other threads:[~2006-08-13  1:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-13  1:13 Peter Ebden [this message]
2006-08-13  2:10 ` [gentoo-embedded] 64-bit chrooting? Mike Frysinger
2006-08-13  4:16   ` Peter Ebden

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=44DE7CA4.4080605@ac.co.nz \
    --to=peter.ebden@ac.co.nz \
    --cc=gentoo-embedded@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