Re: Why is libc updated every time there's an update to the kernel

On Wed, Aug 15, 2018 at 02:34:54PM +0200, Ulf Volmer wrote: > On 15.08.2018 14:02, Reco wrote: > > On Wed, Aug 15, 2018 at 08:33:37AM -0300, Marcelo Lacerda wrote: > > >> but I imagine that a > >> security update to it doesn't actually change anything to libc source code, > >> so why do the two of

Re: Why is libc updated every time there's an update to the kernel

On 15.08.2018 14:02, Reco wrote: > On Wed, Aug 15, 2018 at 08:33:37AM -0300, Marcelo Lacerda wrote: >> but I imagine that a >> security update to it doesn't actually change anything to libc source code, >> so why do the two of them always upgrade together? > > Today's stable kernel update brought

Re: Why is libc updated every time there's an update to the kernel

Hi. On Wed, Aug 15, 2018 at 08:33:37AM -0300, Marcelo Lacerda wrote: > I know that the kernel and libc are deeply integrated On the contrary, libc merely states a minimal supported kernel version, and you're free to use more-or-less recent kernel with it. You'll miss all new system calls,

Why is libc updated every time there's an update to the kernel

I know that the kernel and libc are deeply integrated but I imagine that a security update to it doesn't actually change anything to libc source code, so why do the two of them always upgrade together?