mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Tilley " "(Brad)" <rtilley@vt.edu>
To: jw schultz <jw@pegasys.ws>
Cc: Adrian Bunk <bunk@fs.tum.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Bugs and Releases Numbers
Date: 14 Jan 2003 11:37:11 -0500	[thread overview]
Message-ID: <1042562235.420.37.camel@oubop4.bursar.vt.edu> (raw)
In-Reply-To: <20030113225217.GC17075@pegasys.ws>

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]



On Mon, 2003-01-13 at 17:52, jw schultz wrote:

> No.  A new kernel need not be released right away.  Patches
> would be made available for affected recent releases.
> Anyone running self-built downloaded kernels is expected to
> be able to patch them when needed.  Distributions would
> apply the patch to their trees and make the new kernel
> (source and binaries) available through their usual security
> update channels.

It has been my experience that distro kernels come with everything and
then more of everything. Sure, they're mostly modular, but this approach
adds complexity that's unnecessary. So, I normally get kernel.org stable
kernel source and build a non-modular kernel specifically for my
hardware. 

I was just trying to determine how security patches are handle by the
kernel developers, that's all. The idea that people should look to
distros for security is absurd to me, especially if the bug in question
affects the vanilla kernel.
 
> It simply isn't necessary to rush a release (contrary to the
> principles of stable) just because there is a security hole.
> Patches are sufficient.  Besides, most sites run the
> distribution kernels anyway so they will get the fix through
> those channels.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2003-01-14 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 14:53 Richard B. Tilley  (Brad)
2003-01-13 15:07 ` Adrian Bunk
2003-01-13 15:17   ` Richard B. Tilley  (Brad)
2003-01-13 22:52     ` jw schultz
2003-01-14 16:37       ` Richard B. Tilley  (Brad) [this message]

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=1042562235.420.37.camel@oubop4.bursar.vt.edu \
    --to=rtilley@vt.edu \
    --cc=bunk@fs.tum.de \
    --cc=jw@pegasys.ws \
    --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

all inboxes | Powered by JetHome®