Debian install use .config from slack?
 

I've just finished a fresh install of Debian SID netinst. It uses a quite old kernel (2.2.20) and want to upgrade it to 2.6.1. Can I use the .config file from my slack (running fine) to config the kernel without going true all those settings again?

Second question is about lilo. Never had any probs with it but for some reason I'm not getting triple boot done this time.
Deb boots fine so is winxp. Slack is on a reiserfs partition and reiserfs is not supported by the current deb kernel installed. Does that have anything to do with not being able to config lilo to boot it? image=/dev/hdb and root=/boot/vmlinuz gives me a error about not being able to find the vmlinuz (I'm at work not sure about the exact error message).

Any clues?

Regards

youshould be able to share the .config ok, as long as it's for the same kernel version (or within a couple of versions...) i've done it in the past, and other than having additional options from patches applied to your slackware source there's little to go wrong. any unsupported options would just get ignored.... with a kernel that old though you'll have a lot of updates to run before a 2.6 kernel has a chance of running though. it'll install but the first thing you're likley to hit is "QM_MODULES NOT DEFINED" or similar, so you need to upgrade modutils or whatever it was called.

lilo... no it won't relate to the slack kernel, it just sounds like you are configuring lilo wrong. This is the kind of thing that made me switch to grub, as it makes so much more sense once you get to grips with the syntax for it. in order to make lilo boot from an alternative vmlinuz you have to update lilo and then rerun lilo to update the MBR. THe thing with lilo is that the paths reference in it are all relative to the booted system you are running in, so assuming you have a seperate /boot for debian you will need to mount this other partition inside slack so you can actually SEE the file, and then reference it in lilo.conf as that path. so even thoguh in deb you're going to have /boot/vmlinuz, the slack lilo.conf will contain something horrible like /mnt/debian/vmlinuz. yuck!

The lilo part makes sence and perhaps it's time to start using grub ;) I've been thinking about that for some time now.

Reading your post about having to update a lot since the kernel is old, I think I better look for a more recent kernel in a netinst debian image. Strange though that a link to a netinst image on the debian site (it is contrib, true) points to such an outdated set. I noticed that even USB isn't compiled in the kernel. perhaps I'd just better get the first install cd from debian stable and switch to netinstall and SID in the process. This (I think) should at least give me a 2.4.x kernel and I had no problems going to 2.6.1 on slack from there. Can't be much different on Deb I guess (even though I prefer to compile my own kernel instead of the debian way). Good to know I can use the .configure file. Thanx for your answer, hope to have Deban 2.6.1 up and running soon!