Alexander De Sousa wrote:
On Sat, Jan 31, 2009 at 9:16 PM, Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar <mailto:vmlinuz386@yahoo.com.ar>> wrote:
Hi, OK Now the problem is solved, i see a grub-install parameter useful :)
--grub-shell=FILE, with this override the use of the problematic /sbin/grub.
1) No chroot is needed. 2) Now the correct grub is installed at MBR/BOOT not the grub-gfx ;)
Patch is attached
-- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar <http://www.djgera.com.ar/> KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
--- setup.orig 2009-01-31 18:12:15.000000000 -0200 +++ setup 2009-01-31 18:12:51.000000000 -0200 @@ -1081,7 +1081,7 @@ DIALOG --msgbox "GRUB root and setup devices could not be auto-located. You will need to manually run the GRUB shell to install a bootloader." 0 0 return 1 fi - $DESTDIR/sbin/grub-install --recheck --root-directory=$DESTDIR $ROOTDEV >/tmp/grub.log 2>&1 + $DESTDIR/sbin/grub-install --recheck --grub-shell=$DESTDIR/sbin/grub --root-directory=$DESTDIR $ROOTDEV >/tmp/grub.log 2>&1 cat /tmp/grub.log >$LOG # unfreeze xfs filesystems if [ -x /usr/sbin/xfs_freeze ]; then
That's it! That way grub is installed instead of grub-gfx, so... there is no other problem regarding GRUB, right? As the grub package available in the core repository is already patched to suport ext4 and big inode size.
Anyway, that chroot line didn't work :(. But there you don't have to worry about it, use the --grub-shell parameter and everything will be ok.
-- Alexander Yes!, No other relevant problem for GRUB here. But maybe, a good choice, is that the final ISO (x86_64) include a patched grub-gfx (-11 revision) for rescue and other purposes.
-- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D