From owner-freebsd-hackers Mon Sep 20 18:24:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id 71A6914DB6 for ; Mon, 20 Sep 1999 18:24:15 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp-gw.butya.kz ([192.168.1.193] helo=butya.kz) by lion.butya.kz with esmtp (Exim 2.12 #1) id 11TEd2-0004ny-00; Tue, 21 Sep 1999 08:21:57 +0700 Message-ID: <37E6DDDC.403569A5@butya.kz> Date: Tue, 21 Sep 1999 08:22:36 +0700 From: Boris Popov Organization: @home X-Mailer: Mozilla 4.61 [ru] (X11; I; FreeBSD 3.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: Warner Losh , Matthew Dillon , Chuck Robey , Julian Elischer , Wayne Cuddy , FreeBSD Hackers List Subject: Re: what is devfs? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > 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. Why not to create a simple 'devfs' device ? devfsd can sleep at polling it and devfs device itself can provide hooks in the kernel to register all important events and pass them to devfsd. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message