On Saturday 07 April 2007 22:27:08 [EMAIL PROTECTED] wrote: > Wait, you're saying that *emerging* grub-static is repartitioning your > drive? I'm going to go out on a limb, without actually looking at the > grub ebuild, and say: no, no it's not.
Watch this: # fdisk -l /dev/hda [...] Device Boot Start End Blocks Id System /dev/hda1 * 1 7 56196 83 Linux [...] # emerge grub-static Calculating dependencies ..... ..... ..... .... done! >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) sys-boot/grub-static-0.97 to / [...] >>> sys-boot/grub-static-0.97 merged. [...] # fdisk -l /dev/hda Disk /dev/hda: 80.0 GB, 80026361856 bytes [...] Device Boot Start End Blocks Id System /dev/hda1 1 7 56196 93 Amoeba [...] Now I'm going to have to boot a CD and run fdisk to delete and re-create /dev/hda1, then chroot to the root partition and run grub to reinstall itself. > I'm not familiar with why you'd need the grub-static package, instead of > just 'USE="static" grub', I haven't thought of doing that; perhaps I should try it. I used to use grub-static a few years ago when 64-bit grub had not yet been developed, in accordance with the standard installation instructions of the time; I suppose I've just stuck with it. > ... you should duplicate the conditions under which your grub-static > package was initially built by using /etc/portage/package.*, > and then put grub-static (and not grub) in your 'world'. It turns out that 'world' does have grub-static, not grub. Sorry I was unclear about that. How would I arrange package.* to pass --usepkg to emerge? Maybe I won't have to if your suggestion works (USE=static emerge grub). -- Rgds Peter Humphrey Linux Counter 5290, Aug 93 -- [email protected] mailing list
