From owner-freebsd-arch Tue Jan 5 04:32:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09999 for freebsd-arch-outgoing; Tue, 5 Jan 1999 04:32:50 -0800 (PST) (envelope-from owner-freebsd-arch@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09994 for ; Tue, 5 Jan 1999 04:32:48 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id NAA10163 for ; Tue, 5 Jan 1999 13:32:18 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id NAA14229 for freebsd-arch@freebsd.org; Tue, 5 Jan 1999 13:32:18 +0100 (MET) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02594; Sun, 3 Jan 1999 16:55:45 -0800 (PST) (envelope-from jmb) Date: Sun, 3 Jan 1999 16:55:45 -0800 (PST) Message-Id: <199901040055.QAA02594@hub.freebsd.org> From: "Jonathan M. Bresler" To: freebsd-arch@FreeBSD.ORG Mail-Followup-To: freebsd-arch@FreeBSD.ORG X-To: Warner Losh In-reply-to: <199901032109.OAA57058@harmony.village.org> (message from Warner Losh on Sun, 03 Jan 1999 14:09:16 -0700) Subject: Re: Implementing a DEVFS daemon References: <199901032109.OAA57058@harmony.village.org> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Consider having a daemon that saves the state of a particular /devfs > tree. This daemon will wake up every now and again and read the > /devfs tree. When it notices changes, it will record them in its > database. This database will be in text format for easy editing. The timing issues seem to be ugly to me. It would be nice if shutdown forced this daemon to roam over the /devfs tree. It almost sounds like we need upcalls from the kernel to the daemon -- at which point I wonder why the daemon is not in the kernel. I still have to read 99% of the kernel, so if this is wacky tell me and I'll shut up. jmb [Personally, I think this sounds like the perfect excuse for implementing file notification in FreeBSD. Somebody at McKusicks course was working on that - if that person is reading this, please speak up! -EE] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message