Messages in this thread | | | Date | Tue, 24 Dec 1996 11:21:38 -0700 | From | (David Sherburne) | Subject | Kernel to big for lilo? |
| |
I am having a similar problem to the followin e-mail :
Date: Mon, 23 Dec 1996 14:25:42 -0900 (AKST) From: Britton <fsblk@aurora.alaska.edu> To: linux-kernel@vger.rutgers.edu Cc: linux-kernel-digest@vger.rutgers.edu Subject: Re: linux-kernel-digest V1 #672 Mime-Version: 1.0 Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk Status: U
This question is basic but it is kernel-related. I am trying to upgrade from 1.2.13 to 2.0.27 and everything works well except the kernel generated is not compressed. It is over 1 M and lilo says this is too big. I am using make dep ; make clean ; make zImage as in the README. The only thing that I can think of that might be getting me is the fact that I am not compiling in the standard directory since I'm not ready to replace everything yet. The compilation mechanism seems well aware of this fact, however, and it seems unlikely it would get confused on the last stage. Any suggestions greatly appreciated. Thanks to the person/people who wrote menuconfig, it helps lots.
----------------
I also have rebuilt the kernel to enable networking using TCP/IP but lilo complains about the size of the new kernel (anybody know why?). I am presently running Linux 2.0.0 (Slackware 3.0) on P6 200MHz with 99MB RAM. When I originally configured lilo I answered yes to putting it on the Master Boot Record (are there any other options? and what does this mean?).
Thanks in advance -Dave
++++++++++++++++++++++++++++++++++++++++++++++++ R. David Sherburne KES 3725 Talbot St. Suite 1 San Diego, CA 92106 (619)224-9794 (office) (619)553-3566 (On-site) rdsherb@nosc.mil ++++++++++++++++++++++++++++++++++++++++++++++++
| |