I am using http://www.kroah.com/lkn/ as a guide to upgrade from kernel 2.4.33.3 to 2.6.20.7. Chapters 4 & 7 discuss making/configuring the .config file. I think I know what to do but I want to clarify the following:

1) Can I copy a .config file from version 2.4 to version 2.6?
2) If I do this and subsequently run "make menuconfig", will I see the settings of the 2.4 kernel as default-selected options?

In a nutshell, will having the old .config file in the new kernel directory make it easier to tweak the config file using the menu config tools, or do those wizards ignore the contents of the current .config file?

Just start with a new config. You can look off the only one, but the make system won't recognize it or interpret it properly.

Did you work really hard on the 2.4.x config or something ?

Why not just do it? Copy the thing over and run make menuconfig and see what you get. It's not like Linus himself is gonna come slap you for it.

You certainlay can just copy over your old config file. There are some options that won't show up correctly though as they are relocated or changed. In particulat you may find that you need to re-select the framebuffer options so you don't get a black screen your first time.
The best way to handle this may be to copy over the old file and then run 'make oldconfig' which will only ask you about the options which have changed or are new. Then run 'make menuconfig' and double check before compiling.

yes, and I'd add to be _especially_ careful about scsi/sata driver(s) that you might need. there were many options changed between 2.4-2.6 series kernels and if you don't fix them (make oldconfig does a good job, but for instance libata should be disabled, and proper drivers enabled..) you damned to kernel panic heellllll....

bwahahaha!!!!!!!

oh, sorry... did i type that out loud.

You could also start with the kernels/huge26.s/config file from the Slackware-11.0 distribution, and modify it to suit your needs.

No. I was under the assumption that when I initially installed SW there may have been some custom settings written to my current .config file. I was more concerned of getting to a setting in the new one that I was unfamiliar with and having a default option pre-selected for me that would work with my machine.

Then you can copy in one of the Slackware 2.6.x configs and start with that if you want.

This has to be the strangest thing I've seen on LQ. Does slackware have a separate set of device driver writers who are replacing libata? If you disable libata, you will not have SATA access.

no, im a dope.. its libata that replaced the old ide-ata support. sorry folks.

BLK_DEV_IDE_SATA <-old
ATA <- new

sorry all.