Weblog entry #13 for fsateler
mkdir /mnt/temp mount /dev/sda1 /mnt/temp mount --bind /dev /mnt/temp/dev mount --bind /proc /mnt/temp/proc mount --bind /sys /mnt/temp/sys chroot /mnt/temp grubWhen grub loads, I then did the following:
root (hd0,0) install /boot/grub/stage1 (hd0) /boot/grub/stage2Then rebooted, and got a grub console instead of my usual grub screen. No problem: just do
configfile (hd0,0)/boot/grub/menu.lstand the usual interface is up.
After my desktop loaded, I found the grub-install command that would do a better install than me:
grub-install /dev/sdaAnd then I had a completely normal boot screen. I just had to add the new Windows entry to menu.lst and I was set.
So there goes the ancient fear that installwing Windows after Linux is a pain. There are, of course, cases in which it is a pain (I remember once windows messed with my partition table and linux wouldn't boot), but this time I had absolutely no problems.
--
Felipe Sateler
Comments on this Entry
--
"It's Not Magic, It's Work"
Adam
[ Parent | Reply to this comment ]
It's probably simpler to run "setup" instead of "install" when you invoke grub from the Etch installer. You'd just need two commands:
root (hd0,0) setup (hd0)
That should take care of the menu as well, so you don't have to muck about in the grub console after rebooting--not that it's particularly hard to do that... but this is just a *little* easier. :-)
[ Parent | Reply to this comment ]
--------
Felipe Sateler
[ Parent | Reply to this comment ]
davide
[ Parent | Reply to this comment ]
--------
Felipe Sateler
[ Parent | Reply to this comment ]