That is a bold statement my friend.
Sorry - this is not a bold statement any more than bold than linux itself. SuSe better start understanding this if it ever wants to be a first class system.
I compile 1-2 kernels a day, without any problems whatsoever.
Yah Know what - I've been compiling kernels since 2.0.12 Maybe 1000 times I've compiled kernels on RH, Slackware, Strorm, Debian and SuSe. This compile DOES NOT WORK because the sysv init system and the kernel module is SCREWED....(as hinted at in the docs). module.conf was invisible to the 7.0 system with a hand compile and the initiation system was screwed with the RPM's...problbly secondary to PAM or the location of the files? AND BTW - mod-ulits? Where waas that under the 7.0 tree in yast? dir .. axx xx [o] * 8.0M Mar 12 16:02 k_deflt.rpm axx xx [o] * 9.5M Mar 2 12:52 k_deflt_24-2.4.2-4.i386.rpm axx xx [ ] * 8.1M Mar 12 16:02 k_i386.rpm axx xx [i] * 9.6M Mar 2 13:19 k_i386_24-2.4.2-5.i386.rpm axx xx [ ] * 9.8M Mar 2 13:19 k_psmp_24-2.4.2-4.i386.rpm xxx xx [ ] * 8.3M Mar 12 18:30 k_smp.rpm x xx [ ] * 9.8M Mar 2 13:15 k_smp_24-2.4.2-5.i386.rpm xx[o] *330.1K Mar 2 11:04 lvm-0.9.1_beta4-1.i386.rpm axx xx [o] *324.8K Mar 2 11:04 lvm-0.9.1_beta4-1.src.rpm axx xx [o] * 2.8M Mar 12 13:50 yast-1.07.3-1.i386.rpm axx xx [o] * 2.8M Mar 12 13:50 yast-1.07.3-1.src.rpm Hmm - not there..... Aside which YAST is also largely broken..... BTW - I don't think 7.1 installed the new Firewall or Forwarding tools to deal with iptables..... I'm still investigating.
And you are free to compile your kernel anytime -- you just loose the ability to get installation support.
Screw that - that is flat out no right of SUSE and is PART of the problem....Changing the oil shouldn't invalidate the agreement... especially when there is a SECURITY HOLE in the 7.0 Kernel
And you _don't_ have to compile your own kernels. How about getting the security updates instead?
THEY FAIL