From: Willy Tarreau <w@1wt.eu>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: Harsh Shandilya <msfjarvis@gmail.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 3.10.108 (EOL)
Date: Tue, 14 Nov 2017 23:18:44 +0100 [thread overview]
Message-ID: <20171114221844.GA3929@1wt.eu> (raw)
In-Reply-To: <29db159f-7cb3-1a4f-28a2-73830f8afc22@dd-wrt.com>
On Tue, Nov 14, 2017 at 11:00:46PM +0100, Sebastian Gottschall wrote:
> Am 05.11.2017 um 08:46 schrieb Willy Tarreau:
> > On Sun, Nov 05, 2017 at 06:59:48AM +0000, Harsh Shandilya wrote:
> > > Is this not pushed yet? I only see 3.10.107
> > Now it is there. Please avoid to rely on it for too long and quickly
> > upgrade to 4.4 or any other maintained version that suits your needs.
> >
> > Willy
> >
> even if EOL has to come once for sure, its the last kernel which can be used
> on certain devices (embedded) since the kernel is growing bigger and bigger
> and wont run good anymore with limited resource
It's not totally true, each new kernel also provides options to disable
certain parts that are not used by everyone (syscalls, subsystems, etc).
And anyway the end of life has been indicated on kernel.org for 18 months
and in every announce in 2017, so it cannot be a surprize anymore :-) At
least nobody seemed to complain for all this time!
Cheers,
Willy
next prev parent reply other threads:[~2017-11-14 22:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 23:06 Linux 3.10.108 (EOL) Willy Tarreau
[not found] ` <CALpmF+EbmuxvNWiBccGgtw=xDEW1=2hvxfVNp_r4dfiSF2o1UQ@mail.gmail.com>
2017-11-05 7:05 ` Willy Tarreau
2017-11-05 7:46 ` Willy Tarreau
2017-11-14 22:00 ` Sebastian Gottschall
2017-11-14 22:18 ` Willy Tarreau [this message]
2017-11-14 22:40 ` Sebastian Gottschall
2017-11-15 4:32 ` Willy Tarreau
2017-11-15 8:09 ` Sebastian Gottschall
2017-11-15 8:50 ` Greg KH
2017-11-17 23:46 ` Alan Cox
2017-11-18 7:31 ` Willy Tarreau
2017-11-20 15:46 ` Alan Cox
2017-11-18 7:37 ` Sebastian Gottschall
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=20171114221844.GA3929@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=msfjarvis@gmail.com \
--cc=s.gottschall@dd-wrt.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).