From owner-freebsd-hackers Sun Feb 10 9:40: 1 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d31.as13.nwbl0.wi.voyager.net [169.207.135.159]) by hub.freebsd.org (Postfix) with ESMTP id DD90237B405 for ; Sun, 10 Feb 2002 09:39:56 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g1ABhqq28131; Sun, 10 Feb 2002 11:43:52 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Sun, 10 Feb 2002 11:43:52 +0000 (GMT) From: Mike Silbersack To: Guy Helmer Cc: hackers@FreeBSD.ORG Subject: RE: nullfs and unionfs In-Reply-To: <000001c1b24e$ffacea40$0200000a@spencer> Message-ID: <20020210113701.S28078-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 10 Feb 2002, Guy Helmer wrote: > It looks like there are still some serious problems with this. I just > tried a similar thing on FreeBSD 4.4 and 4.5. I created a directory of > binaries to use for multiple jails, then null-mounted (read-only) the > binaries for each of the jails to use. To allow the /etc and other > parts of the jails to be written, I union-mounted a per-jail writeable > filesystem over each of the null mounts. It seemed to work well until > my jail setup program actually started a binary from inside the jail > (i.e., from the null mount) when the kernel panic'ed with trap 12. > > > Guy Helmer > Palisade Systems, Inc. If I'm not mistaken, nullfs had been fixed significantly in -current, but the changes were not MFC'd... I'm not entirely sure on this, you might wish to consult cvsweb to verify what has / has not been merged. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message