From: "Mihir Sevak" <mihir.sevak@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] beginner's question
Date: Thu, 28 Sep 2006 16:42:43 -0400 [thread overview]
Message-ID: <48fcf8860609281342o7d359eedu390487772be390f3@mail.gmail.com> (raw)
Hello everyone,
I am very very very new to embedded linux. And i read gentoo
documentation about creating embedded linux. It gave me a very good
guide line and i am very much thankful of whole gentoo embedded team
for the same.
I have a project in which i have to create embedded linux on 64MB.
Gentoo embedded guideline gives me a very good start but it needs
around 1.5 to 2 GB memory. Unfortunately i don't have that much space.
Would you please guide me how to address this issue ???
I read about qemu-img command. If i use that command and create
an image of 64M then will it occupy only 64MB space on real flash or
it will extract itself to occupy more space??
I really appreciate your help in advance.
--
"How can anything be impossible when impossible itself says I M Possible???"
Mihir
--
gentoo-embedded@gentoo.org mailing list
reply other threads:[~2006-09-28 20:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48fcf8860609281342o7d359eedu390487772be390f3@mail.gmail.com \
--to=mihir.sevak@gmail.com \
--cc=gentoo-embedded@lists.gentoo.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