From: David Relson <relson@osagesoftware.com>
To: gentoo-embedded@lists.gentoo.org <gentoo-embedded@lists.gentoo.org>
Subject: [gentoo-embedded] disk image question
Date: Mon, 8 Feb 2010 19:26:18 -0500 [thread overview]
Message-ID: <20100208192618.671473e0@osage.osagesoftware.com> (raw)
Hello,
I'm working with PC/104 cards with vortex86 and vortex86sx SOCs. So far
the project has been using large 1GB DOM (disk-on-modules), but it's
now time to prepare for installation to 32MB and 128MB DOMs.
I've not done this kind of thing before, so have invented a scheme.
Hopefully it makes sense, but I thought I'd ask those of you with more
experience...
My current plan is to create 32MB and 128MB images (using a USB
flash drive) and put them on a bootable USB drive which will
allow the installlation procedure to use dd to program the embedded
DOMs. I'm planning on partitioning the DOM as 1/8 DOS (formatted msdos)
and 7/8 linux (formatted ext2), populating the partitions from my
workstation, using dd to preserve the images, then putting the two
images on the install flash drive.
Does this make sense? Is there a better way to create the 2
differently sized install images and package them for installation?
Thanks!
David
reply other threads:[~2010-02-09 1:28 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=20100208192618.671473e0@osage.osagesoftware.com \
--to=relson@osagesoftware.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