From: DervishD <lkml@dervishd.net>
To: Tom Fredrik Blenning Klaussen <bfg-kernel@blenning.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/config reducing kernel image size
Date: Tue, 14 Sep 2004 20:01:24 +0200 [thread overview]
Message-ID: <20040914180124.GA624@DervishD> (raw)
In-Reply-To: <1095183412.1834.7.camel@host-81-191-110-70.bluecom.no>
Hi Tom :)
* Tom Fredrik Blenning Klaussen <bfg-kernel@blenning.no> dixit:
> > > There is no point in storing all the comments and unused options in the
> > > kernel image. This typically reduces the config size to about 1/5th
> > > before compressing, and to about 1/4th after compressing.
> > I'm with you in that there is no point in storing the comments,
> > but I disagree about the unused options. Storing the unused options
> > as comments is more useful than it seems ;)
> This is why I added a config option.
But removing the comments is a good idea. Even reformatting the
contents, or something like that.
> > I'm not really sure about it, but I think that the unset options
> > are left as comments for the sake of automation. The space saving
> > doesn't (IMHO) worth the pain.
> I'm not sure either, but I don't know of any programs that uses this.
Neither do I.
> Putting this config file inside the same source tree as it was compiled
> with, and then just starting and stopping menuconfig will restore it to
> it's original form.
That's true.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
next prev parent reply other threads:[~2004-09-14 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 16:33 /proc/config reducing kernel image size Tom Fredrik Blenning Klaussen
2004-09-14 17:26 ` DervishD
2004-09-14 17:36 ` Tom Fredrik Blenning Klaussen
2004-09-14 18:01 ` DervishD [this message]
2004-09-15 10:11 ` Herbert Poetzl
2004-09-14 17:44 ` Norberto Bensa
2004-09-14 17:57 ` Tom Fredrik Blenning Klaussen
2004-09-14 18:11 ` Norberto Bensa
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=20040914180124.GA624@DervishD \
--to=lkml@dervishd.net \
--cc=bfg-kernel@blenning.no \
--cc=linux-kernel@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