On 07/23/2012 10:40 AM, Dan Shelton wrote:
On 20 July 2012 17:04, Michal Hlavinka <[email protected]> wrote:
Suse 12.1 is already shipping an updated kernel rpm with the fix
applied and they push the fix to SLES this month, maybe this
>>
I asked kernel developers about that patch and got following answer:
...
2. it changes old behaviour (visible to user space) (even if wrong) => can be
read as regression
...
4. we are trying to keep _absolute_ minimum of the kernel changes and avoid
them by all means if we are able.
So this change will take some time and I can't even guarantee it'll get
in the kernel if there is no explicit support request for this
Awwww, it seems I missed the announcement that M$ has taken over
redhat.com.
You missed nothing, no one took over rh. We already pushed this fix in
Fedora, but RHEL is different product where different approach is expected.
> Hey, they only have to take over Ubuntu, Suse, Debian,
CentOS, kernel.org and then can finally strip-charge all world for
explicit support requests down to the bones for every fundamental
functionality.
What? You want a 'Y' working key? Send explicit support request and a
$50 cheque.
This is oversimplification. The fact is that explicit support request is
required. Why? Because we guarantee that kernel won't change ABI, API
nor behaviour to user space. Take rhel5, it's deployed for 5 years,
nobody complained about this, some people used workaroudns for this.
They do not expect change in kernel in this time. They expect known
behaviour here.
The other fact is that with explicit support request, no extra cheque is
required.
Yet another fact is that support request is required = someone who
really use RHEL and has issues with old behaviour requests the change,
not some idealist, because such change always will upset some people and
also it will turn against us with "you did not keep your promise to not
change userspace visible behaviour" from those who "don't care".
Ant the last fact is that this change will be in next rhel major version
release.
Anyway, this discussion is off-topic for ast devel list. If you still
have concerns or want ask some questions how support works, please
contact appropriate rh department.
Michal
_______________________________________________
ast-developers mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-developers
