From owner-freebsd-hackers Mon Sep 20 9:29:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E34D5150AF for ; Mon, 20 Sep 1999 09:29:28 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA96358; Mon, 20 Sep 1999 10:29:27 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA18279; Mon, 20 Sep 1999 10:28:45 -0600 (MDT) Message-Id: <199909201628.KAA18279@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: what is devfs? Cc: Matthew Dillon , Chuck Robey , Julian Elischer , Wayne Cuddy , FreeBSD Hackers List In-reply-to: Your message of "Mon, 20 Sep 1999 11:49:20 EDT." References: Date: Mon, 20 Sep 1999 10:28:45 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : Well, with devd or devfsd its still going to read the persistant store : when started by the system on reboot; I'd imagine you'd be able to : make checkpoint intervals tunable and tell it which permission updates you : wanted to ignore and use the defaults; tty devices come to mind. Yes. That's true. That's why the idea of devfsd is simple, but implementing it well enough for people to be happy with it is much much harder. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message