On 16/03/07, alan c <[EMAIL PROTECTED]> wrote: > But then I installed suse into an empty partition, and suse worked > fine, but boy, did it screw up the other choices! > I have spend some hours sorting it out (limited knowledge, improving > fast). The yast boot editor was not acting consistently nor was it > allowing an easy full edit facility. It was also not apparently > possible to edit the file menu.1st directly. > > I am not very sure why this episode has been so confusing for suse > yast. Maybe there were too many kernels, or something. But the lack of > full edit facility when the chips were down was a real pain.
Might have something to do with the extra comments that Debian-based distros add into menu.lst to automagically handle kernel upgrades. Just a thought. I've never used Suse. Hwyl, Neil. -- [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.kubuntu.org/UKTeam/
