On Wed, 2004-11-17 at 03:51, Tom Allison wrote:
> my dhcpd.conf file is on another computer, so I can't use ltspadmin 
> tools to manage it.
> 
> I noticed the block:
> 
>   host ws001 {
>                  hardware ethernet     00:d0:59:39:a8:a1;
>                  fixed-address         192.168.1.200;
>                  filename              "/lts/vmlinuz-2.4.26-ltsp-2";
>              }
> 
> 
> Am I correct in assuming that in the future, any new kernels will 
> require me to change this file (vmlinux-2.4.26-ltsp-2) to point to the 
> new kernel?

I think you would be better off making the 'filename' entry global, so
you only have to change it once whenever your kernel changes.  Here's an
example for you.  Note that there are 3 filename entries for 7
workstations; one is for PXE workstations, one is for a terminal I'm
using to test a new kernel, and one is for all of the other terminals. 
Also notice that unknown terminals show up in the range
192.168.0.(200-249); I get the MAC address from the dhcp log and add it
to dhcpd.conf.

#Sample DHCP config for Tom Allison
authoritative;
deny                            bootp;
ddns-update-style               none;
default-lease-time              21600;
max-lease-time                  604800; # One week
server-name                     "server.InsertDomainHere";
option  subnet-mask             255.255.255.0;
option  broadcast-address       192.168.0.255;
option  routers                 server;
option  domain-name-servers     192.168.0.254;
option  domain-name             "InsertDomainHere";
ddns-domainname                 "InsertDomainHere";
option  option-128              code 128 = string;
option  option-129              code 129 = text;
option  option-128              e4:45:74:68:00:00; #This never changes
option  root-path               "/opt/ltsp/i386"; 

# Etherboot clients
group {
 filename                "/lts/vmlinuz-2.4.24-ltsp-4";
 host ws1 { hardware ethernet 00:04:72:73:74:75 ; fixed-address ws1; }
 host ws2 { hardware ethernet 00:D0:09:0A:0B:0C ; fixed-address ws2; }
 host ws4 { hardware ethernet 00:04:5A:5B:5C:5D ; fixed-address ws3; }
 host ws5 { hardware ethernet 00:D0:7C:7D:7E:7F ; fixed-address ws4; } 
 host ws6 { hardware ethernet 00:04:5a:5b:5c:5d ;
                      fixed-address ws5;
                      filename "/lts/vmlinuz-testing"; }
 host ws7 { hardware ethernet 00:04:5a:5b:5c:5e ; fixed-address ws6; }
}

# PXE clients
group {
 filename "/lts/2.4.24-ltsp-4/pxelinux.0" ; 
 host ws3 { hardware ethernet 90:12:02:03:04:05 ; fixed-address ws7; }
}

subnet  192.168.0.0     netmask 255.255.255.0   {
        range           192.168.0.200   192.168.0.249;
        allow   unknown-clients;
        use-host-decl-names     on;
        get-lease-hostnames     off;
        next-server             server.jacobsladdercharlotte.org;
        option  log-servers     server.jacobsladdercharlotte.org;
        #option option-129              "vga=0x301 console=/dev/tty2";
        #option option-129              "INITRD_DBG=8"  ;
}


--

David Johnston <[EMAIL PROTECTED]>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to