From: Michel Lanners <mlan@cpu.lu>
To: dan_bethe@yahoo.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: slim kernel source
Date: Thu, 28 Mar 2002 08:27:05 +0100 (CET) [thread overview]
Message-ID: <E16qUJT-0000An-00@piglet.grunz.lu> (raw)
In-Reply-To: <20020327183028.71552.qmail@web11002.mail.yahoo.com>
On 27 Mar, this message from Dan Bethe echoed through cyberspace:
> Hi all. Is there a utility or procedure which can remove a bunch of the code
> from extraneous architectures from my kernel source tree? I only want to build
> kernels for my beloved Powermac 8500 and so I can do without code specific to
> ia32, S390, Alpha, MIPS, and friends.
Hmmm...
> Even if you just know of a few directories I can remove and save a couple dozen
> megs of space, that'd be good.
A random benh 2.4 kernel tree has 127 MB once de-tgz'ed. Of these, 69 MB
are drivers, for which it is difficult to know what you need and what
you don't need. Removing random stuff in there might break the kernel
Makefiles, too.
Which leaves arch/ (22 MB) and include/ (15 MB). In arch, 2.6 MB is ppc/
(not one of the leaner arch'es :-), but there have been cases of one
arch relying on code of some other arch.
In include/, the asm-* part is roughly 10 MB, of which asm-ppc eats
600K. Again, the caveat about dependencies between arch'es apply.
In general, the kernel sources are not meant to be cut in pieces. You
can certainly remove large parts, but you're on your own if anything
breaks.
Cheers
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-28 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 18:30 slim kernel source Dan Bethe
2002-03-28 7:27 ` Michel Lanners [this message]
2002-03-28 9:16 ` Ethan Benson
2002-03-28 16:20 ` Hollis Blanchard
2002-03-28 9:19 ` Geert Uytterhoeven
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=E16qUJT-0000An-00@piglet.grunz.lu \
--to=mlan@cpu.lu \
--cc=dan_bethe@yahoo.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).