I'm trying to compile openMosix into a kernel(also i have never compiled a kernel before). I've read the stuff on the openMosix site, slackware.com and the stuff that DaOne posted at the top of this forum. I have tried twice now and about an hour or so into the compile (on a P166) it says:
warning: this kernel is too big to fit on a floppy disk (or someting close to that)
and then it ends. I don't know if that's what is supposed to happen so I tried to boot that kernel and when I selected it in lilo it tries to load and then it says that it is too big. Can anybody help me? I'd appreciate any ideas.

thanks

soup

well not really anythign to say other than you need to be more selective about your kernel, only use modules that you need, and consider making them as modules instead of compiling them into the kernel directly

Actually if you're not planning to boot off a floppy, your kernel is just fine. Heck, even my kernel is more than 1.4MB. It's still compiled, and should reside in your arch/i386/boot directory from where u compiled it... eg: /usr/src/linux/arch/i386/boot

I'm not booting off a floppy. And I don't want to. But I guess for some reason it thinks I do want to. Is there something that I didn't do that tells it I don't want to boot off a floppy?

Nah, it's just a notification. Don't lose sleep over it

a larger kernel is, natually, slower and more cumbersome, and kinda defies the whole point of compiling your own kernel in the first place.

Then how do I get it to boot? as I said when I select it in lilo it just says it's too big and then won't boot.

exactly what it says is:
boot:
Loading Linux_OMEBDA too big

i called it Linux_OM in lilo

Assumed you have copied the bzImage to your /boot partition?
Assumed you have copied the System.map there as well?

Maybe you haven't ran /sbin/lilo after editing your lilo.conf file?

I must not have run /sbin/lilo because i just ran it and now it seems to be working. thanks a lot Azmeen

soup

No prob man... congrats!