From owner-freebsd-hackers Tue Jul 11 14:38:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0809E37B958; Tue, 11 Jul 2000 14:38:52 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA03456; Tue, 11 Jul 2000 23:38:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Gary T. Corcoran" Cc: Archie Cobbs , Warner Losh , Mike Smith , FreeBSD Hackers Subject: Re: Module parameters? In-reply-to: Your message of "Tue, 11 Jul 2000 17:03:55 EDT." <396B8BBB.4AA1867D@lucent.com> Date: Tue, 11 Jul 2000 23:38:37 +0200 Message-ID: <3453.963351517@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <396B8BBB.4AA1867D@lucent.com>, "Gary T. Corcoran" writes: >No, I know it's not that easy. We need to be able to do things >like have "TransmissionMode=4" on the kldload command line, and >have that parse the decimal value 4, and then go into the module >and set the value of the TransmissionMode variable to actually be >4 immediately after loading the module into memory, before any of >its subroutines are called. This is what the Linux module loader >allows, and it's extremely useful... I have a much simpler idea: The loader needs to pass an argc+argv to the modules "configure" routine, and the module can do whatever it damn pleases with the passed arguments. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message