On Tue, Sep 03, 2013 at 04:57:47PM -0400, Jeff Mahoney wrote:
On 9/3/13 4:22 PM, Greg KH wrote:
On Tue, Sep 03, 2013 at 03:34:06PM -0400, Jeff Mahoney wrote:
Ok, so there are two things here.
The first is whether the goal is to identify arbitrary kernels. From my perspective, it's not. I only want to be able to identify kernels that are part of the official release and, as such, kernels that are under the limited amount of maintenance and support we offer for openSUSE.
Ok, so then just stick with what we have here, since when do people start running SLES kernels on openSUSE boxes and ask for support?
That's not what I'm trying to prevent, Greg. It's the random kernels that get built as part of other OBS projects, Tumbleweed, etc. People don't try to run SLES kernels on openSUSE boxes - but they do run a full SLES environment and then try to get support via openSUSE channels. Those get flushed out pretty quickly already and that's not the problem I'm trying to solve. As I said, I have a separate proposal already for the SLES kernel naming so that part of the problem is probably already solved.
Ok, forget the SLES stuff, shouldn't be mentioned here at all :)
More obvious than having the release string in the Oops itself? This is something that saves the triagers effort and costs the end user *nothing*. And then there's the issue of collisions between numbering of official releases and someone playing around with their own project but forgetting they installed a test kernel. Here's an example: someone taking a release kernel, grafting a new DRM subsystem onto it, and then filing bug reports against it when it didn't work right. It "looks" like an official release when you see the Oops but it most definitely is not.
How are you going to prevent this from happening by adding the distro to the release number? That should be part of the spec file they just forked from the openSUSE:13.1 repo, so it should be added to their own "custom" kernel as well, right? Or how are you suggesting it be added to the package, in a step not in OBS that anyone would not normally be able to do as part of the kernel build process? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org