From owner-freebsd-hackers Tue Mar 10 01:11:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17086 for freebsd-hackers-outgoing; Tue, 10 Mar 1998 01:11:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17074 for ; Tue, 10 Mar 1998 01:11:31 -0800 (PST) (envelope-from tcobb@staff.circle.net) From: tcobb@staff.circle.net Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Tue, 10 Mar 1998 04:01:35 -0500 Message-ID: <8188AD2EBC3CD111B7A30060082F32A40C3FA7@freya.circle.net> To: hackers@FreeBSD.ORG Subject: RE: UNION FS appropriate? Date: Tue, 10 Mar 1998 04:01:33 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, March 10, 1998 4:07 AM, Eivind Eklund wrote: > On Mon, Mar 09, 1998 at 11:30:51PM -0800, Julian Elischer wrote: > > You don't need chroot. > > I'm fairly certain Julian is trying to say 'union' here, just to clear > up any confusion. > Yup. For those watching from home, it appears that the solution to my dilemma may in fact be NULLFS. I've now done a test quick test on a dog of a machine (P75, 32MB) mounting 1000 NULLFS mounts with no discernable issues. The only problem I can find is that the NULLFS implementation doesn't respect rdonly mount options. I suspect that it uses the mount options of the underlying FS. Still exploring that part of it. - Troy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message