From: Bill Davidsen <davidsen@tmr.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Will there be security updates for 2.6.17 kernels?
Date: Fri, 15 Dec 2006 12:27:41 -0500 [thread overview]
Message-ID: <4582DB0D.5080905@tmr.com> (raw)
In-Reply-To: <9a8748490612140710o478bf73p7efc607f545cf499@mail.gmail.com>
Jesper Juhl wrote:
> On 14/12/06, Manuel Reimer <Manuel.Spam@nurfuerspam.de> wrote:
>> Hello,
>>
>> my problem is, that the slackware maintainers decided to use kernel
>> 2.6.17. Here is their comment, they posted to the changelog:
>>
> <snip>
>>
>> They had a 2.6.16 kernel in /extra before and as far as I know the
>> 2.6.16 kernel series still gets security updates.
>>
>> Is this also the case for 2.6.17 kernels?
>
> No, that is not planned. 2.6.16.x is an exception. -stable kernels
> (those with 2.6.x.y versions) are only released for the latest stable
> 2.6.x kernel. So currently that's 2.6.19 and as soon as 2.6.20 comes
> out there will not be any more 2.6.19.x, only 2.6.20.x - I hope
> that's clear...
>
A happy exception I would say, given that there have been several
changes since then which might impact existing application software.
There are reasons to stay with 2.6.16 until applications have been
updated to handle the new unchanged behavior. See "VCD not readable" for
details.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-12-15 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 14:59 Will there be security updates for 2.6.17 kernels? Manuel Reimer
2006-12-14 15:10 ` Jesper Juhl
2006-12-14 19:33 ` Manuel Reimer
2006-12-15 17:27 ` Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-14 20:18 Mario Vanoni
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=4582DB0D.5080905@tmr.com \
--to=davidsen@tmr.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@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