From: 1stFlight <1stflight@ameritech.net>
To: Eng Se-Hsieng <g0202512@nus.edu.sg>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Oversized kernel
Date: Wed, 12 Mar 2003 06:04:45 -0500 [thread overview]
Message-ID: <3E6F144D.3090501@ameritech.net> (raw)
In-Reply-To: <720FB032F37C0D45A11085D881B03368A2B496@MBXSRV24.stu.nus.edu.sg>
Are you using "make bzImage:" when you compile? It makes for a smaller
kernel
Eng Se-Hsieng wrote:
>Dear all,
>
>I've just compiled a new kernel and the vmlinuz is over 2Mb in size.
>Since mkbootdisk returns : Not enough space and I don't have a CD writer
>on my system, I'm unable to create a boot disk and am a little wary
>about not having one.
>
>How does one know what are the minimum options to choose in order to
>reduce the size of the vmlinuz? My system is a Toshiba Satellite 4030CDT
>(Celeron 266 Mhz)
>
>Thank you.
>
>Regards,
>Se-Hsieng
>-
>To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.linux-learn.org/faqs
>
>
>
--
It's not that life is so short, it's that death is so long...
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2003-03-12 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 9:59 Oversized kernel Eng Se-Hsieng
2003-03-12 10:02 ` Eckhardt, Rodolpho H. O.
2003-03-12 11:04 ` 1stFlight [this message]
2003-03-13 0:35 ` Eric
[not found] <720FB032F37C0D45A11085D881B03368A2B496@MBXSRV24.stu.nus.ed u.sg>
2003-03-12 16:19 ` Ray Olszewski
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=3E6F144D.3090501@ameritech.net \
--to=1stflight@ameritech.net \
--cc=g0202512@nus.edu.sg \
--cc=linux-newbie@vger.kernel.org \
/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