3:53 p.m.
I have tried editing kickstart file so that instead of ext4 iso image
uses btrfs but this fails everytime I try it.
What am I doing wrong? Has anybody managed to create btrfs livecd
image via livecd-creator?
How? Please show me your example kickstart files.
I see that there was bug opened but now is closed:
https://bugzilla.redhat.com/show_bug.cgi?id=571910
If this is not user (mine) error this bug should be reopened,
Some more info is also on my blog:
http://kernelreloaded.blog385.com/index.php/archives/btrfs-fedora-remix/
--
pratite me na twitteru - www.twitter.com/valentt
blog: http://kernelreloaded.blog385.com
linux, anime, spirituality, windsurf, wireless, ronjenje, pametne kuće, zwave
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic, MSN: valent.turkovic(a)hotmail.com
2:24 a.m.
On Sun, May 30, 2010 at 12:47 PM, Valent Turkovic
<valent.turkovic(a)gmail.com> wrote:
So am I first person who even tried creating btrfs livecd image?
Nobody even tried?
Somebody already replied here that changing fs type in kickstart is
not enough, in imgcreate/fs.py ext* specific tools are used.
We also probably need a new name for embedded roofs image instead of
ext3fs.img (which is already wrong since ext2-4 are supported).
Alan
5:59 a.m.
On Mon, May 31, 2010 at 9:24 AM, Alan Pevec <apevec(a)gmail.com> wrote:
On Sun, May 30, 2010 at 12:47 PM, Valent Turkovic
<valent.turkovic(a)gmail.com> wrote:
> So am I first person who even tried creating btrfs livecd image?
> Nobody even tried?
Somebody already replied here that changing fs type in kickstart is
not enough, in imgcreate/fs.py ext* specific tools are used.
We also probably need a new name for embedded roofs image instead of
ext3fs.img (which is already wrong since ext2-4 are supported).
Alan
Thank you Alan for your reply.
Hmm, then I don't understand how guys in the mentioned bugzilla entry
got it working? Are they even talking about livecd btrfs in this bug -
https://bugzilla.redhat.com/show_bug.cgi?id=571910 ?
If there is a quick fix for this, please tell me what I can do and how
to edit imgcreate/fs.py so that btrfs livecd image creation works. I'm
really eaget to try btrfs via livecd image.
Cheers!
--
pratite me na twitteru - www.twitter.com/valentt
blog: http://kernelreloaded.blog385.com
linux, anime, spirituality, windsurf, wireless, ronjenje, pametne kuće, zwave
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic, MSN: valent.turkovic(a)hotmail.com
6:42 a.m.
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.
Hmm, then I don't understand how guys in the mentioned bugzilla
entry
got it working? Are they even talking about livecd btrfs in this bug -
https://bugzilla.redhat.com/show_bug.cgi?id=571910 ?
If there is a quick fix for this, please tell me what I can do and how
to edit imgcreate/fs.py so that btrfs livecd image creation works. I'm
really eaget to try btrfs via livecd image.
2:33 p.m.
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?
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.
From what I have seen they also use anaconda because it looks almost
the same, with some minor UI changes.
2:53 p.m.
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
3:43 p.m.
On Mon, May 31, 2010 at 9:53 PM, Sebastian Dziallas <sebastian(a)when.com> wrote:
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.
Hi Yi, do you have any plans to post some of your work upstream i.e. here?
If not, we'll start to cherry-pick from your repo, lots of good stuff
there, like btrfs support :)
Thanks,
Alan
> 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
9:47 a.m.
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.
Why do you think I tried to hijack a bug? What would I do with it? Who
would pay ransom for it? ;)
I honestly thought that bug report was related to livecd and not only
to anaconda, sorry.
9:04 a.m.
Hi Yi, do you have any plans to post some of your work upstream i.e.
here?
If not, we'll start to cherry-pick from your repo, lots of good stuff
there, like btrfs support :)
Thanks,
Alan
Hi Yi,
are you aware that your btrfs code is not working? I concluded that
because even if Meego 1.0 image is supposed to be btrfs it only
installs if you choose ext3 partition type anaconda during the
install. Are you aware of that bug?
Alan if you get any core from Meego into Fedora's version of
livecd-creator I'm willing to be test the code and see if it creates
valid btrfs iso images.
If these is a way to do it right now just tell me how.
Hope I can help by other means if not by coding...
5075
days inactive
5081
days old
livecd@lists.fedoraproject.org
10 comments
4 participants
participants (4)
-
Alan Pevec -
Jasper Hartline -
Sebastian Dziallas -
Valent Turkovic