Installing Slackware on a custom kernel
 

I have a very lean kernel on my desktop slackware computer (yeah, I'm proud of it). I installed it all onto one partition, and I am going to reinstall it with a better partitioning system, and I was wondering if it is possible to install Slackware using my current kernel? I am guessing I could just keep my .config file and copy it into the source directory after installing and then recompile that, but I thought this way would be cooler, if it is possible.

You SHOULD be able to add it to the /kernels folder on your slackware install , reimage the iso and burn again. Not sure if there is a list where you can add it in to the list of kernels tho....From what I can figure out, just mkdir /kernel/kernel.i or whatever you wanna name it, copy in the bzImage, config, and System.map, and it SHOULD show as a installable kernel.

Let us know if it works...If it does, you should be able to make the source as a package, and add that in too.

I'm VERY interested in this. If it works for you, I'll try it too. (Why I don't do it first: I only have three blank cd-r disks right now....lol)

Right, well I am going to work for about 3 hours today (Sunday, bleh :() when I get home I will try it. I mean, whats the worst that can happen? Another coaster?

True. You can then mail it to AOL here in the States. Maybe they'll get the hint....

LOL AOL coaster, I have a ton of em' here too.

Hey if you get that working how to use a custom kernel at install can you post how you did it? I'd really be interested how that is done PLEASE pretty PLEASE :D

Fogie

Hey, If the OP does not, I'll track 'em down and bludgeon 'em across the torso with a bag of AOL disks.....

Actually, I'm working on doing that(making the custom install cd/kernel) right now...Got some more blanks. Now, if my cd drivr stays working (Been burning only half a disk lately, no matter what os I use...Might have to burn it on the wife's XP box ....shudder...)

I thought of a smallish issue....No modules for the custom kernel....
Might be able to copy them from /lib/kernel

Also, may need headers. From where, I do not know. I look more into this as it goes...

Yeah I just dumped the files and burnt. Didnt work, coaster #1.

Reburn, this time with the whole current directory (I know I could do it over the network, but I am not sure how) that I use. ie no KDE or emacs etc. This didnt boot. I forgot to make it a bootable cd! Coaster #2... or is it? I booted from my slack cd and did a swap at the prompt. It worked! Everything ran and installed perfectly. So I rebooted. No text after lilo. I don't know what happened here to be honest. I did a blind log in and started XFCE, that brought my monitor to life, just no CLI at boot.

I fiddled with that for a while, even compiled the kernel again via SSH. Still nothing. This is the same kernel that worked before this reinstall, so who knows. So I just reinstalled with my normal slack cd and am compiling my custom kernel from my .config file. I happened to get my hands on an old P3 system which I'll pick up on Wednesday, and which will become my test system for getting this to work I think. It will be interesting

cwwilson, I just wanna be sure before I try again, how would I burn a bootable slack disk?

This looks interesting. Just a couple thoughts, I've never actually done this...

I don't think you need to fuss with the kernel headers. I think you just need the kernel headers for the kernel version used to build glibc.

hsimah... to burn a bootable CD, there's a README on the first install disk at /isolinux/README.TXT.

I used a mirror script to make the mirror and the ISO's for current. The only issue is that it would remove my "additions" before it would make the iso.

So I added a few lines in to add the files back before it made the iso....And it worked. Unfortunately, I have only one blank cd right now. I'll burn cd1 and see if it lets me start the process and install the custum kernel at the end of the install. (can do the rest later). At least it will let me kow if the kernel would work.

If it's successfull, I'll post a step by step here, maybe even a mini HOW-TO.

Cool, I hope it works :D.

I am having a weird problem with my install of slack on my desktop. I copied the .config file out of my /usr/src/linux directory (2.4.31 kernel) and reinstalled with the default options from my 10.2 CDs. My ethernet card decided it didnt want to work, but I eventually fixed that by using DHCP instead of static IP address (I do like my IP's static though). Then I did a make mrproper in the source directory and copied in my .config and did make menuconfig, it seemed to be the same (I'd assume it should be) as before my reinstall, so I compiled it (make dep, make clean, make bzImage, make, make install, make modules, make modules_install) and rebooted. Now I get an error at startup with regards to agpgart... I have no idea why it is not working this time! I think I'll jsut format and reinstall again, with the a new slack CD, mines several months old now and fairly scratched.

Why do you want to do this? I usually install Slackware using the stock kernel, then copy my custom kernel across.

Never had a problem doing things this way.

I've found it handy to make a CD containing my custom kernel (including System.map, config, modules and source tree) and complete copies of my /etc & /var directories.

Mostly, because it's an interesting project. Better than sleeping....

Yes, but it would become redundant as soon as the installation is finished. Time better spent sleeping, IMO... :D

Because it's there?

To become one with the system?

Seriously, I do a pretty lean install on my laptop, and I'm reckless with experimenting on it. I always burn an install disk with custom tagfiles anyway, so that I can easily reinstall. I might as well toss my own kernel on there too. I'll give it a try after the next release. (cwwilson... if you get there first, I would be interested in knowing what you did.)