If I compile latest kernel from kernel.org, make a deb package and install it on my Debian system, shall I worry about libc (and any other libraries?) and kernel being out-of-sync?

I vaguely understand that kernel developers try hard to not break API/ABI exposed to userspace, but I guess once in a while breaks do happen, at least for some legitimate reasons? If so, is there a place that documents the mapping of working libc version vs kernel version?

  • You mostly would worry about libc or header file upgrades if you actually want to use new features. Unless then you don't need to worry (on the other hand not compiling your own kernel is even more reliable) – eckes Dec 9 '19 at 11:02

Linus is tougher on userspace breakage than pretty much any of his other policies. Breaks are way rarer than "once in a while", essentially unheard-of. Just don't worry about it at all.

| improve this answer | |
  • Thanks @Joseph. The reason I am asking is that kernel build generates three packages, one of them is linux-libc-dev, which will install a bunch of files in /usr/include/linux folder. These files seem to output a bunch of kernel headers into userspace, does that mean only addition but no deletion/replacement can happen, so that exposed API would not break? – QnA Dec 10 '19 at 23:56
  • @QnA They should be safe too. – Joseph Sible-Reinstate Monica Dec 11 '19 at 0:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.