| 1 |
On 10/13/07, Volker Armin Hemmann <volker.armin.hemmann@××××××××××××.de> |
| 2 |
wrote: |
| 3 |
> |
| 4 |
> On Sonntag, 14. Oktober 2007, Kevin O'Gorman wrote: |
| 5 |
> > I see that building a kernel ends with checking for "update-grub", which |
| 6 |
> I |
| 7 |
> > don't have. Should I? Where does it come from? |
| 8 |
> |
| 9 |
> I don't know. I see that message too. Every single time. And so far I have |
| 10 |
> had |
| 11 |
> no problems caused by the lack of it. |
| 12 |
> -- |
| 13 |
> gentoo-user@g.o mailing list |
| 14 |
> |
| 15 |
> |
| 16 |
From: |
| 17 |
http://www.fifi.org/cgi-bin/man2html/usr/share/man/man8/update-grub.8.gz |
| 18 |
NAME update-grub - program to generate GRUB's menu.lst file SYNOPSIS * |
| 19 |
update-grub* DESCRIPTION *update-grub* is a program used to generate the * |
| 20 |
menu.lst* file used by the grub bootloader. It works by looking in |
| 21 |
*/boot*for all files which start with " |
| 22 |
*vmlinuz-*". They will be treated as kernels, and grub menu entries will be |
| 23 |
created for each. It will also create the initial *menu.lst* if none exists, |
| 24 |
after prompting the user. It will also add initrd lines for ramdisk images |
| 25 |
found with the same version as kernels found. e.g. /boot/vmlinuz-2.4.5 and |
| 26 |
/boot/initrd-2.4.5 will cause a line of "initrd=/boot/initrd-2.4.5 or |
| 27 |
simliar to be added for the kernel entry in the menu.lst. |
| 28 |
|
| 29 |
|
| 30 |
|
| 31 |
----- |
| 32 |
|
| 33 |
And no, you don't need it. Writing and maintaining your own menu.lst ( |
| 34 |
grub.conf) works just fine. |
| 35 |
|
| 36 |
-- |
| 37 |
- Mark Shields |
Archives