Dropping security.
Alastair McKinstry <[EMAIL PROTECTED]> writes:
> dann frazier wrote:
>> On Wed, Aug 02, 2006 at 11:06:23AM +0000, Bastian Blank wrote:
>>
>>> If you want to be correct, you can't use linux-source. So the security
>>> team have to support another kernel source.
>>>
>>
>> A kernel-patch package that applies on top of the kernel team's
>> linux-source is the approach I'd suggest. But to reiterate, if
>> something in a kernel update causes the patch to no longer apply, I
>> would want to have a reliable contact (hopefully 2 people) whom we can
>> call upon for assistance.
>>
>>
>>
>
> How about the mISDN kernel modules as a format? I.e. preparing both
> patches (ie linux-patch-lustre.deb) that build on top of the kernel(s)
> (vanilla and debian) and
> modules that install direct on the relevant kernels shipped in etch?
> This is what I am currently
> working on.
>
> Regards
> Alastair McKinstry
A linux-patch-lustre.deb is a given for me. We do compile custom
kernels with a few other patches locally so I will always need the
patch.
I'm not sure lustre modules for the stock (lustre unpatched) kernels
are of much use though. Have you tried a patchless lustre setup? I've
seen a few mails about it on the lustre ML but what I saw from
skimming over them the performance and stability isn't the best.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
