IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 18 June 2016   (all times are UTC)

00:54pew_0 has joined IRC (pew_0!4a8bee41@gateway/web/freenode/ip.74.139.238.65)
01:00pew_0 has left IRC (pew_0!4a8bee41@gateway/web/freenode/ip.74.139.238.65, Quit: Page closed)
03:45gdi2k has left IRC (gdi2k!~gdi2k@49.151.17.102, Ping timeout: 276 seconds)
04:03gdi2k has joined IRC (gdi2k!~gdi2k@49.151.17.102)
04:54Fenuks has joined IRC (Fenuks!~Fenuks@95.191.253.62)
06:00gdi2k has left IRC (gdi2k!~gdi2k@49.151.17.102, Ping timeout: 276 seconds)
06:27ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:50kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:24e4:f95b:ce1e:6904)
07:34ricotz_ has joined IRC (ricotz_!~ricotz@p5B2A9E53.dip0.t-ipconnect.de)
07:34ricotz_ has joined IRC (ricotz_!~ricotz@ubuntu/member/ricotz)
07:37ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 260 seconds)
08:10gdi2k has joined IRC (gdi2k!~gdi2k@49.151.17.102)
08:29komunista has joined IRC (komunista!~slavko@87.244.209.121)
08:29
<komunista>
hi all
08:30
please, I am using the LTSP on Debian wheezy for long time
08:31
some time ago we bought Intel NUC and I have problem with its VGA card
08:32
<alkisg>
komunista: wheezy? isn't it time to upgrade it yet?
08:32
<komunista>
it works, but always only once: the first LDM fails, after restart second attempt success, and all other fails, until I unplug the power adapter
08:32
I afraid to update, because when I did last update to wheezy, the other thin clients are much slower
08:33
I tried to compile new xserver-xorg-intel drivers, but it doesn't helps
08:33
I tried to upgrade the kernel to 3.16, but doesn't helps too
08:34
is here some trick for this type client, please?
08:38
<alkisg>
I would suggest that you try a stretch chroot and check if it's slow or not
08:39
If the client works fine there, then no need to bother backporting newer drivers to old distributions, I don't think you'll find any kernel or xorg developers interested in helping you there
08:40
In general, such issues need a newer kernel and xorg
08:42
<komunista>
update the chroot is not a problem, the slowing is due applications
08:43
but I remember that I read somewhere, that running chroot and real server on different versions is not good idea
08:43
<alkisg>
If you're using thin clients, then yes it might be an option to use a stretch chroot in your wheezy or whatever else you have, server
08:43
From some version and on, ltsp, nbd-server etc are quite compatible with newer versions
08:44
It depends on your current ltsp and nbd-server versions
08:44
Which versions do you have of those packages?
08:44
E.g. I'm able to run ubuntu 12.04 chroots to 16.04 servers, and vice-versa, but I do have a newer ltsp package
08:46
Btw, new intel nuc clients should be ltsp fat clients, not thin clients :)
08:53
<komunista>
ltsp-server -> 5.4.2-6+deb7u1
08:53
nbd-server -> 1:3.2-4~deb7u5
08:54
I don't want fat clients, I want software at one place, it is a school class
08:54
<alkisg>
We have 1000 schools here with thin and fat clients and the teachers maintain the software graphically in one place without chroots
08:54
What you're doing is more difficult, not more easy
08:55
!ltsp-pnp
08:55
<ltsp>
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
08:55
<alkisg>
It works in debian fine as well
08:55
And schools need browsing and multimedia, it's a pitty if you don't take advantage of the nuc cpu speed for that
08:56
So anyway back to the upgrading questions, are you using nfs or nbd?
08:56
<komunista>
when I start to play with NUC, I noticed, that the last change on chroot was in 2008 :)
08:56Fenuks has left IRC (Fenuks!~Fenuks@95.191.253.62, Ping timeout: 250 seconds)
08:56
<komunista>
I am using nbd, versions see above
08:57
<alkisg>
OK, because newer versions of nfs has some issues with newer kernels
08:57
<komunista>
not 2008, 2012, sorry
08:57
I never used nfs for ltsp
08:58
<alkisg>
(we're not using chroots at all here, we're installing software using the gui)
08:58
So, you should be able to use a stretch chroot in your wheezy server if you want
08:58
But my advice is, go for ltsp-pnp
09:00
<komunista>
I have only one NUC and others are slow 486 clients with low memory, if I will have more NUC than others, I can try this but now for one machine...
09:00
<alkisg>
486? I can't believe that
09:01
<komunista>
I don't remember exactly, it is some years when I install them, I know that they are 800 MHz CPU and 256 MB RAM
09:02
<alkisg>
Those will make fine thin clients with ltsp-pnp
09:02
<komunista>
and horrible VGA, something as chrome
09:03
<alkisg>
We have schools that use ltsp-pnp with 400 mhz, 128 ram here
09:03
<komunista>
when the NUC starts correctly, it is amazing when I compare with these old machines
09:04
bigger resolution (I have forced low resolution due performance), NUC works on full 1280x1024 great
09:04
only starting :(
09:06
<alkisg>
Having some fat clients increases the performance of thin clients because it leaves more network bandwidth available
09:06
Also, use 16 bit color depths for thin clients, and LDM_DIRECTX
09:06
<komunista>
but back, do you think that it can be safe to mix stable chroot with old-stable server?
09:07
<alkisg>
Finally, use the epoptes network benchmark tool to verify that your network speed is what you expect; it's very frequently a source of "unknown" performance issues
09:07
It should work with only 1-2 manual changes, yes
09:09
<komunista>
I did tray epoptes some years ago, it doesnot works on all c lients (all was the same), someone from LTSP team was logged into my network (I forget who), but we cannot find source of problem...
09:10
<alkisg>
Maybe it was me
09:10
We solved a lot of issues with bad clients in the last years, I haven't seen epoptes failing recently
09:11
E.g. one problem that might be what you're describing, was the cmos battery failure on clients causing bad dates, which then caused expired certificates
09:11
So the correct solution would be to replace the batteries,
09:11gdi2k has left IRC (gdi2k!~gdi2k@49.151.17.102, Ping timeout: 276 seconds)
09:11
<alkisg>
and the epoptes side of the solution was to generate a certificate valid since 1970
09:13
<komunista>
OK, I will try the jessie chroot in this week, and then I return ;)
09:13
thanks for info
09:13
<alkisg>
Why not stretch?
09:14
It's a chroot, it's stable enough for a chroot...
09:14
It'll last you longer that way
09:14
<komunista>
I will take look into ltsp-pnp in more depth
09:14
uff, then OK I will try strech, as I mentioned I am fearing ;-)
09:15
regards
09:15
and thanks again
09:15
<alkisg>
You're welcome
09:16komunista has left IRC (komunista!~slavko@87.244.209.121)
10:30kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:24e4:f95b:ce1e:6904, Ping timeout: 260 seconds)
10:58epoptes_user4 has joined IRC (epoptes_user4!05eecc6c@gateway/web/freenode/ip.5.238.204.108)
10:58epoptes_user4 has left IRC (epoptes_user4!05eecc6c@gateway/web/freenode/ip.5.238.204.108)
10:59ricotz_ is now known as ricotz
11:50lee_ is now known as lee
12:30grobi has joined IRC (grobi!4dbac828@gateway/web/freenode/ip.77.186.200.40)
12:34
<grobi>
is it possible to choose from several images for example 32 or 64 bit - at (pxe) start process
12:46GodFather has joined IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com)
13:29kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:24e4:f95b:ce1e:6904)
14:31alkisg_android has joined IRC (alkisg_android!~yaaic@athedsl-154180.home.otenet.gr)
14:32
<alkisg_android>
grobi, yes, with either dhcp, per mac, or via pxelinux ifcpu module
14:33
but usually we use one i386 chroot for all clients
14:46alkisg_android has left IRC (alkisg_android!~yaaic@athedsl-154180.home.otenet.gr, Ping timeout: 240 seconds)
15:05
<grobi>
thanks alkisg,.. the image is thus always linked to the client? it is not possible to select between 32bit and 64bit on startup? do I understand this in the right manner...
15:06Fenuks has joined IRC (Fenuks!~Fenuks@95.191.253.62)
15:34gp has joined IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net)
15:49Softeisbieger has joined IRC (Softeisbieger!~Softeisbi@ip-62-143-13-166.hsi01.unitymediagroup.de)
16:13Softeisbieger has left IRC (Softeisbieger!~Softeisbi@ip-62-143-13-166.hsi01.unitymediagroup.de, Remote host closed the connection)
16:53alkisg_android has joined IRC (alkisg_android!~yaaic@athedsl-154180.home.otenet.gr)
16:55
<alkisg_android>
grobi, you can hardcode the mac, or use ifcpu for automatic selection, or use a pxe menu, or a pxelinux menu
16:55
4 methods :)
16:56
but why not use i386 anywhere? it supports up to 64 gb ram...
17:00gp has left IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net, Quit: Leaving)
17:29alkisg_android has left IRC (alkisg_android!~yaaic@athedsl-154180.home.otenet.gr, Ping timeout: 264 seconds)
17:32
<grobi>
thats right :-) I just want to test something...
17:44grobi has left IRC (grobi!4dbac828@gateway/web/freenode/ip.77.186.200.40, Quit: Page closed)
18:25lmds_ has left IRC (lmds_!~lmds@tui.pi-et-ro.net, Ping timeout: 258 seconds)
18:44Fenuks has left IRC (Fenuks!~Fenuks@95.191.253.62, Ping timeout: 264 seconds)
18:53johnson1k86 has joined IRC (johnson1k86!~john@p5B0E98A0.dip0.t-ipconnect.de)
19:04GodFather has left IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com, Ping timeout: 250 seconds)
19:30vmlintu has joined IRC (vmlintu!~vmlintu@a91-153-33-91.elisa-laajakaista.fi)
20:08vmlintu has left IRC (vmlintu!~vmlintu@a91-153-33-91.elisa-laajakaista.fi, Ping timeout: 244 seconds)
20:33johnson1k86 has left IRC (johnson1k86!~john@p5B0E98A0.dip0.t-ipconnect.de, Quit: Verlassend)
20:44ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)