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


Channel log from 25 January 2016   (all times are UTC)

01:43Ark74_lap has left IRC (Ark74_lap!~Luis@177.239.209.188, Ping timeout: 245 seconds)
02:01Ark74_lap has joined IRC (Ark74_lap!~Luis@177.239.209.188)
02:44Ark74_lap has left IRC (Ark74_lap!~Luis@177.239.209.188, Ping timeout: 250 seconds)
03:51bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, Remote host closed the connection)
04:03Ark74_lap has joined IRC (Ark74_lap!~Luis@189.220.253.111.cable.dyn.cableonline.com.mx)
04:25gehidore is now known as man
04:25man is now known as gehidore
04:50vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
06:32alkisg_away is now known as alkisg
06:55ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:13mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:52uXus has left IRC (uXus!~uXus@217.77.222.72, Remote host closed the connection)
08:03uXus has joined IRC (uXus!~uXus@217.77.222.72)
08:26vmlintu has joined IRC (vmlintu!~vmlintu@a88-112-3-40.elisa-laajakaista.fi)
08:26Softeisbieger has joined IRC (Softeisbieger!~Softeisbi@dsl37-153-56.pool.bitel.net)
08:50Guest78338 is now known as fnurl
10:44Faith has joined IRC (Faith!~paty_@unaffiliated/faith)
11:23adminaula has joined IRC (adminaula!3e0ec914@gateway/web/freenode/ip.62.14.201.20)
11:42gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
12:30robb_nl has joined IRC (robb_nl!~robb_nl@ip-213-49-84-117.dsl.scarlet.be)
12:42robb_nl has left IRC (robb_nl!~robb_nl@ip-213-49-84-117.dsl.scarlet.be, Ping timeout: 256 seconds)
13:14aj_ has joined IRC (aj_!58b6b90e@gateway/web/freenode/ip.88.182.185.14)
13:17
<aj_>
Hi guys! LTSP on Ubuntu 15: diskless clients boot into initramfs: "Overlayfs: missing 'workdir'"
13:17
Any hint?
13:26mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
13:42Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving)
14:11aj_ has left IRC (aj_!58b6b90e@gateway/web/freenode/ip.88.182.185.14, Quit: Page closed)
14:41eddytv has joined IRC (eddytv!~eddy@216.130.192.2)
14:45
<eddytv>
I'm currently running 5.5.5~r2703+p1238+201512091628~ubuntu14.04.1 with two clients. The problem is that the two clients are not booting up with the same X session config and I can't figure out why.
14:46
I'd like both clients to boot up identically, but am not sure where to go to "clean up" whatever is causing them to behave differently. The hardware of the two clients is identical.
15:13bennabiy has joined IRC (bennabiy!~bennabiy@unaffiliated/bennabiy)
15:26mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
15:30
<alkisg>
eddytv: what's your lts.conf like?
15:41
<eddytv>
It has the two client MAC addresses in brackets, with only three entries under each one: HOSTNAME, LDM_USERNAME and LDM_PASSWORD
15:42
<alkisg>
And your user's /home/username/.dmrc files, what do they have in them?
15:42
<eddytv>
Just [Desktop] / Session=xfce
15:44
<alkisg>
This defines the session in the first user. Does the second user have the same session too?
15:44
<eddytv>
Yes, but clients aren't active at the same time, they're just in different locations in the house.
15:45
<alkisg>
And when you say they have different x session configs, what do you mean? What do you see different?
15:46vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
15:46
<eddytv>
One client automaticall opens an XTerm and has the correct X resolution (100 dpi) and looks "normal".
15:47
The other client (identical hardware) doesn't open the XTerm and has a much bigger dpi so the fonts are HUGE.
15:47
<alkisg>
Do they both show the xfce desktop?
15:47
<eddytv>
I just can't figure out why they are behaving differently.
15:48
Yes. The Xfce desktop background, menu config, etc. are otherwise the same.
15:48
<alkisg>
Then it's not a matter of xsession config, and it's not a matter of ltsp,
15:48
it's just a matter of how these users customized their xfce session
15:48
For that part, ask in #xfce
15:48
It would be from the desktop properties etc
15:49
<eddytv>
But if they're both using the same credentials, how are they being differentiated?
15:49
<alkisg>
So you only have one user, not two?
15:49
<eddytv>
Correct
15:49
<alkisg>
For example, for gnome, there's .config/monitors.xml, which has settings on a per-monitor basis
15:50
Ask in #xfce for the similar config file
15:50
<eddytv>
OK. Would the sound configuration also be affected? One of the clients boots up with a sound device "muted" and I have to manually run alsamixer each time to un-mute that device.
15:51
<vagrantc>
alkisg: anything new to test for LTSP/LDM/epoptes?
15:51
<alkisg>
Pulse saves sound settings on .pulse, yes on a per-output basis
15:51
eddytv: but you can also run commands to unmute audio in lts.conf
15:52
Hi vagrantc, ltsp and ldm are ready, while Phantomas has just finished the last touches for epoptes,
15:52
<eddytv>
Oh, I didn't realize that. That would be helpful. Do you have an example of doing that handy?
15:52
<alkisg>
not sure if he's pushed them yet or if he will do so today/tomorrow
15:52
See the lts.conf manpage
15:52
!lts.conf
15:52
<ltsp>
lts.conf: (#1) http://manpages.ubuntu.com/lts.conf, or (#2) lts.conf manpage is available in the ltsp-docs package
15:52
<vagrantc>
alkisg: ok, cool. will do some more testing and hopefully upload
15:53
<alkisg>
vagrantc: I was thinking for epoptes, it would be nice if Phantomas prepared the changelog etc, and you only uploaded it, so that he gains some experience "points" for DM...
15:53
<vagrantc>
alkisg: works for me
15:53
<alkisg>
Cool
15:54
<vagrantc>
be sure to run lintian on the build beforehand, though
15:55
<alkisg>
Sure
15:58
<eddytv>
alkisg: I didn't find any references to audio in the lts.conf man page, but a google search did turn up: http://chrisjrob.com/2009/02/17/ltsp5-sound-client-unmute-fix/
16:01
<alkisg>
eddytv: it's not the correct approach, the ltsp way to arrange the volume is described in the lts.conf manpage
16:01
Did you search for "volume" inside the man page?
16:02
<eddytv>
Ha, I did not. Thanks.
16:02
<alkisg>
That person is using a custom script which isn't needed, as ltsp already has a script like that (better, actually)
16:03
<eddytv>
Excellent. I was searching for stuff like "mute" and "audio".
16:03ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
16:04
<eddytv>
So my particular problem is that the "S/PDIF" sound channel/device defaults to being muted, which prevents audio from going out the HDMI port.
16:05
Are there ways to adjust "arbitrary" sound devices besides PCM/Front/CD/Mic?
16:05
<vagrantc>
alkisg: re-added memtest86+.bin code, heh. :)
16:05
<alkisg>
:)
16:05
It was as simple as changing the keyword :)
16:06
eddytv: yes, just use the variable that corresponds to your audio device
16:06
<vagrantc>
i remember when i dropped support for it, we had discussed just dropping it since it wasn't really all that ltsp related
16:06
<alkisg>
LTSP has dynamically named variables there
16:06
vagrantc: yes, then I asked in #syslinux and they told me that we were using the wrong keyword
16:07
Since we know it's a kernel, we should be using the kernel keyword, not the generic one (don't remember the names now)
16:07
linux, not kernel
16:08
The kernel keyword means "use autodetection based on the extension etc"
16:08
While we don't want autodetection for memtest
16:08
<eddytv>
alkisg: thanks for the pointers. At least I have some ideas on how to move forward now.
16:08
<alkisg>
np
16:15
<vagrantc>
alkisg: cool.
16:23robb_nl has joined IRC (robb_nl!~robb_nl@ip-213-49-84-117.dsl.scarlet.be)
17:27bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, Read error: Connection reset by peer)
17:28bennabiy has joined IRC (bennabiy!~bennabiy@unaffiliated/bennabiy)
17:49Ark74 has left IRC (Ark74!~Ark74@189.220.253.111.cable.dyn.cableonline.com.mx, Quit: Saliendo)
17:50Softeisbieger has left IRC (Softeisbieger!~Softeisbi@dsl37-153-56.pool.bitel.net, Ping timeout: 250 seconds)
18:06gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
18:20Softeisbieger has joined IRC (Softeisbieger!~Softeisbi@dsl37-153-56.pool.bitel.net)
18:22ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 256 seconds)
18:22ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
18:42robb_nl has left IRC (robb_nl!~robb_nl@ip-213-49-84-117.dsl.scarlet.be, Ping timeout: 264 seconds)
19:14Dave___ has joined IRC (Dave___!63634655@gateway/web/freenode/ip.99.99.70.85)
19:16
<Dave___>
I was wondering specifically which Thin Client hw is supported by LTSP v5: HP?, Dell? (Sorry I new to this)
19:17
Is there a list of Thin Client hardware that has had success?
19:22
<Hyperbyte>
Dave___, basically, it depends on the Linux distribution you're using for your client.
19:22
<Dave___>
oh
19:22
Ubuntu
19:22
<Hyperbyte>
Well, if the clients work with regular Ubuntu, they should work with LTSP.
19:23
LTSP is a way of booting Linux over the network on clients without a harddisk
19:23
<vagrantc>
Dave___: any computer that can PXE boot over the network is in theory a candidate for an LTSP client, you don't *need* hardware specifically designed as a thin client
19:23
<Hyperbyte>
LTSP itself doesn't have specific hardware that is or isn't supported, it depends on what the Linux distribution does.
19:24
<Dave___>
I was thinking of purchasing some HP Thin client, but they were imaged for Windows. I wanted the thin client to be ubuntu. Is the away to change the embedded images on these HP units
19:24
<Hyperbyte>
Dave___, why were you considering the HP clients?
19:25
<Dave___>
It was the first one I saw. seemed to be reasonably priced. on fixed income
19:26
<Hyperbyte>
They're quite expensive most of the time actually.
19:26
<Dave___>
oh
19:26
<Hyperbyte>
You are going to use thin clients, rather than fat clients?
19:26
You have a powerful computer to use as server?
19:26
<Dave___>
I thought that would work. managing one resource providing system
19:27
so yes: thin client
19:27
<Hyperbyte>
Both thin and fat clients have that.
19:27
<Dave___>
is that a bad choice
19:27
What would you suggest to a newbie, as myself
19:28
<Hyperbyte>
Thin client: boots Linux, logs in to the server and starts the entire desktop on the server, thus not using any of the client hardware. It does require a fast network, gigabit preferably, especially with higher screen resolutions.
19:28
Fat client: boot Linux, logs in to the server, but starts the entire desktop on the client (like a normal computer would), so it uses all of the client hardware and doesn't strain the server. Doesn't require a lot of bandwith per say, depending on your image size and how active your users are.
19:29
<Dave___>
hmmmm
19:29
my network is 100mb
19:29
cat 5
19:29
<Hyperbyte>
So it's either: start all software remotely, transmitting input/output over network between client and server
19:30
Or start all software locally, using the server's image instead of a harddisk.
19:31
<Dave___>
With a network that I'll probably not re-wire for sometime what would you say?
19:31
I've only a need for less that 9 clients
19:32
<Hyperbyte>
I use thin clients one at a company for ~15 clients, with a very powerful server. Dual Opteron, 32 GB RAM... it's on purpose there, because we don't want noise from running computer fans, or heat generated by the components in our offices.
19:32
-one
19:32
For another company, with about ~10 clients, I use fat clients because they don't have a powerful server and have more powerful client hardware.
19:33
<Dave___>
Ok, so I need a very high end LTSP server?
19:33
<vagrantc>
if you're unsure, i'd recommend finding some reasonably priced computers and go with fat clients
19:33
the server requirements for fat clients are very minimal
19:33
<Dave___>
sorry, I'm a slow typist
19:33
<vagrantc>
you can use just about any old computer
19:34
<Dave___>
That sounds great.
19:34
<Hyperbyte>
Dave___, also, nothing is stopping you from trying both.
19:34
<Dave___>
Where can I learn more about the "fat Client"
19:34
<Hyperbyte>
If you use ltsp-pnp, you can switch been thin/fat clients with a simple configuration option.
19:35
<Dave___>
I'm assuming this site here: LTSP
19:35
<Hyperbyte>
You could even say in the config "this client has only 512 MB ram, so it has be thin else it won't run, but the rest can be fat"
19:35
<vagrantc>
!ltsp-pnp | echo Dave___
19:35
<ltsp>
Dave___ 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
19:35
<Dave___>
ok, I see I need to up my education here.
19:36
<Hyperbyte>
Dave___, my advice, start trying things before you buy clients.
19:37
<Dave___>
Okay, but when you mean trying things. Does that mean find some old equipment and try to apply the LTSP environment on them.
19:37
<Hyperbyte>
Do an installation... get some random PC which you can reinstall, or boot Ubuntu from a USB stick even, and set up an actual LTSP server. Then try out thin, try out fat...
19:37
Yes.
19:38
<Dave___>
Okay. I think I can do that
19:38
<Hyperbyte>
Then you can experience what bottlenecks are... generally speaking it's either the client, the server or the network. If you have 100mbit, it's not unthinkable network could be a big factor.
19:38
<Dave___>
Do you know of any useful reading material
19:38
<Hyperbyte>
Dave___, wiki.ltsp.org
19:39
<Dave___>
Of course. Dahhhh
19:39
<Hyperbyte>
And you can always stick around here, ask questions, chat...
19:39
<Dave___>
Thank you. so much
19:39
<Hyperbyte>
Sometimes it takes a while to get a reply, but eventually you will.
19:39
You could install an IRC client on your computer so you don't have to use the webinterface even.
19:40
<Dave___>
I really appreciate this. Much thanks. Truly Dave H
19:40
<Hyperbyte>
You're welcome. Hyper B.
19:40
<Dave___>
I'll be back after a little more reading and experimentation.
19:40
Thank you!
19:40
Ciao
19:42Dave___ has left IRC (Dave___!63634655@gateway/web/freenode/ip.99.99.70.85, Quit: Page closed)
19:43Dave___ has joined IRC (Dave___!63634655@gateway/web/freenode/ip.99.99.70.85)
21:03vmlintu has left IRC (vmlintu!~vmlintu@a88-112-3-40.elisa-laajakaista.fi, Ping timeout: 265 seconds)
21:19vmlintu has joined IRC (vmlintu!~vmlintu@a88-112-3-40.elisa-laajakaista.fi)
21:31m3741 has joined IRC (m3741!8c20b7fe@gateway/web/freenode/ip.140.32.183.254)
21:32Softeisbieger has left IRC (Softeisbieger!~Softeisbi@dsl37-153-56.pool.bitel.net, Remote host closed the connection)
21:40ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:43eddytv has left IRC (eddytv!~eddy@216.130.192.2, Ping timeout: 260 seconds)
22:15vmlintu has left IRC (vmlintu!~vmlintu@a88-112-3-40.elisa-laajakaista.fi, Ping timeout: 240 seconds)
23:23eddytv has joined IRC (eddytv!~eddy@c-68-60-64-128.hsd1.mi.comcast.net)