All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grammostola Rosea <rosea.grammostola@gmail.com>
To: Debian Developers <debian-devel@lists.debian.org>
Cc: pkg-multimedia-maintainers@lists.alioth.debian.org,
	rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: realtime kernel for Debian
Date: Sun, 29 Mar 2009 20:28:14 +0200	[thread overview]
Message-ID: <49CFBDBE.5020408@gmail.com> (raw)
In-Reply-To: <49CF50D3.1080000@gmail.com>

Grammostola Rosea wrote:
> Andreas Tille wrote:
>> On Sat, 28 Mar 2009, Cassiel wrote:
>>
>>> debian stable aims to production servers,
>>
>> That's wrong.  Debian stable aims at production systems.  If your
>> arguing would be true I wonder why stable contains applications like
>> Openoffice.org or audio players or  ...
>>
>>> IMO multimedia users can/should live with
>>> testing without any fear of system crashes and security updates.
>>
>> I guess there are multimedia users out there who care much about a
>> stable system, reproducible results and have to earn some money from
>> their work - so they do not want to deal with unforseable changes.
>> Please do not advertise testing as a release which is ready for
>> users.  (Yes, I admit I use testing in the way you describe - but
>> *I* know what I'm doing.)
>>
>>
> But is not that big problem to install two kernels? One, the default 
> Lenny kernel and an RT kernel from testing?
>
To get some progress here, I'm searching for a person who wants and is 
capable in filing a wishlist bug (with a patch vs. the package linux-2.6

thanks in advance,

\r


       reply	other threads:[~2009-03-29 18:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200903242311.10783.nescivi@gmail.com>
     [not found] ` <alpine.DEB.2.00.0903250812230.17709@wr-linux02>
     [not found]   ` <49CA1781.3050603@gmail.com>
     [not found]     ` <20090325131713.GH15865@ltw.loris.tv>
     [not found]       ` <49CDFB4D.7070908@gmail.com>
     [not found]         ` <f1357b430903280615u215182fan2e62581394174603@mail.gmail.com>
     [not found]           ` <alpine.DEB.2.00.0903282331360.22173@wr-linux02>
     [not found]             ` <49CF50D3.1080000@gmail.com>
2009-03-29 18:28               ` Grammostola Rosea [this message]
2009-03-29 18:55                 ` realtime kernel for Debian Uwe Kleine-König
2009-03-29 19:01                   ` Grammostola Rosea
2009-03-29 19:56                     ` Uwe Kleine-König
2009-03-30  8:22                       ` Alexander Reichle-Schmehl
2009-03-30 15:13                         ` Uwe Kleine-König
     [not found]                       ` <49DF05B6.6000603@gmail.com>
     [not found]                         ` <20090413195356.GA13942@pengutronix.de>
     [not found]                           ` <4A09CEBC.70207@gmail.com>
2009-05-13  9:35                             ` Uwe Kleine-König
2009-06-04  9:28                               ` Grammostola Rosea
2009-10-02 20:20                               ` Uwe Kleine-König
2009-10-02 21:04                                 ` rosea grammostola

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=49CFBDBE.5020408@gmail.com \
    --to=rosea.grammostola@gmail.com \
    --cc=debian-devel@lists.debian.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=pkg-multimedia-maintainers@lists.alioth.debian.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 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.