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


Channel log from 30 June 2017   (all times are UTC)

01:16GodFather has joined IRC (GodFather!~rcc@cpe-74-79-119-9.twcny.res.rr.com)
01:35GodFather has left IRC (GodFather!~rcc@cpe-74-79-119-9.twcny.res.rr.com, Ping timeout: 260 seconds)
05:14Statler has joined IRC (Statler!~Georg@p579FE689.dip0.t-ipconnect.de)
06:20markus_e92 has left IRC (markus_e92!~markus_e9@91-115-20-178.adsl.highway.telekom.at, Ping timeout: 240 seconds)
06:22markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-20-178.adsl.highway.telekom.at)
06:31Eric4 has joined IRC (Eric4!~eric@sdi.iut-valence.fr)
06:56ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:02bobptz has joined IRC (bobptz!c23feff3@gateway/web/freenode/ip.194.63.239.243)
07:23ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
07:42wim1 has joined IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT)
07:43Leolo_2 has left IRC (Leolo_2!~fil@24-54-27-253.mg.cgocable.ca, Ping timeout: 240 seconds)
07:45wim1 has left IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT, Client Quit)
08:21Statler has left IRC (Statler!~Georg@p579FE689.dip0.t-ipconnect.de, Remote host closed the connection)
08:41gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
09:09lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Remote host closed the connection)
09:12Statler has joined IRC (Statler!~Georg@mail.lohn24.de)
09:14Statler has joined IRC (Statler!~Georg@mail.lohn24.de)
10:13markus_e92 has left IRC (markus_e92!~markus_e9@91-115-20-178.adsl.highway.telekom.at, Ping timeout: 260 seconds)
10:15markus_e92 has joined IRC (markus_e92!~markus_e9@62-46-101-30.adsl.highway.telekom.at)
10:48wim1 has joined IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT)
11:04gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
11:28ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
11:41roseco has joined IRC (roseco!2955b816@gateway/web/freenode/ip.41.85.184.22)
11:44
<roseco>
hello everyone.
11:45wim1 has left IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT, Quit: wim1)
11:47Eric4 has left IRC (Eric4!~eric@sdi.iut-valence.fr, Ping timeout: 240 seconds)
11:49
<roseco>
on LTSP, I notice that all thing clients have the same address IP that the LTSP server. How can we identify only each thing client ? regards.
12:07ZAJDAN has joined IRC (ZAJDAN!4d30954b@gateway/web/freenode/ip.77.48.149.75)
12:09
<roseco>
join
12:10
join
12:17Eric4 has joined IRC (Eric4!~eric@sdi.iut-valence.fr)
12:27gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
12:43
<Eric4>
Any idea how i can on my fat clients set hostname from dns on boot ? I guess on a regular debian/ubuntu it's set by dhclient, and on ltsp ip parameters are set by pxe + ltsp script right ? Is there a simple way or shall i write a script ?
13:02
<||cw>
roseco: you mean as detected by a web server or whatever? the thin client user session run on the server itself, so that's why. what do you need to know the client for?
13:03
Eric4: pretty sure it still uses dhclient.
13:03
normal dhcp/dns works here anyway
13:07
<Eric4>
Thx. Still discovering how it works under the hood.
13:30manilse has joined IRC (manilse!c362e40a@gateway/web/freenode/ip.195.98.228.10)
13:31
<manilse>
sur un serveur eole-eclair, les applications non-embarquéees ne se chargent pas sur le client
13:38manilse has left IRC (manilse!c362e40a@gateway/web/freenode/ip.195.98.228.10, Quit: Page closed)
13:56quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 1.7)
13:57quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
14:12professor^Servid has joined IRC (professor^Servid!bd4826dd@gateway/web/freenode/ip.189.72.38.221)
14:13
<professor^Servid>
good morning. I'm teacher and i'm using epoptes on lab info
14:13
but a i can't broadcast my screen to my students
14:13
anyone can help me?
14:15professor^Servid has left IRC (professor^Servid!bd4826dd@gateway/web/freenode/ip.189.72.38.221)
14:17
<alkisg>
!localxterm | echo roseco:
14:17
<ltsp`>
roseco: localxterm: Any applications that you launch on a thin client actually runs on the server, not on the client itself. If you want to open a program on the client locally, you can type 'ltsp-localapps <program>' in a run dialog or in a terminal. For example, 'ltsp-localapps xterm' to open a terminal running on the client.
14:18
<alkisg>
Eric4: ltsp in ubuntu/debian use ipconfig or udhcpc, and normally set dns from dhcp. But if you're using ipappend 3, which is the default in ltsp-pnp, then there's no second dns request, so you have to use lts.conf HOSTNAME
14:42ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
14:58roseco has left IRC (roseco!2955b816@gateway/web/freenode/ip.41.85.184.22, Ping timeout: 260 seconds)
15:05adrianorg has left IRC (adrianorg!~adrianorg@177.156.60.244, Ping timeout: 240 seconds)
15:54gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
16:06vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
16:42Leolo_2 has joined IRC (Leolo_2!~fil@24-54-27-253.mg.cgocable.ca)
17:13JR_ has joined IRC (JR_!ad858910@gateway/web/freenode/ip.173.133.137.16)
17:15
<JR_>
Hey, running 4 LTSP servers on a VM box...plenty of mem and cpu...no swapping. Load balance with simple dns round-robin. All thin clients are diskless workstation terminals...last generation..
17:15
cannot get firefox to be performant
17:15
compression of SSH seems faster, as turning it off seems to make FF almost unusable
17:16
15 users or so per ltsp instance
17:16
<vagrantc>
i'd strongly recommend exploring LTSP fat clients
17:16
<Leolo_2>
how much RAM on the thin clients?
17:16
<JR_>
is there any big ticket areas to consider...it seems that the VM environment really is a killer
17:16
<vagrantc>
!fat-client | echo JR_
17:16
<ltsp`>
JR_ I do not know about 'fat-client', but I do know about these similar topics: 'epoptes-fat-clients'
17:17
<Leolo_2>
because firefox loves RAM
17:17
also, have you tested running firefox at off-peak hours, when nobody but you are using LTSP?
17:18
<vagrantc>
given that firefox is essentially a massive multimedia platform these days, and the network bandwidth required for that on a thin client is *huge*
17:18
!fat
17:18
<ltsp`>
I do not know about 'fat', but I do know about these similar topics: 'fatclient-printers', 'epoptes-fat-clients', 'fat-internal-disks', 'fat-passwd', 'fat-sudo', 'fatclients'
17:18
<vagrantc>
!fatclients | echo JR_
17:18
<ltsp`>
JR_ fatclients: Nowadays LTSP supports thin and fat clients. They are both diskless and netbooted from the same LTSP chroot, but while thin clients run the session on the server and transfer the screen, fat clients run the session locally with their own CPU/RAM, thus performing amazingly better. See also !ltsp-pnp and https://help.ubuntu.com/community/UbuntuLTSP/FatClients
17:19
<JR_>
this is great info
17:19
i have been running LTSP for well over a decade
17:19
<vagrantc>
!ltsp-pnp
17:19
<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
17:19
<JR_>
and struggling to keep it going athough I really want to
17:20
<vagrantc>
unfortunately, the thin client model isn't really viable with modern software
17:20
at least, most software isn't written with thin clients in mind
17:21Statler has left IRC (Statler!~Georg@mail.lohn24.de, Remote host closed the connection)
17:22
<Leolo_2>
what vagrantc said.
17:23
any time a user needs firefox or openoffice, I switch them to a fat client or a full desktop
17:24
<vagrantc>
and so, we're mostly pushing fat clients these days ... still get the benefits of central management and network booting
17:25
it also means the servers don't have to be nearly as powerful
17:26
of course, you need more powerful clients, but even fairly old clients still can function well as fat clients
17:26
main limitation is ram
17:32markus_e92 has left IRC (markus_e92!~markus_e9@62-46-101-30.adsl.highway.telekom.at, Ping timeout: 255 seconds)
17:33markus_e92 has joined IRC (markus_e92!~markus_e9@62.46.101.30)
17:34lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18)
17:36
<alkisg>
vagrantc: Hi there... I asked about the ldm/ltspfs project move, and translations won't be lost. Do we want to do it?
17:38
I also committed a readme that documents how we're managing translations, because it can be a bit confusing...
17:43JR_ has left IRC (JR_!ad858910@gateway/web/freenode/ip.173.133.137.16, Quit: Page closed)
17:59kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:3109:6d00:445:f469:3791:efba)
18:24Eric4 has left IRC (Eric4!~eric@sdi.iut-valence.fr, Ping timeout: 260 seconds)
18:24lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Remote host closed the connection)
18:38
<vagrantc>
alkisg: kind of depends on how subprojects go ... e.g. can i get a list of bugs related to all subprojects? how hard is it to find?
18:41lucascastro has joined IRC (lucascastro!~lucas@186.193.185.13)
18:47lucascastro has left IRC (lucascastro!~lucas@186.193.185.13, Remote host closed the connection)
19:21
<alkisg>
vagrantc: launchpad doesn't support subprojects. It supports "series", which are versions of the same repository, and "project groups", to declare common security settings
19:21
To get a list of ltsp bugs, you go to:
19:22
!ltsp-bug
19:22
<ltsp`>
ltsp-bug: To file a bug report for upstream LTSP, go to https://bugs.launchpad.net/ltsp
19:22
<alkisg>
For LDM, it would be: https://bugs.launchpad.net/ldm
19:22
And for LTSPFS, it would be: https://bugs.launchpad.net/ltspfs
19:22
Since it's different code trees with different releases and with different packages, I'm not sure what a "subproject" would mean in that context
19:23
And of course it's possible to move bug reports to other projects, if they're filed against the wrong project
19:24
<vagrantc>
wasn't ltspfs originally it's own project?
19:25
alkisg: i guess, what is the harm in having "series" that are unrelated?
19:25
<alkisg>
ltspfs doesn't have a project in https://launchpad.net/ltspfs
19:25
<vagrantc>
alkisg: i think it used to
19:25
<alkisg>
vagrantc: do you have subprojects in bugs.debian.org?
19:25
Deleting a project requires a launchpad admin to do it
19:26
<vagrantc>
alkisg: no, but i have ways at looking at all my bugs
19:26
<alkisg>
I don't know who would have filed such a bug report for that
19:26
Same in launchpad too, there are ways to look at one's bugs in all projects
19:26
<vagrantc>
e.g. all bugs related to ~/ltsp-upstream ?
19:27
alkisg: it was a long time ago, maybe before you were even involved
19:27
alkisg: with ltspfs
19:27
<alkisg>
https://bugs.launchpad.net/~ltsp-upstream lists bugs that are assigned to the team
19:27
Not all the bugs of all the projects of the team
19:28
<vagrantc>
but that requires someone to actually assign them to the team?
19:28
<alkisg>
Yes but we don't want that
19:29
<vagrantc>
for the most part, i use launchpad as a storage for revision control, and only nominally deal with bugs... but this sounds like it would make it harder to deal with bugs
19:29
<alkisg>
I can't see why
19:29
I did have trouble in the past when I was confused with all the bugs under ltsp
19:29
<vagrantc>
it's just not clear to me what we really gain by splitting them into separate projects ...
19:29
<alkisg>
But if each package has its own bugs, I can't see why it would be more confusing
19:30
Well, we did a mistake and we're correcting it
19:30
Isn't that reason enough?
19:30
<vagrantc>
i recall this mistake being intentionally implemented to avoid fragmenting all the various projects in ltsp...
19:31
but honestly, i don't follow launchpad's organizational structure well at all...
19:31
mostly, i just don't want to have to keep changing VCS URLs
19:31
<alkisg>
But those are broken since we moved to git
19:32
So those need to be fixed anyway
19:32
And, projects have static URLs, unlike series
19:33
Compare https://code.launchpad.net/ltsp (=project) with https://code.launchpad.net/~ltsp-upstream/ltsp/+git/ldm (series)
19:34
<vagrantc>
ok, that's a much simpler URL, as long as it stays that way, that's preferrable.
19:34
<alkisg>
Yes projects have a single / in their urls
19:34
No long paths, for bugs, code, questions, etc etc
19:35
<vagrantc>
if it makes it simpler and not prone to change, i'm all for it. :)
19:35
<alkisg>
Phew :)
19:36
I thought it would take at least 30 more minutes to convince you :P :D
19:36
<vagrantc>
i remember when we switched to git, the previous git repository URLs changed, which seemed pointless
19:36
but hopefully we won't have to go through all that again
19:36
more than this one time....
19:36
<alkisg>
I think so. Unless we move to github :D
19:37
<vagrantc>
and then back again!
19:37
<alkisg>
We'll have some small changes when launchpad supports git in translations
19:37
<vagrantc>
may as well switch to gitlab along the way
19:37
i'll welcome the fixes to translations
19:37
oh, and there's pagure, i guess
19:42
<alkisg>
If github starts providing full integration with a specific translations service, and translators move away from launchpad, I'll consider move there... other than that... I'll stick with launchpad, I like that it has a lot of services integrated
19:43
<vagrantc>
i struggle with launchpad, but luckily alkisg usually points me to things i should be aware of :)
20:03kjackal_ has left IRC (kjackal_!~quassel@2a02:587:3109:6d00:445:f469:3791:efba, Ping timeout: 255 seconds)
20:59bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, Remote host closed the connection)
21:08ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
21:44ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)