From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0b; Windows NT 5.0) Description of problem: Upgrade from 7.1. I choosed do not intsalled Boot loader 3rd option. Because I was intalling on a dual boot machine and wanted to preserve my previous loader. It left an ubootable machine How reproducible: Didn't try Steps to Reproduce: 1.upgrade from 7.1 2. 3. Additional info:
Was the entire machine unbootable, or just the Linux partition(s)? This option is usually intended to be used by a sys-admin who will make the Linux kernel boot some other way... but if, for instance, a Windows boot-able partition is unable to boot after this upgrade, then there's a big problem.
Well, no not entire machine. Only Linux was non-bootable. However as I discussed on beta-testers mailing list, I suspected /etc/lilo.conf file was not being updated properly if "no boot loader" option is selected during installation/upgrade. It turn out I was correct. I booted with a floppy, edited /etc/lilo.conf file and run lilo -v command to update Linux Boot Sec info on NT Loader partition. Now I can boot into Linux partition
You selected no bootloader. So of course we didn't update the bootloader configuration, we didn't do *anything* to it just like you asked for