[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fwd: Progress report on CodeFestAkihabara, macbook Debian installation experience


> > 
> > # apt-get install refit (when it enters past the NEW queue)
> > # gptsync /dev/sda
> > 
> > I've temporarily put refit packages on:
> > http://www.netfort.gr.jp/~dancer/tmp/20060702/
> I chrooted into /target from the second console of d-i and
> copied the deb package I got from your link.
> I the installed it and run 
> # gptsync /dev/sda
> I then installed lilo and rebooted into osx; installed
> refit inside osx and now I can succesfully dual boot.
> Thanx alot for you help.

I think parted is being clever and complying with the spec; which
means it's creating a MBR FAT(fdisk) partition table containing only
one partition. This means if you install with debian-installer, you 
have a broken FAT partition and a correct GPT partition.

At this time, calling gptsync will 'fix' the partition table.

Then, you will be able to install lilo, to the partition. Note that
you don't install lilo to MBR, because MBR doesn't mean much to
MacBook EFI; if you install to the partition, rEFIt will chain load
for you. lilo will need to read the FAT partition table, which means
GPT and FAT needs to be synced.

Also it means that partition to install lilo needs to reside on the
first 4 partitions, since FAT only has 4 primary partitions.

> BTW, the patch below is needed to avoid some warnings
> Davide
> zino@slurp:~/refit/refit-0.7$ diff -u debian/rules.orig debian/rules
> --- debian/rules.orig   2006-07-03 21:05:28.000000000 +0200
> +++ debian/rules        2006-07-04 01:28:42.000000000 +0200
> @@ -42,7 +42,7 @@
>         -$(MAKE) -C refit clean
>         -$(MAKE) -C gptsync -f Makefile.unix clean 
>         #-$(MAKE) -C gptsync -f Makefile clean 
> -       -rm gptsync/*.so gptsync/*.o gptsync/gptsync.efi
> +       -rm -f gptsync/*.so gptsync/*.o gptsync/gptsync.efi
>         dh_clean 

Thanks for the patch. However, this warning could be useful
sometimes. It is only emitted for the first-time build only. The error
is ignored with a '-' at the beginning.  For second-time build, a
warning will mean that the rm command is trying to remove something
that doesn't exist, which would be nice to know.

dancer@{debian.org,netfort.gr.jp}   Debian Project

Reply to: