Discussion:
[Ltsp-discuss] Debian Stretch ltsp 5.5.5-1
richard kweskin
2016-01-09 10:29:28 UTC
Permalink
Hello and happy 2016 to everyone

A fresh install of Debian Stretch amd64 on the server with lxde and
then added ltsp-server-standalone and dnsmasq.

Edited /etc/dnsmasq.d/ltsp-server-dnsmasq.conf and replaced all
instances of amd64 with i386.

service dnsmasq restart

Edited /etc/ltsp/ltsp-server.conf to have ARCH=”i386” and DIST=”wheezy”

Edited /etc/ltsp/ltsp-build-client.conf to have ARCH=”i386” and
DIST=”wheezy”

aptitude update && aptitude -y full-upgrade && aptitude clean

ltsp-build-client (without parameters)

However, this last command created a chroot with a minimal wheezy i386
without xorg and without lxde. Should I not have created
/etc/ltsp/ltsp-build-client.conf?

Richard

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #
Vagrant Cascadian
2016-03-26 01:36:49 UTC
Permalink
Edited /etc/ltsp/ltsp-server.conf to have ARCH=”i386” and DIST=”wheezy”
...
ltsp-build-client (without parameters)
However, this last command created a chroot with a minimal wheezy i386
without xorg and without lxde. Should I not have created
/etc/ltsp/ltsp-build-client.conf?
I tried this with ltsp 5.5.7-1 (just uploaded to Debian), and it worked
fine for me. I used in ltsp-build-client.conf:

ARCH="i386"
DIST="wheezy"
MIRROR="http://ftp.us.debian.org/debian"

and then ran "ltsp-build-client".

Then I installed nfs-kernel-server, ran ltsp-config nfs, edited
/etc/ltsp/dhcpd.conf to use i386 (using isc-dhcp-server), and
booted. LDM came up fine, and it logged into the server a a thin client.

After installing a window manager (openbox), it worked as a fat client
as well.


So not sure if you're still having the issue, or what the issue was in
the first place, but it appears to work correctly in newer versions of
LTSP at least.


live well,
vagrant
richard kweskin
2016-03-26 15:05:31 UTC
Permalink
Post by Vagrant Cascadian
Post by richard kweskin
Edited /etc/ltsp/ltsp-server.conf to have ARCH=”i386” and
DIST=”wheezy”
...
Post by richard kweskin
ltsp-build-client (without parameters)
However, this last command created a chroot with a minimal wheezy i386
without xorg and without lxde. Should I not have created
/etc/ltsp/ltsp-build-client.conf?
I tried this with ltsp 5.5.7-1 (just uploaded to Debian), and it worked
ARCH="i386"
DIST="wheezy"
MIRROR="http://ftp.us.debian.org/debian"
and then ran "ltsp-build-client".
Then I installed nfs-kernel-server, ran ltsp-config nfs, edited
/etc/ltsp/dhcpd.conf to use i386 (using isc-dhcp-server), and
booted. LDM came up fine, and it logged into the server a a thin client.
After installing a window manager (openbox), it worked as a fat client
as well.
So not sure if you're still having the issue, or what the issue was in
the first place, but it appears to work correctly in newer versions of
LTSP at least.
live well,
vagrant
Apologies to Vagrant for having sent this to him personally. I meant
this for the list:

My issue then was that using the DIST= parameter in
ltsp-build-client.conf confused the running of "ltsp-build-client" as
Alkis suggested then (i.e. xorg was missing.) Once I removed
ltsp-build-client.conf and instead put those parameters into the
commandline the resulting "ltsp-build-client" indeed did provide xorg. I
apologise for confusing this issue with my ignorance concerning the
window manager. As both of you pointed out to me it is not needed by
thin clients and can be added for fat clients. I hadn't known that at
the time of my writing then.

However, as you now report, this issue of DIST= in
ltsp-build-client.conf seems to be no longer a problem. I will try again
soon with this newer version and report back.

Thank you once again for your continued work and support with ltsp!

Richard

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional

Loading...