Gerardo Exequiel Pozzi wrote:
Allan McRae wrote:
Gerhard Brauer wrote:
Am Sat, 31 Jan 2009 20:23:34 +1000 schrieb Allan McRae <allan@archlinux.org>:
Would it be a good idea to move grub-gfx to [extra] if it is being used on the installer?
Hmm, abstain... First i wonder that we use a community package on/for installation sources, but it's only the grub-gfx package. So i have no problem belong this to community at all. (I also thought about maintaining a separate grub-gfx only for archiso...). I see the problem mainly on our testing procedure: this behavior must have be detected earlier - and not from a "beta tester"(Thanks Gerardo!), WE have had to detect this.... (I detect it on i686 and initiate that this got fixed. Myself (only i686) don't look if x86_64 was rebuild also....
Can someone clarify what package the grub being installed onto the users system is? From the problems here, I am getting the impression that it is the grub-gfx package.
Allan
Hi
In resume: * The package installed at: the root-fs of ISO is grub-gfx. the root of new user system $DESTDIR is grub, but... the MBR/BOOT of the new system is grub-gfx because $DESTDIR/sbin/grub-install (script) uses /sbin/grub (bin) and not $DESTDIR/sbin/grub (bin)
* Under x86_64 grub-gfx fails in ext2/3/4 FS since don't have latest patches that the i686 version have.
May be, a chroot to $DESTDIR and install grub from here with grub-install, or use the old method from 2008.06 that uses grub binary directly. Or another solution.
Thanks for the clarification. I was concerned about grub-gfx being installed to peoples systems by default but had not realized that this was because of a bug. Allan