From: Matt Mackall <mpm@selenic.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1-rc1-tiny1 tree for small systems
Date: Sun, 4 Jan 2004 02:40:05 -0600 [thread overview]
Message-ID: <20040104084005.GU18208@waste.org> (raw)
In-Reply-To: <m13cawi2h8.fsf@ebiederm.dsl.xmission.com>
On Sun, Jan 04, 2004 at 12:42:43AM -0700, Eric W. Biederman wrote:
> Matt Mackall <mpm@selenic.com> writes:
>
> > Contributions and suggestions are encouraged. In particular, it would
> > be helpful if people with non-x86 hardware could take a stab at
> > extending some of the stuff that's currently only been done for X86 to
> > other architectures.
>
> I just tried a kernel build with as much as possible turned off. This
> uncovered a couple of bugs, which I fixed with the attached diff. But
> it looks like there finally is a light at the end of the rainbow.
Thanks. I actually cleaned up all this stuff earlier today, will
probably do another release shortly.
> 220K compressed and 371K uncompressed. This is a serious reduction from
> previous versions. There is still a huge amount of code I can't compile
> out but this is certainly progress. Thank you.
Suggestions? I'm rapidly exhausting a lot of the obvious candidates.
My target build at the moment is ide + ext2 + proc + ipv4 + console, and
that's currently at around 800K uncompressed, booting in a little less
than 2.5MB. Hoping to get that under 2.
--
Matt Mackall : http://www.selenic.com : Linux development and consulting
next prev parent reply other threads:[~2004-01-04 8:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 3:08 2.6.1-rc1-tiny1 tree for small systems Matt Mackall
2004-01-04 7:42 ` Eric W. Biederman
2004-01-04 8:40 ` Matt Mackall [this message]
2004-01-04 16:02 ` Eric W. Biederman
2004-01-05 0:00 ` Eric W. Biederman
2004-01-05 0:34 ` viro
2004-01-05 4:34 ` Eric W. Biederman
[not found] ` <20040105170938.GY18208@waste.org>
2004-01-08 19:22 ` Eric W. Biederman
2004-01-09 20:15 ` Arnaldo Carvalho de Melo
2004-01-10 21:49 ` Matt Mackall
2004-01-08 21:04 ` bill davidsen
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=20040104084005.GU18208@waste.org \
--to=mpm@selenic.com \
--cc=ebiederm@xmission.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;
as well as URLs for NNTP newsgroup(s).