On 20 May 1996, Manoj Srivastava wrote: (clip) > The kernel-source package is a superset of the kernel-headers > package, so the headers have not been "separated" from the rest of > the source. (clip) > manoj > -- > Everyone has a purpose in life. Perhaps yours is watching television. > -- David Letterman %% > Manoj Srivastava Systems Research Programmer, Project Pilgrim, > Phone: (413) 545-3918 A143B Lederle Graduate Research Center, > Fax: (413) 545-1249 University of Massachusetts, Amherst, MA 01003 > <[EMAIL PROTECTED]> <URL:http://www.pilgrim.umass.edu/%7Esrivasta/>
I have heard discussion on this list before about why debian does this; I don't want to argue why;; But will it break anything major if I don't follow this guideline, and esp. is there a temporary way to set things up 'the old way'? Most of what I compile right now wants kernel headers so it can be compatible with the current kernel (ie kernel utilities and patches.) For example I have kernel utilities which use #include<linux/something.h> and I keep catching them raiding the /usr/include directory. [EMAIL PROTECTED] "The C Programming Language -- A language which combines the flexibility of assembly language with the power of assembly language."
