On Sat, Aug 12, 2006 at 12:43:08PM +0930, Arthur Marsh wrote: > > I've wanted to have the automated tools to work for me, so I backed up > /boot/grub/menu.lst, then read the manual page for update-grub before > running it, observing the differences between the backed-up copy and the > automatically updated copy and seeing what needed to be tweaked. > > For instance in my > > ### BEGIN AUTOMAGIC KERNELS LIST > > ## ## Start Default Options ## > > section I have (amongst other things) > > # kopt=root=/dev/hda5 ro > # kopt_2_6_17_1_686=root=/dev/hda5 ro noisapnp > # kopt_2_6_17=root=/dev/hda5 ro noisapnp > > # memtest86=true > > which are read by update-grub (even though the line starts with #) to > rewrite menu.lst to boot the kernel with "noisapnp" in effect, and to > create the memtest grub option: > > title Debian GNU/Linux, kernel memtest86+ > root (hd0,4) > kernel /boot/memtest86+.bin > boot > I use the symlinks /boot/vmlinuz, /boot/initrd.img, /boot/vmlinuz.old and /boot/initrd.img.old to point to my current and previous kernels. These are listed in my menu.lst. Whenever I update the kernel, if /sbin/update-grub is run, it helpfully replaces those with whatever it finds. Usually, /boot/vmlinuz-2.6.8-3-k7 and the like. That is not what I want :-) Though, there seems to be no easy way of getting it recognize that it should use the symlinks, so I have just disabled running update-grub on a kernel install or upgrade. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto
Attachment:
signature.asc
Description: Digital signature