From owner-freebsd-arch Fri Jul 14 15: 0:47 2000 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 7B79637BE9A; Fri, 14 Jul 2000 15:00:42 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA59339; Fri, 14 Jul 2000 15:00:37 -0700 (PDT) Date: Fri, 14 Jul 2000 15:00:36 -0700 (PDT) From: Julian Elischer To: Warner Losh Cc: Adrian Chadd , freebsd-arch@FreeBSD.ORG Subject: Re: SysctlFS In-Reply-To: <200007142145.PAA39245@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jul 2000, Warner Losh wrote: > In message <20000714124805.F17372@ywing.creative.net.au> Adrian Chadd writes: > : As I said in my previous email, persistence isn't the primary problem > : in my eyes. There are many ways people can handle it. What I see as being > : an interesting problem is handling devfs across multiple process/group > : namespaces (jail/chroot) without cluttering up your mount table. > > Yes. Another issue is the new hot plug devices. It is highly > desirable to allow arbitrary commands to run when they come and go. > I have some solutions for both problems.. At least for the devfs in jail problems.. in particular a variant on a symbolic link which is interpretted as a symlink into /dev this would allow many /devs to exist without many mounted filesystems in each jail > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message