From mgoldman at redhat.com Sat Oct 8 09:03:25 2011 From: mgoldman at redhat.com (Marek Goldmann) Date: Sat, 8 Oct 2011 11:03:25 +0200 Subject: [Thincrust-devel] appliance-tools future Message-ID: Hi all, As you probably noticed - appliance-tools package is not very actively maintained these days. To be fair - there was no single commit since about two years. This needs a change. I and Dennis Gilmore are taking over the maintenance of this project because David is now pulled into different tasks. Our first task is to fix Fedora 16 compatibility issues which are pretty urgent: https://bugzilla.redhat.com/show_bug.cgi?id=744388 https://bugzilla.redhat.com/show_bug.cgi?id=744390 Thanks, onward! --Marek From slaine at slaine.org Mon Oct 10 08:59:43 2011 From: slaine at slaine.org (Glen Gray) Date: Mon, 10 Oct 2011 09:59:43 +0100 Subject: [Thincrust-devel] appliance-tools future In-Reply-To: References: Message-ID: On 8 Oct 2011, at 10:03, Marek Goldmann wrote: > Hi all, > > As you probably noticed - appliance-tools package is not very actively maintained these days. To be fair - there was no single commit since about two years. This needs a change. > > I and Dennis Gilmore are taking over the maintenance of this project because David is now pulled into different tasks. Our first task is to fix Fedora 16 compatibility issues which are pretty urgent: > > https://bugzilla.redhat.com/show_bug.cgi?id=744388 > https://bugzilla.redhat.com/show_bug.cgi?id=744390 > > Thanks, onward! Great to see, I was starting to get worried. I actively depend on appliance-tools at my employer so your work will be greatly appreciated. -- Glen Gray From Richard.Timsit at epfl.ch Mon Oct 10 09:45:56 2011 From: Richard.Timsit at epfl.ch (Richard Timsit) Date: Mon, 10 Oct 2011 11:45:56 +0200 Subject: [Thincrust-devel] appliance-tools future In-Reply-To: References: Message-ID: <4E92BED4.50903@epfl.ch> On 10/10/2011 10:59 AM, Glen Gray wrote: > On 8 Oct 2011, at 10:03, Marek Goldmann wrote: > >> Hi all, >> >> As you probably noticed - appliance-tools package is not very actively maintained these days. To be fair - there was no single commit since about two years. This needs a change. >> >> I and Dennis Gilmore are taking over the maintenance of this project because David is now pulled into different tasks. Our first task is to fix Fedora 16 compatibility issues which are pretty urgent: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=744388 >> https://bugzilla.redhat.com/show_bug.cgi?id=744390 >> >> Thanks, onward! > > > Great to see, I was starting to get worried. > > I actively depend on appliance-tools at my employer so your work will be greatly appreciated. > -- Also in my campus, your work will be greatly appreciate ;-) -- Richard Timsit EPFL DIT-TI From bkearney at redhat.com Fri Oct 14 17:16:04 2011 From: bkearney at redhat.com (Bryan Kearney) Date: Fri, 14 Oct 2011 13:16:04 -0400 Subject: [Thincrust-devel] appliance-tools future In-Reply-To: <4E92BED4.50903@epfl.ch> References: <4E92BED4.50903@epfl.ch> Message-ID: <4E986E54.3090900@redhat.com> On 10/10/2011 05:45 AM, Richard Timsit wrote: > On 10/10/2011 10:59 AM, Glen Gray wrote: >> On 8 Oct 2011, at 10:03, Marek Goldmann wrote: >> >>> Hi all, >>> >>> As you probably noticed - appliance-tools package is not very >>> actively maintained these days. To be fair - there was no single >>> commit since about two years. This needs a change. >>> >>> I and Dennis Gilmore are taking over the maintenance of this project >>> because David is now pulled into different tasks. Our first task is >>> to fix Fedora 16 compatibility issues which are pretty urgent: >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=744388 >>> https://bugzilla.redhat.com/show_bug.cgi?id=744390 >>> >>> Thanks, onward! >> >> >> Great to see, I was starting to get worried. >> >> I actively depend on appliance-tools at my employer so your work will >> be greatly appreciated. >> -- > > Also in my campus, your work will be greatly appreciate ;-) > Great news.. .thanks! -- bk From mgoldman at redhat.com Sat Oct 15 11:03:33 2011 From: mgoldman at redhat.com (Marek Goldmann) Date: Sat, 15 Oct 2011 13:03:33 +0200 Subject: [Thincrust-devel] GRUB2 support Message-ID: Hi all, This is my first attempt to add support for GRUB2 (and Fedora 16+ ultimately) to appliance-creator. It wasn't trivial unfortunately :( This is still WIP. Keep in mind that the patch requires also patching grub2, more info here: https://bugzilla.redhat.com/show_bug.cgi?id=746394 Known issues: 1. GRUB2 config file *IS NOT* generated at this time. The issue behind is that grub2-mkconfig creates grub.cfg for *host* and uses specifies loopback devices as partition roots in the grub.cfg. If you have idea how it could be done - please share with me. 2. I'm determining what version of grub is packaged only looking at the package list - I do not resolve packages from package groups specified in kickstart file. This means that if you don't have explicitly added a grub/2 package to package list - it'll be not installed. This needs to be fixed. Other questions: 1. We cannot anymore assume that any of grub executable files are installed on the host. What would be the preferred way to execute grub/2 commands? I choose following: a) try to find the executable on the host and try to use it, b) if there is no executable on the host - try to use the one from image If both of above fails - fail the build. Is that ok? 2. If we want to install grub2 on a disk - we need to have a BIOS boot partition, this means that we need to add something like this to our kickstart file: part biosboot --fstype=biosboot --size=1 --ondisk sda Question: should we generate it somehow if not provided or expect it in kickstart file? I'm currently expecting this. OK, that's all for now, please take a look at the patch and let me know what you think. TTYL --Marek -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Initial-support-for-GRUB2.patch Type: application/octet-stream Size: 9239 bytes Desc: not available URL: From mgoldman at redhat.com Mon Oct 17 16:20:09 2011 From: mgoldman at redhat.com (Marek Goldmann) Date: Mon, 17 Oct 2011 18:20:09 +0200 Subject: [Thincrust-devel] GRUB2 support In-Reply-To: References: Message-ID: I have an update, patch attached. This patch should be applied after the main one mentioned previously. This one adds support for generating grub2 configuration file. It requires the updated grub mentioned before plus an additional patch which allows to specify custom path for scanning for initrd and kernel images. See here: https://bugzilla.redhat.com/show_bug.cgi?id=746730 I've tested this so far with F15 and F16 both with or without a special /boot partition and it seems to work. What do you think? --Marek -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-Generate-grub2-configuration-file.patch Type: application/octet-stream Size: 4726 bytes Desc: not available URL: -------------- next part -------------- On 15 pa? 2011, at 13:03, Marek Goldmann wrote: > Hi all, > > This is my first attempt to add support for GRUB2 (and Fedora 16+ ultimately) to appliance-creator. It wasn't trivial unfortunately :( This is still WIP. > > Keep in mind that the patch requires also patching grub2, more info here: > > https://bugzilla.redhat.com/show_bug.cgi?id=746394 > > Known issues: > > 1. GRUB2 config file *IS NOT* generated at this time. The issue behind is that grub2-mkconfig creates grub.cfg for *host* and uses specifies loopback devices as partition roots in the grub.cfg. If you have idea how it could be done - please share with me. > > 2. I'm determining what version of grub is packaged only looking at the package list - I do not resolve packages from package groups specified in kickstart file. This means that if you don't have explicitly added a grub/2 package to package list - it'll be not installed. This needs to be fixed. > > Other questions: > > 1. We cannot anymore assume that any of grub executable files are installed on the host. What would be the preferred way to execute grub/2 commands? I choose following: > > a) try to find the executable on the host and try to use it, > b) if there is no executable on the host - try to use the one from image > > If both of above fails - fail the build. Is that ok? > > 2. If we want to install grub2 on a disk - we need to have a BIOS boot partition, this means that we need to add something like this to our kickstart file: > > part biosboot --fstype=biosboot --size=1 --ondisk sda > > Question: should we generate it somehow if not provided or expect it in kickstart file? I'm currently expecting this. > > OK, that's all for now, please take a look at the patch and let me know what you think. > > TTYL > > --Marek > > <0001-Initial-support-for-GRUB2.patch>_______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From mgoldman at redhat.com Thu Oct 20 15:52:46 2011 From: mgoldman at redhat.com (Marek Goldmann) Date: Thu, 20 Oct 2011 17:52:46 +0200 Subject: [Thincrust-devel] GRUB2 support In-Reply-To: References: Message-ID: I made a mistake and my patches are created against old ET repo. I recreated them and built appropriate RPMs: http://goldmann.fedorapeople.org/appliance-creator/ These are for F16. Please give it a shot. --Marek On 17 pa? 2011, at 18:20, Marek Goldmann wrote: > I have an update, patch attached. This patch should be applied after the main one mentioned previously. > > This one adds support for generating grub2 configuration file. It requires the updated grub mentioned before plus an additional patch which allows to specify custom path for scanning for initrd and kernel images. See here: > > https://bugzilla.redhat.com/show_bug.cgi?id=746730 > > I've tested this so far with F15 and F16 both with or without a special /boot partition and it seems to work. > > What do you think? > > --Marek > > <0002-Generate-grub2-configuration-file.patch> > > On 15 pa? 2011, at 13:03, Marek Goldmann wrote: > >> Hi all, >> >> This is my first attempt to add support for GRUB2 (and Fedora 16+ ultimately) to appliance-creator. It wasn't trivial unfortunately :( This is still WIP. >> >> Keep in mind that the patch requires also patching grub2, more info here: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=746394 >> >> Known issues: >> >> 1. GRUB2 config file *IS NOT* generated at this time. The issue behind is that grub2-mkconfig creates grub.cfg for *host* and uses specifies loopback devices as partition roots in the grub.cfg. If you have idea how it could be done - please share with me. >> >> 2. I'm determining what version of grub is packaged only looking at the package list - I do not resolve packages from package groups specified in kickstart file. This means that if you don't have explicitly added a grub/2 package to package list - it'll be not installed. This needs to be fixed. >> >> Other questions: >> >> 1. We cannot anymore assume that any of grub executable files are installed on the host. What would be the preferred way to execute grub/2 commands? I choose following: >> >> a) try to find the executable on the host and try to use it, >> b) if there is no executable on the host - try to use the one from image >> >> If both of above fails - fail the build. Is that ok? >> >> 2. If we want to install grub2 on a disk - we need to have a BIOS boot partition, this means that we need to add something like this to our kickstart file: >> >> part biosboot --fstype=biosboot --size=1 --ondisk sda >> >> Question: should we generate it somehow if not provided or expect it in kickstart file? I'm currently expecting this. >> >> OK, that's all for now, please take a look at the patch and let me know what you think. >> >> TTYL