[Thincrust-devel] GRUB2 support

[Marek Goldmann]

I'm using now chroot to install GRUB2, new RPMs available here:

	http://goldmann.fedorapeople.org/bz/744390/

I've commited the code to upstream repo:

	http://git.fedorahosted.org/git/?p=appliance-tools.git

If you have any comments on the code, this is the right time. Please test it as I want to push it to Fedora ASAP.

Thanks!

--Marek

On 20 paź 2011, at 17:52, Marek Goldmann wrote:

> 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
> 
> 
> _______________________________________________
> Thincrust-devel mailing list
> Thincrust-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/thincrust-devel