From owner-cvs-sys Fri Jul 28 18:05:06 1995 Return-Path: cvs-sys-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id SAA17230 for cvs-sys-outgoing; Fri, 28 Jul 1995 18:05:06 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id SAA17223 for ; Fri, 28 Jul 1995 18:05:05 -0700 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id SAA17157 for ; Fri, 28 Jul 1995 18:04:30 -0700 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Fri, 28 Jul 1995 20:05:00 -0500 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 28 Jul 1995 20:05:01 -0500 To: Gary Palmer From: rkw@dataplex.net (Richard Wackerbarth) Subject: /usr/include Cc: cvs-sys@freebsd.org Sender: cvs-sys-owner@freebsd.org Precedence: bulk >Is that the way to go for architectural cleaness? I mean, with >multi-platform support on the horizon, do we want i386-centric files >in /usr/include/sys? I would hope not. I am in agreement with you. When we start talking multi-environment systems, /usr/include is simply the default value for "The Current Environment on This Machine" The include files for a generic compilation will come from some other directory. One of the common abstractions is to separate the "machine" characteristics from the "Operating System" characteristics. Therefore IS appropriate. Just because L!*ux does it wrong is no reason for us to do likewise. Besides, you can create a "compatability" directory which defines the as simply "include " ---- Richard Wackerbarth rkw@dataplex.net