public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Cc: Peter Ebden <peter.ebden@ac.co.nz>
Subject: Re: [gentoo-embedded] 64-bit chrooting?
Date: Sat, 12 Aug 2006 22:10:23 -0400	[thread overview]
Message-ID: <200608122210.23837.vapier@gentoo.org> (raw)
In-Reply-To: <44DE7CA4.4080605@ac.co.nz>

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

On Saturday 12 August 2006 21:13, Peter Ebden wrote:
> 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.

sounds like you disabled 16bit uid syscall support in the kernel

uclibc 0.9.28 does not support the 32bit uid syscalls but ive fixed this in 
latest uClibc svn ...
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2006-08-13  2:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-13  1:13 [gentoo-embedded] 64-bit chrooting? Peter Ebden
2006-08-13  2:10 ` Mike Frysinger [this message]
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=200608122210.23837.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-embedded@lists.gentoo.org \
    --cc=peter.ebden@ac.co.nz \
    /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