Hey Benny!   
      
    BP> note versions from me is the stable versions, hardened-sources is   
    BP> now unstable, so kernel.org is more or less unstable like hell atm   
      
   From my observations glibc-2.27 is the greater culprit.  My current 'stable'   
   system is booting a linux-4.15.1 kernel but with glibc-2.26 as shown below;   
      
   ----- ':read !uname -a' starts   
   Linux mikey 4.15.1 #1 SMP Sun Feb 4 11:04:33 UTC 2018 x86_64 Intel(R) Atom(TM)   
   CPU C2758 @ 2.40GHz GenuineIntel GNU/Linux   
   ----- ':read !uname -a' ends   
      
   ----- ':read !/lib/libc.so.6' starts   
   GNU C Library (GNU libc) stable release version 2.26, by Roland McGrath et al.   
   Copyright (C) 2017 Free Software Foundation, Inc.   
   This is free software; see the source for copying conditions.   
   There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A   
   PARTICULAR PURPOSE.   
   Compiled by GNU CC version 7.3.0.   
   Available extensions:   
           crypt add-on version 2.1 by Michael Glad and others   
           GNU Libidn by Simon Josefsson   
           Native POSIX Threads Library by Ulrich Drepper et al   
           BIND-8.2.3-T5B   
   libc ABIs: UNIQUE IFUNC   
   For bug reporting instructions, please see:   
   .   
   ----- ':read !/lib/libc.so.6' ends   
      
   Both of the above play nicely with libelf-0.170.so which is not the case with   
   glibc-2.27 and linux-4.15.1.  Also I noticed some linker issues with libjpeg   
   since we last chatted.  Bottomline is that I am obviously not ready for a   
   glibc-2.27 'upgrade'.   
      
   Life is good,   
   Maurice   
      
   ... Don't cry for me I have vi.   
   --- GNU bash, version 4.4.18(1)-release (x86_64-silvermont-linux-gnu)   
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)