Results 1 to 2 of 2
My patched slack 2.6.13 kernel patched with patches 2.6.14, 2.6.15, 2.6.16 is 5,055,940 and I'm getting the message that it's too big. I've tried to reduce it with little success. ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 04-24-2006 #1Just Joined!
- Join Date
- Dec 2004
- Location
- Queensland, Australia
- Posts
- 1
kernel too big message from lilo
My patched slack 2.6.13 kernel patched with patches 2.6.14, 2.6.15, 2.6.16 is 5,055,940 and I'm getting the message that it's too big. I've tried to reduce it with little success. I'm not willing to make it the only kernel available for boot. I'm using lilo. What would the size be if I maxed the number of modules? Anyone have any suggestions?
- 05-01-2006 #2Just Joined!
- Join Date
- Sep 2005
- Location
- Augustana College
- Posts
- 69
Compiling as many drivers as possible into modules will help, as this means that they are not part of the kernel. Do you need to patch the kernel you have, or could you download the entire source for the 2.6.16 kernel and compile that? I suspect that all of the patches are bloating your kernel size beyond the size difference you'd see just from moving straight to the newer version.
Reply With Quote 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
