From owner-freebsd-hackers  Wed Sep 10 18:39:15 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA13742
          for hackers-outgoing; Wed, 10 Sep 1997 18:39:15 -0700 (PDT)
Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA13737
          for <freebsd-hackers@freebsd.org>; Wed, 10 Sep 1997 18:39:09 -0700 (PDT)
Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA06133;
	Thu, 11 Sep 1997 11:07:11 +1000 (EST)
Message-Id: <199709110107.LAA06133@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Simon Shapiro <Shimon@i-Connect.Net>
cc: freebsd-hackers@freebsd.org
Subject: Re: /usr/include/sys How To question 
In-reply-to: Your message of "Wed, 10 Sep 1997 16:50:31 MST."
             <XFMail.970910165031.Shimon@i-Connect.Net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 11 Sep 1997 11:07:07 +1000
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> How do I integrate opt_dlm.h into sys/dlm.h so that it will reflect the
> proper sizing? If the kernel was built on the target machine, it is simple.
> If not, it can be nasty.  

Think about it for a second, and you will realise that what you ask is 
impossible.  (imagine two kernels built with different values, eg.)

If you only have a small number of these tunables, make them sysctl 
variables.  Otherwise, define a structure containing them and a new 
ioctl to retrieve it.

mike