From owner-freebsd-hackers Wed Feb 10 14:42:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00299 for freebsd-hackers-outgoing; Wed, 10 Feb 1999 14:42:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00294 for ; Wed, 10 Feb 1999 14:42:21 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA19852; Wed, 10 Feb 1999 14:21:29 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdr19844; Wed Feb 10 22:21:26 1999 Date: Wed, 10 Feb 1999 14:21:21 -0800 (PST) From: Julian Elischer To: Brian McGovern cc: hackers@FreeBSD.ORG Subject: Re: How to attach line disciplines (aka Stupid Question #2962) In-Reply-To: <199902101857.NAA00779@bmcgover-pc.cisco.com> 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 use the MODULE_DECALRE macro. (Didn't we answer thsi for you a few days ago?) also see the ng_tty module for netgraph (ftp://ftp.whistle.com/pub/archie/netgraph/index.html) On Wed, 10 Feb 1999, Brian McGovern wrote: > I'm in the process of writing a relatively simple line discipline for doing > some data translations on input and output. I've been looking at the SLIP and > PPP line disciplines as examples, but I haven't quite figured out how to > attach this new line discipline without having a network interface to go > with it. > > What I really need to have happen is on boot time, call a function > vldattach(). This initializes all of the internal strutures, and sets > linesw[x] = my discipline, which should allow applications to change to > discipline X.... Pointers? > -Brian > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message