Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261836AbTKBUta (ORCPT ); Sun, 2 Nov 2003 15:49:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261837AbTKBUt3 (ORCPT ); Sun, 2 Nov 2003 15:49:29 -0500 Received: from madrid10.amenworld.com ([62.193.203.32]:7693 "EHLO madrid10.amenworld.com") by vger.kernel.org with ESMTP id S261836AbTKBUt2 (ORCPT ); Sun, 2 Nov 2003 15:49:28 -0500 Date: Sun, 2 Nov 2003 21:49:34 +0100 From: DervishD To: Linux-kernel Subject: Using proc in chroot environments Message-ID: <20031102204934.GB54@DervishD> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4i Organization: Pleyades User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1388 Lines: 34 Hi all :) I'm using a chroot environment on my main disk as a 'crash test dummy', and I need to access the proc filesystem inside it. Since hard links are not allowed for directories, the only solution I can think of is to mount proc inside the chroot environment just after chrooting. This works, I've tested, but I have two problems: - Any change in the chroot proc happens too in the main one (like using /proc/sys/kernel variables). Not a big deal, since I want the chroot environment to mimic the main filesystem where the original proc is mounted, but is annoying. - I must mount copies of devpts, usbfs, etc... under the 'second' proc, too, and this is even more annoying. The perfect solution for me is to hardlink the proc directory of the chrooted environment to the proc directory on the true root dir, but since this is not possible, whan can I do instead of remounting a second copy of proc (which, by the way, makes /proc/mounts a little bit weird...)? Thanks a lot in advance :)) Ra?l N??ez de Arenas Coronado -- Linux Registered User 88736 http://www.pleyades.net & http://raul.pleyades.net/ - 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/