linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Karl O. Pinc" <kop@meme.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: load firmware for in-kernel driver
Date: Wed, 27 Oct 2010 19:55:57 +0000	[thread overview]
Message-ID: <1288209357.32233.12@mofo> (raw)
In-Reply-To: <201010262219.o9QMJD0u004860@robo.generali.ch>

On 10/27/2010 12:48:35 PM, Hr. Philip Rueegsegger wrote:
> >On 10/27/2010 11:23:57 AM, Hr. Philip Rueegsegger wrote:
> >>  You
> >> know, I'd 
> >> like to stick with the kernel source provided by Debian just
> because
> >> of security 
> >> updates.
> >
> >Use the newer kernel from backports.debian.org.
> 
> What about security updates? Are they delivered equally regularely as
> from the 
> stable tree? After a quick look on http://backports.debian.org I
> couldn't see an 
> answer to my question. Thanks.

Good question.  I'd like to be sure of the answer myself.

Traditionally not, but backports is recently officially part of
Debian so things may have changed.  The kernel also tends
to be more rigorously maintained and may be a
special case.  The backports.debian.org FAQ says
security is best-effort but depends on the maintainer.
You might try asking security@debian.org or possibly 
debian-kernel@lists.debian.org. The latter seems
to be listed as one of the package maintainers
so might be the right choice.  

(The security team
faq says nothing about backports and now that it's
official maybe it should.  The question in the
backports faq is weirdly grey-ed out and italicized;
that confuses me slightly.)




Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein


  parent reply	other threads:[~2010-10-27 19:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 22:19 load firmware for in-kernel driver Hr. Philip Rueegsegger
2010-10-27 12:36 ` Andrey Borzenkov
2010-10-27 14:01 ` Hr. Philip Rueegsegger
2010-10-27 14:10 ` Kay Sievers
2010-10-27 16:23 ` Hr. Philip Rueegsegger
2010-10-27 17:02 ` Karl O. Pinc
2010-10-27 17:48 ` Hr. Philip Rueegsegger
2010-10-27 19:55 ` Karl O. Pinc [this message]
2010-10-28  1:19 ` Greg KH
2010-11-01 18:57 ` Hr. Philip Rueegsegger
2010-11-01 20:09 ` Greg KH

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=1288209357.32233.12@mofo \
    --to=kop@meme.com \
    --cc=linux-hotplug@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).