From owner-freebsd-current  Tue Apr  8 13:19:28 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA28455
          for current-outgoing; Tue, 8 Apr 1997 13:19:28 -0700 (PDT)
Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA28450
          for <current@freebsd.org>; Tue, 8 Apr 1997 13:19:22 -0700 (PDT)
Received: (from dufault@localhost)
	by hda.hda.com (8.8.5/8.8.5) id QAA14157
	for current@freebsd.org; Tue, 8 Apr 1997 16:16:42 -0400 (EDT)
From: Peter Dufault <dufault@hda.com>
Message-Id: <199704082016.QAA14157@hda.hda.com>
Subject: POSIX 4 question
To: current@freebsd.org
Date: Tue, 8 Apr 1997 16:16:41 -0400 (EDT)
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

A follow up to the earlier discussion about POSIX 4:

In adding the correct interface I'm tempted to:

1. (Easy) Make everything contingent on "OPT_POSIX4" and
"OPT_POSIX4_ENABLED" (second option says _POSIX_C_SOURCE isn't
requesting an earlier interface);

2. #define all of the new POSIX 4 "_POSIX_feature_test" macros so
that at compile time it appears ALL features are possibly present;

3. #define the minimum limit required in the system headers if not
already defined;

4. Have sysconf return that the functionality isn't configured in;

5. Provide stub functions that fail.

Then the functionality can be loaded in one feature at a time via
the LKM mechanism at run time without changing the system headers,
and at LKM load time they can provide the correct info to sysconf.

Comments?  I like the idea of having the infrastructure in place
to ensure consistency in loading, unloading, sysconf, etc.

Peter

-- 
Peter Dufault (dufault@hda.com)   Realtime Machine Control and Simulation
HD Associates, Inc.               Voice: 508 433 6936