| 1 |
Peter Humphrey <prh@××××××××××.uk> posted |
| 2 |
200704072158.54016.prh@××××××××××.uk, excerpted below, on Sat, 07 Apr |
| 3 |
2007 21:58:53 +0100: |
| 4 |
|
| 5 |
>> The problem is that, having found problems with the 64-bit grub, I long |
| 6 |
>> ago got used to installing the 32-bit version, with "emerge --usepkg |
| 7 |
>> grub-static". That works fine, but because grub is in the world file it |
| 8 |
>> gets included in the wholesale reinstallation - but without the |
| 9 |
>> --usepkg parameter. |
| 10 |
> |
| 11 |
> What I should have finished by saying is that, after emerge grub-static, |
| 12 |
> fdisk shows the boot partition /dev/hda1 as of type 0x92, Amoeba |
| 13 |
> (whatever that is), and that Boot Magic can't recognise it and refuses |
| 14 |
> to boot through it. |
| 15 |
|
| 16 |
OK, to get some things straight. |
| 17 |
|
| 18 |
1) There is no such thing as 64-bit grub. It's 32-bit (or rather, 16- |
| 19 |
bit, but compiled with 32-bit gcc, which handles 16-bit real-mode apps |
| 20 |
like grub too). To compile grub on amd64, you need either a multilib |
| 21 |
system, or a 32-bit chroot with a 32-bit toolchain. If you are running |
| 22 |
64-bit only, you can't compile grub because it needs either a 32-bit gcc |
| 23 |
or a multilib gcc to compile. |
| 24 |
|
| 25 |
2) The package called grub-static is a 32-bit pre-compiled binary. |
| 26 |
Nothing is compiled merging it, it just merges the pre-compiled binary. |
| 27 |
Thus, --use-package in theory has little effect on it because it's pre- |
| 28 |
compiled in any case. (The exception would be if the ebuild has changed |
| 29 |
without changing the version, or if a different version would be merged |
| 30 |
without --use-package.) |
| 31 |
|
| 32 |
It would appear that loading a current grub into the boot-sector on that |
| 33 |
partition causes it to be detected as amoebafs for whatever reason. Your |
| 34 |
existing package apparently doesn't have that reason, and you can boot |
| 35 |
thru it. |
| 36 |
|
| 37 |
For the time being, I believe your fix (taking grub out of world so it |
| 38 |
doesn't try to merge) should work. |
| 39 |
|
| 40 |
However, as Jean-Marc suggests, there's little reason to chain grub thru |
| 41 |
partition-magic's boot-manager, when grub should handle booting virtually |
| 42 |
anything (including but not limited to Linux, BSD, and the various MS-DOS |
| 43 |
and MSWormOS platforms) you need to boot directly. Thus, why not install |
| 44 |
grub into the main hard drive boot sector directly, and do away with the |
| 45 |
Partition-Magic boot-manager? Then you'd be able to clear it out of the |
| 46 |
partition's boot-sector, and not need to worry about it. |
| 47 |
|
| 48 |
-- |
| 49 |
Duncan - List replies preferred. No HTML msgs. |
| 50 |
"Every nonfree program has a lord, a master -- |
| 51 |
and if you use the program, he is your master." Richard Stallman |
| 52 |
|
| 53 |
-- |
| 54 |
gentoo-amd64@g.o mailing list |
Archives