From: Eli Carter <eli.carter@inet.com>
To: linuxlist@visto.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel size
Date: Fri, 07 Dec 2001 10:46:20 -0600 [thread overview]
Message-ID: <3C10F25C.FACDA516@inet.com> (raw)
In-Reply-To: <3C07FA8E0005C3C2@iso1.vistocorporation.com> (added by administrator@vistocorporation.com)
rohit prasad wrote:
>
> Hi,
>
> I have compiled a kernel on a machine with a partition size of 20GB and am running it there.
>
> I ftp'd this kernel to another machine with similar partition size of 20GB but when I run lilo there I get a message "Fatal: Size too Big"
>
> Why is that.
Guesses: different versions of lilo, and you're getting the failure on
the older version? Maybe it's refering to the size of the kernel as
opposed to the disk partition?
Eli
--------------------. Real Users find the one combination of bizarre
Eli Carter \ input values that shuts down the system for days.
eli.carter(a)inet.com `-------------------------------------------------
next prev parent reply other threads:[~2001-12-07 16:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 8:53 kernel size rohit prasad
2001-12-07 16:46 ` Eli Carter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 15:38 Ken Applebaum
2002-04-11 16:40 ` Conn Clark
2001-12-13 4:38 Kernel size rohit prasad
2001-10-09 14:16 kernel size VDA
2001-10-09 13:26 ` [solid]
2001-10-09 13:28 ` Nikita Danilov
2001-10-09 14:16 ` Richard B. Johnson
2001-10-09 14:43 ` Ingo Oeser
2001-10-09 14:52 ` Richard B. Johnson
2001-10-09 15:43 ` Horst von Brand
2001-10-09 15:53 ` Richard B. Johnson
2001-10-10 1:29 ` Keith Owens
2001-10-10 13:00 ` Richard B. Johnson
2001-10-10 14:47 ` vda
2001-10-11 12:41 ` vda
2001-10-10 1:30 ` Kenneth Johansson
2001-10-09 15:55 ` Jakub Jelinek
2001-10-10 1:27 ` Keith Owens
2001-10-04 13:11 Security question: "Text file busy" overwriting executables but not shared libraries? Eric W. Biederman
2001-10-04 14:24 ` Kernel size Richard B. Johnson
2001-10-13 20:35 ` Aaron Lehmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C10F25C.FACDA516@inet.com \
--to=eli.carter@inet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxlist@visto.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.