Hi Peter, Peter Stein schrieb: > Thin clients are i386 architecture. But we have multiple workstations the > clients can login via ldm and those machines should provide local device > support. Therefor they need ltspfs. The ltsp-server only provides the chroot > for booting. So it's pretty similar to your situation. Get ltspfs to work on > an amd64 machine. > That's at least a bit. - Means, I'm not alone with this task and I'm optimistic, we'll get this thing sorted out.
However, I'm not any further yet. The interesting thing is though, that
similar errors were reported in March from Etch-Users - and it sound's
as if they were using pure i386.
So possibly something is broken in the amd64 scripts somewhere? - C.f.
my next post, as I'm going to reply to the original mail from then.
Please keep me posted, if you have any success.
Thanks
Stefan.
--
Stefan U. Hegner
<[EMAIL PROTECTED]>
* * *
D-32584 Löhne --- good ole Germany
internet: http://www.hegner-web.de
* * *
GPG-Key | D9DB 51BD 2DA6 9B3A 41CB
F-Print | 0287 05A1 8D11 38BA CE91
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_____________________________________________________________________
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
