On Wednesday 17 May 2017, Karel Zak wrote: > On Wed, May 17, 2017 at 10:42:53AM +0200, Ruediger Meier wrote: > > v3 just to avoid big numbers. But could also be a hint regarding > > the minimum supported/tested kernel version. I believe that we have > > already a few incompatibilities for kernel <2.6.32. Maybe we could > > cleanup our code, only supporting kernel >=3.1. > > I'm almost sure we have users who use util-linux on old kernels. For > example RHEL6 with 2.6.32 is pretty common and I have no problem to > compile util-linux there. And sometimes we also backport patches from > util-linux upstream to RHEL6 etc ;-) Hehe, I think 2.6.32 LTS is a very good lower boundary and it's almost kernel v3. ;) This version was released in 2009 and widely used (SLE, RHEL, Xen and many devices, routers, etc.). I remember 73f4f3d9 where I fixed a 3 year old bug in ipcs. Probably nobody noticed this. So I don't think that anbody is really using recent ul on even older kernels. > It's fine to kill things for 2.2 (etc.) but for I'd like to be > friendly to 2.6 users (if possible). We could remove <=2.4 hacks from our code, if any. Especially such very old history in the man pages, like tunelp.8: "... the -T option on a 2.0.36 kernel with an tunelp compiled under 2.1.131 or later may have unexpected effects." cu, Rudi > Karel > > > ./lscpu --version > lt-lscpu from util-linux 2.30-rc1-25-b7eb > > $ ./lscpu > Architecture: s390x > CPU op-mode(s): 32-bit, 64-bit > Byte Order: Big Endian > CPU(s): 4 > On-line CPU(s) list: 0-3 > Thread(s) per core: 1 > Core(s) per socket: 1 > Socket(s) per book: 1 > Book(s): 4 > Vendor ID: IBM/S390 > Machine type: 2827 > BogoMIPS: 2913.00 > Hypervisor vendor: (null) > Virtualization type: full > Dispatching mode: horizontal > Flags: esan3 zarch stfle msa ldisp eimm dfp etf3eh > highgprs > > $ uname -a > Linux devel2.s390.bos.redhat.com 2.6.32-550.el6.s390x #1 SMP Fri Apr > 3 10:12:50 EDT 2015 s390x s390x s390x GNU/Linux -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
