> From [EMAIL PROTECTED] Wed Sep 15 13:50:22 1999
>
> Good morning to everyone.
>
> > correct me if I'm wrong, but I think the current recipe is patching 2.2.12
> > with the latest raid alpha patch (for 2.2.11) and when patch complains
> > about fs.h, tell it to completely skip fs.h since changes to that file are
> > already in 2.2.12
>
> The current problem with 2.2.12 is that the 2.2..11 (08/24/1999)
> patches run headlong into the memory leak patches that Dave Miller
> posted and which Alan incorporated into the 2.2.13 patch set.
>
> The RAID code seems to make use of the mark_buffer_lowprio stuff that
> got deleted as part of the memory leak patch. I haven't really had
> time to look at the RAID code closely but a brief examination seemed
> to indicate that the changes necessary to handle the memory leak patch
> were not trivial. I would be happy to give this a try but I would
> need some type of cookbook to follow.
>
> This all pretty much implies that a new RAID patchset will be required
> when 2.2.13 hits the streets.
Sigh. So what do the RAID deities suggest someone use for "production"
if they're starting out with a clean install and can use any ol'
kernel or raid patch they desire? What's the most stable at this
point?
Cheers,
Chris
--
Christopher Mauritz
[EMAIL PROTECTED]
