[dave@hiauly1.hia.nrc.ca: Incorrect file name simplication]

[John David Anglin]

> I'd like some more context.  How do we get a silly path like that in
> the first place?

It appears that a number of include have relative include paths.
For example, sys/audit.h has

#ifdef KERNEL
#include "../h/ansi_compat.h"
#include "../h/types.h"
#include "../h/time.h"
#include "../h/param.h"
#else
#include <ansi_compat.h>
#include <sys/types.h>
#include <sys/time.h>
#include <sys/param.h>
#endif /* KERNEL */

With the links as they are, the same files are loaded for both cases.
I would guess that at one time the files were installed in both /sys/h
and /usr/include/sys.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)