At 22:16 13-06-2001 -0400, you wrote:
First setup dhcpd and tftpd. Copy bootnet.img to your tftp root directory. NOTE: if you have a 3Com/Lanworks NIC, you may need to run bootnet.img through the "imggen" utility. eg: mv bootnet.img tmp.img imggen -a tmp.img bootnet.img Actually, I should point out this is the ONLY way I've tried it, since I have a Lanworks NIC card. I _THINK_ other NICs don't require the use of "imggen". I think the installation gets confused, because it thinks it needs to start the network, but the network is actually already up. I don't have the exact error message right now, but I believe it's when the installation tries to send it's own DHCP request (in order to bring up the network). If I remember correctly, there might be an NFS error as well. That tells me that perhaps the network is getting restarted and the NFS mount for the root filesystem is lost. What I'd like to be able to do, is set some kind of installation method where the install files (RedHat/base/*, RedHat/RPMS/*) are already available... ie, it doesn't need to use NFS, FTP, HTTP, CD-ROM, HD to get the files, because they're already there. In other words, my NFS root can just contain the entire RedHat tree, and the installation just needs to know where to find it. If anyone has any suggestions how to get this to work, please let me know.
You say you use the bootnet.img. Shouldn't you use the boot.img disk in this case. I have never used the option, but as far as I know the installation option 'harddisk' gets its source tree from under the root tree.
Koos.
