From owner-freebsd-arch Wed Nov 28 10:44:35 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 15C2D37B419; Wed, 28 Nov 2001 10:44:32 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fASIhFV38119; Wed, 28 Nov 2001 19:43:15 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: Josef Karthauser , Garrett Wollman , mjacob@feral.com, arch@FreeBSD.ORG Subject: Re: Anybody working on devd? In-Reply-To: Your message of "Wed, 28 Nov 2001 13:03:58 EST." Date: Wed, 28 Nov 2001 19:43:15 +0100 Message-ID: <38117.1006972995@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Robert Watson writes: >Note that the race can be fixed by modifying your source of events for >"the common application". Hence my recommendation (made after your post, >as I caught up) that devd/devfsd feed off of a /dev/somethinginparticular, >and that they generate event information on /dev/somethingmoregeneral, >[...] And where do you want to run the devd for jails ? Inside the jail ? Do you really want to spend a process per jail to be able to open a PTY in the jail ? It doesn't scale... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message