I was the person who reported this problem on the 5th - I did come up with a
fix for it and submitted it to Jim off-list, although it appears he hasn't
connected the two events.
The problem is that the elderly dhclient that ships with the existing
ltsp_initrd_kit cannot properly parse the DHCP response from the Windows
server. This is purely a version problem, there is nothing non-standard
about what Windows DHCP is doing. I fixed this by building a new initrd
using the dhclient from the version 3.0 DHCP server.
Jim has promised to look at integrating my changes into a future
ltsp_initrd_kit. In the meantime, if anyone want the fix for this just
email me direct (I am not on the ltsp-discuss list) and I will send you
updated boot images and/or my initrd sources.
From: <[EMAIL PROTECTED]>
RE: Windows DHCP?
2002-02-20 06:48
Martin,
This very same thing happened to someone else back on Feb 5th.
I searched the mailing list archives, and unfortunately, it doesn't
look like they solved it either.
Jim McQuillan
[EMAIL PROTECTED]
On Wed, 20 Feb 2002, Martin wrote:
> Made the change as suggested... it now goes to the correct server...
BUT.... despite only
specifying the "Root Path" as below, the client tries to mount
/opt/ltsp/i386000.
> I've tried putting it in quotes and various other things, but it always
appends "000" to
the end! Has anyone else seen anything similar?
> Am pulling my hair out now - windows - argh!
From: Abraham Pearson <[EMAIL PROTECTED]>
RE: Windows DHCP?
2002-02-20 08:27
We have the same problem here, I never got around to asking if it could be
fixed.
We're just living with the three zero's . I changed the name of the nfs
directory to match what the
DHCP clients ask for - in our case ltsp3000. Let me know if anyone figures
this one out.
_____________________________________________________________________
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.openprojects.net
