From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-embedded+bounces-3281-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1NKXxb-0002sD-Bc
for garchives@archives.gentoo.org; Tue, 15 Dec 2009 14:01:07 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 17F81E091F;
Tue, 15 Dec 2009 14:00:58 +0000 (UTC)
Received: from mail-fx0-f225.google.com (mail-fx0-f225.google.com [209.85.220.225])
by pigeon.gentoo.org (Postfix) with ESMTP id BAA7DE0928
for <gentoo-embedded@lists.gentoo.org>; Tue, 15 Dec 2009 14:00:57 +0000 (UTC)
Received: by fxm25 with SMTP id 25so4200456fxm.26
for <gentoo-embedded@lists.gentoo.org>; Tue, 15 Dec 2009 06:00:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:from:date:message-id:subject:to:content-type;
bh=Tq+ALnu52gdCEwtdt3GhDBlvuv2VWmL7ELnEXPTfP6g=;
b=rQ913liZMtbelcX+8Pl5G4mdDIDWb0rZfeUiG4HB5u5h5lE9dWGFt0jJEFCzO4SjRF
Q4aIxWzIEbsBUXjsDhLhJAIpFAR+h6HzpE3EFzI3KkLSpkhDjgtPOVDZFg1npKAnKwAE
ftqF9HZIhbFHdk6IOjNeDTbcQ1A2vYx5eoTvY=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:content-type;
b=xUQ7w1En9frb9k/T2QFRivbP9OyuhF1ATwptrw2sCk3gC6xVeukiqAC+81FsupfDrQ
jwsdqASyZxkNnufiLjlnc1NxX0IXv7mXTCYpnhkivgbsapzbQ0ANkQMFS+7+0wVCK4pl
fGuAyjMs/6LprkL+qO9hPk1MxhBaU0gN5wHCA=
Precedence: bulk
List-Post: <mailto:gentoo-embedded@lists.gentoo.org>
List-Help: <mailto:gentoo-embedded+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-embedded+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-embedded+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-embedded.gentoo.org>
X-BeenThere: gentoo-embedded@lists.gentoo.org
Reply-to: gentoo-embedded@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.223.97.155 with SMTP id l27mr1606510fan.91.1260885657168; Tue,
15 Dec 2009 06:00:57 -0800 (PST)
In-Reply-To: <1260883909.9491.2.camel@gentoo-dev>
References: <166af1cf0912140817j66fb0ba3q96f1e8285790bc8@mail.gmail.com>
<4B267265.7080406@wildgooses.com> <3dc1583f0912140947q106e673fkcb541cc8929c0321@mail.gmail.com>
<20091214180657.29028.qmail@stuge.se> <4B274E81.7060005@chaintronics.com>
<20091215103359.12281.qmail@stuge.se> <1260883909.9491.2.camel@gentoo-dev>
From: Shinkan <shinkan@gmail.com>
Date: Tue, 15 Dec 2009 15:00:37 +0100
Message-ID: <166af1cf0912150600m56ddf384ve30cb972d1555b01@mail.gmail.com>
Subject: Re: [gentoo-embedded] emerge --root : users not created
To: gentoo-embedded@lists.gentoo.org
Content-Type: multipart/alternative; boundary=0015174c3520b2ad4b047ac4d15d
X-Archives-Salt: b6c4af5a-b401-4a40-834c-8622003c5001
X-Archives-Hash: 4328384c0f6f7480313ac865dcfac368
--0015174c3520b2ad4b047ac4d15d
Content-Type: text/plain; charset=UTF-8
2009/12/15 Ahmed Ammar <b33fc0d3@gentoo.org>
>
> Well how exactly do you expect chroot to succeed when the host is x86
> and the ${ROOT} is arm?
>
To some questions I read :
I use a amd64 host to build amd64 targets environments.
I use cross-emerge and not crossdev or chroot because my target don't have
and WILL NOT have portage, gcc, make or any other build-related tool. My
targets will run on livecd, so they won't even have (tmp-excluded) writing
needs.
My build needs REQUIRES by process that I could not even put gcc/portage/etc
on my target, chroot and build with them, then remove them.
For now, I think of chrooting to useradd manually, or copying some
pre-generated /etc/{passwd,shadow,group,...} to my target dir.
I do think it's a bug, because man emerge says that --root is supposed to do
everything emerge could do but somewhere else.
If I emerge locally a ebuild that makes a user, I expect emerge
--root=/target to also make users on /target filesystem.
--
Pierre.
"Sometimes when I'm talking, my words can't keep up with my thoughts. I
wonder why we think faster than we speak. Probably so we can think twice." -
Bill Watterson
--0015174c3520b2ad4b047ac4d15d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">2009/12/15 Ahmed Ammar <span dir=3D"ltr"=
><<a href=3D"mailto:b33fc0d3@gentoo.org">b33fc0d3@gentoo.org</a>></sp=
an><br><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rg=
b(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class=3D"im">
<br>
</div>Well how exactly do you expect chroot to succeed when the host is x86=
<br>
and the ${ROOT} is arm?<br></blockquote><div><br><br>To some questions I re=
ad :<br>I use a amd64 host to build amd64 targets environments.<br>I use cr=
oss-emerge and not crossdev or chroot because my target don't have and =
WILL NOT have portage, gcc, make or any other build-related tool. My target=
s will run on livecd, so they won't even have (tmp-excluded) writing ne=
eds.<br>
My build needs REQUIRES by process that I could not even put gcc/portage/et=
c on my target, chroot and build with them, then remove them.<br><br>For no=
w, I think of chrooting to useradd manually, or copying some pre-generated =
/etc/{passwd,shadow,group,...} to my target dir.<br>
<br>I do think it's a bug, because man emerge says that --root is suppo=
sed to do everything emerge could do but somewhere else.<br>If I emerge loc=
ally a ebuild that makes a user, I expect emerge --root=3D/target to also m=
ake users on /target filesystem.<font color=3D"#888888"><br>
</font></div></div><br clear=3D"all"><br>-- <br>Pierre.<br>"Sometimes =
when I'm talking, my words can't keep up with my thoughts. I wonder=
why we think faster than we speak. Probably so we can think twice." -=
Bill Watterson<br>
--0015174c3520b2ad4b047ac4d15d--