On Saturday 10 September 2005 14:35, john bartee wrote:
Carl, I will give that a go. I was not denigrating the product only letting the list know that the Release Candidate would not install for me -- which is a big deal if this is getting ready for prime time. I have never had any issues nor had to use such a manual kludge to install any of the many SUSE installations I have done over the years (maybe I am just lucky). I apologize for any sloppy reporting and will provide more precise diagnosis in the future.
Hi John, It's only a "big deal" if it fails to install on a 'typical' newcomer's system... you know, M$haft eating up a single drive and, maybe, a new second drive installed for Linux. Most people with multiple OS's and many partitions on their systems are presumed, I think, to know how to deal with hiccups. The boot loader configuration module isn't sentient :-) much less perfect... so when it gets confused, you've got to be prepared to intervene. That's why I always check it before committing any changes. And the fact that neither of us has to do that very often is a testament to the ingenuity of everyone at SUSE. Also, I left out a couple of important points in case you are new to Grub. It starts counting at '0' and defaults to omitting /dev/hdb (presumed optical.) Example "grub speak": /dev/hda1 = hd0,0 /dev/hda2 = hd0,1 /dev/hda3 = hd0,2 ... /dev/hdc1 = hd1,0 /dev/hdc2 = hd1,1 /dev/hdc3 = hd1,2 and so on. So, if you see the directive "kernel (hd3,4)/boot/vmlinuz" in Grub's menu.lst (which resides in /boot/grub/) it is pointing to a Linux system installed on /dev/hde4. If you mount /dev/hde4 and don't see a /boot directory containing the files initrd or vmlinuz, you know that menu.lst entry is bogus. hth & regards, - Carl