From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] Oldest still supported kernel
Date: Thu, 16 May 2019 04:35:23 -0400 (EDT) [thread overview]
Message-ID: <1051593197.23090826.1557995723298.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190516073826.GA14532@dell5510>
----- Original Message -----
> Hi,
>
> do we declare oldest still supported kernel version?
> According to distrowatch [1] still supported RHEL-6.9 is using v2.6.32.
6.9 is already EOL, but there still are other supported RHEL6 streams (up to 2024).
> Is it the oldest version we want to support or even something older?
I'd like minimum to be at least 3.10.0 / glibc-2.17 (RHEL7).
Older distros use LTP mostly for regression tests, so it might be acceptable
for users to switch to older release tag, rather than always latest master.
There's also an option, we create a "legacy" branch for old distros,
and accept only critical fixes (no new tests, rewrites, etc.). It would
be unsupported, but provide place where legacy users can cooperate.
> Latest still supported stable kernel is 3.16, which is obviously too new for
> enterprise distros.
>
> It'd be nice to specify latest supported kernel (and glibc) version in docs
> and remove old autotools checks (we have some checks for v2.6.25).
>
> Kind regards,
> Petr
>
> [1] https://distrowatch.com/table.php?distribution=redhat
>
next prev parent reply other threads:[~2019-05-16 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 7:38 [LTP] Oldest still supported kernel Petr Vorel
2019-05-16 8:35 ` Jan Stancek [this message]
2019-05-16 9:07 ` Cyril Hrubis
2019-05-16 9:49 ` Li Wang
2019-05-16 11:09 ` xuyang
2019-05-16 12:28 ` Cyril Hrubis
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=1051593197.23090826.1557995723298.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.