From: Herbert Poetzl <herbert@13thfloor.at>
To: Tom Fredrik Blenning Klaussen <bfg-kernel@blenning.no>,
linux-kernel@vger.kernel.org
Subject: Re: /proc/config reducing kernel image size
Date: Wed, 15 Sep 2004 12:11:10 +0200 [thread overview]
Message-ID: <20040915101110.GA12585@MAIL.13thfloor.at> (raw)
In-Reply-To: <20040914180124.GA624@DervishD>
On Tue, Sep 14, 2004 at 08:01:24PM +0200, DervishD wrote:
> 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.
well, the kernel config uses it, to decide if
some option is known, or has to be defaulted/asked
try to remove one of those 'comments' from a config
and run 'make oldconfig', you'll get asked for this
specific option ...
best,
Herbert
> > 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/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
next prev parent reply other threads:[~2004-09-15 10:13 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
2004-09-15 10:11 ` Herbert Poetzl [this message]
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=20040915101110.GA12585@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--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