Hi folks, just spent another day playing around LTSP 5 and made some progress - for those who read quick my questions first:
-> Is there somewhere some UP-TO-DATE Documentation on LTSP 5,
especially on
- lts.conf options?
- remote sound?
-> How are the kernels updated using LTSP 5? What means of manually
trying out various client-fs kernels do I have?
And here's a brief status-report for the mail-archive (comments are
welcome):
Am Freitag, den 28.12.2007, 21:30 +0100 schrieb Stefan Ulrich Hegner:
> Biggest headache at the moment is, that the client's xserver seems to
> start but then aparently dies down in automatic boot and I get a
> text-login.
That problem was in front of the console - I had xfs-support configured
but specified the wrong server. ... too bad.
> However, could it be, that there are problems with the downloadable
> i386-client-fs for Debian/Etch from the LTSP site? (I run amd64 so I
> can't build one myself)
[some errors during boot ...]
> This makes me believe, that my client root-fs is buggy, even though it's
> an official download.
http://ltsp.mirrors.tds.net/pub/ltsp/ltsp-5.0/ltsp_debian_etch_i386-1.tar.bz2
I now strongly suppose that this client-fs is somehow buggy, especially
since I cut fix most of the problems going down another avenue:
I finally went down the long path by building my own i386 debian lenny
root-fs on amd64 using debootstrap & chroot (thanks to the debian amd64
howto this was manageable quite easy - but I had to force-install
ltsp-server due to the depend on nfs-kernel-server that could not be
installed in chroot).
Nevertheless, the supplied i386-Kernel 2.6.22-3-486 won't boot properly.
After doing some research I found that I'm not the only one encountering
this behaviour:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=458127
The next problem is, that no login is possible with ldm using this
client-fs - possibly another bug in the ltsp-package. Whenever I try to
login using ldm, I get
verifying password, please wait ...
and after 5 Min. or so ldm resets.
It took me a whole while since I'd read the remarks about the
"SCREEN_01" to "06" options in
http://wiki.debian.org/LTSP/FAQ
http://wiki.debian.org/LTSP/Upgrading_4.2
only superficially ... if it says 01-06 does conflict, that does not
mean that "SCREEN_07" conflicts, too. So having set
SCREEN_07 = startx
(and patched /usr/lib/ltsp/screen.d/startx to work with "-indirect"
instead of "-query") I'm up and running for the moment.
The Next step will be remote sound with LTSP 5.
Thanks
Stefan.
--
/ Stefan Ulrich Hegner aka "Hegi" - Loehne/ Westfalen - Germany \
| [EMAIL PROTECTED], my Cyberhome http://www.hegner-web.de|
\ GPG-Fprint D9DB 51BD 2DA6 9B3A 41CB 0287 05A1 8D11 38BA CE91 /
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
