>>>>> "Kirk" == Kirk Goins <[email protected]> writes:
Kirk> First I live mostly in Windows and a set of IBM hardware called Kirk> Power Systems. I am a educated 'user' not an admin on any PC Kirk> based OS so here goes my story. Kirk> I was able to boot from the CD and then poke around on the hard Kirk> disk. With help from the list here I found the file Kirk> /boot/grub/grub.cfg. Never did find the suggested menu.lst I Kirk> believe someone mentioned. This files first line is DO NOT EDIT Kirk> this file. I made a backup and then edited away. There are many Kirk> groups starting with menuentry and ending with a } . I removed Kirk> the 2 sets referring to the -39 kernel and saved the the Kirk> file. The system now boots. If I run update-grub it would read Kirk> the folder with the boot images and would put the -39 entries Kirk> back in. So for now I I have deleted all the files from the Kirk> /boot that had the -39 in the name then reran update-grub and Kirk> all is well or at least back to working. Kirk> Still having a problem finding the actual parm(s) to set so grub Kirk> will pause a few seconds on boot before starting the Kirk> default. Maybe I will bring it to the clinic next weekend. I believe the filename confusion is a result of difference between GRUB1 and GRUB2. GRUB2 changed the configuration a bit. The file you changed is built automatically from other information. The warning you saw was as follows: # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub Update-grub (or update-grub2) will (I think) look for available kernels in /boot and build boot options out of them. I wonder if you might have run out of disk space during an update? -- Russell Senior, President [email protected] _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
