On Monday 23 April 2001 20:38, Mads Martin J�rgensen wrote:
* Brooklyn Linux Solutions CEO
[Apr 23. 2001 18:30]: Your confused. This is not an issue of support, this is an issue of the distro not being broken in the first place.
A normal kernal compilation is not a special something which maybe SuSe should allow, it is the corner stone of a working open source system. If the distro is so BROKEN that you can't compile the Linux source code as necessary for security (which as a matter of fact is the issue with the 2.18 code now being insecure), then the system is broken.
That is a bold statement my friend. I compile 1-2 kernels a day, without any problems whatsoever.
I'n setting up two PC's here at home I recompiled the 2.2.18 kernel on both more times that I can remember without any problems. But, while I chose the 2.2.18 kernel during a clean install, YaST2 decided I needed the 2.4.0 kernel source tree instead. I had to install the 2.2.18 source tree to get it to compile. No big deal, though. Somebody must have thought that because the system already included the modularized 2.2.18 kernal, I would not need the 2.2.18 source. I'd only need the 2.4 source, assuming I would compile it and move to the 2.4 kernel. Or so it seems. ???
And you are free to compile your kernel anytime -- you just loose the ability to get installation support.
And you _don't_ have to compile your own kernels. How about getting the security updates instead?