On Mon, May 31, 2010 at 9:33 PM, Valent Turkovic
<valent.turkovic(a)gmail.com> wrote:
On Mon, May 31, 2010 at 1:42 PM, Jasper Hartline
<jasper.hartline(a)gmail.com> wrote:
> The bug you just tried to hijack is related to the Anaconda installer,
> and kickstart files used for it. Not livecd-tools or livecd-creator.
> livecd-creator is tied heavily to Ext3 currently, and unless you are
> willing to write patches currently
> there is no quick fix to use BTRFS on the LiveCD, LiveCD is SquashFS
> anyways, the only part which is
> added which has a usable filesystem is the COW Ext3 in an overlay file
> which is created when using livecd-iso-to-disk
>
> Anaconda and livecd-creator or two different things.
Thank you for your explanation and quick reply, I just tested LiveUSB
image od Meego 1.0 that is based on Fedora and uses btrfs fs iso
image. How have they made it?
From what I understand, they are using a forked version of
livecd-creator. Here (and generally in their GIT repos) are the
sources:
http://meego.gitorious.org/meego-developer-tools/image-creator
I haven't looked at the changes they made, though.
Is anybody from Fedora/RedHat in contact with Meego team and knows
how they managed to create btrfs liveusb image it that function is not
currently build into Fedora 13's Anaconda installer.
I think the Mini SIG is the closest there. However, for image creation
this should be the right place here already.
--Sebastian
>From what I have seen they also use anaconda because it looks
almost
the same, with some minor UI changes.
--
livecd mailing list
livecd(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/livecd