From owner-freebsd-arch Sun Jul 9 0: 5: 1 2000 Delivered-To: freebsd-arch@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C792837C130 for ; Sun, 9 Jul 2000 00:04:58 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6974wR13285 for arch@freebsd.org; Sun, 9 Jul 2000 00:04:58 -0700 (PDT) Date: Sun, 9 Jul 2000 00:04:58 -0700 From: Alfred Perlstein To: arch@freebsd.org Subject: making the snoop device loadable. Message-ID: <20000709000458.M25571@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I noticed that with a bit of hacking the snp device can be made loadable. Making it unloadable is a bit of a pain, but I can implement it using refcounting on the amount of ttys that have snp devices hooked onto them so that the machine doesn't panic if you unload it. The 'problem' that happens is that kern/tty.c now needs to include snoop.h unconditionally, and it also has to provide some exernally visible pointers to functions for the loadable snoop device to hook into. Basically, does anyone have a problem with snp becoming loadable before I commit to finishing off the work? (it's loadable now, but not unloadable). thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message