From owner-freebsd-arch Wed Feb 21 11:49:43 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id DF64E37B491 for ; Wed, 21 Feb 2001 11:49:37 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net ([10.32.2.26]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 152C5JGR; Wed, 21 Feb 2001 14:49:42 -0500 Reply-To: Randell Jesup To: Terry Lambert Cc: jonathan@graehl.org (Jonathan Graehl), freebsd-arch@FreeBSD.ORG Subject: Re: modifying config files for a running daemon References: <200102202219.PAA28977@usr05.primenet.com> From: Randell Jesup Date: 21 Feb 2001 14:50:23 -0500 In-Reply-To: Terry Lambert's message of "Tue, 20 Feb 2001 22:18:59 +0000 (GMT)" Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: >> Providing it on an arbitrary FS _without_ requiring the writer to >> use the defined protocol would be quite a hairy change to make, of course. > >Actually, it's pretty trivial; it's one area where a stacking >layer wouldn't need it's own vnodes in order to stack. > >You could do it by building a pseudo-vector instance for each >mount when you were creating the VFS instance. The pseudo-vector >would catch the event, and then call the real vector. Hmmm, I hadn't considered the VFS layer. Ignoring networked FS's (since NFS wouldn't support this directly, I assume, without extensions), this should work. >You couldn't just tag the system calls, since write faults as >a result of mmap() don't go through the system call path. Right. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message