From: Chris Fowler <cfowler@outpostsentinel.com>
To: linux-mtd@lists.infradead.org
Subject: Update on my problem
Date: Thu, 21 Feb 2002 08:03:38 -0500 [thread overview]
Message-ID: <200202211355.g1LDtdL04701@skylab.outpostsentinel.com> (raw)
Many of you guys lately has been halping overcome some issues I've been having during an initrd execution. I appreciate the efforts. I'm eamiling you to inform you what I did to fix it in case you ever run into the same problem.
I have to compile my linuxrc.c program statically. lib-c is just too big to place on a initrd image. To keep the size down from 400k I used a program called diet. It bacsically executes gcc and use some of its own libraries. My loader
went from 400k to 22k using it. This allowed me to stuff more program on the initrd image. I ran into some major problems using zlib and this program so I wnet back to a normal static binary. My loader is now 400k but seems to
be working great. I can download software packages form the network and use those as my roofs just as easy as the package on flash. I can also restore a backup package that the user has the option to create at flash time.
It appears to be working great.
Thanks for all your help.
Chris
next reply other threads:[~2002-02-21 12:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 13:03 Chris Fowler [this message]
2002-02-21 14:05 ` jffs2_scan_make_ino_cache() in scan.c very slow Joakim Tjernlund
2002-02-21 14:18 ` David Woodhouse
2002-02-21 14:34 ` Joakim Tjernlund
2002-02-21 15:34 ` Joakim Tjernlund
2002-02-21 15:47 ` David Woodhouse
2002-02-21 16:14 ` Joakim Tjernlund
2002-02-21 21:58 ` Thomas Gleixner
2002-02-21 22:05 ` Joakim Tjernlund
2002-02-21 22:22 ` Thomas Gleixner
2002-02-21 22:27 ` Joakim Tjernlund
2002-02-21 22:44 ` Thomas Gleixner
2002-02-21 22:49 ` Joakim Tjernlund
2002-02-21 22:43 ` jffs2_scan_make_ino_cache() in scan.c very slow, new improvment Joakim Tjernlund
2002-02-22 10:56 ` Joakim Tjernlund
2002-02-21 19:27 ` Update on my problem Russ Dill
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=200202211355.g1LDtdL04701@skylab.outpostsentinel.com \
--to=cfowler@outpostsentinel.com \
--cc=linux-mtd@lists.infradead.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