Robert Jakubowski wrote: > > So there are two entries for SuSE because it found two different > > initrds. Unless both are really links to the same file? > > > > Yes, it is a link. Ok, that's a bug, it should notice links. > > The logs show that os-prober worked and found all OSes, including Fedora > > and Red Hat 8. It was unable to find a way to boot Fedora and RH8 though > > so they did not get onto the menu. Possibly it was unable to parse the > > fstab files, so can you send the /etc/fstab's from the Fedora and RH8 > > systems? > > > > The files are attached. I am guessing now, but maybe it matters that my > Fedora doesn't have a link /boot/vmlinuz -> /boot/vmlinuz-x.y.z. Ah, it's as I thought, Red Hat is using disk labels in their fstab files, and the current code doesn't know what to do with them. > > Also, it seems it failed to correctly parse the grub menu.lst from your > > SuSE system, although a fallback allowed it to make it bootable anyway. > > Can you also send that file? > > I am not sure if I understand..., why would it need to parse the grub menu > from the Suse? Because it can yeild better, more informative results, than using heuristics of looking for initrds and kernels. > I also got an email from Christian Perrier who was interested in getting > more information from me. Do you somehow share whatever I send you? Or, > maybe, I should cc it to a list. Could you briefly explain how the whole > bugs solving process works or point at where I could read about it? This > is my first bug I have submitted :-). If you cc the bug report in your replies, then the information is publically available, else not. Once someone fixes the bug, you'll get a message to let you know. -- see shy jo
Attachment:
signature.asc
Description: Digital signature