From owner-freebsd-ports Fri Dec 3 21:27:21 1999 Delivered-To: freebsd-ports@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id B9F2214D2F; Fri, 3 Dec 1999 21:27:13 -0800 (PST) (envelope-from darius@dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id PAA07250; Sat, 4 Dec 1999 15:55:04 +1030 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 04 Dec 1999 15:53:09 +1030 (CST) From: "Daniel J. O'Connor" To: Nick Hibma Subject: RE: modules in ports Cc: FreeBSD Ports Mailing List Cc: FreeBSD Ports Mailing List , FreeBSD CURRENT Mailing List Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 03-Dec-99 Nick Hibma wrote: > Has anyone ever devised a good way to put a module in a port? Well the skip port creates a module.. > Maybe it is the more general question of how to relate modules to > other parts of the base system, like the kernel, downloadable firmware > files, etc. Urk! :) Creating a module which will build outside the source tree is fairly simple, for an example have a look at wpaul's if_dc driver which does this. Then you can just install in in /usr/local/share/myport/kld and load it from /usr/local/etc/rc.d/myport.sh --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message