On Wednesday 02 February 2005 13:07, Lanman wrote:
SNIP
> So, I guess the next question is how can I accomplish this? I'm finding
> a lot of info on how to configure PXE, but none of it seems to have a
> clear (ie; Plan English) explanation on how to do it step-by-step, and
> nothing I've found shows me how to launch an install command in the
> process.
>
> Any help you might be able to offer would be greatly appreciated.
Best show by example.
I use PXE to boot drakTermServ for my MythTV frontend.
Here is my setup
On DHCP server
/etc/dhcpcd.conf
#########
server-identifier jennings;
default-lease-time 36000;
max-lease-time 144000;
#ddns-update-style ad-hoc;
ddns-update-style none;
option etherboot-signature code 128 = string;
option kernel-parameters code 129 = text;
not authoritative;
subnet 192.168.1.0 netmask 255.255.255.0{
range 192.168.1.48 192.168.1.59;
option domain-name "localdomain";
option domain-name-servers 192.168.1.251;
option nis-servers 192.168.1.251;
option lpr-servers 192.168.1.251;
option netbios-name-servers 192.168.1.251;
option routers 192.168.1.251;
option subnet-mask 255.255.255.0;
option time-servers 192.168.1.251;
}
# Include client machine configurations
include "/etc/dhcpd.conf.etherboot.clients";
#############
in /etc/dhcpd.conf.etherboot.clients
###########
host myth1 {
hardware ethernet 00:40:63:d8:b8:65;
next-server 192.168.1.47;
fixed-address 192.168.1.55;
#type fat;
if substring (option vendor-class-identifier, 0, 9) = "PXEClient"
{
filename "via-rhine.zimg.pxe";
}
else if substring (option vendor-class-identifier, 0, 9) = "Etherboot"
{
option etherboot-signature E4:45:74:68:00:00;
option kernel-parameters "nofloppy ";
filename "boot-via-rhine.2.6.8.1-12mdk.nbi";
}
#hdw_config true;
}
#####################
Notes:
These two files do not have to be cascaded to together. That is just how
drakTermServ sets it up.
My file checks the MAC address of the client, and if it matches it gives a
fixed IP address and tells the client the IP address of the tftp server
(192.168.1.47) The tftp server can be the same host as the DHCP server if
you like.
When the PXE client connects to the DHCP server it identifies itself as
"PXEClient", the server then tells it to get the initial boot file
"via-rhine.zimg.pxe". This file has a driver for via-rhine and a bootloader.
drakTermServ created this file for me. Alternatively you could use PXElinux
as an initial bootloader. (http://syslinux.zytor.com/pxe.php)
After loading the bootloader the client will run 'Etherboot' and asks for a
DHCP address again this time identifying itself as "Etherboot". This time the
DHCP server tells it to get "boot-via-rhine.2.6.8.1-12mdk.nbi" which is a
boot image of a 2.6.8.1 kernel with via_rhine driver. drakTermServ created
this image for me. You can create your own images quite easily, but the
method has slipped my mind for the moment.
The tftp server is easy to set up. just install it and put the files to serve
in
/var/lib/tftpboot
I found this article very useful when learning about PXE Its worth reading all
the way through.
http://www.viaarena.com/Default.aspx?PageID=5&ArticleID=52
HTH
derek
--
www.jennings.homelinux.net
http://twiki.mdklinuxfaq.org
____________________________________________________
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
____________________________________________________
