Ben Green wrote:
> On Fri, 16 Jun 2006 06:30:20 +0100, toman <[EMAIL PROTECTED]> wrote:
>
>
>> Hi,
>> Does anyone know if the next-server command works in the version of
>> dhcpd that Ubuntu (dapper) uses ?
>> Let me ask it this way: what is it supposed to do, and does it actually
>> do that? I was trying to split off LTSP services from our DHCP/DNS/LTSP
>> box that I recently upgraded to Dapper. (The upgrade is a whole
>> different nightmare.)
>> After much fussing around I had to move my boot images back to my DHCP
>> server, because that seemed to be the
>> only TFTP server it would query. Ideas? This seems to work on my suse
>> machines at home.
>>
>
> The changes that made next-server NECESSARY happened somewhere in the
> development of dhcp3. It should work in older versions, and it specifies
> where a machine should look next for it's files after getting a DHCP
> lease. The dhcp3-server package in Dapper, version 3.0.3, is late enough
> to mean that the next-server bit is necessary for PXE and Etherboot to
> work. Regardless, it should do what it's meant to do in any version of
> dhcp3. There will be other dhcp packages in Dapper, just as there are in
> debian, but that's the one I can confirm does what it should.
>
> We use next-server here to mean that our one DHCP server will point our
> clients to the LTSP box for it's kernel, and not the DHCP box itself, most
> handy.
>
Well thanks, but as I said this seems to work on my suse 10.0 boxes at
home, but not on the dapper-upgraded
machine at work. I've decided it doesn't matter, as the TFTP server only
gets hit once on booting a terminal, and
I would rather have only one TFTP server up on the network.
J. Toman
_____________________________________________________________________
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
