Mailinglist Archive: opensuse-kernel (131 mails)
| < Previous | Next > |
Re: [opensuse-kernel] kernel SLE11_BRANCH
- From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
- Date: Tue, 4 Jan 2011 16:57:27 -0500
- Message-id: <AANLkTimNXYxbY4ovr0SEmVb30d1AZOGmtnSvqk60UxXC@mail.gmail.com>
On Tue, Jan 4, 2011 at 4:15 PM, Wolfgang Rosenauer
<wolfgang@xxxxxxxxxxxxx> wrote:
Wolfgang,
Remember I volunteered to be part of the Evergreen kernel team if you
moved to the 2.6.32 kernel.
At that point it becomes much easier to leverage the LTS status of
that kernel and pull security patches from the various LTS releases.
OTOH, I have not seen any volunteers (except yourself) for userspace
packages, so you do have to question the viability of moving forward.
Greg
--
Greg Freemyer
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
CNN/TruTV Aired Forensic Imaging Demo -
http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/
The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kernel+help@xxxxxxxxxxxx
<wolfgang@xxxxxxxxxxxxx> wrote:
Am 04.01.2011 22:02, schrieb Greg KH:
On Tue, Jan 04, 2011 at 09:50:41PM +0100, Wolfgang Rosenauer wrote:
I'm far away from being a kernel hacker unfortunately. I might just end
up being the one trying to merge security patches I find somewhere into
that kernel to keep 11.1 running.
The changes I would need right now are some to the spec file templates
as I cannot rely on SUSE's internal PDB to fix package descriptions up.
So I'm planning to go through the templates and fill in useful text.
Ick, no, don't do that, just use obs and the scripts we have for
generating packages directly from the kernel git tree, and you will not
need to edit any of those template files at all.
I use OBS and if you check your kernel:SLE11_BRANCH project you will
find that your kernel packages there have exactly that issue. All have
summary "Dummy summary" and description "Dummy description".
And if you all don't have someone to maintain your kernel, that actually
knows how to handle kernel security issues, that might be a good thing
to fix before thinking that Evergreen is going to be a viable platform
that someone can actually trust.
Yes, and I never claimed something else. And given the responses to my
initiative up to now I'm inclined to stop my efforts asap.
It's not fun (and not possible) to drive this a one man show so
apparently noone out there needs it. I also don't need it just for my
private little dedicated server. I can and should just use CentOS.
I was thinking there is a gap in our offers and we would find people to
join in. That wasn't the case yet and I still wanted to start the
experiment with 11.1 and would never recommend to people to use it but
given they have nothing from now on but are also not able to switch
everything was better than nothing.
So yes, your comment was rather motivating to me :-(
Wolfgang
Wolfgang,
Remember I volunteered to be part of the Evergreen kernel team if you
moved to the 2.6.32 kernel.
At that point it becomes much easier to leverage the LTS status of
that kernel and pull security patches from the various LTS releases.
OTOH, I have not seen any volunteers (except yourself) for userspace
packages, so you do have to question the viability of moving forward.
Greg
--
Greg Freemyer
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
CNN/TruTV Aired Forensic Imaging Demo -
http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/
The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kernel+help@xxxxxxxxxxxx
| < Previous | Next > |