hi: the "boot.img" comes from dhcp server. my dhcp server is also a bootp server, when mkd 9.0 install via dhcp, it accepts that information also, so it try to locate "boot.img" :( now i know why. sorry for wasting everybody's time....
Regards, tbsky > sorry i didn't test it much, since i thought it's easy to reproduce. > now more information below: > i found if i use "static ip" (eg: type ip myself), then everything > is fine(i can install!!). command "ps" shows: > runinstall2 --method ftp > but if i use "dhcp", then a terrible thing happen. command "ps" > can not show full command line, so i "cat /proc/9/cmdline", and get > runinstall2 --method ftp --kickstart boot.img > now we found where boot.img come from.. but i don't know why.. > maybe now u can reproduce it. > in my case it is caused by using "dhcp".. > my dhcp server is mandrake 8.2(with all errta update) > Regards, > tbsky >> > Guillaume Cottenceau <[EMAIL PROTECTED]> writes: >> > >> >> > * found network config file /tmp/ifcfg-eth0 >> >> > * found network config file /etc/resolv.conf >> >> > * getFile boot.img: >> >> > * errOpeningFile boot.img >> >> > * warning: Error reading fle boot.img at >> >> > /usr/bin/perl-install/install-any.pm line 909. >> >> >> >> Pixel, any idea? >> > >> > no really none. >> > >> > can you give /proc/cmdline during install? >> >> cat /proc/cmdline >> initrd=network.rdz ramdisk_size=32000 root=/dev/ram3 vga=788 >> BOOT_IMAGE=vmlinuz i think it's easy to reproduce? >> or it's only my own problem? > > well you are the only one reporting this bug! > > can you also check runinstall2 cmdline during install (use "ps" and > give line containing runinstall2)
