Today, Trond Eivind Glomsrød wrote:
> Because the reason for not shipping 2.2.18 when we did the errata was
> its failing of stresstests.
yuck, failing how? (if this is already discused and archived somewhere
a pointer would be appreciated, I didn't see it come across either of
the redhat lists I'm on, and a few net searches the last time I started
this process didn't turn it up.)
Yesterday, Dan Cyr wrote:
> Be careful with some of the patches. I tried doing that awhile ago, but
> ran into a problem with software raid support. The software raid patch
> for 2.2.18 patched in just fine, but it didn't work at all, in fact it
> broke software raid support all together. After a few emails to the
> maintainer of the software raid patch, he did fix it.
yeah, btdt... although for me it was the ipsec-masq patch. :(
The last time I did this little exercise I spent more time chasing down
where all these various patches came from and getting the latest copies
than anything else... it's (yet another) reason why I'm happy to pay
my $50 to let RH do all this most of the time, but I really need a patch
that's in 2.2.18 and can't find any srpms that have already done this
floating around in contrib or rawhide (though that is where I stole the
2.2.17 I'm starting from ;) so I figure as long as I'm at it I might
as well go "bleeding edge".... I also figured the RH folks that usually
do this are, shall we say, a bit busy with 2.4.* and the 7.1 beta....
--
now the forces of openness have a powerful and
unexpected new ally - http://ibm.com/linux
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
