On 2017-07-29, Barry Cisna wrote:
> Replaced Debian Jessie with Debian Stretch. In the past have always
> installed the i386 client chroot on server just to able to use older
> hardwares. This install decided to try amd64.
...
> Have used ltsp since its inception
> It's been
On 2017-05-21, Michael Pope wrote:
> I'm using LTSP under Debian 8 Jessie which I've just upgraded from
> Wheezy. The upgraded went great.
Given that Debian stretch is in the deep stages of freeze... you might
want to consider upgrading to stretch soon, and basically skip
On 2017-05-16, Sean Carte wrote:
> In /var/lib/tftpboot/ltsp/i386/lts.conf I've tried both:
>
> LDM_XSESSION=/usr/bin/lxsession -s Lubuntu -e LXDE
This is a public service announcement to the *ENTIRE INTERNET*
Please stop using LDM_XSESSION in this way.
It's just
On 2017-04-27, W Forum W wrote:
> I use LTSP 5.5.9 (Debian Stretch).
> I would like to configure NTP for all FAT Clients.
> If I use NBD image it does not take the option TIMESERVER in lts.conf
You'll need to configure lts.conf from the tftp directory, not the
client's /etc/lts.conf in the
On 2017-03-19, Prince Jeremy wrote:
> I have setup an Ubuntu server with LTSP server packages installed. Now
> I am trying to build a client for an Odroid-C2 board (ARM). I execute
> the following command from the Odroid-C2 running Ubuntu Mate 16.04.2
> LTS:
>
> $ ltsp-build-client --arch=armhf
On 2017-03-10, Michael Crider - HOEC wrote:
> We are running 64bit fat clients with Ubuntu 16.04, tied to a server
> with the same architecture and OS. We have a 32bit application that
> needs a handful of 32bit libraries to run. On a normal desktop install I
> could do "apt install
On 2017-02-22, Rolf-Werner Eilert wrote:
> Browsing the file, I wonder why there is this if-else clause with either
> pxelinux.0 OR nbi.img. I saw this on other examples in the net.
>
> On my system, I have only pxelinux.0 defined in dhcpd.conf, and there is
> no nbi.img file anywhere. So I
On 2016-12-09, Finn Andersen wrote:
> Sssd is used on the server. I'm using a fat-client, which is authenticating
> the "ltsp-way" with ldm/ssh. The kerberos ticket needs to live on the local
> machine running the fat-client image. The fat-client image doesn't have
> sssd installed. Btw I'm using
On 2016-12-07, Finn Andersen wrote:
> I'm about to install LTSP on Debian Jessie and tried to enter values into
> the configuration file /etc/ltsp/ltsp-build-client.conf, to build a
> fat-client image.
>
> I defined this variable
> FAT_CLIENT_DESKTOPS="mate-desktop-environment"
>
> But mate is
On 2016-10-04, Robert Mavrinac wrote:
> ldm was already installed in the chroot, but the client still only
> boots as a thin client.
>
> These servers normally present clients configured using the ltsp-pnp
> method. I was trying to also add special purpose clients for
> occasional programming
On 2016-09-20, Rolf-Werner Eilert wrote:
> What would be the main reason for preferring fat clients? Is fat clients
> more than just independent PCs with a complete OS which merely mount
> their $HOMEs from some kind of NAS?
In the context of LTSP, Fat Clients boot from the network and
On 2016-09-11, doyin dada wrote:
> I have Debian GNULinux 8.5 on my server.
>
>
> Kindly advise me on how I could setup my X3 Thinclients so that they could
> connect to the server.
You might want to try:
https://wiki.debian.org/LTSP/Howto
The LTSP-PNP method
On 2016-06-30, Frank Heuser wrote:
> Am 28.06.2016 19:47, schrieb Frank Heuser:
>> Hello,
>> I installed a xenial 16.4 LTSP-Server with XFCE. Most programs seem to
>> work. But I have problems with moneyplex (a homebanking software). It
>> worked flawless in LTSP under lucid 10.4 with gnome2.
On 2016-05-16, Tim wrote:
> I installed LTSP on top of Ubuntu Server 14.04. I have just about
> everything working, except I cannot sudo within the client. My user
> (mythltsp) is added to the server and is part of the sudo group on the
> server.
Up until fairly recently, the LTSP clients had
On 2016-03-26, Craig Cook wrote:
> Ubuntu 15.10 running 5.5.5~r2703+p1238+201512091628~ubuntu15.10.1 from this
> ppa:
> http://ppa.launchpad.net/ts.sch.gr/ppa/ubuntu
>
>
> /var/lib/tftpboot/ltsp/amd64/pxelinux.cfg/default shows this:
>
> # This file is regenerated when update-kernels runs.
> #
On 2016-01-09, richard kweskin wrote:
> 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
>
On 2016-02-11, William Fragakis wrote:
> A recent post prompted me to begin considering and testing a move from
> Wheezy to Jessie.
>
> Current situation is that we are running LTSP off Wheezy 64 bit (server
> has 16 gb ram).
>
> Most of our clients are Atom based - require 32 bit - so using i386
On 2016-02-08, Michael Pope wrote:
> I'm running LTSP on a Debian Wheezy server and in my Chroot area I'm
> using Debian 'testing' due to hardware compatibility for some thin
> clients in the kernel. Currently the kernel on the thin clients is 3.16
> and I would like to upgrade this to 4.3 which
On 2016-02-04, richard kweskin wrote:
> On a fresh install of Debian Stretch amd64 and subsequent updating:
...
> ltsp-build-client --dist=wheezy --arch=i386
>
> creates the desired chroot (dist and arch as asked for) which includes
> xorg but no desktop environment.
...
> My question here is
On 2016-01-23, Mahmoud Ramadan wrote:
> Thank u all...the issue has been solved by using #chmod -R 777 cups it was
> a permission issue with the configuration files causes cups to trigger
> message filter errors...but again solved with fixing the cups folder
> permissions...thanks gain...
A word
On 2016-01-20, Truth wrote:
> While everything was fine with my test-setup using Debian 8.2 (i386,
> linux-3.16) ...
> I tried to install the same ltsp-pnp server on Debian 8.2 (using
> linux-4.3 from the backports).
You'll need the backported LTSP packages from jessie-backports, and may
as
On 2015-11-03, Helmut Lichtenberg wrote:
> I updated my nbd-kernel image (Debian Jessie) to a recent kernel
> (4.2.0-0.bpo.1-586) from backports.
>
> The client stops at booting and prints out:
>
>Could not load neither overlayfs nor aufs
You need a newer version of LTSP to work with newer
On 2015-10-01, Christopher Roberts wrote:
> Apologies if my earlier email was overly brief! I started typing up a much
> longer one and then thought that my first response should be to simply ask
> if there was a specific reason why you felt that they could not be combined.
>
> At the end of the
On 2015-09-27, Mark Foley wrote:
> I would like to experiment with LTSP. Unfortunately, my distro (Slackware) is
> not one of those listed on your installation page and the reference to "If
> your
> favorite distribution is not listed below, you can also package it directly
> from
> the upstream
On 2015-09-27, Mahmoud Ramadan wrote:
> I want to configure a Cisco router as LTSP DHCP server, my configuration on
> the Cisco IOS as follows:
>
> ip dhcp pool LTSP-DHCP-Pool
> network 192.168.1.0 255.255.255.0
> bootfile pxelinux.0
> next-server 192.168.1.10
> default-router 192.168.1.1
>
On 2015-09-18, Johan Kragsterman wrote:
> I want fat clients that boots the normal PXE/TFTP/initrd way.
> BUT: I do not want the /home directory to be mounted to the LTSP
> server, but to another (nfs) server.
Specify NFS_HOME=ip.of.server:/path/to/homedir in lts.conf.
> And I do not want
On 2015-09-02, andrea biancalana wrote:
> LTSP server on Debian Stable exporting NFS Debian testing with kernel 4.1.0:
>
> fat clients doesn't boot with message: "failed to find cpu0 device node"
Not sure where *that* message is coming from; might be a red herring
unrelated to the real issue...
On 2015-09-02, Robert Mavrinac wrote:
> I have several Debian 8 LTSP_PNP servers. I tried to make a change in
> /etc/ltsp/update-kernels.conf, but discovered it isn't actually
> sourced by any other files, so the changes are not propagated when the
> image or kernels are updated.
I routinely
On 2015-09-02, Robert Mavrinac wrote:
> Yes, I'm using "ltsp-update-image --cleanup /", and I think that is
> exactly the problem. I have tested this serveral times just now, and
> it still doesn't work with the base "/".
I think the problem is in /usr/share/ltsp/cleanup.d/50-update-kernels,
as
On 2015-09-02, Robert Mavrinac wrote:
> That was it! Thank you.
Good.
> For now I will delete PXE-related files in /boot, if they exist,
> before running "ltsp-update-image --cleanup /". I tested this and it
> works as expected. I did, however, have to edit
> /etc/ltsp/update-kernels.conf to
On 2015-06-23, Robert Mavrinac wrote:
I have built a new i386 LTSP-PNP server, and inxi -G on the server yields:
Graphics: Card: Matrox Systems MGA G200eW WPCM450
Display Server: X.Org 1.16.4 drivers: mga (unloaded: fbdev,vesa)
Resolution: 1680x1050@59.88hz,
On 2015-05-15, Michael Peters wrote:
Hello I have several LTSP-PNP with Debian 8 running . I want to
convert to Master/Slave or Main/Application setup. With LTSP-PNP
there is no chroot just the image file (/opt/ltsp/images/i386.img) so
where do I put get_hosts; all guides I have seen refer
On 2015-05-07, John Hupp wrote:
I find that /etc/hosts in the fat client filesystem does not match the
/etc/hosts found in the image. It seems that LTSP must be
auto-generating one at client boot. In any case /etc/hosts in the fat
client filesystem has an alias line that resolves server
On 2015-05-02, David Burgess wrote:
I would also like to connect to an Ubuntu desktop to this server, so I
installed the ltsp-server, ldm-server and ltspfs packages. My lts.conf
looks like this:
[default]
SCREEN_06 = xfreerdp
SCREEN_07 = ldm
LDM_SERVER = slab
RDP_SERVER = citrocet
On 2015-05-01, gordon wrote:
I am using the ltsp-pnp approach with Ubuntu 14.04. I am using freerdp
1.2. How can I make usb thumbdrive redirection to work with both fat and
thin clients?
My command line currently looks like the following:
xfreerdp /f /multimon +compression
On 2015-03-25, Short, Kermit wrote:
Greetings! Every time I boot up a client off of my LTSP server, I get
a network port scan notice from our network security team indicating
that I've got an X Server Listening on my client. Does anyone know
how to do the tcp -nolisten trick (or equivalent)
On 2015-03-17, Funke, Martin wrote:
so i found the issue that causes a black screen.
I changed my lts.conf to:
SCREEN_07=rdesktop
RDP-SERVER=Server_ip
RDP_OPTIONS=”-r disk:Drive=/mnt/usb”
In /etc/fstab I added /dev/sda1 /mnt/usb auto defaults 0 0
With this I can access my data only when
On 2015-03-16, John Hupp wrote:
I want to write a script that, for my thin clients, will run a different
screen locker if the script detects that it is in an LTSP session.
The biggest problem I'm running into is testing for LTSP.
Check for the LTSP_CLIENT environment variable; it should be
On 2015-03-04, John Hupp wrote:
On 2/27/2015 10:21 PM, Vagrant Cascadian wrote:
On 2015-02-27, John Hupp wrote:
But to come to the most flagrant part of the
problem, if the user tries to unmount the drive, it produces:
Error: umount: /media/user2/usbdisk-sbd1 is not in the fstab
On 2015-03-03, Great Avenger Singh wrote:
So when we add the ssh keys, Do I have to add keys in chroot or in
root server?
ltsp-update-sshkeys is all you should need to run, which should copy the
public keys from your server and add them to the chroot's
/etc/ssh/ssh_known_hosts file. It will
On 2015-02-06, Lars Madsen wrote:
Because of the strange NBD hickups we are experiencing, where LDM some
times freezes after some time
Wow, that's really unfortunate that you're experiencing that
problem. Not sure what's different with your setup and the many other
installs that don't seem to
think there is a way to
disable the menu entirely.
live well,
vagrant
On Tuesday, March 10, 2015 7:46 PM, Vagrant Cascadian
vagr...@debian.org wrote:
On 2015-03-10, mario salcedo wrote:
I have a LTSP5 Server with Debian GNU/Linux 6.0.10 (squeeze). The
clients autologon for all
On 2015-03-11, mario salcedo wrote:
LDM_FORCE_SESSION and LDM_FORCE_LANGUAGE work cool.
But I want that my users dont reboot and shutdown thinclients.
I did
chmod 750 /sbin/shutdown
chmod 750 /opt/ltsp/i386/sbin/shutdown
But nothing. The users can shutdown or reboot the thinclient.
On 2015-03-10, mario salcedo wrote:
I have a LTSP5 Server with Debian GNU/Linux 6.0.10 (squeeze). The
clients autologon for all users. Now a new politic in my work use
Active Directory for all. I get join LTSP SERVER to Active Directory,
the users login with their credentials. My problem is
On 2015-03-10, Ivaylo Ganchev wrote:
I have a couple of classrooms administered with LTSP. For one of them, I
would need to give a choice between more than one image at startup.
Is there a proper way to do that ? I looked at the
/srv/tftp/ltsp/i386/pxelinux.cfg/default config file and I think
On 2015-02-12, Tim Johnston wrote:
ltsp-server-standalone 5.5.1-1ubuntu2
...
I have /var/lib/tftpboot/ltsp5/i386/lts.conf as:
[default]
SERVER=192.168.10.1
SCREEN_01=shell
SCREEN_02=telnet
SCREEN_03=kiosk
...
TELNET_HOST=192.168.10.1
...
screen_02 says
On 2015-02-28, Great Avenger Singh wrote:
Does the following command work fine when we use NFS with Debian?
#ltsp-update-image
There is no need to run ltsp-update-image if you are using NFS.
live well,
vagrant
signature.asc
Description: PGP signature
On 2015-02-27, John Hupp wrote:
Running LTSP-PNP (with ltspfs 1.3-1) on Lubuntu 14.04.2 i386, I'm
looking for elegant handling of flash drives. (Also music/data CD and
DVD discs, but starting with this question.) So far I'm finding this:
With the relevant lts.conf settings at default, and
On 2015-02-05, Antti Hynönen wrote:
I am using Ubuntu 14.04 ltsp-pnp but lock screen doesn't work on the clients?
If you have a really recent version of LTSP/LDM, the LDM_HASHPASS=true
option may help with that. Not sure how to re-enable locking on ubuntu,
though.
live well,
vagrant
On 2015-02-21, Michael Peters wrote:
I am ready to deploy LTSP with Lubuntu 14.04. The home directories,
DHCP, CUPS, LDAP for authentication, are all on external servers. All
works well except printing in LibreOffice on the fat client. I am
having the same issue with LTSP-PNP as well. The
On 2015-02-12, Tim Johnston wrote:
On recently upgraded Ubuntu 14.04 (trusty).
I've installed
ltsp-server-standalone 5.5.1-1ubuntu2
and done the ltsp-build client.
I have /var/lib/tftpboot/ltsp5/i386/lts.conf as:
[default]
SERVER=192.168.10.1
SCREEN_01=shell
On 2015-02-10, Takala Tuomas wrote:
I tried like this, but it doesn't work. What went wrong? How should i do it
in Finland?
TIMESERVER=pool.ntp.org
TIMESERVER=0.fi.pool.ntp.org
If your are using thin clients on an isolated LTSP-specific network, it
may not be able to route to the internet
On 2015-02-10, Rolf-Werner Eilert wrote:
Just thought that the new RasPi or the Odroid C1 might work good as LTSP
terminals. They both have 1 GB RAM, the RasPi being somewhat slower.
They might make decent thin clients, though it may take a while for the
kernel support to get upstream,
On 2015-02-10, Harry Lavender wrote:
I'm not entirely sure how BerryTerminal works, but since ARM cannot
execute x86 code (i386 build of LTSP), I'd guess that it uses LDM and
some kind of RDP mixture.
Last I looked, BerryTerminal was just a build of various LTSP software
such as LDM, ltspfs,
On 2015-02-10, Harry Lavender wrote:
The new Raspberry Pi's will make excellent thin clients. I have a guide
here for the model B+, but I will be updating it once I get round to
acquiring a new raspberry pi B2.
www.uzerp.com/blog/running-raspberry-pis-as-thin-clients-with-ubuntu-14-04-lts/
On 2015-02-04, Ivaylo Ganchev wrote:
I inherited a LTSP server and I can't understand how the auto-login part
works.
When the thin-client boots, it logs-in automaticaly.
The IP address is obtained via DHCP. The thin-clients are declared in static.
In the lts.conf there is 'LDM_AUTOLOGIN =
On 2015-01-31, Nicolas LEBRUN wrote:
I'm trying to build a ltsp-server as versatile as possible (old kernel
or not, fat or not...) because clients can be very different... We
have actually about 20 servers on Wheezy with NFS chroots with no fat.
...
And i have many questions
- NBD seems to
On 2015-01-30, Lars Madsen wrote:
Today I just noticed that on the images servered up by the production
system some services are not running. For example cron.
...
also no cron is listed in /etc/init.d/, even though it *is* in
/opt/ltsp/i386/etc/init.d in the chroot.
I also tried unpacking
On 2015-01-25, Vla wrote:
unfortunately it seems that local printing is broken in debian because
of licensing issues :-(
Printers have been supported in LTSP upstream (and in Debian) since 2007
with the introduction of jetpipe... If there are still issues with
printing support on Debian (or
the volume setting you want...
live well,
vagrant
-Ursprüngliche Nachricht-
Von: Vagrant Cascadian [mailto:vagr...@debian.org]
Gesendet: Montag, 15. Dezember 2014 19:08
An: Funke, Martin; 'LTSP (ltsp-discuss@lists.sourceforge.net)'
Betreff: Re: [Ltsp-discuss] LTSP Soundsetting
On 2014-12
On 2015-01-22, Helmut Lichtenberg wrote:
Jakub Stoppa schrieb am 22.01.2015 17:30:
Another question, where do I put logout scripts?
If you use bash aus your user's shell read 'man bash':
/etc/bash.bash.logout
The systemwide login shell cleanup file, executed when a login shell exits
On 2015-01-17, Michal Rybárik wrote:
we have been using OpenSUSE 11.3 + LTSP + XDMCP for past 4 years as
office destops, usually serving 5-7 users. Things were working well, but
accidentaly we lost server system image few months ago, and fresh server
had to be installed. We had some issues
On 2015-01-16, Edgar Kogler wrote:
Has anybody experience with HP t510 Thinclients and LTSP ? Or is it
more handy using a diskless PC (e.g. to reuse it someday later as a
Standard PC) ?
I haven't used them specifically, but reading these specs:
On 2015-01-12, Michael Pope wrote:
I'm using a fresh install of Debian testing on my server and have
install chromium and the latest firefox. I can boot a thin client in and
happily run firefox, but if I start chromium the thin client logs out
straight away. The thin client in question is a
On 2015-01-10, Jakub Stoppa wrote:
I have a new install of Edubuntu 14.04.1 64-bit running on an ESXi 5.5 U1
host. We opted to run the GNOME fallback interface since we run a number
of low spec PCs with 1 to 2 GB RAM with iterated Intel graphics (i815 and
i845).
On the ThinClients I am able
On 2014-12-28, Ivan Mincik wrote:
I am using LTSP in Fat client mode, with LDAP authentication [1]. I
see, that LDM is still using SSH tunnel for authentication.
I am wondering how hard is to authenticate directly with LDAP server
without using SSH tunnel and optionally replace LDM with
On 2014-12-18, Rolf-Werner Eilert wrote:
I would like to have an LTSP 5 alongside with an LTSP 4.2 on the same
server. Long time ago, I had this running. But I do not remember every
detail, and answers in the net are either outdated or too unfocused.
As far as I understand, the only glitch
On 2014-12-17, Ben Green wrote:
Quoting Takala Tuomas tuomas.tak...@seinajoki.fi:
I have done :
Apt-get autoremove and apt-get autoclean. Do i need ti do something else?
For the first I would recommend:
apt-get --purge autoremove
for the second:
apt-get clean
None of those are likely
On 2014-12-15, Funke, Martin wrote:
Xubuntu 14.04 + LTSP 5.5.1
i would like to start a rdp session instead of ldm. So in lts.conf I
changed SCREEN_07 from ldm to rdesktop.
So far its working but there is a little problem. The sound settings
are not loud enough.
Is there a way to tell the
On 2014-12-09, Great Avenger Singh wrote:
I feel from Vagrant words we don't need LDAP authentication anymore
for LTSP setup or I am wrong somewhere?
Well, long term proper PAM integration to be able to use LDAP, SAMBA,
*SQL, Kerberos, etc. would be better, but there are workarounds/hacks
for
On 2014-12-08, Lance Levsen wrote:
Here is the Debian way, https://wiki.debian.org/LDAP/PAM
If they're thin clients, getting it working on the server and
application servers is sufficient, if thick as well, you have to set up
NSS/PAM in their chroot too.
Not necessarily. LTSP fat clients
On 2014-12-01, Lance Levsen wrote:
Has anyone run any tests with systemd? I have concerns regarding the
nature of the beast and the amount of subsystems that are being
integrated into it.
Is this even an LTSP problem given how LTSP boots the clients?
In Debian Jessie it works fine with
On 2014-11-27, richard kweskin wrote:
On 2014-11-26 13:50, Johan Kragsterman wrote:
Anyway, what I do then is to ctrl-alt-F1, and then the connection
picks up, and I reach the console. But if I do ctrl-alt-F7 I'm back
without a signal. I believe I would get a signal if I could restart
the
On 2014-11-26, Johan Kragsterman wrote:
How is the display manager work in fat clients...?
It seems there is no local display manager...?
Both LTSP fat and thin clients use LDM, which does LTSP specific
configuration, and sets up the sshfs homedir, user account, triggers
ltspfs mounts, etc.
On 2014-11-16, Michael Pope mich...@dtcorp.com.au wrote:
Booting the thin client with the USB DVD drive connected and DVD
inserted the user can see the contents of the DVD. If I remove the DVD
and insert it again whilst logged in, the DVD does not show up in
/media/user/cdrom.
Booting with
On 2014-11-13, Michael Pope mich...@dtcorp.com.au wrote:
I'm running debian 7.6 stable as my LTSP server and I'm using shuttle
DS437's as my thin clients. I'm trying to use a USB DVD drive on my thin
client and it doesn't up in the file manager 'nautilus or thunar'.
Where have you looked in
On 2014-10-17, Jaap Winius wrote:
It appears we cannot prevent our Linux users from logging into
multiple workstations simultaneously.
Have you tried the lts.conf values:
LDM_LIMIT_ONE_SESSION
boolean, default False
Only allow a given user to log into one
On 2014-10-17, Jaap Winius wrote:
Quoting Vagrant Cascadian vagr...@debian.org:
You can get some of this sort of functionality by using xrdp on the
server, combined with either LDM's RDP support, or the
SCREEN_07=xfreerdp. ...
...
I was simply wondering if an LTSP system with thin clients
On 2014-10-03, Bruno Vane wrote:
I'm using Lubuntu 14.04, dedicated chroot.
Try this, in /var/lib/tftpboot/ltsp/youchroot/lts.conf, add in [Default]
section this line:
LDM_XSESSION=/usr/bin/lxsession -s Lubuntu -e LXDE
This is a poor fix, as you're not running /etc/X11/Xsession at all, or
all
), only changed the lts.conf.
Now I'll try Vagrant's tip.
2014-10-03 18:04 GMT-03:00 Vagrant Cascadian vagr...@debian.org:
On 2014-10-03, Bruno Vane wrote:
I'm using Lubuntu 14.04, dedicated chroot.
Try this, in /var/lib/tftpboot/ltsp/youchroot/lts.conf, add in
[Default]
section this line
On 2014-09-25 10:07:38 -0500, Mored Berdat wrote:
I follow instructions and variations given by Vagrant and the result on
client is:
http://tinypic.com/view.php?pic=21aa44ns=8
I can't see anything at that URL. Could you summarize what it says?
My conf
Debian 7 x86_64 updated
LTSP1:
On 2014-09-24 16:26:02 -0500, Bruno Vane wrote:
I'm trying to setup CUPS in Fat Client to connect to another Fat Client
with CUPS server and USB printer attached. I need to manually set
ServerName 192.168.1.X in /etc/cups/client.conf. After Fat Client reboot,
the attribute is changed to
On 2014-09-21 05:13:00 -0500, Denis Croombs wrote:
We have build 3 LTSP servers for 3 teams, 2 work perfectly ALL of the
time (different Vlans)
But 1 after approx 1 week the newest setup (max 11 users) of these
severs will be working and then if you reboot a PXE booted client
(worked
On 2014-09-19 11:23:01 -0500, Rainer Stumbaum wrote:
P.S.: Is the bug reporting system on https://bugs.launchpad.net/ltsp
actually used? I reported some bugs and patches there and did note yet
receive a response.
Yes it is used. Sorry you haven't gotten a response...
Unfortunately there
On 2014-09-14 11:16:52 -0500, Jakob Unterwurzacher wrote:
ldm now reads the full output from ssh even if it dies on the way.
Proper error messages are logged and displayed, wrapped in _() so
they can be localized.
Thanks for the (updated) patch! It's an issue that's long been a thorn
in the
On 2014-09-15 14:02:15 -0500, Robert Mavrinac wrote:
On 29/08/14 01:07 PM, Vagrant Cascadian wrote:
Looks like you need to load the overlayfs or aufs modules. It's not
uncommon for container technologies to disallow loading modules by
default, as that can compromise the security of the host
On 2014-09-10 01:47:58 -0500, Denis Croombs wrote:
We have some LTSP servers (on Xen hosts) and are trying to get sound
working are there any recommended how-to's
We are using ubuntu on the LTSP and all works perfectly so far except the
sound.
I found with at least one Ubuntu 14.04 install
On 2014-09-10 14:39:21 -0500, Denis Croombs wrote:
Hi, we have some lisp servers
Wow, Lisp! Er, LTSP. :)
and pc's pxe booting as thin long-running all apps on the ltsp server,
but when we do a vulnerability scan it tells us that it is finding an
x server on each pxe booted device iPhone
On 2014-09-10 15:10:14 -0500, Vagrant Cascadian wrote:
I haven't yet verified for myself if 6007 is open in either the default
or LDM_DIRECTX case, but will do so shortly...
Seems to be an open port with or without LDM_DIRECTX, starts up as soon
as LDM is running.
I'm not sure what *exacty* X
On 2014-09-10 14:39:21 -0500, Denis Croombs wrote:
when we do a vulnerability scan it tells us that it is finding an x
server on each pxe booted device iPhone using port 6007/tcp.
Thanks for reporting the issue, we didn't use the -nolisten tcp flag
when starting the X server. I've fixed this in
On 2014-09-08 08:41:15 -0500, Paweł Ptasznik wrote:
Yeah, thank you for your answer, but the project you have referred to
considers RPi as Fat clients. Actually, I have played a bit with @gbaman's
project and I have to admit that it works. Nonetheless, RPi Fat clients are
extremely slow,
On 2014-09-05 10:18:24 -0500, James McQuillan wrote:
If you are using Gigabit ethernet, you don't need a crossover cable.
part of the gigabit spec is to automatically sense whether the devices are
plugged into a switch or directly into another machine.
Though I've definitely encountered thin
On 2014-08-29 08:56:43 -0700, Robert Mavrinac wrote:
Are you using chroot images? That I can do. The problem with OpenVZ is
OS-level virtualization, just the same way it might be for VServer.
Obviously from the output, I'm running this on a Proxmox server.
root@server:/# ltsp-update-image
meant for this to go to the list...
On 2014-08-27 14:16:51 -0700, asmo.koski...@arkki.info wrote:
I still have to figure out where to put those host keys and how.
root@debian-ltsp-pnp:~# ls /etc/ssh
moduli sshd_config ssh_host_dsa_key.pub=20=20
ssh_host_ecdsa_key.pub
On 2014-08-20, richard kweskin wrote:
On 2014-08-17 14:23, richard kweskin wrote:
now added aptitude -R install ltsp-client
...
9 edit /etc/ltsp/update-kernels.conf to have BOOT_METHODS=NBD and add
the line IPAPPEND=3 at the end
After editing this, you need to run:
On 2014-08-17, richard kweskin wrote:
Taking these steps
1 installed wheezy with lxde from a live usb stick I had.
2 aptitude update aptitude -y full-upgrade aptitude clean
3 aptitude -R install ltsp-server-standalone dnsmasq nbd-server
looking for update-kernels.conf
...
9 find /etc
On 2014-08-16, Francesco Parisi wrote:
If I do:
# ltsp-chroot -m apt-get upgrade
I get several errors
When reporting issues, it is really helpful to actually cut-and-paste
the errors that you were getting, and the exact commands you typed to
get there.
instead if I do:
$ su -
#
On 2014-08-16, Francesco Parisi wrote:
OS: Debian edu 7.1 (main/LTSP combined server)
Problem: etckeeper failed to commit changes in /etc when make apt-get
install/remove/upgrade in chroot /opt/ltsp/i386 (fat client os)
The problem happens every time I run apt-get as root (with su - but
On 2014-08-15, richard kweskin wrote:
In /etc/ltsp/update-kernels.conf the line
LIST_KERNELS_DEFAULT=486
is for older clients and
LIST_KERNELS_DEFAULT=686-pae
is for capable clients.
Is the one line appropriate for all the clients so that one must put
the lowest common need?
No need
On 2014-08-14, richard kweskin wrote:
9 patched /usr/share/ltsp/update-kernels (using
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2569
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2570
)
10 aptitude install pxelinux
These two steps
1 - 100 of 282 matches
Mail list logo