Bryan O'Donoghue wrote:
> Stephen Shirley wrote:
>> Also, as a nit pick, you should not be using the kernel headers, but
>> rather the headers of the kernel your glibc was compiled against,
>> which should be under /usr/include/{bits,asm,asm-generic,linux}
>>>> Why would that be now?
>> If the Kernel sets the signal state for a process, with a particular
> number and for argument's sake the signal number had changed from kernel
> version x, to kernel version y, you'd want to be aware of the current
> meaning of the signal number, ergo you'd want to check the meaning of
> the signal number in the *currently* running kernel, as opposed to the
> kernel, you libc may or may not have been compiled against?
>http://linuxmafia.com/faq/Kernel/usr-src-linux-symlink.html
Short version: the kernel can take care of backwards compatibility
Steve
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
