The below message seems to qualify as the testing report. The lilo problem is reported as a bug at: http://www.debian.org/Bugs/db/51/51418.html
It's not that /dev/hda should be used, but that the active partition and fixing the mbr steps were not run. I just verified it on my machine, so if I fail to respond after monday, it's because I can't boot :-) The debconf problem is reported and apparently fixed at: http://www.debian.org/Bugs/db/55/55844.html Brandon Brandon Mitchell * http://public.surfree.com/bmitch [EMAIL PROTECTED] * ICQ: 30631197 ---------- Forwarded message ---------- Date: Fri, 21 Jan 2000 14:28:55 -0500 (EST) From: [EMAIL PROTECTED] To: Brandon Mitchell <[EMAIL PROTECTED]> Subject: Customer potato report This set used the 2.2.4 boot stuff and was gen'd from a Jan 12 mirror copy. Probably you already know about this but passing it on just in case. I can't hold back on generating potato images - most customers would rather deal with these bugs in order to have it right away. +----------------------------------------------------------------------+ + Paul Wade Greenbush Technologies Corporation + + mailto:[EMAIL PROTECTED] http://www.greenbush.com/ + +----------------------------------------------------------------------+ > I was able to boot from a floppy and found out why potato can't boot > from hard disk. It was writing /etc/lilo.conf wrong: > > > boot=/dev/hda2 > > root=/dev/hda2 > > install=/boot/boot.b > > map=/boot/map > > delay=20 > > image=/vmlinuz > > label=Linux > > read-only > > The first line should be > > > boot=/dev/hda > > Right before the installation said "Next: Reboot", I went down to > "Execute Shell", edited /etc/lilo.conf, reran lilo, and then exited and > rebooted and it boots fine from the hard disk. Only other major problem > I ran into was debconf seems to have perl bugs in > > /usr/lib/perl5/Debian/DebConf/FrontEnd/Dialog.pm > > that keep it from being configured or keep other things that rely on > debconf from being configured. Oh well, so far I just installed > packages that didn't rely on debconf. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
