From: Padraig Brady <padraig.brady@corvil.com>
To: garrett@tbaytel.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE, TRIVIAL, RFC] Linux source strip/bundle script
Date: Tue, 01 Oct 2002 12:52:53 +0100 [thread overview]
Message-ID: <3D998C95.9060606@corvil.com> (raw)
In-Reply-To: 200210010734.14949.garrett@tbaytel.net
Garrett Kajmowicz wrote:
> As per the suggestion of the lkml FAQ section 7-7, I have spent some time
> working on a script to automatically go through the Linux source tree and
> generate a stripped down version of the kernel source code (x86 only), along
> with a few additional 'modules' which will contain additional funtionality,
> if desired (such as irda or scsi support).
>
> I have requested an account on kernel.org, and hope to run/test this script
> for each full, stable release. I would like all of the input possible on the
> script. Please note that this is the first version, so there are probably
> many rough areas.
>
> For a copy of the script please try:
>
> http://garrett.dyndns.biz/makemini.sh.bz2
>
> Please Cc: all comments to:
>
> Garrett Kajmowicz
> gkajmowi@tbaytel.net
1. There is a distinct dearth (hmm an anagram of redhat) of loops.
2. When trashing the source like this you may as well remove
trailing whitespace (reduces kernel by 200K after compression).
3. What's the difference in size between 2.4.19.tar.bz2 and
2.4.19-bastardized.tar.bz2 ?
4. Is this just for (a) removing redundant code after installation or
(b) providing subset version(s) for download.
5. If 4(a) wouldn't you need to parse the .config to find the appropriate
bits to remove?
Pádraig.
next prev parent reply other threads:[~2002-10-01 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 11:34 [ANNOUNCE, TRIVIAL, RFC] Linux source strip/bundle script Garrett Kajmowicz
2002-10-01 11:52 ` Padraig Brady [this message]
2002-10-01 12:14 ` Garrett Kajmowicz
2002-10-01 16:48 ` Daniel Phillips
2002-10-17 22:39 ` john slee
2002-10-17 23:08 ` Garrett Kajmowicz
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=3D998C95.9060606@corvil.com \
--to=padraig.brady@corvil.com \
--cc=garrett@tbaytel.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.