I have installed ltsp-4.1.1 with USE="nas", but nasd was not installed in the thin client tree (at /opt/ltsp-4.1.1/i386). Portage downloads many ltsp* files, including one called ltsp_nasd-1.2-0-i386.tgz, but this doesn't contain nasd, so perhaps this is a problem with the ltsp-4.1.1 distribution. A simple workaround is to copy the nasd file from ltsp-4.1, which was contained in the file ltsp_nasd-1.1-0-i386.tgz. Reproducible: Always Steps to Reproduce: 1. 2. 3.
nasd is the server, is this really required on the workstation?
Yes. Whilst the files that the ltsp package installs are on the server they are mostly in the /opt/ltsp-4.1.1/i386 directory that is exported to the thin clients. I.E. they are the thin clients' operating system, and it is here that nasd should also be installed so that the terminals can run it.
Yeah, i know how ltsp works, but i don't know how nas works. Why do the clients need to run the server?
It is the same idea as with X. The terminals run the server program, and applications connect to it to send some sound.
I've run into this problem also. As for the question in comment 3, the ltsp client needs to run the nas server (nasd) which then controls the soundcard on the ltsp client. Applications that are run on the ltsp server need to use a nas output (plugin) instead of an oss output (plugin) or an alsa output (plugin), either of which would control the soundcard on the ltsp server. The nas output (plugin) then connects to the nas server (nasd) that is running on the ltsp client and thus sound can be heard on the ltsp clients.
Re-assign wrt Bug 23545, maintainer retired.
antarus@kyoto ~/code/pkgcore/bin $ ./pquery --revdep=net-misc/ltsp antarus@kyoto ~/code/pkgcore/bin $ old
Alec needs to follow his own friggin guidelines; adding maintainer-needed to cc.
package.masked for security bug 142661.
(Proxy) Maintainer changed. Warwick, your turn now.
*** Bug 179701 has been marked as a duplicate of this bug. ***
Hmm, old package. Not in tree anymore. Please see: bug #177580 - ltsp-5
