-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/21/04 2:33 PM -0500, Doug Sutherland wrote: > Are you sure about this ... Yeah pretty much. > > the kopt way is actually less work as if you append speakup_synth > > to the kernel lines, you will need to redo it whenever you install > > a new kernel. The advantage to kopt is that when a new kernel-image > > gets installed, update-grub is automatically run and your > > speakup_synth line affects the new version. [snip] > Unlike Lilo, it is not necessary to re-run or re-install the boot > loader after every change to /boot/grub/menu.lst. menu.lst is automatically > found on GRUB's root disk and read during GRUB's boot process. The update-grub program doesn't rerun or reinstall the boot loader. It just regenerates a section of menu.lst from the kopts lines and the images found in /boot. > I don't think you need to update-grub every time you change menu-lst. > In fact, as I said earlier, I added a line for a new slackware install > before even installing slackware, and grub just worked. You don't *need* to run it, but it *will* be run the next time a kernel-image Debian package is installed and if you don't take that into account when editing the menu.lst then your changes may be wiped out. There may be a way to tell dpkg not to run update-grub when installing new kernels so you can maintain the menu.lst by hand, but this is IMHO more work. Debian seems to be more interested in automating configuration of everything, where in slackware the accepted practice is to do it by hand. To get the real power of Debian is to understand how to control it with minimum work, but retain control of what is really going on. That is why many Debian users suggest Slackware to learn on, but like using Debian once they know what's going on. There I go ranting again, sorry. - -- Clarke's Corollary: Any technology distinguishable from magic is insufficiently advanced. Thomas Stivers e-mail: stivers_t at tomass.dyndns.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAXfKs5JK61UXLur0RAhmtAJ4ylyLCwMgogVYOJPoFiOOa+Bg9UwCeMGr+ ets0dBzx2K278GmPMPna3M4= =uxIN -----END PGP SIGNATURE-----
