Please release a stable kernel Linux 3.0
Quoted 10 lines · Al Viro
Quoted 6 lines · Zolt?n HUBERT
And as I understand it, this is (was ?) the whole point of stable/development kernels. "We" can trust a newer stable kernel to be a drop-in replacement for an older stable kernel (from the same series), while development kernels need time to stabilise with the new whizz-bang-pfouit stuff that you all so nicely add.
"Drop-in" in which sense? That out-of-tree modules keep working? Not really...
Al, be reasonable. There are many out-of-tree GPL modules that won't be accepted into mainline, never mind those that shouldn't be accepted. But these modules do have a right to not be obsoleted by constant API changes.
You are effectively inhibiting the development of an out-of-tree GPL module pool, by constantly pulling the rug under that community.
Do you think this is fair?
Thanks!
--
Al
Quoted 9 lines · Al Boldi
Quoted 8 lines · Al Viro
Quoted 6 lines · Zolt?n HUBERT
And as I understand it, this is (was ?) the whole point of stable/development kernels. "We" can trust a newer stable kernel to be a drop-in replacement for an older stable kernel (from the same series), while development kernels need time to stabilise with the new whizz-bang-pfouit stuff that you all so nicely add.
Quoted 6 lines
Quoted 2 lines
"Drop-in" in which sense? That out-of-tree modules keep working? Not really...
Al, be reasonable. There are many out-of-tree GPL modules that won't be accepted into mainline, never mind those that shouldn't be accepted. But these modules do have a right to not be obsoleted by constant API changes.
"have a right" are strong words.
Who is granting them this right?
Quoted 4 lines
You are effectively inhibiting the development of an out-of-tree GPL module pool, by constantly pulling the rug under that community.
Do you think this is fair?
Why are these modules not submitted for inclusion into the kernel?
Quoted 2 lines
Thanks!
Al
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 18 lines · Adrian Bunk
Quoted 8 lines · Al Boldi
Quoted 7 lines · Al Viro
Quoted 6 lines · Zolt?n HUBERT
And as I understand it, this is (was ?) the whole point of stable/development kernels. "We" can trust a newer stable kernel to be a drop-in replacement for an older stable kernel (from the same series), while development kernels need time to stabilise with the new whizz-bang-pfouit stuff that you all so nicely add.
Quoted 5 lines
Quoted 2 lines
"Drop-in" in which sense? That out-of-tree modules keep working? Not really...
Al, be reasonable. There are many out-of-tree GPL modules that won't be accepted into mainline, never mind those that shouldn't be accepted. But these modules do have a right to not be obsoleted by constant API changes.
"have a right" are strong words.
Who is granting them this right?
Quoted 7 lines
Quoted 4 lines
You are effectively inhibiting the development of an out-of-tree GPL module pool, by constantly pulling the rug under that community.
Do you think this is fair?
Why are these modules not submitted for inclusion into the kernel?
I was trying to figure that out for this one:
http://code.ximeta.com/trac-ndas
No mention of ever trying to get this upstream AFAICT... but this is interesting:
The linux market is limited comparing that of MS Windows. it is very hard for us to support the various linux distros. we, Ximeta, are trying to support those requests as many as we can, though the resources are very limited.
Quoted 31 lines · Chuck Ebbert
Quoted 18 lines · Adrian Bunk
Quoted 8 lines · Al Boldi
Quoted 7 lines · Al Viro
Quoted 6 lines · Zolt?n HUBERT
And as I understand it, this is (was ?) the whole point of stable/development kernels. "We" can trust a newer stable kernel to be a drop-in replacement for an older stable kernel (from the same series), while development kernels need time to stabilise with the new whizz-bang-pfouit stuff that you all so nicely add.
Quoted 5 lines
Quoted 2 lines
"Drop-in" in which sense? That out-of-tree modules keep working? Not really...
Al, be reasonable. There are many out-of-tree GPL modules that won't be accepted into mainline, never mind those that shouldn't be accepted. But these modules do have a right to not be obsoleted by constant API changes.
"have a right" are strong words.
Who is granting them this right?Quoted 7 lines
Quoted 4 lines
You are effectively inhibiting the development of an out-of-tree GPL module pool, by constantly pulling the rug under that community.
Do you think this is fair?
Why are these modules not submitted for inclusion into the kernel?
I was trying to figure that out for this one:
Quoted 7 lines
No mention of ever trying to get this upstream AFAICT... but this is interesting:
The linux market is limited comparing that of MS Windows. it is very hard for us to support the various linux distros. we, Ximeta, are trying to support those requests as many as we can, though the resources are very limited.
One of their module contains a 180 kB binary blob and MODULE_LICENSE("Proprietary, Send bug reports to [email protected]").
And it calls tons of functions EXPORT_SYMBOL'ed by their other 3 modules that are MODULE_LICENSE("Dual BSD/GPL")...
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedHi Chuck,
Quoted 5 lines · Chuck Ebbert
I was trying to figure that out for this one:
Quoted 8 lines
No mention of ever trying to get this upstream AFAICT... but this is interesting:
The linux market is limited comparing that of MS Windows. it is very hard for us to support the various linux distros. we, Ximeta, are trying to support those requests as many as we can, though the resources are very limited.
I would not worry about that one too much:
[~] ls -la ndas-1.1-6/*.sfx
-rw-r--r-- 1 TOROKHDM mkgroup-l-d 60416 Jun 27 12:22 ndas-1.1-6/libndas.a.sfx
Signature · 1 line
Dmitry
Quoted 13 lines · Adrian Bunk
Quoted 12 lines · Al Boldi
Quoted 10 lines · Al Viro
Quoted 6 lines · Zolt?n HUBERT
And as I understand it, this is (was ?) the whole point of stable/development kernels. "We" can trust a newer stable kernel to be a drop-in replacement for an older stable kernel (from the same series), while development kernels need time to stabilise with the new whizz-bang-pfouit stuff that you all so nicely add.
"Drop-in" in which sense? That out-of-tree modules keep working? Not really...
Quoted 7 lines
Quoted 4 lines
Al, be reasonable. There are many out-of-tree GPL modules that won't be accepted into mainline, never mind those that shouldn't be accepted. But these modules do have a right to not be obsoleted by constant API changes.
"have a right" are strong words.
Who is granting them this right?
Good-will GPL style.
Quoted 6 lines
Quoted 4 lines
You are effectively inhibiting the development of an out-of-tree GPL module pool, by constantly pulling the rug under that community.
Do you think this is fair?
Why are these modules not submitted for inclusion into the kernel?
There are many reasons for this, but basically they are too under-developed to be included, and need more time to mature out-of-tree.
Thanks!
--
Al
Quoted 9 lines · Al Boldi
Quoted 8 lines · Al Viro
Quoted 6 lines · Zolt?n HUBERT
And as I understand it, this is (was ?) the whole point of stable/development kernels. "We" can trust a newer stable kernel to be a drop-in replacement for an older stable kernel (from the same series), while development kernels need time to stabilise with the new whizz-bang-pfouit stuff that you all so nicely add.
Quoted 6 lines
Quoted 2 lines
"Drop-in" in which sense? That out-of-tree modules keep working? Not really...
Al, be reasonable. There are many out-of-tree GPL modules that won't be accepted into mainline, never mind those that shouldn't be accepted. But these modules do have a right to not be obsoleted by constant API changes.
Modules do not have any rights; it's software, for fsck sake...
Quoted 2 lines
You are effectively inhibiting the development of an out-of-tree GPL module pool, by constantly pulling the rug under that community.
The same thing happens with any yet-to-be-merged code.
Quoted 1 line
Do you think this is fair?
Yes, it is fair. Decision to maintain your code out of tree indefinitely is your decision.
Quoted 13 lines · Al Viro
Quoted 12 lines · Al Boldi
Quoted 10 lines · Al Viro
Quoted 6 lines · Zolt?n HUBERT
And as I understand it, this is (was ?) the whole point of stable/development kernels. "We" can trust a newer stable kernel to be a drop-in replacement for an older stable kernel (from the same series), while development kernels need time to stabilise with the new whizz-bang-pfouit stuff that you all so nicely add.
"Drop-in" in which sense? That out-of-tree modules keep working? Not really...
Quoted 6 lines
Quoted 4 lines
Al, be reasonable. There are many out-of-tree GPL modules that won't be accepted into mainline, never mind those that shouldn't be accepted. But these modules do have a right to not be obsoleted by constant API changes.
Modules do not have any rights; it's software...
Ok, this should have been read as kernel/module dev/user right to leverage each others code under GPL and out of good-will to yield an increased harvest.
Quoted 9 lines
Quoted 2 lines
You are effectively inhibiting the development of an out-of-tree GPL module pool, by constantly pulling the rug under that community.
The same thing happens with any yet-to-be-merged code.
Quoted 1 line
Do you think this is fair?
Yes, it is fair. Decision to maintain your code out of tree indefinitely is your decision.
It's not my decision, it's the kernel maintainers decision to reject inclusion for one reason or another. One reason could be a simple "we don't think this is useful".
Also, I think it's unrealistic to expect thousands of little-used modules to be included into mainline.
But, should we hinder that community to grow?
Thanks!
--
Al
Quoted 5 lines · Al Boldi
Quoted 5 lines
Quoted 2 lines
You are effectively inhibiting the development of an out-of-tree GPL module pool, by constantly pulling the rug under that community.
The same thing happens with any yet-to-be-merged code.
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
Do you think this is fair?
Yes, it is fair. Decision to maintain your code out of tree indefinitely is your decision.
It's not my decision, it's the kernel maintainers decision to reject inclusion for one reason or another. One reason could be a simple "we don't think this is useful".
"I maintain a patch to $PROGRAM; maintainers of $PROGRAM don't think it's useful; they should abstain from making changes that might require rewrite of that patch". Would you argue that this is fair?
BTW, "if it's GPLed, it's entitled to any internal function" is a shell game; it tries to convert GPL-given right to get to those functions into some kind of promise that those functions won't be changed.
EXPORT_SYMBOL_GPL() should've been EXPORT_SYMBOL_INTERNAL(); like it or not, in-tree code *is* in different position exactly because it can be modified by whoever makes a change affecting such code. For in-tree module one can expect such modifications to be done; for out-of-tree the same is obviously not true, but conclusion is not "you can't do changes", it's "authors of out-of-tree module get to do such modifications themselves".
Sure, there are subsets of exports that have stronger promise of not being changed often; if a set of functions makes sense as an interface, it's less likely to change than randomly selected function that just had an export slapped on it at some point. The promise is not absolute and it's not based on some obligations to out-of-tree modules; it's simply a common sense.
Again, most of the exports had been added with very little justification at request of out-of-tree module authors. That pile is many years past the stage when it could be described as set of sane interfaces and it's your [collective] fault. Don't expect sympathy when you find the resulting devalvation unpleasant to deal with...
Quoted 11 lines · Al Viro
Quoted 10 lines · Al Boldi
Quoted 9 lines
Quoted 2 lines
You are effectively inhibiting the development of an out-of-tree GPL module pool, by constantly pulling the rug under that community.
The same thing happens with any yet-to-be-merged code.
Quoted 1 line
Do you think this is fair?
Yes, it is fair. Decision to maintain your code out of tree indefinitely is your decision.
Quoted 7 lines
Quoted 3 lines
It's not my decision, it's the kernel maintainers decision to reject inclusion for one reason or another. One reason could be a simple "we don't think this is useful".
"I maintain a patch to $PROGRAM; maintainers of $PROGRAM don't think it's useful; they should abstain from making changes that might require rewrite of that patch". Would you argue that this is fair?
No, that's not fair. But, what's fair is to ask maintainers of $PROGRAM to be so kind and expose a stable API via some layer, which can be used to connect external patches which are considered not useful, in the hope that some day it may grow into something useful.
Quoted 19 lines
BTW, "if it's GPLed, it's entitled to any internal function" is a shell game; it tries to convert GPL-given right to get to those functions into some kind of promise that those functions won't be changed.
EXPORT_SYMBOL_GPL()should've beenEXPORT_SYMBOL_INTERNAL(); like it or not, in-tree code *is* in different position exactly because it can be modified by whoever makes a change affecting such code. For in-tree module one can expect such modifications to be done; for out-of-tree the same is obviously not true, but conclusion is not "you can't do changes", it's "authors of out-of-tree module get to do such modifications themselves".Sure, there are subsets of exports that have stronger promise of not being changed often; if a set of functions makes sense as an interface, it's less likely to change than randomly selected function that just had an export slapped on it at some point. The promise is not absolute and it's not based on some obligations to out-of-tree modules; it's simply a common sense.
Quoted 5 lines
Again, most of the exports had been added with very little justification at request of out-of-tree module authors. That pile is many years past the stage when it could be described as set of sane interfaces and it's your [collective] fault. Don't expect sympathy when you find the resulting devalvation unpleasant to deal with...
Ok, so some people made a mistake, and now everybody has to suffer?
What we need is a solution. What is your suggestion?
Would a stable API exposing wrapper module be feasible?
Thanks!
--
Al