As root (either via "su -" or "sudo su -" or "sudo command")
apt-get install grubThat will install grub for you onto your booting drive.
Then Debian provides you with a Nice little "menu.lst" generator that works on many levels. As long as you have "Debian based kernels" You know "linux-image" or "kernel-image" stuffs, it basically removes all problems associated with the change over.
first, remove or rename /boot/grub/menu.lst (or remove it if it is a symlink, if non-existant, no biggy)
Then run (as root)
update-grubIt'll be something like this stuff below.
king:~# update-grub\nSearching for GRUB installation directory ... found: /boot/grub\nTesting for an existing GRUB menu.list file ...\n\nCould not find /boot/grub/menu.lst file. Would you like /boot/grub/menu.lst generated for you? (y/N) y\nSearching for splash image ... none found, skipping ...\nFound kernel: /vmlinuz-2.6.15-1-k7\nFound kernel: /vmlinuz-2.6.14-1-k7\nFound kernel: /memtest86+.bin\nUpdating /boot/grub/menu.lst ... done\n\nking:~#
That is literally the whole shooting match.
There is only one issue that may come up if you are using XFS for your filesystem format on your "root partition for grub" (if only / then /. If /boot is seperate the only /boot). During the "xfs_freeze" stage of writing the journal out during the Master-Boot-Record or during the initial placing of the grub booting stages files it could go bad. This is a known problem, is fixed in the XFS code repository for the XFS kernel module, but not for "Official" Linux. There is some debate as to if the "fix" in its current form will ever make it into the Linux Tree.
--
[link|mailto:greg@gregfolkert.net|greg],
[link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @
iwetheyFreedom is not FREE.
Yeah, but 10s of Trillions of US Dollars?
SELECT * FROM scog WHERE ethics > 0;
0 rows returned.