Differences between version 21 and predecessor to the previous major change of GrubNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 21 | Last edited on Monday, September 10, 2007 5:22:29 pm | by IanMcDonald | Revert |
| Older page: | version 20 | Last edited on Monday, September 10, 2007 5:16:12 pm | by IanMcDonald | Revert |
@@ -27,8 +27,12 @@
If that still doesn't work, it's possible that [GRUB] is looking in the wrong place for your config. If you installed [GRUB] using something like =grub-install --root-device=/boot '(hd0)'= it will install to __/boot/grub/__ etc, however if your __/boot__ is on a separate partition (as I described in the example above) then it's fairly likely that [GRUB] is looking in __/boot/boot/grub/__ for __menu.lst__ -- and not finding it.
Easiest fix (it stops this happening again in the future, so perhaps the best fix?) is to symlink __/boot__ into __/boot__ by doing =ln -s /boot /boot/=. You should now be able to cd into __/boot/boot/grub__ and it'll have your __menu.lst__ there.
+
+!! Adding a new kernel to grub
+
+If you're building your own kernels or doing KernelDevelopment then you need to manually edit the files for [grub(8)] or on many distros you can run [update-grub(8)]. One thing to note is that if you rearrange hard drives you need to edit the menu.lst file to tell it which drive is which and the kernel options before running [update-grub(8)]. The lines needed have a hash symbol in front of them which makes them look like a comment only, but they are not a comment at all!!
!! Using a different kernel for the next reboot only
<pre>
