Running redhat 6.0 on a P166 (go ahead, laugh). Recompiling the 2.2 kernel, but when I run lilo after adding my new kernel image to /etc/lilo.conf, it says: 'kernel /boot/newlinux too big'. This new kernel is about 1M smaller than the stock kernel, which obviously is okay. Anybody seen this before?

It might say a bit more after that, like "Too big for floppy". Which is possible if you built more into this kernel than the stock one had.

Cool

nope! the size of the image is about 465k That should fit on a floppy. Like I said, it's about 1M smaller than the stock kernel; the only thing I added was apm support, which is not included in the Redhat 6.0 kernel by default.

Then I just did 'make dep clean modules modules_install zImage' and then copied my zImage over into /boot/newlinux.

There were no errors during compilation.

At the end of compilation it didn't send out a message about kernel size might be too big for floppy?

Instead of zImage try bzImage, it might compress better.

Also, might I ask why a RH6 when that's a good, what, 3 years old?

Cool

It's a P166. Tried installing redhat 9 on it earlier and installation had unexplained problems. RH6 runs fine, although X is a little slow. The big reasons for getting a newer version of an OS is 1) a kernel that has drivers for new hardware, and 2)Better, more elaborate WM. I don't have any new hardware, and I'm pushing it right now as far as KDE or enlightenment is concerned, anyway. It's running on a small lab network that's not connected to the Internet, so I don't even need to worry about the latest security fix for Apache, or whatever. I'm just trying to make the kernel a little tighter.

Once again, my compiled zImage is only 465k, which shouldn't have any problems fitting on a floppy, and it's strictly smaller than the stock kernel. If the stock kernel is not too big and lilo doesn't have any problems adding it, why should it have problems adding my new kernel?

That's a good question I cannot see any reason other than maybe the stock kernel wasn't reporting correctly...

Hopefully one of the more experienced users on the forum will know and reply. In the meantime, I'd give a go at bzImage just to see if that does the trick (it might have to do with how lilo uncompresses a kernel).

Cool

thx anyway, cool,

btw, (unrelated) how did you pull all of that shit off of the Windows desktop? (saw yer screenshot) I'm running a dual boot at home between W2k and Mandrake; it'd be nice to be able to clean up my W2k desktop like that.

I don't know what version of LILO you are using, but you might consider upgrading that and the kernel. Even if you are using an older distribution, you should still keep up with the boot loader and kernel upgrades.

that's probably the answer, moses. I probably will. The real pain is that this PC is in a lab in the data center of the company I work for. The wee bas'ards won't let me connect it to the Internet, and I don't have a burner handy here. So if I wanna download something larger than 1.44M, I gotta go home and burn it. I'll go see if I can find that RH9, and install stuff from the source RPMs, I guess. Maybe it's a bug, but I'd sure would like to know for sure that I'm not doing anything wrong (other than using a crappy PC with an outdated distro). that's all!

thanks,
florestan

I don't remember. It's been a while, but I think that if you remove the icons to a directory on the desktop, that you then make a System directory, you can "hide" system directories but they will appear in the Taskbar "Desktop" link

I don't really remember though...

Cool

This might be a stupid post but thought I'd chuck it in anyway.

Is your /boot directory on a separate partition, and if so is it large enough to hold two kernels (the running one and the one you are trying to compile) ?