From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JWVDt-0005wR-K7
	for qemu-devel@nongnu.org; Tue, 04 Mar 2008 06:22:17 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JWVDr-0005uD-QA
	for qemu-devel@nongnu.org; Tue, 04 Mar 2008 06:22:17 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JWVDr-0005u3-GD
	for qemu-devel@nongnu.org; Tue, 04 Mar 2008 06:22:15 -0500
Received: from miranda.se.axis.com ([193.13.178.8])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <edgar@axis.com>) id 1JWVDq-0005Lo-RR
	for qemu-devel@nongnu.org; Tue, 04 Mar 2008 06:22:15 -0500
Received: from axis.com (edgar.se.axis.com [10.93.151.1])
	by miranda.se.axis.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	m24BMCps022024
	for <qemu-devel@nongnu.org>; Tue, 4 Mar 2008 12:22:12 +0100
Date: Tue, 4 Mar 2008 12:22:12 +0100
From: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
Subject: Re: [Qemu-devel] [PATCH] -chroot and -su options.
Message-ID: <20080304112212.GA9347@edgar.se.axis.com>
References: <200803031828.22657.rob@landley.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200803031828.22657.rob@landley.net>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org

On Mon, Mar 03, 2008 at 06:28:22PM -0600, Rob Landley wrote:
> Quick and dirty patch to teach qemu application emulation how to chroot (and
> drop privs), so you don't have to pollute a target filesystem with host code,
> and/or figure out how to build qemu static in order to run a dynamic binary.

Hi Rob,

Right, doing the chroot from within qemu avoids the issue with polluting the target/. Thanks for the example.
 
The chroot approach still suffers from the need of initially having higher privileges. Personally, I still prefer the sysroot option and avoid that need but either way helps me.

Best regards
-- 
Edgar E. Iglesias
Axis Communications AB