From: "Tom Troonbeeckx" <tom.troonbeeckx@ideaxis.com>
To: Arvind <lists@duh-uh.com>
Cc: linux-admin@vger.kernel.org
Subject: RE: Kernel compile => disk error continued
Date: Wed, 17 Sep 2003 11:51:52 +0200 [thread overview]
Message-ID: <ALECJBOGPBKDNCCOAFDDKEPOCPAA.tom.troonbeeckx@ideaxis.com> (raw)
In-Reply-To: <20030917005304.GA1124@localhost>
Thx all for the information, you posted
The problem is meanwhile resolved. After resetting some options(builtin ->
modules) it didn't complain .
Thx for the tips...
-----Original Message-----
From: linux-admin-owner@vger.kernel.org
[mailto:linux-admin-owner@vger.kernel.org]On Behalf Of Arvind
Sent: woensdag 17 september 2003 2:53
To: linux-admin@vger.kernel.org
Subject: Re: Kernel compile => disk error continued
> I use a virtual scsi setup in order to write CD's. After reading the
> documentation the size error has to do with the initrd-X.X.X.img. at first
> sight.
>
> Mine previous kernel did build this one automatically. Any idea's to
build
> this image for the new kernel (2.4.22)
Did you do a:
make bzImage
As far as I remember, the vmlinuz target used to be very big and
didn't fit in the first 1024 cylinders or something like that.
Only lilo used to have such problems, though, and not grub.
bzImage is a compressed kernel image.
Arvind
--
Surprise! You are the lucky winner of random I.R.S. Audit! Just type
in your name and social security number. Please remember that leaving
the room is punishable under law:
Name
#
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2003-09-17 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 10:11 Kernel compile => disk error continued Tom Troonbeeckx
2003-09-15 4:57 ` Gustavo Guillermo
2003-09-17 0:53 ` Arvind
2003-09-17 9:51 ` Tom Troonbeeckx [this message]
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=ALECJBOGPBKDNCCOAFDDKEPOCPAA.tom.troonbeeckx@ideaxis.com \
--to=tom.troonbeeckx@ideaxis.com \
--cc=linux-admin@vger.kernel.org \
--cc=lists@duh-uh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).