From: Saul Wold <sgw@linux.intel.com>
To: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
OpenEmbedded List <openembedded-core@lists.openembedded.org>
Cc: Yocto Discussion <yocto@yoctoproject.org>
Subject: Deprecating hddimg/isoimg
Date: Tue, 20 Dec 2016 12:23:27 -0800 [thread overview]
Message-ID: <1482265407.12532.55.camel@linux.intel.com> (raw)
Folks,
For years we have wanted to get rid of the hddimg/iso type, we now have
the WIC tool integrated into OE-Core such that we can build properly
partitioned disk images.
Historically the hddimg was a single FAT filesystem that contained
boot-loader, the kernel and a rootfs.img file for booting Intel Arch
machines. This has a 4G limit due to the FAT limitations and we are
starting to see this limit hit more frequently.
Are there any other usages out there that we are not aware of?
Any reasons that this should not get deprecated at this time?
Sau!
next reply other threads:[~2016-12-20 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 20:23 Saul Wold [this message]
2016-12-20 21:10 ` [Openembedded-architecture] Deprecating hddimg/isoimg Mark Hatle
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=1482265407.12532.55.camel@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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