Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753808Ab2BFGdn (ORCPT ); Mon, 6 Feb 2012 01:33:43 -0500 Received: from out.selfhost.de ([82.98.82.95]:52867 "EHLO outgoing.selfhost.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751432Ab2BFGdm (ORCPT ); Mon, 6 Feb 2012 01:33:42 -0500 Message-ID: <4F2F7438.8040600@afaics.de> Date: Mon, 06 Feb 2012 07:33:28 +0100 From: Harald Dunkel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120202 Thunderbird/10.0 MIME-Version: 1.0 To: Michael Tokarev CC: Kernel Mailing List Subject: Re: /proc/self/mounts in chroot vs lxc References: <4F2E4120.3030506@afaics.de> <4F2E5B08.4010200@msgid.tls.msk.ru> In-Reply-To: <4F2E5B08.4010200@msgid.tls.msk.ru> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1118 Lines: 34 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/05/12 11:33, Michael Tokarev wrote: > > But plain chroot does not create new namespace, the process inherits parent namespace, so there is no way to clean in up cleanly. > If I do a chroot to /mnt, then there is no "/mnt" in /proc/self/mounts within this environment. Instead I see yet another entry for '/'. This certainly looks like something private. Maybe it would be easier for everybody if /proc/mounts (without "/self") could always show the "real" mount points at the top level? A bind mount of /abc to /mnt/abc would appear as /mnt/abc in /proc/mounts at all levels. I could live with that. Regards Harri -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk8vdDQACgkQUTlbRTxpHjcQOgCfXwKqVu7mAFTDctvcs1YAMQCq FIsAn2UHiL+TncraqQffzdecN0eMadJy =huO6 -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/