> > intent). It is fortunate that the bad old days of /usr/include/linux -> > > /usr/src/linux/include are mostly gone, but some systems still do that > > anyway (Slackware?).
It's been years since Slackware has done that. > FWIW - to be precise, Slackware isn't doing what's illustrated above, > exactly. No symlink at all. Rather, /usr/include/linux, if populated > at all, comes only from the kernel-headers package, and is a complete > copy of the kernel headers that are packaged with the kernel source > in that particular distribution. > > I suspect the rationale for this would go along the lines of: The rationale is that the kernel headers in /usr/include should be closely matched to the ones that glibc was compiled against or you can run into trouble. Reference from Linus: http://www.uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html Take care, Pat - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
