Thanks for your reply, just I want to ask why the DHCP is used as image server? do I have to edit the dhcpd.conf? I added two lines to the pxelinux.cfg/default to specify the image server and the image name but it didn't work too, the client still tries to use the DHCP as the image server. Thanks.
________________________________ From: [EMAIL PROTECTED] on behalf of Thomas S Whaples Sent: Tue 6/13/2006 12:21 AM To: [email protected] Subject: Re: [Sisuite-users] PXE boot problems > > since it references that... and put the kernel and initrd files in > the root of > > /tftpboot too. ... > > I never understood why must I copy the initrd and kernel files in > /tftpboot root directory, too. In fact, if the lilo.conf file says that these > files are in other path, this path is the good one and not another one. Well, here's what happens, I guess. Long-winded explanation time!!! Your node starts up, and after a little BIOS action, the little Intel Boot Agent or equivalent gains control. It does a DHCP request. The DHCP request returns some stuff: an IP address for the node, an IP address for the boot server, and a file name: "pxelinux.bin". The boot agent then proceeds to download this file from the boot server via TFTP, and then launches it as a kernel. Now you've got PXELinux running. PXELinux does some stuff, checks its IP address, and converts that into hex. Let's say it comes up with B03C0C19. It asks the boot server for several files via TFTP: /pxelinux.cfg/B03C0C19, and if that doesn't exist it looks for files named B03C0C1, B03C0C, B03C0, B03C, B03, B0, B, and default. Assume it found one of those: now it has a config file. The config file for SIS displays a message warning people that it's about to wipe their machines, gives them a menu... and the menu has several configuration sets, the default being: LABEL systemimager KERNEL kernel APPEND vga=extended initrd=initrd.img root=/dev/ram LABEL is just the name for the menu. KERNEL tells PXELinux the name of... the kernel, which is a file that it's going to get via TFTP. And notice the initrd=initrd.img in there - yep, it's another file that it needs to get via TFTP. You can change the paths, if you want to. You could do multiple kernels/initrds this way if you had to. So: it needs the files to be there in order to get them via tftp. If it's just sitting in /usr/share/systeminstaller/ somewhere, the TFTP daemon can't access them. And then there's lilo. But you're not going to be running lilo unless you're booting from disk. And if you're booting from disk, then you don't need all this tftp stuff.
<<winmail.dat>>
_______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
