From owner-freebsd-hackers Mon Sep 20 10:36:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 278AE15119 for ; Mon, 20 Sep 1999 10:36:14 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id NAA04173; Mon, 20 Sep 1999 13:35:39 -0400 (EDT) Date: Mon, 20 Sep 1999 13:35:38 -0400 (EDT) From: "Matthew N. Dodd" To: Warner Losh Cc: Matthew Dillon , Chuck Robey , Julian Elischer , Wayne Cuddy , FreeBSD Hackers List Subject: Re: what is devfs? In-Reply-To: <199909201628.KAA18279@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Sep 1999, Warner Losh wrote: > 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. I think a minimal feature set for the first rev would satisify 90% of those wanting persistence no? ie just tracking permissions and owners for everything, and restoring them to their previous state on startup. This would require that devfsd be started fairly early. Adding a tunable checkpoint interval would be fairly simple. Beyond that it would be a matter of what specific features the 'power users' wanted. This simple behavior would nearly exactly mimic the behavior of a normal filesystem based /dev. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message