Hendrik Boom wrote: > I have two different Debian systems on my EEEPC -- stable and testing. > > Whenever testing installs a new kernel as a result of the routing update, > my grub/menu.list file gets rewritten. WHen it does this, it matches the > kernels I have in one Debian sysstem with the fie-system root I have in > the other.
This is a little confusing. Are you saying that you are sharing one /boot directory with two different systems? Or something different. > I have to hand-edit menu.list to make things right again, > using static boot stanzas in front of the AUTOMAGIC KERNEL LIST. > > (a) Is there any way I can stop this misbehaviour? In Squeeze the update-grub script is called due to the script located in /etc/kernel/postinst.d/zz-update-grub (previously from the config file /etc/kernel-img.conf) where it calls update-grub. If you can determine the customization needed for your situation then you should be able to edit that file and make modifications there. The grub-legacy /usr/sbin/update-grub script is a text shell script. By reading through what it does there you should be able to understand what is happening and therefore how to deal with it. Your description confuses me because update-grub looks in /boot for existing kernels. But you say that it is the wrong list. That implies to me that you have /boot mounted from the wrong system. In any case, perhaps I should say "worst case", it should be possible to hack on update-grub in place to do what you want. > (b) If I were to progress to grub2, where I gather I can't take control > of the boot process by editing menu.lst, is there some other way of > making sure things go right? I fear that one of these years, upgrading > to grub2 will become inevitable. The grub2 uses a process that assembles parts from here and there together into the resulting /boot/grub/grub.cfg file. That file is effectively read-only since it is assembled from parts located elsewhere. Those parts take pieces from /etc/default/grub where most configuration is expected to be performed and inserted into template files located in /etc/grub.d/* files. Configuration can mostly be done by tweaking variables in /etc/default/grub. Worst case is that the template files in /etc/grub.d/* would need to be modified. The new system is definitely less transparent and more complicated than the previous one. Bob
signature.asc
Description: Digital signature
