https://bugzilla.novell.com/show_bug.cgi?id=851338
https://bugzilla.novell.com/show_bug.cgi?id=851338#c49
--- Comment #49 from Nick Couchman
I completely understand, and I do apologize for the way that comment came out - I wasn't trying to imply that users are incapable of recompiling kernel, just wanted to point out that this thread was leaning more towards arguing why compatibility level should have stayed at 4.1 rather than discussing what can be done about this whole situation.
I certainly have more than an ideological argument here - my question is very practical in nature. I do understand the side of leaving behind legacy and pushing compatibility forward, as longs as there's good reason to do so (performance gains, bugs, etc.), but I think it needs to be balanced with making it usable for a wide variety of folks.
That'd be great. I'm not sure what's the permissions are on the wiki, so if you cannot edit it yourself, just email me instructions and I'll make sure to add it to the article.
I'll try to check in the next couple of days and see what I can do.
Maybe we could also get a kernel-xen-compat package created...
I think this would be the best way to go about it. I'm thinking hosted build service that checks for kernel updates daily, recompiles and pushes it to the repo. That way we probably can come up with a way to boot installtion using EC2 kernel -> add repo with compat kernel -> switch version right during installation and restore regular workflow.
Maybe so...I think the biggest challenge here is building an install initrd image that has the right kernel version that will boot on XenServer but is also an install initrd. That's where I can use some help. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.