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


Channel log from 4 August 2014   (all times are UTC)

03:08FrozenZia has left IRC (FrozenZia!pbrown@evo.paivola.fi, Ping timeout: 255 seconds)
06:11spectra has left IRC (spectra!~spectra@debian/developer/spectra, Ping timeout: 260 seconds)
06:14spectra has joined IRC (spectra!~spectra@debian/developer/spectra)
06:51mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
08:01bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, Read error: Connection reset by peer)
08:01bennabiy has joined IRC (bennabiy!~bennabiy@unaffiliated/bennabiy)
08:40workingcats has left IRC (workingcats!~workingca@212.122.48.77, Remote host closed the connection)
08:47workingcats has joined IRC (workingcats!~workingca@212.122.48.77)
09:40mealstrom1 has left IRC (mealstrom1!~Thunderbi@46.63.63.163, Ping timeout: 264 seconds)
10:19FrozenZia has joined IRC (FrozenZia!pbrown@evo.paivola.fi)
10:35NeonLicht has joined IRC (NeonLicht!~NeonLicht@darwin.ugr.es)
10:37adrianorg has left IRC (adrianorg!~adrianorg@179.180.166.132, Ping timeout: 240 seconds)
10:39adrianorg has joined IRC (adrianorg!~adrianorg@179.179.76.182)
10:47
<muppis>
Anyone experienced with BerryTerminal?
10:59mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.71.254)
11:02bitcheker has joined IRC (bitcheker!~bitchecke@dynamic-adsl-62-10-103-15.clienti.tiscali.it)
11:04mealstrom has left IRC (mealstrom!~Thunderbi@46.63.71.254, Remote host closed the connection)
11:05mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.71.254)
11:25bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
12:09dreville has joined IRC (dreville!~deeville@38.117.108.108)
12:12muppis_ has joined IRC (muppis_!muppis@takaisin.fi)
12:15spectra- has joined IRC (spectra-!~spectra@eregion.nardol.org)
12:19workingcats has left IRC (workingcats!~workingca@212.122.48.77, *.net *.split)
12:19spectra has left IRC (spectra!~spectra@debian/developer/spectra, *.net *.split)
12:19deeville has left IRC (deeville!~deeville@38.117.108.108, *.net *.split)
12:19zamba has left IRC (zamba!marius@flage.org, *.net *.split)
12:19muppis has left IRC (muppis!muppis@takaisin.fi, *.net *.split)
12:21Faith has joined IRC (Faith!~paty@unaffiliated/faith)
12:23mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
12:23workingcats has joined IRC (workingcats!~workingca@212.122.48.77)
12:26zamba has joined IRC (zamba!marius@flage.org)
12:44Gremble has joined IRC (Gremble!~Ben@host-92-27-135-217.static.as13285.net)
12:45Gremble is now known as Guest2758
13:31cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 240 seconds)
13:31cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
13:45championofcyrodi has joined IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
13:49mealstrom has left IRC (mealstrom!~Thunderbi@46.63.71.254, Remote host closed the connection)
13:49bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Quit: Goin' down hard)
13:50mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.71.254)
13:53cryptrat has joined IRC (cryptrat!32c3bb3e@gateway/web/freenode/ip.50.195.187.62)
13:54
<cryptrat>
anyone get the ltsp-localapps command to work, all i get is: sorry, command-not-found has crashed! when i try to run it
13:57mealstrom1 has joined IRC (mealstrom1!~Thunderbi@46.63.71.254)
13:57mealstrom has left IRC (mealstrom!~Thunderbi@46.63.71.254, Remote host closed the connection)
13:58you_ has joined IRC (you_!~you@118.186.153.230)
14:01
<you_>
the thin-client's login screen couldnot show username and password correctly in chinese. so i add match in the fonts.conf, but it still doesn't work. what should i do? thnks
14:01mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
14:03
<Hyperbyte>
cryptrat, where are you running the command?
14:03
cryptrat, and are you using fat or thin clients?
14:05
<championofcyrodi>
so... Saturday night the LTSP server successfully built an image in the docker container. OpenSSH is working too. I'm about to go test it out now, but I am pretty sure it's gonna work. If so, I'll have a portable isolated LTSP instance to deploy on all the networks!
14:07
<you_>
the thin-clients seems not work smoothly, they are a little slow
14:16
<bennabiy>
championofcyrodi: now just document it :)
14:17
<championofcyrodi>
i have been on my blog
14:17
but it's still more or less a draft
14:18
okay.. im getting coffee and cereal and going to go try it out...
14:18
bennabiy got me excited and has now distracted me from my other tasking.
14:19championofcyrodi has left IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
14:20FrozenZia has left IRC (FrozenZia!pbrown@evo.paivola.fi, Ping timeout: 240 seconds)
14:22you_ has left IRC (you_!~you@118.186.153.230, Quit: 离开)
14:28mealstrom1 has left IRC (mealstrom1!~Thunderbi@46.63.71.254, Ping timeout: 244 seconds)
14:33championofcyrodi has joined IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
14:34
<championofcyrodi>
failure...
14:34
should have got coffee before testing maybe.
14:35
same issue, tftp boots over UDP, nbd connects. Can't authenticate... no idea what 'server' it's trying to authenticate with. Thought 'SERVER=hostname' in lts.conf would override, but perhaps i misunderstood the lts.conf MAN page...
14:37
i guess i'm going to set a root pw on the image and login w/ tty1. maybe /etc/hosts on the running image will help
14:43
<cryptrat>
Hyperbyte, i am running fat clients
14:44
i'm running it in a terminal on the fat client
14:51adrianorg has left IRC (adrianorg!~adrianorg@179.179.76.182, Read error: Connection reset by peer)
14:54
<Hyperbyte>
cryptrat, right. And what are you trying to accomplish with the "ltsp-localapps" command?
14:55
championofcyrodi, why do you have SERVER= in lts.conf?
14:55
By default it uses the server it booted from, why do you need to override this?
14:55
<cryptrat>
just trying to see if i can get a local app like firefox to work locally on the fat client
14:55adrianorg has joined IRC (adrianorg!~adrianorg@177.134.61.196)
14:56
<Hyperbyte>
cryptrat, but the whole point of fat clients as opposed to thin clients, is that -everything- runs locally.
14:56
cryptrat, with thin clients, not only the disk image is on the server, but also all applications are ran on the server.
14:57
cryptrat, with fat clients, all software already runs locally. Only the disk image is taken from the server, but all the software already runs on the client. That's why you have no "ltsp-localapps" command - it wouldn't make sense to have it.
14:58
<cryptrat>
ok is there a difference in how you make a fat client image compared to a thin client?
14:58
<Hyperbyte>
cryptrat, yes.
14:59
<cryptrat>
can i have a diskless fat client load as a thin client ?
15:00
<Hyperbyte>
cryptrat, yes.
15:00adrianorg has left IRC (adrianorg!~adrianorg@177.134.61.196, Ping timeout: 255 seconds)
15:00
<championofcyrodi>
YAY I GOT IT WORKING!
15:00
<Hyperbyte>
Fat client vs. thin client isn't dependant on specific hardware or client configuration. Any client can be fat or thin, assuming minimum hardware requirements are met.
15:01
<championofcyrodi>
Hyperbyte: because the server hosting the LTSP software isnt the same server i want SSHFS authentication with.
15:01mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
15:01
<Hyperbyte>
cryptrat, you should ask alkisg, he's the master when it comes to fat vs thin and the like....
15:02adrianorg has joined IRC (adrianorg!~adrianorg@177.156.57.132)
15:02
<cryptrat>
ok, because i'm just trying to breathe life into some old dells that are sitting around collecting dust
15:02
<championofcyrodi>
apparently SSH_OVERRIDE_PORT is not working properly in lts.conf... or my lts.conf isnt working. I just modified /etc/ssh/ssh_config on the image using the root account... set Port 2222, (the port mapped to my container from the host) and BAM, its working.
15:03
<cryptrat>
is it better to use the alternate cd or to try and add ltsp to an existing server?
15:06
<championofcyrodi>
cryptrat: i found the alternate cd to be easiest with 12.04
15:06
however the alternate didnt exist w/ 14.04, so i used the 14.04 server edition... then apt-get install ltsp-server-standalone
15:06
works well if you have 2 network cards and don't want conflict w/ current DHCP
15:09
<Hyperbyte>
cryptrat, if you have old hardware you want to power using one beefier server, then you want thin clients.
15:37
<cryptrat>
i have a beefy server, quad core xeon w/ 8gb of ram on a supermicro mobo
15:38
4 1tb drives in a raid 10 array
15:43
<championofcyrodi>
okay, so i documented the LTSP -> Docker process here: http://championofcyrodiil.blogspot.com/2014/08/ubuntu-1404-ltsp-docker-container.html
15:43
let me know if anything seems unclear or confusing. (i'm sure there are some things)
15:43
also my scenario is over complicated by the separate VLAN.
15:48vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
15:49
<vagrantc>
bennabiy: well, the hashpass thing seems to be working as expected for me
15:49
<bennabiy>
That is great
15:49
<vagrantc>
good work
15:50
<bennabiy>
Hopefully it won't be needed for too much longer ;)
15:50
<vagrantc>
of course, it's got weirdnesses like trying to change password will seem successful, until you log out
15:50
and remoteapps and localapps will get out of sync with password data... but hey, screensavers work!
15:51
<bennabiy>
The whole point of it is that it matches your remote password when you start your session
15:51
otherwise you could just default the local password to foo for every user
15:52alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
15:52* bennabiy welcomes alkisg
15:52* vagrantc waves to alkisg
15:52
<alkisg>
Hi bennabiy, hi vagrantc, hi all
15:52
<vagrantc>
bennabiy: there are a few compiler warnings in the build log...
15:53
<bennabiy>
from my portion of the code?
15:53
<vagrantc>
bennabiy: but they are similar areas to other code you emulated, so not really introduced by you
15:53
<bennabiy>
hrm.
15:53
<vagrantc>
would be good to fix both the old and new code :)
15:53
<bennabiy>
true
15:54
I did notice there were some warnings in the existing code
15:54
perhaps I can look at that later
15:54Guest2758 has left IRC (Guest2758!~Ben@host-92-27-135-217.static.as13285.net, Quit: I Leave)
15:57
<vagrantc>
hrm. some automake update, too.
15:59
<bennabiy>
Make a list :)
15:59* vagrantc really wonders about https://bugs.launchpad.net/bugs/1325388/+attachment/4123781/+files/0001-Bye-bye-No-response-from-server-add-ssh-error-loggin.patch
16:02
<vagrantc>
would be really good to start writing testsuites.
16:02
there are many things that would be really hard to test, but we should try to test what's testable.
16:04
<cryptrat>
hello alkisg, i was told you know the most about fat vs thin clients,
16:04
<bennabiy>
LDM is somewhat difficult to debug properly because of its need to be called by xinit
16:04
<alkisg>
Hi cryptrat
16:04FrozenZia has joined IRC (FrozenZia!pbrown@evo.paivola.fi)
16:05
<bennabiy>
It takes a lot of extra logging to try to figure out what is going on, since it cannot be easily attached to with a debugger.
16:06
<vagrantc>
yes, but portions of code could be written to be able to be passed various responses to make sure the right responses come out ... i.e. you could fake an ssh session with stdin/stdout and such
16:06
<alkisg>
cryptrat: what are your client specs? cpu and ram?
16:06
<vagrantc>
course, faking ssh is proably a whole complicated, and somewhat dangerou thing to support... heh.
16:06
<bennabiy>
yes
16:07
<vagrantc>
but surely there are things we could test better.
16:07* bennabiy imagines a world without ldm...
16:07
<cryptrat>
older dell p4 1gb ram
16:08* Asterisks imagines a world without bennabiy
16:08
<alkisg>
!ltsp-pnp | echo cryptrat:
16:08
<ltsp>
cryptrat: 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
16:08
<alkisg>
cryptrat: that way they'd run as fat clients, same as you say you have them now
16:08* bennabiy starts to see the letters LTSP and 6 coming together
16:08
<alkisg>
cryptrat: If you want thin clients, then start with the desktop iso and run ltsp-build-client
16:08* vagrantc has been seeing that mirage for a few years now
16:09
<alkisg>
cryptrat: the ltsp-localapps command is in the ltsp-server package, that's why it didn't run from a fat client, because it doesn't make sense there, apps already run locally
16:09
<bennabiy>
Hi Asterisks. No need to imagine.
16:09
<vagrantc>
i don't know what it's going to take to get the impetus to push LTSP6 into reality...
16:10
was hoping to get some hackfests going in person, but geography makes that a challenge
16:10
<bennabiy>
A solid list of what LTSP 6 alpha is going to need to contain to be called 6
16:10
Identifying what is going to be removed
16:10
Starting a fork, so that development can take place
16:10
<championofcyrodi>
hey guys, any thoughts on the lts.conf's SSH_OVERRRIDE_PORT not working for me? Perhaps I'm "doing it wrong.", or I have a different expectation for it's use.
16:11
<vagrantc>
bennabiy: well, we've already got libpam-sshauth, and ltsp already works with it, but it's missing support for some features
16:11
forget what all it's missing
16:11
<championofcyrodi>
when i manually switch the client's ssh_config to 'Port 2222', i can login/authenticate just fine. However, it causes all user's default ssh session to attempt port 2222. So was hoping the SSH_OVERRIDE_PORT parameter would use 2222 just for the SSHFS connection.
16:11
<vagrantc>
so, we need a way to track the issue
16:12
<bennabiy>
We need somewhere to be able to document what is done, what needs to be done, and the problems faced
16:12
<vagrantc>
it's not my favorite, but launchpad probably has some issue tracking features that might work for this
16:13
<cryptrat>
i pretty much followed the LTSP/ProxyDHCP setup
16:13
<bennabiy>
Yes.
16:14
vagrantc: if you can find out what features are missing support, I might be able to look into it a little more later. I need to push a project through right now, but might have more time next week or so.
16:14
<cryptrat>
and you're saying the ltsp-pnp would have been better?
16:15
<vagrantc>
bennabiy: http://wiki.ltsp.org/wiki/Dev:LTSPPamNotes
16:15
bennabiy: that's the status as of october
16:15
<alkisg>
cryptrat: ltsp-php includes proxydhcp, it's just an easy way to get fat clients, you probably ALSO followed https://help.ubuntu.com/community/UbuntuLTSP/FatClients
16:15
<bennabiy>
Also, what would need to change for dependencies pulled down?
16:16
Would it be someones preference to use LightDM or GDM or MDM etc, or would it be lts.conf config?
16:17
it looks like it is only lightDM, but would others be supported?
16:18
<vagrantc>
bennabiy: arbitrary DMs are supported, just need to support pam
16:18
bennabiy: i tested with lightdm, gdm3 and kdm when i did the testing
16:19
although kdm was slightly glitchy, and gdm has a quirk or two ... but in theory, any display manager would work
16:19
<bennabiy>
that is encouraging
16:20
<cryptrat>
@cryptrat yeah i used the --fat-client tag to build an image
16:21
and i've also used chroot and tried lxde trying to get better performance
16:22
can you make a fat client act like a thin client, i mean what really is the difference in how it determines which is which with ltsp
16:22
<vagrantc>
bennabiy: that was essentially the point... to be able to use any pam-supporting display manager
16:23
bennabiy: and merely hook in our ltsp-specific bits, rather than maintain a whole display manager
16:23
cryptrat: LTSP_FATCLIENT=true|false
16:24
it typically guesses based on that lts.conf setting, or the value of FAT_RAM_THRESHOLD
16:25
<cryptrat>
ok i'll try that
16:25
<bennabiy>
vagrantc: Please keep me posted. I would be willing to put a little time towards it, but would probably not be able to attend any type of hackfests unless they were right here.
16:26
vagrantc: I might be able to help a bit while a hackfest is going on though
16:27
<vagrantc>
bennabiy: the most active developers are spread out over many timezones
16:27
<bennabiy>
half a world :)
16:30* vagrantc wonders if setting up an event before or after the LTSP BTS that was focused on LTSP development, perhaps in some easier to get to location that northeastern maine
16:33
<championofcyrodi>
Is "/etc/ltsp/lts.conf" in ltsp-server 5.5.1 parsed for LDM Options?
16:34
<vagrantc>
to be safe, you want to make sure to edit /var/lib/tftpboot/ltsp/*/lts.conf or /srv/tftp/ltsp/*/lts.conf
16:34
but it depends on your setup
16:34
<bennabiy>
out to lunch, back in a bit
16:36
<championofcyrodi>
yea... tried the var/lib/tftpboot... Path, didn't seem to pick up the parameter. hmmm... Maybe because it's below the [OLD_MONITOR] tag instead of [Default]...
16:37
I assume i need to only bounce tftpd-hpa when i update that file?
16:38
<vagrantc>
shouldn't need to restart anything
16:39
<championofcyrodi>
SWEET! that was it! Needed to go under the [Default] flag instead of [OLD_MONITOR]... i just paged down to the bottom and didnt realize i was placing it under a different parsing option
16:39
<vagrantc>
championofcyrodi: yes, you need to put changes in the default section or a section which will match your hardware
16:39* vagrantc wonders if the default generated lts.conf should just include [Default] entries
16:40
<championofcyrodi>
thats a hard one vagrantc. it was really my ignorance, rushing and failure to read the full configuration file that was the issue.
16:41
PEBCAK
16:41telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
16:42
<championofcyrodi>
Perhaps putting some of the more common default values in the file would help. I could see a lot of users wanting to change the default SSH port, both for mapping conflict reasons as well as security through ambiguity.
16:42telex has joined IRC (telex!~telex@freeshell.de)
16:42
<championofcyrodi>
e.g. SSH_OVERRIDE_PORT is already in the file, so I wouldn't be adding it to the bottom under [OLD_MONITOR]
16:42
<vagrantc>
championofcyrodi: it's a pretty ig wall of text... so i understand why you did it that way
16:43
championofcyrodi: SSH_OVERRIDE_PORT doesn't sound like a common option to me
16:43
<championofcyrodi>
but what if your SSHFS is behind a proxy that already uses 22?
16:43* vagrantc wonders if it isn't already too verbose
16:44
<vagrantc>
championofcyrodi: that's not a common configuration, from years of elping people with ltsp issues
16:44alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
16:44
<championofcyrodi>
The cloud is changing the game.
16:45
<vagrantc>
but we don't really have any mechanism to check what options people are using
16:45
<championofcyrodi>
true
16:45
<vagrantc>
LTSP over the cloud would be impressively poor performance
16:45
i guess if you were using NX or something similar, it might work...
16:45
<championofcyrodi>
LTSP instances distributed with out of the box configurations would not be.
16:46
NX is def. faster than X
16:46
thats what most of my fat client users are using.
16:46
OpenNX
16:47
thin clients just dont have the screen draw rates they desire.
16:47
(they being the users i have)
16:48* vagrantc keeps meaning to look into supporting the x2go client in LTSP
16:49
<vagrantc>
x2go has it's own thin client system, but i'm fairly certain the client could work with LTSP
16:50
i guess the server-side support isn't in debian though. hrmpf.
16:50
<championofcyrodi>
I'm using FreeNX on the server side for NX connections.
16:50
seems to work pretty well in 14.04 using the precise release.
16:51
the authentication issues have been a pain for me to troubleshoot in the past.
16:51
before i got on fat clients, i was looking for a way to integrate NX as a 'background' session option on the login screen... heh
16:52
gave up pretty quick
16:52
<vagrantc>
it would be feasible to support in LDM ...
16:52
it currently supports both ssh and rdp
16:54
<championofcyrodi>
its hard to say its really worth it... I see LTSP as commonly used for two things... 1.) Old Hardware where buying new isnt an option, 2.) Companies who can afford newer hardware, but want to streamline their workstations into something more efficient. For me its the 2nd option.
16:54
For us, a $400 NUC w/ ~20 WATTs is much cheaper than a $1200 Desktop ~350 WATTs.
16:55
<vagrantc>
sure
16:55
<championofcyrodi>
So with 16GB on NUC, Fat Client is really ideal replacement for a desktop if the user has backend server hardware they can use.
16:56
So we fall under option 2 and wouldnt really benefit from NX support via Thin client... but people in option 1 def. would
16:56
<vagrantc>
yeah, even fairly old hardware performs as well if not better as a fat client
16:56
<championofcyrodi>
Or low bandwidth maybe... fat client images are big
16:57
<vagrantc>
i mean, core2 systems with 2-4GB of ram ...
16:57
<cryptrat>
as soon as i added the LTSP_FATCLIENT=false the ldm session quit loading
16:57
<vagrantc>
but the image size doesn't affect how much data is transferred, it only transfers blocks that are actually used
16:58
<championofcyrodi>
rly?
16:58
<vagrantc>
yes
16:59
cryptrat: so, it presents the login screen, but login fails?
17:00
<championofcyrodi>
still... you can get up to 1GB pretty quick w/ Unity, thunderbird, pidgin/empathy, chrome...
17:00
<vagrantc>
sure
17:00
can't make something from nothing, but with reasonable expectations... hah! :)
17:01
<championofcyrodi>
I'm curious as to how a thin client would work inside docker... i got X forwarding to work a few weeks back... but had issues w/ an actual desktop session... X couldnt start because there were no virtual consoles available...
17:01
like tty7
17:02
i did some googling, but apparently there arent many people trying to run X sessions in Docker yet. However, I used to run X sessions in solaris containers, and switch tty via keyboard to switch container desktop sessions... so i know its possible.
17:03
so i bet thin clients would work fine since the X session is still on the client side.
17:04
<vagrantc>
right
17:16dsugar100 has joined IRC (dsugar100!~dsugar@columbia.tresys.com)
17:19
<cryptrat>
yes i log in and get prompt failed to load session with a log out button
17:19
take out the fat_client=false and it loads just fine
17:25
<championofcyrodi>
is it possible to configure tftpd to use something like 'SERVER2' if 'SERVER' is not available/fails?
17:29
<cryptrat>
could if have something to do with this error: Exported device is too big for me. Get 64-bit machine
17:37
<vagrantc>
cryptrat: you probably need to install a session manager on your server
17:37
cryptrat: apt-get install ldm-server
17:39
cryptrat: wait, that would happen long before you get to the login screen
17:39
<cryptrat>
ldm-sever is already the newest version
17:39
<vagrantc>
cryptrat: the "exported device is too big" error
17:40
cryptrat: ls /usr/share/xsessions/*.desktop
17:40
<cryptrat>
i don't get that if i boot a test vm, but on the physical hardware i d
17:40
<vagrantc>
you're probably not booting the same environment, then...
17:44cryptrat has left IRC (cryptrat!32c3bb3e@gateway/web/freenode/ip.50.195.187.62, Quit: Page closed)
17:45cryptrat has joined IRC (cryptrat!32c3bb3e@gateway/web/freenode/ip.50.195.187.62)
17:46
<cryptrat>
i show the gnome and ubuntu.desktop files
17:50
<championofcyrodi>
holy jeez... it worked..
17:50
NUC -> LAN DHCP -> VLAN Interface -> Firewall -> CentOS Host -> Docker LTSP Container (TFTP) -> nbd/ltsp session!
17:56
<vagrantc>
championofcyrodi: congrats!
18:11
<championofcyrodi>
and since the DHCP is on the normal LAN, the DNS hosts are the proper hosts from that LAN, rather than the DNS behind the firewall the container uses.
18:18
<bennabiy>
championofcyrodi: ok, so post a howto :)
18:19
vagrantc: I agree about only having [DEFAULT] under generated lts.conf since hardly anyone actually reads through all the comments, and usually just appends their changes to the end of a file.
18:23
<vagrantc>
i wonder if lts.conf works with the default section being the last section ...
18:38vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
18:42cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 250 seconds)
18:42
<championofcyrodi>
bennabiy: http://championofcyrodiil.blogspot.com/2014/08/ubuntu-1404-ltsp-docker-container.html
18:42
Do you mean post a 'how to' somewhere else?
18:43
<bennabiy>
great. Thank you :) You could always put a howto on the UbuntuLTSP page
18:44cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
18:46
<cryptrat>
anyone have any ideas why the ltsp_fatclient=false would stop the client from being able to load an ldm session, i get to the login screen but it won't load
18:48
<bennabiy>
championofcyrodi: Not sure if you noticed, but the <stdio.h> etc includes got stripped from your blog (June)
18:48
<championofcyrodi>
huh... didn't notice that...
18:50
that's my work around i put together for the screen locking back in june... it works pretty well most of the time... except when you switch input X using some other Xforwared application...
18:50
<bennabiy>
ended up with something like <unistd .h=""></unistd>
18:50
<championofcyrodi>
so i changed it to read from /dev/input/mouse0
18:50
<bennabiy>
Yes, I was looking over it.
18:50
<championofcyrodi>
which works most of the time except when you use a physical KVM because i'm not 'reconnecting'
18:51
<bennabiy>
You could use the updated LDM, which now fills in the shadow with the current user
18:52
<championofcyrodi>
does it read from the host shadow file?
18:52
(ltsp server)
18:52
<bennabiy>
No, it relies on the fact that the host accepted the input from the ssh connect and hashes that password
18:52
<championofcyrodi>
ooo... that is fancy.
18:52
<bennabiy>
it only does it if the host authenticated the session
18:52
<championofcyrodi>
that will work perfectly
18:53
<bennabiy>
you should be able to grab the ppa from alkis or myself (I think alkisg's daily build should have the update by now)
18:57
https://code.launchpad.net/~ltsp-upstream/+archive/ubuntu/daily
18:57
or...
18:57
<championofcyrodi>
nice. I'll definitely look in to it at a later time. especially when i start getting into system hardening in a month or so
19:00
<bennabiy>
or ppa:bennabiy/ldm-test if that one doesn't work?
19:14ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 244 seconds)
19:41ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
19:59mealstrom1 has joined IRC (mealstrom1!~Thunderbi@46.63.63.163)
19:59mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 250 seconds)
20:04vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
20:25cryptrat has left IRC (cryptrat!32c3bb3e@gateway/web/freenode/ip.50.195.187.62, Ping timeout: 246 seconds)
20:47cryptrat has joined IRC (cryptrat!32c3bb3e@gateway/web/freenode/ip.50.195.187.62)
20:48* vagrantc wonders what would be a relevent replacement on Ubuntu for ldm-server Recommends: gnome-session | x-session-manager | x-window-manager
20:49* vagrantc is likely to change gnome-session to mate-desktop or something for Debian
20:51
<championofcyrodi>
latest gnome-session fails sessions create w/o 3D support, even if requesting 2D Ubuntu session via NX
20:51
with a really nice error about a fail whale being dead...
21:03bitcheker has left IRC (bitcheker!~bitchecke@dynamic-adsl-62-10-103-15.clienti.tiscali.it, Quit: {exiting})
21:03championofcyrodi has left IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
21:45
<vagrantc>
hrm. seems like debian jessie doesn't default to loading the "loop" module, which causes failures with ltsp-update-kernels when used in ltsp-pnp mode ...
21:45
i guess ltsp-update-kernels could just "modprobe loop"
21:58adrianorg has left IRC (adrianorg!~adrianorg@177.156.57.132, Ping timeout: 240 seconds)
22:01adrianorg has joined IRC (adrianorg!~adrianorg@187.113.219.207)
22:07Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
22:17dsugar100 has left IRC (dsugar100!~dsugar@columbia.tresys.com, Quit: dsugar100)
22:19
<cryptrat>
does dnsmasq interfere with normal dns?
22:23
<vagrantc>
it can...
22:23
depends on how you've got it configured
22:23
i think ubuntu may have some default dnsmasq configuration?
22:24
<cryptrat>
just the default ltsp/proxydhcp
22:25
and i think i finally got it to work... had to install ubuntu-desktop to my server for the fatclient=false to find the ldm session and its running much faster
22:25
but my server seems to keep losing dns
22:25
add dns server to the resolv.conf and the thin client can route
22:26
but thats just a quick fix
22:27adrianorg has left IRC (adrianorg!~adrianorg@187.113.219.207, Ping timeout: 240 seconds)
22:29adrianorg has joined IRC (adrianorg!~adrianorg@179.180.171.142)
22:30
<vagrantc>
cryptrat: if /etc/dnsmasq.d/ltsp.conf might have something that disables dns
22:30
cryptrat: you might want to comment that out and restart dnsmasq
22:31
or uncomment it ... bind=0 or something?
22:35
<cryptrat>
i left it default port=0
22:36
<vagrantc>
i think you want to comment that out and restart dnsmasq
22:36
<cryptrat>
could i set the dns in the interfaces?
22:37
<vagrantc>
you've basically told dnsmasq "don't do dns queries", and ubuntu uses dnsmasq by default to look for dns queries ...
22:37* vagrantc wonders what the point of setting port=0 in dnsmasq is about
22:37
<vagrantc>
i guess you used to have to do that to not break dns because of some other issue?
22:39
cryptrat: sorry it's so confusing.
22:39
-p, --port=<port> Listen on <port> instead of the standard DNS port (53). Setting this to zero completely disables DNS function, leaving only DHCP and/or TFTP.
22:41
<cryptrat>
i guess thats what you want though because the server isn't functioning as a dhcp, my router is
22:41
right?
22:43
<vagrantc>
no.
22:43
your server is configured to use dnsmasq to look for it's DNS, so you want to comment out port=0, otherwise it will be asking dnsmasq for dns, and dnsmasq won't be listening.
22:44
if you're doing proxydhcp, you need the dhcp and tftp support.
22:44
and if you don't believe me, just try it. :P
23:01vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
23:03cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 250 seconds)
23:05cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
23:25ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 240 seconds)
23:30
<cryptrat>
commenting that out doesn't seem to change anything, did restart dnsmasq and reboot the client
23:34
neither does setting the dns in the lts.conf seem to do anything
23:41
gotta be something other than dnsmasq, as the server itself isn't resolving even if i stop the dnsmasq service