On Samstag, 10. Juli 2004 01:08, Post, Mark K wrote: > Is that ever going to change? �If so, when? �If not, why not? �One of the > good things about the Open Source development model is the transparency > involved. �I'm once again feeling like a mushroom when it comes to the > Linux/390 kernel source. �Some more transparency would really help out right > about now. �If nothing else, a daily snapshot of the S/390 portion of the > tree would be a nice start.
Sorry if this is still confusing. For the 2.6.x kernels, the rule should
really be: Use the latest official version. Aside from very few exceptions,
these always contain the latest code. Many improvements that go directly
into the official version are not backported to the DeveloperWorks release,
because they don't fix any bugs there.
The only significant exceptions I know of for 2.6.7 are these:
- The shared-IPv6-card patch:
linux-2.6.5-s390-base-14-april2004.diff
Sadly, no one has so far come up with a solution that can be
merged into the official kernel, so you have to apply this
to be able to use IPv6 with multiple VM guests on one card.
- The lost-dirty-bit fix:
linux-2.6.5-s390-04-16-april2004.diff
This came too late for 2.6.7 but is integrated in the latest
BitKeeper snapshots, like many other less important bug fixes.
- The xip2fs filesystem (you know the story...).
We're always trying to minimize the number of these patches, but probably
some more work should be put into documenting the state.
If you have found anything else in the DeveloperWorks stream that is not
in the real kernel, please tell!
Arnd <><
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
pgpPudKTJnacL.pgp
Description: signature
