linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Garrett Kajmowicz <gkajmowi@tbaytel.net>
To: linux-kernel@vger.kernel.org
Cc: padraig.brady@corvil.com
Subject: Re: [ANNOUNCE, TRIVIAL, RFC] Linux source strip/bundle script
Date: Tue, 1 Oct 2002 08:14:17 -0400	[thread overview]
Message-ID: <200210010814.17353.gkajmowi@tbaytel.net> (raw)
In-Reply-To: <3D998C95.9060606@corvil.com>

> 2. When trashing the source like this you may as well remove
>     trailing whitespace (reduces kernel by 200K after compression).

	I do not modify the source code files themselves.  I simply 'prune' the tree, 
creating 'dummy' Config.in and Makefiles as requred to prevent things from 
breaking too much.  The only file that I edit in any way is the config.in in 
arch/i386 to change the scsi enabled default from y to n. This was so that 
people who don't download the scsi 'module' don't run into problems with 
compile failing.  I will be making a few patches to the source tree for the 
Config.in files to make this and other relted things less likely to happen.


> 3. What's the difference in size between 2.4.19.tar.bz2 and
>     2.4.19-bastardized.tar.bz2 ?

Size of some of the packages that I have done with this script:

linux-2.4.19-base.tar.bz2	-	11 MB
linux-2.4.19-scsi.tar.bz2	-	2.5 MB
There are currently 15 other 'modules', not listed here

> 4. Is this just for (a) removing redundant code after installation or
>     (b) providing subset version(s) for download.

This will provide a subset for download.  Due to not having the ability to 
host, it may be applied to the full code after download for testing purposes.

> 5. If 4(a) wouldn't you need to parse the .config to find the appropriate
>     bits to remove?

I prune the tree at the directory level.  If I do not want/need irda support, 
I wipe out the irda directory, recreate it with a dummy Makefile and 
Config.in file so the make menuconfig script doesn't break, and the kernel 
will compile.  This results in less savings, but in higher stability/ 
reliability.

  reply	other threads:[~2002-10-01 12:13 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
2002-10-01 12:14   ` Garrett Kajmowicz [this message]
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=200210010814.17353.gkajmowi@tbaytel.net \
    --to=gkajmowi@tbaytel.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=padraig.brady@corvil.com \
    /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;
as well as URLs for NNTP newsgroup(s).