public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Khalid Aziz <khalid_aziz@hp.com>
To: Paul.Clements@steeleye.com
Cc: Khalid Aziz <khalid@fc.hp.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5] Retrieve configuration information from kernel
Date: Tue, 29 Oct 2002 11:18:57 -0700	[thread overview]
Message-ID: <3DBED111.96A3A1E8@hp.com> (raw)
In-Reply-To: Pine.LNX.4.10.10210291204590.28595-100000@clements.sc.steeleye.com

Paul Clements wrote:
> 
> Have you considered compressing the config info in order to reduce
> the space wastage in the loaded kernel image? Could easily be 10's of KB
> (not that that's a lot these days). The info would then be retrieved via
> "gunzip -c", et al. instead of a simple "cat".

I wanted to start with a simple implementation first. There are a couple
of things that can be done in future to further improve meory usage: (1)
Drop "CONFIG_" and "# CONFIG_" from each line and add it back when
printing from /proc/ikconfig and extract-ikconfig script, (2) Compress
the resulting configuration. Something to do in near future :)

-- 
Khalid

====================================================================
Khalid Aziz                                Linux and Open Source Lab
(970)898-9214                                        Hewlett-Packard
khalid@hp.com                                       Fort Collins, CO

"The Linux kernel is subject to relentless development" 
				- Alessandro Rubini

  reply	other threads:[~2002-10-29 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 16:24 [PATCH 2.5] Retrieve configuration information from kernel Khalid Aziz
2002-10-29 17:11 ` Paul Clements
2002-10-29 18:18   ` Khalid Aziz [this message]
2002-10-29 19:30     ` Chris Friesen
2002-11-05 17:27       ` Khalid Aziz
2002-10-30 10:42     ` Padraig Brady
2002-11-05 17:23       ` Khalid Aziz

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=3DBED111.96A3A1E8@hp.com \
    --to=khalid_aziz@hp.com \
    --cc=Paul.Clements@steeleye.com \
    --cc=khalid@fc.hp.com \
    --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