Re: kernels, header files, modules and a read-only /usr

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2003-07-03 at 12:53, Robert P. J. Day wrote:
>   (ok, it's my turn to ask dumb questions again.)
> 
>   following up on a previous post of mine, i'm still trying
> to clarify the issues related to building and running a new
> kernel, and header files.
> 
>   historically, of course, the kernsl source has always been
> dumped under /usr/src/linux-2.x.yy or something to that effect.

correct, but not for building modules against

> and, from memory, it was always recommended to create the symlink
> /usr/src/linux to point at the source directory for the currently
> running kernel.

incorrect

> 
>   why was this?  IIRC, it's because other builds needed access
> to the kernel header files for the currently-running kernel so
> they could be created compatible, is that about right? 

incorrect;
ANYTHING that requires the headers from the currently running kernel
needs to use the
/lib/modules/`uname -r`/build/include
directory.


Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Fedora Users]     [Centos Users]     [Kernel Development]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat Phoebe Beta]     [Yosemite Forum]     [Fedora Discussion]     [Gimp]     [Stuff]     [Yosemite News]

  Powered by Linux