From bkearney at redhat.com Mon Apr 6 12:44:38 2009 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 06 Apr 2009 08:44:38 -0400 Subject: [Thincrust-devel] Product Release Message-ID: <49D9F936.7040504@redhat.com> John: Sorry for the delay.. this got hung up in the filter system. If you would like to post to the list, you can subscribe at http://www.redhat.com/mailman/listinfo/thincrust-devel. As for your question. The tooling which you see here is available in Fedora, and is used to build some of the spins and other image based tooling. I can not comment to inclusion in a RHEL release, but we are looking to make this available as part of EPEL. David Huff, do you have status comments on that? Does that help answer your concerns? -- bk -------------- next part -------------- An embedded message was scrubbed... From: thincrust-devel-bounces at redhat.com Subject: Auto-discard notification Date: Thu, 02 Apr 2009 12:06:22 -0400 Size: 7659 URL: From lists at arctur.us Tue Apr 7 19:13:32 2009 From: lists at arctur.us (Mitch Skinner) Date: Tue, 07 Apr 2009 12:13:32 -0700 Subject: [Thincrust-devel] fedora 10 AMI, host key fingerprint in ec2-converter Message-ID: <49DBA5DC.9040407@arctur.us> Hello list, I've got two questions: 1. When I launch the fedora 10 ami (ami-2a5db943) listed here: http://thincrust.org/aos.html The console output says: Fedora release 10.90 (Rawhide) Did you mean for it to be Rawhide? Did y'all put together a non-Rawhide F10 AMI? 2. The EC2 documented way of getting the host key fingerprint (to avoid MITM attacks) is for rc.local on the instance to output the fingerprint on the console; then the user can view it with ec2-get-console-output. The Amazon F8 image has this in its rc.local: echo "-----BEGIN SSH HOST KEY FINGERPRINTS-----" |logger -s -t "ec2" ssh-keygen -l -f /etc/ssh/ssh_host_key.pub |logger -s -t "ec2" ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub |logger -s -t "ec2" ssh-keygen -l -f /etc/ssh/ssh_host_dsa_key.pub |logger -s -t "ec2" echo "-----END SSH HOST KEY FINGERPRINTS-----" |logger -s -t "ec2" Seems like this ought to go into ec2-converter; it looks like it would fit right into the rclocal_config method in ec2config.py. I'm not sure about the "logger" stuff, though. Regards, Mitch From sebastian at when.com Tue Apr 7 21:19:23 2009 From: sebastian at when.com (Sebastian Dziallas) Date: Tue, 07 Apr 2009 23:19:23 +0200 Subject: [Thincrust-devel] boot issues with appliance on F11 Message-ID: <49DBC35B.4020803@when.com> Hi all, we from SugarLabs have been trying to build virtual appliances and have uploaded them here: http://download.sugarlabs.org/soas/appliances/ But the most recent appliances don't seem to boot and not even to get past GRUB. This has been reported when using VirtualBox. It's a bit strange, as Bryan has confirmed being able to build a minimal F10 appliance under F10. We're using Rawhide for our build machine, though, while the appliance is based on the F11 beta state. The kickstart file is up in the Sugar on a Stick GIT repo here (we're including the base.ks and the sugar.ks, which are in the same repo): http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.ks Here's the ticket on sugarlabs.org: http://dev.sugarlabs.org/ticket/677 Any help with that would be really appreciated. Thanks & Best Regards, --Sebastian From jboggs at redhat.com Wed Apr 8 00:32:35 2009 From: jboggs at redhat.com (Joey Boggs) Date: Tue, 07 Apr 2009 20:32:35 -0400 Subject: [Thincrust-devel] boot issues with appliance on F11 In-Reply-To: <49DBC35B.4020803@when.com> References: <49DBC35B.4020803@when.com> Message-ID: <49DBF0A3.7040706@redhat.com> I've taken a quick look so far, The aos-rawide image does boot fine along with the sugar customizations to the kickstart under kvm, I'm downloading virtualbox now to test. I've downloaded the tarball with the images you've built and it contains an xml file and a vmdk disk image. What are the steps run to generate your build so we can more closely replicate the process? Sebastian Dziallas wrote: > Hi all, > > we from SugarLabs have been trying to build virtual appliances and > have uploaded them here: http://download.sugarlabs.org/soas/appliances/ > > But the most recent appliances don't seem to boot and not even to get > past GRUB. This has been reported when using VirtualBox. > > It's a bit strange, as Bryan has confirmed being able to build a > minimal F10 appliance under F10. We're using Rawhide for our build > machine, though, while the appliance is based on the F11 beta state. > > The kickstart file is up in the Sugar on a Stick GIT repo here (we're > including the base.ks and the sugar.ks, which are in the same repo): > > http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.ks > > > Here's the ticket on sugarlabs.org: http://dev.sugarlabs.org/ticket/677 > > Any help with that would be really appreciated. > > Thanks & Best Regards, > --Sebastian > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From jboggs at redhat.com Wed Apr 8 03:41:01 2009 From: jboggs at redhat.com (Joey Boggs) Date: Tue, 07 Apr 2009 23:41:01 -0400 Subject: [Thincrust-devel] boot issues with appliance on F11 In-Reply-To: <49DBF0A3.7040706@redhat.com> References: <49DBC35B.4020803@when.com> <49DBF0A3.7040706@redhat.com> Message-ID: <49DC1CCD.6010207@redhat.com> I retract my previous statement, aos-rawhide does boot fine with the original provided kickstart, using the additional customizations does produce an unbootable machine that hangs at a cursor. I'll keep working on this and try to narrow it down some more. Joey Joey Boggs wrote: > I've taken a quick look so far, The aos-rawide image does boot fine > along with the sugar customizations to the kickstart under kvm, I'm > downloading virtualbox now to test. I've downloaded the tarball with > the images you've built and it contains an xml file and a vmdk disk > image. What are the steps run to generate your build so we can more > closely replicate the process? > > > > > > Sebastian Dziallas wrote: >> Hi all, >> >> we from SugarLabs have been trying to build virtual appliances and >> have uploaded them here: http://download.sugarlabs.org/soas/appliances/ >> >> But the most recent appliances don't seem to boot and not even to get >> past GRUB. This has been reported when using VirtualBox. >> >> It's a bit strange, as Bryan has confirmed being able to build a >> minimal F10 appliance under F10. We're using Rawhide for our build >> machine, though, while the appliance is based on the F11 beta state. >> >> The kickstart file is up in the Sugar on a Stick GIT repo here (we're >> including the base.ks and the sugar.ks, which are in the same repo): >> >> http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.ks >> >> >> Here's the ticket on sugarlabs.org: http://dev.sugarlabs.org/ticket/677 >> >> Any help with that would be really appreciated. >> >> Thanks & Best Regards, >> --Sebastian >> >> _______________________________________________ >> Thincrust-devel mailing list >> Thincrust-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/thincrust-devel > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From sebastian at when.com Wed Apr 8 23:53:16 2009 From: sebastian at when.com (Sebastian Dziallas) Date: Thu, 09 Apr 2009 01:53:16 +0200 Subject: [Thincrust-devel] boot issues with appliance on F11 In-Reply-To: <49DC1CCD.6010207@redhat.com> References: <49DBC35B.4020803@when.com> <49DBF0A3.7040706@redhat.com> <49DC1CCD.6010207@redhat.com> Message-ID: <49DD38EC.2050005@when.com> Joey Boggs wrote: > I retract my previous statement, aos-rawhide does boot fine with the > original provided kickstart, using the additional customizations does > produce an unbootable machine that hangs at a cursor. I'll keep working > on this and try to narrow it down some more. Thanks a lot for looking into this! So these are our customizations which are causing it not to boot? Maybe we're really missing a package or so... Anyway, here's the python script we're using to generate the appliance: http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.py All the stuff we're using should be in that repo. --Sebastian > Joey > > Joey Boggs wrote: >> I've taken a quick look so far, The aos-rawide image does boot fine >> along with the sugar customizations to the kickstart under kvm, I'm >> downloading virtualbox now to test. I've downloaded the tarball with >> the images you've built and it contains an xml file and a vmdk disk >> image. What are the steps run to generate your build so we can more >> closely replicate the process? >> >> Sebastian Dziallas wrote: >>> Hi all, >>> >>> we from SugarLabs have been trying to build virtual appliances and >>> have uploaded them here: http://download.sugarlabs.org/soas/appliances/ >>> >>> But the most recent appliances don't seem to boot and not even to get >>> past GRUB. This has been reported when using VirtualBox. >>> >>> It's a bit strange, as Bryan has confirmed being able to build a >>> minimal F10 appliance under F10. We're using Rawhide for our build >>> machine, though, while the appliance is based on the F11 beta state. >>> >>> The kickstart file is up in the Sugar on a Stick GIT repo here (we're >>> including the base.ks and the sugar.ks, which are in the same repo): >>> >>> http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.ks >>> >>> >>> Here's the ticket on sugarlabs.org: http://dev.sugarlabs.org/ticket/677 >>> >>> Any help with that would be really appreciated. >>> >>> Thanks & Best Regards, >>> --Sebastian From jboggs at redhat.com Thu Apr 9 13:03:22 2009 From: jboggs at redhat.com (Joey Boggs) Date: Thu, 09 Apr 2009 09:03:22 -0400 Subject: [Thincrust-devel] boot issues with appliance on F11 In-Reply-To: <49DD38EC.2050005@when.com> References: <49DBC35B.4020803@when.com> <49DBF0A3.7040706@redhat.com> <49DC1CCD.6010207@redhat.com> <49DD38EC.2050005@when.com> Message-ID: <49DDF21A.6010409@redhat.com> I'm still working through the items in base.ks but it's definitely something in there, works fine when I remove everything below the packages section at the top. I've removed the 2 added init scripts and it still does it. So just working my way down the list. Sebastian Dziallas wrote: > Joey Boggs wrote: >> I retract my previous statement, aos-rawhide does boot fine with the >> original provided kickstart, using the additional customizations does >> produce an unbootable machine that hangs at a cursor. I'll keep >> working on this and try to narrow it down some more. > > Thanks a lot for looking into this! So these are our customizations > which are causing it not to boot? Maybe we're really missing a package > or so... > > Anyway, here's the python script we're using to generate the appliance: > > http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.py > > > All the stuff we're using should be in that repo. > > --Sebastian > >> Joey >> >> Joey Boggs wrote: >>> I've taken a quick look so far, The aos-rawide image does boot fine >>> along with the sugar customizations to the kickstart under kvm, I'm >>> downloading virtualbox now to test. I've downloaded the tarball with >>> the images you've built and it contains an xml file and a vmdk disk >>> image. What are the steps run to generate your build so we can more >>> closely replicate the process? >>> >>> Sebastian Dziallas wrote: >>>> Hi all, >>>> >>>> we from SugarLabs have been trying to build virtual appliances and >>>> have uploaded them here: >>>> http://download.sugarlabs.org/soas/appliances/ >>>> >>>> But the most recent appliances don't seem to boot and not even to >>>> get past GRUB. This has been reported when using VirtualBox. >>>> >>>> It's a bit strange, as Bryan has confirmed being able to build a >>>> minimal F10 appliance under F10. We're using Rawhide for our build >>>> machine, though, while the appliance is based on the F11 beta state. >>>> >>>> The kickstart file is up in the Sugar on a Stick GIT repo here >>>> (we're including the base.ks and the sugar.ks, which are in the >>>> same repo): >>>> >>>> http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.ks >>>> >>>> >>>> Here's the ticket on sugarlabs.org: >>>> http://dev.sugarlabs.org/ticket/677 >>>> >>>> Any help with that would be really appreciated. >>>> >>>> Thanks & Best Regards, >>>> --Sebastian > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From sebastian at when.com Thu Apr 9 23:16:09 2009 From: sebastian at when.com (Sebastian Dziallas) Date: Fri, 10 Apr 2009 01:16:09 +0200 Subject: [Thincrust-devel] boot issues with appliance on F11 In-Reply-To: <49DDF21A.6010409@redhat.com> References: <49DBC35B.4020803@when.com> <49DBF0A3.7040706@redhat.com> <49DC1CCD.6010207@redhat.com> <49DD38EC.2050005@when.com> <49DDF21A.6010409@redhat.com> Message-ID: <49DE81B9.4050303@when.com> Joey Boggs wrote: > I'm still working through the items in base.ks but it's definitely > something in there, works fine when I remove everything below the > packages section at the top. I've removed the 2 added init scripts and > it still does it. So just working my way down the list. Hi again, sorry, I should have really double-checked this. Really. Well, we happened to have quite a number of kickstarts for various projects around, and I started to merge those some time ago. But apparently, all the live media scripts also went into the appliance.ks (obviously, because the base.ks gets pulled in). But I don't really see a reason for this, except the fact that I seem to have had too few coffee when committing that change. So finally, I modified that appliance.ks now again to have all the stuff in one file (at least in this case). I'll go and give it a try tomorrow, and report back then as soon as possible. Sorry for the confusion and thanks again, --Sebastian > Sebastian Dziallas wrote: >> Joey Boggs wrote: >>> I retract my previous statement, aos-rawhide does boot fine with the >>> original provided kickstart, using the additional customizations does >>> produce an unbootable machine that hangs at a cursor. I'll keep >>> working on this and try to narrow it down some more. >> >> Thanks a lot for looking into this! So these are our customizations >> which are causing it not to boot? Maybe we're really missing a package >> or so... >> >> Anyway, here's the python script we're using to generate the appliance: >> >> http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.py >> >> >> All the stuff we're using should be in that repo. >> >> --Sebastian >> >>> Joey >>> >>> Joey Boggs wrote: >>>> I've taken a quick look so far, The aos-rawide image does boot fine >>>> along with the sugar customizations to the kickstart under kvm, I'm >>>> downloading virtualbox now to test. I've downloaded the tarball with >>>> the images you've built and it contains an xml file and a vmdk disk >>>> image. What are the steps run to generate your build so we can more >>>> closely replicate the process? >>>> >>>> Sebastian Dziallas wrote: >>>>> Hi all, >>>>> >>>>> we from SugarLabs have been trying to build virtual appliances and >>>>> have uploaded them here: >>>>> http://download.sugarlabs.org/soas/appliances/ >>>>> >>>>> But the most recent appliances don't seem to boot and not even to >>>>> get past GRUB. This has been reported when using VirtualBox. >>>>> >>>>> It's a bit strange, as Bryan has confirmed being able to build a >>>>> minimal F10 appliance under F10. We're using Rawhide for our build >>>>> machine, though, while the appliance is based on the F11 beta state. >>>>> >>>>> The kickstart file is up in the Sugar on a Stick GIT repo here >>>>> (we're including the base.ks and the sugar.ks, which are in the >>>>> same repo): >>>>> >>>>> http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.ks >>>>> >>>>> >>>>> Here's the ticket on sugarlabs.org: >>>>> http://dev.sugarlabs.org/ticket/677 >>>>> >>>>> Any help with that would be really appreciated. >>>>> >>>>> Thanks & Best Regards, >>>>> --Sebastian From dhuff at redhat.com Thu Apr 9 23:52:28 2009 From: dhuff at redhat.com (David Huff) Date: Thu, 09 Apr 2009 19:52:28 -0400 Subject: [Thincrust-devel] Appliance-tools F-10 update Message-ID: <49DE8A3C.3000600@redhat.com> All, bz 479875 was closed this week as WONTFIX due to a dependence on mkinitrd and issues with including an updated mkinitrd in F-10. The test rpm livecd-tools-021-1.fc10 was also un-pushed from testing because it will not be included in F-10 updates. I have also un-pushed appliance-tool-003.11-1.fc10 form updates testing b/c now has broken dep on livecd-tools-021-1.fc10. I have uploaded both rpms, as well as an updated mkinitrd, to http://thincrust.net/download/ for those who need this new rpm. The new features, specifically the ability to use the 'device' directive in ks, will be available in F11. I will also update the Wiki with instructions how to get the latest version for F-10. -D From sebastian at when.com Sat Apr 11 16:17:31 2009 From: sebastian at when.com (Sebastian Dziallas) Date: Sat, 11 Apr 2009 18:17:31 +0200 Subject: [Thincrust-devel] boot issues with appliance on F11 In-Reply-To: <49DE81B9.4050303@when.com> References: <49DBC35B.4020803@when.com> <49DBF0A3.7040706@redhat.com> <49DC1CCD.6010207@redhat.com> <49DD38EC.2050005@when.com> <49DDF21A.6010409@redhat.com> <49DE81B9.4050303@when.com> Message-ID: <49E0C29B.6000506@when.com> Replying to myself... ;) Well, it really turned out that the livecd scripts were the cause - with my most recent commits, the appliance boots now again. These scripts seem to have gotten somehow accidentally included. I built a new version and uploaded it: http://lists.sugarlabs.org/archive/sugar-devel/2009-April/013718.html Joey and Bryan, again thanks for looking into this! --Sebastian Sebastian Dziallas wrote: > Joey Boggs wrote: >> I'm still working through the items in base.ks but it's definitely >> something in there, works fine when I remove everything below the >> packages section at the top. I've removed the 2 added init scripts and >> it still does it. So just working my way down the list. > > Hi again, > > sorry, I should have really double-checked this. Really. > > Well, we happened to have quite a number of kickstarts for various > projects around, and I started to merge those some time ago. But > apparently, all the live media scripts also went into the appliance.ks > (obviously, because the base.ks gets pulled in). > > But I don't really see a reason for this, except the fact that I seem to > have had too few coffee when committing that change. So finally, I > modified that appliance.ks now again to have all the stuff in one file > (at least in this case). I'll go and give it a try tomorrow, and report > back then as soon as possible. > > Sorry for the confusion and thanks again, > --Sebastian > >> Sebastian Dziallas wrote: >>> Joey Boggs wrote: >>>> I retract my previous statement, aos-rawhide does boot fine with the >>>> original provided kickstart, using the additional customizations >>>> does produce an unbootable machine that hangs at a cursor. I'll keep >>>> working on this and try to narrow it down some more. >>> >>> Thanks a lot for looking into this! So these are our customizations >>> which are causing it not to boot? Maybe we're really missing a >>> package or so... >>> >>> Anyway, here's the python script we're using to generate the appliance: >>> >>> http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.py >>> >>> >>> All the stuff we're using should be in that repo. >>> >>> --Sebastian >>> >>>> Joey >>>> >>>> Joey Boggs wrote: >>>>> I've taken a quick look so far, The aos-rawide image does boot fine >>>>> along with the sugar customizations to the kickstart under kvm, I'm >>>>> downloading virtualbox now to test. I've downloaded the tarball >>>>> with the images you've built and it contains an xml file and a vmdk >>>>> disk image. What are the steps run to generate your build so we can >>>>> more closely replicate the process? >>>>> >>>>> Sebastian Dziallas wrote: >>>>>> Hi all, >>>>>> >>>>>> we from SugarLabs have been trying to build virtual appliances and >>>>>> have uploaded them here: >>>>>> http://download.sugarlabs.org/soas/appliances/ >>>>>> >>>>>> But the most recent appliances don't seem to boot and not even to >>>>>> get past GRUB. This has been reported when using VirtualBox. >>>>>> >>>>>> It's a bit strange, as Bryan has confirmed being able to build a >>>>>> minimal F10 appliance under F10. We're using Rawhide for our build >>>>>> machine, though, while the appliance is based on the F11 beta state. >>>>>> >>>>>> The kickstart file is up in the Sugar on a Stick GIT repo here >>>>>> (we're including the base.ks and the sugar.ks, which are in the >>>>>> same repo): >>>>>> >>>>>> http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.ks >>>>>> >>>>>> >>>>>> Here's the ticket on sugarlabs.org: >>>>>> http://dev.sugarlabs.org/ticket/677 >>>>>> >>>>>> Any help with that would be really appreciated. >>>>>> >>>>>> Thanks & Best Regards, >>>>>> --Sebastian From bkearney at redhat.com Wed Apr 15 13:00:20 2009 From: bkearney at redhat.com (Bryan Kearney) Date: Wed, 15 Apr 2009 09:00:20 -0400 Subject: [Thincrust-devel] boot issues with appliance on F11 In-Reply-To: <49E0C29B.6000506@when.com> References: <49DBC35B.4020803@when.com> <49DBF0A3.7040706@redhat.com> <49DC1CCD.6010207@redhat.com> <49DD38EC.2050005@when.com> <49DDF21A.6010409@redhat.com> <49DE81B9.4050303@when.com> <49E0C29B.6000506@when.com> Message-ID: <49E5DA64.2010706@redhat.com> Sebastian Dziallas wrote: > Replying to myself... ;) > > Well, it really turned out that the livecd scripts were the cause - with > my most recent commits, the appliance boots now again. These scripts > seem to have gotten somehow accidentally included. > > I built a new version and uploaded it: > > http://lists.sugarlabs.org/archive/sugar-devel/2009-April/013718.html > > Joey and Bryan, again thanks for looking into this! > > --Sebastian Glad to hear that it is working! -- bk > > Sebastian Dziallas wrote: >> Joey Boggs wrote: >>> I'm still working through the items in base.ks but it's definitely >>> something in there, works fine when I remove everything below the >>> packages section at the top. I've removed the 2 added init scripts >>> and it still does it. So just working my way down the list. >> >> Hi again, >> >> sorry, I should have really double-checked this. Really. >> >> Well, we happened to have quite a number of kickstarts for various >> projects around, and I started to merge those some time ago. But >> apparently, all the live media scripts also went into the appliance.ks >> (obviously, because the base.ks gets pulled in). >> >> But I don't really see a reason for this, except the fact that I seem >> to have had too few coffee when committing that change. So finally, I >> modified that appliance.ks now again to have all the stuff in one file >> (at least in this case). I'll go and give it a try tomorrow, and >> report back then as soon as possible. >> >> Sorry for the confusion and thanks again, >> --Sebastian >> >>> Sebastian Dziallas wrote: >>>> Joey Boggs wrote: >>>>> I retract my previous statement, aos-rawhide does boot fine with >>>>> the original provided kickstart, using the additional >>>>> customizations does produce an unbootable machine that hangs at a >>>>> cursor. I'll keep working on this and try to narrow it down some more. >>>> >>>> Thanks a lot for looking into this! So these are our customizations >>>> which are causing it not to boot? Maybe we're really missing a >>>> package or so... >>>> >>>> Anyway, here's the python script we're using to generate the appliance: >>>> >>>> http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.py >>>> >>>> >>>> All the stuff we're using should be in that repo. >>>> >>>> --Sebastian >>>> >>>>> Joey >>>>> >>>>> Joey Boggs wrote: >>>>>> I've taken a quick look so far, The aos-rawide image does boot >>>>>> fine along with the sugar customizations to the kickstart under >>>>>> kvm, I'm downloading virtualbox now to test. I've downloaded the >>>>>> tarball with the images you've built and it contains an xml file >>>>>> and a vmdk disk image. What are the steps run to generate your >>>>>> build so we can more closely replicate the process? >>>>>> >>>>>> Sebastian Dziallas wrote: >>>>>>> Hi all, >>>>>>> >>>>>>> we from SugarLabs have been trying to build virtual appliances >>>>>>> and have uploaded them here: >>>>>>> http://download.sugarlabs.org/soas/appliances/ >>>>>>> >>>>>>> But the most recent appliances don't seem to boot and not even to >>>>>>> get past GRUB. This has been reported when using VirtualBox. >>>>>>> >>>>>>> It's a bit strange, as Bryan has confirmed being able to build a >>>>>>> minimal F10 appliance under F10. We're using Rawhide for our >>>>>>> build machine, though, while the appliance is based on the F11 >>>>>>> beta state. >>>>>>> >>>>>>> The kickstart file is up in the Sugar on a Stick GIT repo here >>>>>>> (we're including the base.ks and the sugar.ks, which are in the >>>>>>> same repo): >>>>>>> >>>>>>> http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/appliance.ks >>>>>>> >>>>>>> >>>>>>> Here's the ticket on sugarlabs.org: >>>>>>> http://dev.sugarlabs.org/ticket/677 >>>>>>> >>>>>>> Any help with that would be really appreciated. >>>>>>> >>>>>>> Thanks & Best Regards, >>>>>>> --Sebastian > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel