Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: versioning
Date: Wed, 17 May 2017 18:08:15 +0200	[thread overview]
Message-ID: <201705171808.15179.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20170517150455.svjd332dyrq4zfyh@ws.net.home>

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



  reply	other threads:[~2017-05-17 16:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  7:47 versioning Karel Zak
2017-05-17  8:42 ` versioning Ruediger Meier
2017-05-17  8:47   ` versioning Ruediger Meier
2017-05-17 13:23     ` versioning Bernhard Voelker
2017-05-17 13:51       ` versioning Karel Zak
2017-05-17 15:04   ` versioning Karel Zak
2017-05-17 16:08     ` Ruediger Meier [this message]
2017-05-17 17:36 ` versioning Bruce Dubbs
2017-05-17 19:07   ` versioning Ruediger Meier
2017-05-17 21:09     ` versioning Karel Zak
2017-05-18  9:29       ` versioning Sami Kerola
2017-05-18 10:36         ` versioning Karel Zak
2017-05-18 18:08           ` versioning J William Piggott
2017-05-18 19:56             ` versioning Karel Zak
2017-05-18 20:55               ` versioning Rüdiger Meier
2017-05-19  8:12                 ` versioning Karel Zak
2017-05-19 19:00                 ` versioning J William Piggott
2017-05-20 19:34                   ` versioning Karel Zak
2017-05-22 21:37                     ` versioning J William Piggott
2017-05-23  7:57                       ` versioning Karel Zak
2017-05-23  8:05                         ` versioning Karel Zak
2017-05-23 20:54                           ` versioning J William Piggott
2017-05-24 10:02                             ` versioning Ruediger Meier
2017-05-27 18:55                             ` versioning J William Piggott
2017-05-29 10:22                               ` versioning Karel Zak
2017-05-18 10:43         ` versioning Ruediger Meier
2017-05-17 17:46 ` versioning J William Piggott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201705171808.15179.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox