Skip to contentSkip to conversation

2.2.13 build OOB?; need for some standardization here?

DISCUSSION Kevin_Hendricks 3 participants 3 messages Sep 28, 1999 – Sep 30, 1999

lore
Share & tools
lore
#0 lore raw

Hi,

Quoted 3 lines

I don't think this has anything to do with distributions. People can install whatever version of whatever software they want, regardless of their initial distribution.

But Linux PPC and YellowDog linux ship with different kernel versions and different usb style support do they not. Then there is the glibc stuff. Both shipped with glibc 2.1.1 (versions) but the latest LinuxPPC uses (or has) glibc 2.1.2 (which because of incompatibilities is a nightmare for jdk using native threads).

Quoted 4 lines

True... One solution would be to reply to bug reports with "reproduce it in kernel.org's 2.2.12 and we'll look at it." All of the kernel stuff you mentioned is just part of kernel development, and I don't see how that can be stopped.

I disagree. I really think it would help to have one clearing house for the kernel source tree with all of the latest patches installed so that there are not awhole bunch of different incompatible versions flying around (the usb stuff for instance).

I think we should either fix the way Linus and company decides when to release a stable version, or get our own "Alan Cox" to act as shepard over our own stable "ppc" kernel tree and make that person "official".

Quoted 2 lines

Pick a target. It should probably be the newest stable release of stuff, ie kernel.org 2.2.12, glibc 2.1.2, XFree86 3.3.5.

Yes, that is what I have done. Although I chose glibc 2.1.1 until the other distributions start shipping glibc 2.1.2.

But this just illustrates my point. Everytime you force someone to support only a set subset of packages, you fragment the Linux/PPC user base even further. Since our base is so small to begin with, any fragmentation will have a very big impact.

Quoted 1 line

I don't think anyone's worrying much about glibc 1.99 any more...

I do for my 8100 machine hanging around still running MkLinux DR3

Quoted 25 lines
Quoted 11 lines

Then there is the whole question of where to get your kernel source from? You can't seem to use the official kernel source trees for even the *stable* relases of 2.2.X.

Is there any chance 2.2.13 will actually build out of the box on PPC without having to add Paul's patches and/or getting it via rsync from Paul's tree. Maybe so this time since I noticed Paul's name under Alan Cox's pre-patch list of contributors.

Shouldn't the official *stable* kernel tree always build-out-of-the-box on each supported platform? If so, why isn't this happening in general?

That would be nice. Unfortunately, x86 people can't exactly test their changes on PPC, and so more than once the "stable" branch doesn't work here. There have been conversations about it.

Again, I don't think it has much to do with the distributions. TurboLinux and early MkLinux (both with glibc 1.99) are very small. MkLinux w/ glibc2 is limited to the x100 PowerMac users for the most part. Debian is pretty small because of its installation procedure. I hope LinuxPPC R4 people have upgraded by now, and LinuxPPC 1999 and YDL 1.1 are pretty damn close. I really don't think there's that much of a division (aside from very small slices of the pie chart here and there).

Quoted 5 lines

Summary: pick target versions of the packages you're worried about. Someone else pointed out that Unix software vendors pick a few Unices to develop for. Since you have finite resources (like commercial vendors), you should do the same. I think you'll find that you can group a very large percentage of the Linux/PPC userbase under the glibc 2.1.2 flag.

And if everyone does that, we will just fragment things even further. That is my whole point. Before we diverge even farther, lets figure out someway to prevent the kind of support problems that plague x86 with all its versions / libraries / glibcs/ etc.

By the way, (my case in point) I don't think glibc 2.1.2 is that prevalent out there. It only just shipped with Linux PPC Q3, Champion server 1.1 does not install it (which makes my point clearer I hope) and the other distributions afaik are shipping one version of glibc 2.1.1 or another.

So do I build for glibc 2.1.2, glibc 2.1.1, only one kernel version, only one distribution, what?

That is what I think we *all* should avoid if possible.

My 2 cents.

Kevin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#1 lore raw
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Kevin Hendricks writes:

Kevin> I think we should either fix the way Linus and company decides when to release a Kevin> stable version, or get our own "Alan Cox" to act as shepard over our own stable Kevin> "ppc" kernel tree and make that person "official".

I tend to agree with Kevin here. The Linux core kernel developers
need to improve their release engineering process. I realize that Linux/PPC was on the fringe for a long time, and both Paul and Cort have done a lot of excellent work these past few months adding functionality and improving the overall design. This rapid development makes it hard for Linus and company to keep up. However, x86 development should not break PowerPC and other ports as much as I have seen.

PowerPC and other architectures are becoming more important and
demonstrating the diversity of Linux. The breakage and instability does not cast a good light on bazaar-style development model and Linux when we are trying to broaden the Linux market.

David

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#2 lore raw

Hi all,

On 28 Sep, this message from David Edelsohn echoed through cyberspace:

Quoted 11 lines

Kevin> I think we should either fix the way Linus and company decides when to release a Kevin> stable version, or get our own "Alan Cox" to act as shepard over our own stable Kevin> "ppc" kernel tree and make that person "official".

I tend to agree with Kevin here. The Linux core kernel developers
need to improve their release engineering process. I realize that Linux/PPC was on the fringe for a long time, and both Paul and Cort have done a lot of excellent work these past few months adding functionality and improving the overall design. This rapid development makes it hard for Linus and company to keep up. However, x86 development should not break PowerPC and other ports as much as I have seen.

I fully agree here. I think every Linux arch should have a single person responsible for the port, and new releases of stable kernel versions should get every arch maintainer's OK before release. That would at least catch most of the 'doesn't compile on...' type of bugs.

However, I fear that Paul, the current PPC maintainer according to kernel documentation, would need to spend even more time on Linux than he currently does... which I'm not sure he is prepared to do.

Quoted 4 lines

PowerPC and other architectures are becoming more important and
demonstrating the diversity of Linux. The breakage and instability does not cast a good light on bazaar-style development model and Linux when we are trying to broaden the Linux market.

Absolutely true. There are two main problems I see here: getting PPC patches into the kernel, and checking that other people's work on the kernel doesn't break anything PPC-specific. Both problems caused headaches in the past...

Michel

-------------------------------------------------------------------------

Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   [email protected]            |
http://www.cpu.lu/~mlan        |                     Learn Always. "

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/