Jerry Kreps wrote:
I did install with yast1 and yes, it did install a kernel source, but it was for the 2.4 kernel, not the 2.2.18 kernel. I used yast to remove the 2.4 kernel and install the 2.2.18 kernel. Yast is an rpm tool and uses rpm files Nothing I want to do about that. Are you saying that I should download a tar source and install it? I'm not keen on that idea.
No this is not what I meant. First have a look to what kernel rpms are installed either thru yast or via rpm -q . What I do normall is since the sue compiled kernel is unnecessarly big for my needs, I do issue a make cloneconfig command to get the suse config options. Then I remove the precooked kernel and the related kernel modules with yast and then compile my own kernel (for that I use the suse kernel source rpm lx_suse something) This way unresolved symbols do not come to the screen. On the other hand other than making the kernel image smaller, I think all the necessary modules are built by Suse so there should not be any problems using the suse supplied kernel (actually this is a must for suse support request) Yast for me is not an rpm tool but and administraiton tool using rpm as one menthod and actually does not use the full rpm commands (someone correct me I am wrong) yast uses rpm with --nodeps and --force options IIRC -- Togan Muftuoglu