I had a question

I wanted to try the 2.6.15 Kernel, so I tried to xconfig it, but it uses the old /boot/config-uname-r file it basiclly can't find a bunch of symbols (guessing they are suse specific).

/boot/config-2.6.13-15.7-default:24:warning: trying to assign nonexistent symbol SUSE_KERNEL

Or with SuSE is it better to wait for the YOU update? I want to compile my own .

Also,

Does anyone know where i can get ncurses-devel, if you try to install from the CD"s it says it isn't there on CD5.

Note: Here is how I compiled the Kernel:

make mrproper
make xconfig
--- Missing Symbol Errors ---
make dep
make clean
make bzImage
make modules
make modules_install

Thanks in advance

If you want a hassle free install of te new kernel with no configuration yoruself. Go to ftp://ftp.suse.com/pub/projects/kernel/kotd, you can get kernels preconfed for easier install. Then you can just install them as rpm, and suse will handle it all for it. They also have patches available if you do the compile yourself to add the suse stuff in the same area.

First the easy part: If you can't find ncurses-devel on your installation medium, try to add online repositories to the installation sources. You can use either YaST->Software->Installation Source or the command 'installation_sources -a <URL>' from command line (root). For URL's, have a look at the sticky threads.

Now the more tricky one: I think it's a good idea to use the old configuration as a template. However, the SUSE kernel is patched, so it does contain additional features (causing the warning-message). I wouldn't be too worried about this. I have no idea how to force 'make xconfig' to use the real (non-SUSE) default settings. I actually thought it would do it automatically. But as I said before: It's just a warning, not an error!

It's surely safer to wait for a YOU update, since this will contain all the SUSE patches, but it's half the fun!

BTW: You can skip 'make dep' and combine 'make bzImage' and 'make modules' by typing just 'make'.

I am compiling custom kernels from both: vanilla and SuSE's HEAD and I never had your problem. Currently I am running custom from SuSE's HEAD 2.6.15.
If you are using old .config this would be obvious.
Once config is loaded save it and all missing references will be gone (I am not sure if this is clear?). In other words: kernel change, so old stuff may be deleted and new appears. Nothing wrong here.

Personally I am always making fresh .config for each x.x.number.x and up: so for x.x.11.x x.x.12.x and so on and for x.2.x.x. x.4.x.x x.6.x.x
I don't bother with the last version number.

Yes, I know after the first time you run the xconfig then the errors will go away the second time (because well duh!, it isn't using the same config file anymore ).

But what SuSE patches are included into it?

well,
get suse's head src.rpm unpack it, and there you have what you are looking for