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


Channel log from 13 March 2015   (all times are UTC)

00:27gbaman has joined IRC (gbaman!~gbaman@31.205.109.64)
00:29roue has left IRC (roue!~roue@66-188-172-213.dhcp.stcd.mn.charter.com, Ping timeout: 264 seconds)
00:31gbaman has left IRC (gbaman!~gbaman@31.205.109.64, Ping timeout: 240 seconds)
00:47gbaman has joined IRC (gbaman!~gbaman@31.205.109.64)
03:12yomama_ has joined IRC (yomama_!c6004c66@gateway/web/freenode/ip.198.0.76.102)
03:12roue has joined IRC (roue!~roue@66-188-172-213.dhcp.stcd.mn.charter.com)
03:18yomama_ has left IRC (yomama_!c6004c66@gateway/web/freenode/ip.198.0.76.102, Quit: Page closed)
03:59doctari has left IRC (doctari!~doctari@2602:30a:2ccf:9f00:c407:8014:d6a2:f492, Ping timeout: 256 seconds)
04:12doctari has joined IRC (doctari!~doctari@2602:30a:2ccf:9f00:18fd:5aec:b26d:7ae5)
04:15gbaman has left IRC (gbaman!~gbaman@31.205.109.64, Remote host closed the connection)
04:28vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
05:09work_alkisg is now known as alkisg
05:27gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
05:30telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
05:31gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 245 seconds)
05:32telex has joined IRC (telex!teletype@freeshell.de)
06:24ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
06:28gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
06:33gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 252 seconds)
06:57staffencasa has left IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu, Read error: Connection reset by peer)
06:58staffencasa has joined IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu)
07:30khildin has joined IRC (khildin!~khildin@ip-83-134-135-161.dsl.scarlet.be)
08:23khildin has left IRC (khildin!~khildin@ip-83-134-135-161.dsl.scarlet.be, Quit: I'm gone, bye bye)
08:46ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 250 seconds)
08:49ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
09:34khildin has joined IRC (khildin!~khildin@209.105-245-81.adsl-dyn.isp.belgacom.be)
10:26alkisg has left IRC (alkisg!~alkisg@srv1-dide.ioa.sch.gr, Quit: Leaving.)
10:28work_alkisg has joined IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr)
10:53khildin has left IRC (khildin!~khildin@209.105-245-81.adsl-dyn.isp.belgacom.be, Ping timeout: 272 seconds)
11:05khildin has joined IRC (khildin!~khildin@209.105-245-81.adsl-dyn.isp.belgacom.be)
11:08khildin has left IRC (khildin!~khildin@209.105-245-81.adsl-dyn.isp.belgacom.be, Client Quit)
11:34khildin has joined IRC (khildin!~khildin@ip-83-134-135-161.dsl.scarlet.be)
12:31Faith has joined IRC (Faith!~paty@unaffiliated/faith)
12:35gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
12:35gbaman has joined IRC (gbaman!~gbaman@31.205.109.64)
12:56khildin has left IRC (khildin!~khildin@ip-83-134-135-161.dsl.scarlet.be, Read error: Connection reset by peer)
13:08gbaman has left IRC (gbaman!~gbaman@31.205.109.64, Remote host closed the connection)
13:18gbaman has joined IRC (gbaman!~gbaman@31.205.109.64)
14:30vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
14:43khildin has joined IRC (khildin!~khildin@209.105-245-81.adsl-dyn.isp.belgacom.be)
15:05vsuojanen has joined IRC (vsuojanen!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com)
15:18khildin has left IRC (khildin!~khildin@209.105-245-81.adsl-dyn.isp.belgacom.be, Ping timeout: 240 seconds)
15:21telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
15:22telex has joined IRC (telex!~telex@freeshell.de)
15:35yomama has joined IRC (yomama!0c3020c5@gateway/web/freenode/ip.12.48.32.197)
15:39khildin has joined IRC (khildin!~khildin@ip-83-134-135-161.dsl.scarlet.be)
15:39vsuojanen has left IRC (vsuojanen!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com, Ping timeout: 256 seconds)
15:41callan has joined IRC (callan!c0c53646@gateway/web/freenode/ip.192.197.54.70)
15:42
<callan>
hi folks, i've got an LTSP network up and running. I have a sensitive simulation program that everyone needs to pass an input file to, and receive an output file from. However, it's been requested that users not be able to copy out the binary in question.
15:43
is it possible to say, install the program on the server instead of in the image, and somehow write a script to send files in and out?
15:46vsuojanen has joined IRC (vsuojanen!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com)
15:49yomama_ has joined IRC (yomama_!0c3020c5@gateway/web/freenode/ip.12.48.32.197)
15:50yomama has left IRC (yomama!0c3020c5@gateway/web/freenode/ip.12.48.32.197, Ping timeout: 246 seconds)
16:09Markus_123 has joined IRC (Markus_123!~Markus123@192-164-48-118.adsl.highway.telekom.at)
16:10Markus_123 has left IRC (Markus_123!~Markus123@192-164-48-118.adsl.highway.telekom.at, Remote host closed the connection)
16:30awei has joined IRC (awei!4b44c5f9@gateway/web/freenode/ip.75.68.197.249)
16:31
<fiesh>
callan: I don't understand, why don't you just remove the read permission from the binary?
16:34Markus_123 has joined IRC (Markus_123!~Markus123@192-164-48-118.adsl.highway.telekom.at)
16:36
<callan>
fiesh: it's my understanding that there are a number of ways around that such as a debugger. Personally I think the read permission is enough, but I've been asked to look for a more complete solution.
16:37
My idea is this: users put their input into a directory, and a server side job picks up the file, runs the program and deposits the output to the user's home directory
16:37
so the program is actually run on the privilaged account, not the regular user's
16:39
<fiesh>
I don't really think there's any need to do anything besides remove the read permission, but if you want to do it like that, just use a script that is triggered by a cron job every minute?
16:43zama_ has left IRC (zama_!~zama@81.4.123.134, Ping timeout: 272 seconds)
16:43zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776)
16:54gbaman_ has joined IRC (gbaman_!~gbaman@31.205.104.150)
16:58gbaman has left IRC (gbaman!~gbaman@31.205.109.64, Ping timeout: 256 seconds)
16:59gbaman_ has left IRC (gbaman_!~gbaman@31.205.104.150, Ping timeout: 244 seconds)
17:02
<awei>
hi, trying to set up thin client, but after pxelinux.0 is loaded, i get a blank screen and then "mount: mounting /dev/nbd0 on /root failed: Invalid argument". any ideas?
17:02
I'm guessing it has something to do w/ this line in my pxelinux.cfg "append ro initrd=initrd.img-3.13.0-46-generic init=/sbin/init-ltsp quiet splash nbdroot=192.168.9.10 root=/dev/nbd0"
17:13yomama_ has left IRC (yomama_!0c3020c5@gateway/web/freenode/ip.12.48.32.197, Ping timeout: 246 seconds)
17:15yomama has joined IRC (yomama!0c3020c5@gateway/web/freenode/ip.12.48.32.197)
17:22work_alkisg is now known as alkisg
17:24
<alkisg>
awei: why do you need to specify the nbdroot ip, is it different from your dhcp server?
17:24
<awei>
i stuck that in there because w/o it i was getting a connection time out
17:24
<alkisg>
awel, is that ubuntu? which version?
17:25
<awei>
alkisg: i was flailing around and found that adding that line made it work. yes, i'm using ubuntu 14.04.2 as the LTSP server
17:25
alkisg: at least it made me get past the connection time out error
17:25
<alkisg>
What about your dhcp server, where is it?
17:25
<awei>
dhcp server is served from Ubuntu as well using isc-dhcp-server
17:26
<alkisg>
Do you happen to also have a router that serves as a dhcp server?
17:26
<awei>
no, it's all VMs right now using host-only network w/o a DHCP server
17:26
<alkisg>
Virtualbox?
17:26
<awei>
yessir
17:27
<alkisg>
Virtualbox does have its own dhcp server, did you disable that?
17:27
<awei>
correct me if i'm wrong, but i think the networking stuff is working
17:27
yes, the dhcp server is disabled
17:27
the thin client can get to the pxelinux.0 file and start running
17:27
<alkisg>
Usually the problem with getting pxelinux but not nbd is a second dhcp server
17:27
So, 192.168.9.10 is your vbox host-only subnet, and it's served by isc-dhcp?
17:28
*and it's your server's vboxnet0 ip...
17:28
<awei>
yes, correct
17:28
<alkisg>
OK, let's try it,
17:28
<awei>
sorry... try which?
17:28
<alkisg>
put break=mount in pxelinux.cfg as a parameter, right next to root=xxx,
17:28
remove quiet splash,
17:29
and you're supposed to get an initramfs shell there
17:29
So there at the client, try this, but put 192.168.9.10 as the server ip:
17:29
!nbdclient
17:29
<ltsp`>
I do not know about 'nbdclient', but I do know about these similar topics: 'nbd-client'
17:29
<alkisg>
!nbd-client
17:29
<ltsp`>
nbd-client: To try mounting the NBD image from the client initramfs: nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0
17:29
<awei>
oh whoa
17:29
i'm loading initrd.img now
17:29
didn't get that last time
17:29
got to initramfs
17:30
<alkisg>
nbd is a lot after initrd, but you don't see it if you have quiet splash
17:30
<awei>
so i got to "Spawning shell with initramfs" and dropped into the the initramfs shell
17:30
<alkisg>
Right, try the nbd-client command there
17:30
<awei>
ok...
17:33awei has left IRC (awei!4b44c5f9@gateway/web/freenode/ip.75.68.197.249, Quit: Page closed)
17:33awei has joined IRC (awei!4b44c5f9@gateway/web/freenode/ip.75.68.197.249)
17:33
<awei>
hi, sorry... connection dropped... i get "Negotiation: Error SErver closed connection"
17:34
<alkisg>
What's the output of this? ls -lha /opt/ltsp/images
17:34
<awei>
might be my syntax error. lemme try again
17:34
no such file or directory
17:34
<alkisg>
nbd-client 192.168.9.10 -N /opt/ltsp/i386 /dev/nbd0
17:35
You haven't ran ltsp-build-client?
17:35
<awei>
i did on my server
17:35
<alkisg>
Ah sorry I meant on the server
17:35
<awei>
on the LTSP server
17:35
<alkisg>
nbd-client command => on the client initramfs,
17:35vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
17:35
<alkisg>
ls -lha command => on the server
17:35
<awei>
yup, i did that
17:35
ok, hold...
17:35* alkisg waves to vagrantc
17:36
<awei>
i have /opt/ltsp/images/i386.img
17:36
<alkisg>
vagrantc: food for thought, for whenever you have time for this... what would you prefer for lts.conf syntax, ini file, yaml, or plain python? :)
17:37
awei: egrep -rv '^#' /etc/nbd*
17:37
Put the results to pastebin
17:39
vagrantc: I recently read about yaml, and it sounded like a good candidate... for example, I don't think numbering the RCFILE_xx commands makes more sense than declaring them as list of strings (in yaml syntax it's very readable)
17:39
<awei>
alkisg: http://pastebin.com/bX0i99WL
17:39
<alkisg>
awei: on the server, try `tail -f /var/log/syslog`, then run the nbd-cilent command on the client again, then check for errors
17:40
<awei>
Negotiation failed/8a: requested export not found.
17:40
hmm... that looks promising
17:46
<alkisg>
Did you restart your nbd-server after generating the image?
17:46
(for the first time?)
17:46
Because your ltsp_i386.conf file seems fine...
17:46
<callan>
one more question, is there a way to send a message from the server to a client's x session? like a popup?
17:47
<awei>
alkisg: i'll do that now
17:50
it looks like it's working... though it says" [ 1129.301297] nbd0: unkonwn partition table" at the prompt
17:52
ok, i was wrong. i just get the prompt back
17:54
<alkisg>
callan: see epoptes
17:54
!epoptes
17:54
<ltsp`>
epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org
17:54
<callan>
perfect
17:54
<alkisg>
callan: about your other question, google for inotify, although it's completely unrelated to ltsp
17:55
awei: the unknown partition table message is normal
17:55
<awei>
ok, so, just let it churn?
17:55
<alkisg>
What is "churn"? sorry i'm not a native english speaker...
17:55
We all see the message on each boot if that's what you're asking
17:56
<awei>
sorry, just let it run
17:56
<alkisg>
Yup... if you remove break=mount now, does it boot? if not, what's the error message?
17:57
<awei>
lemme try
17:59
alkisg: "Failure: Insufficient information to set up nbd,..."
17:59
<vagrantc>
alkisg: i've never really liked yaml to be honest
17:59
<alkisg>
awei: it sounds like you changed more stuff in pxelinux.cfg/default, what's the current command line?
18:00
vagrantc: so we should keep it in an ini-like syntax?
18:01
(python configparser, to be exact, because ini files are loosely defined, e.g. how to declare a var with multiple lines...)
18:01
<awei>
alkisg: it's at initramfs prompt is that what you mean? or is this what you mean: "append ro initrd=initrd.img-3.13.0-46-generic init=/sbin/init-ltsp nbdroot=192.168.9.10 root=/dev/nbd0"
18:01
<alkisg>
awei: generally you shouldn't need nbdroot there
18:01
<awei>
ok, i'll try taking it out now.
18:02
<alkisg>
awei: also, do you have rootpath=/opt/ltsp/i386 in your dhcpd.conf?
18:02
<awei>
lemme look...
18:02
<vagrantc>
alkisg: ini-style seems fine to me...
18:02
<awei>
yea: option root-path "/opt/ltsp/ie86";
18:03
<vagrantc>
alkisg: any backwards-incompatible changes with configparser?
18:03
<alkisg>
vagrantc: too little to worry about, but the major changes would be "no LDM* variables, multiple configuration files in /etc/ltsp/config.d/..."
18:04
So I wouldn't worry much about backwards compatibility with ltsp6, lts.conf files will need to be rewritten anyway to replace the actual content with newer variables
18:04
<vagrantc>
right
18:05
wildcard matching?
18:05
<alkisg>
E.g. with lightdm we probably shouldn't use xrandr_mode_0 but xorg's preferred mode, or however wayland calls it
18:05
<vagrantc>
i.e. [192.168.53.*] ?
18:05
<alkisg>
Phantomas did implement wildcard matching, yes
18:05
Do we also allow python scripts in the configuration dir?
18:06
Or that would be only ltsp code and not sysadmin code?
18:07
<vagrantc>
alkisg: i'd be wary of python-only code in the config scripts, but making it an option could be really valuable
18:08
right now ltsp_config.d sort of fills that role allowing arbitrary code in config
18:08
<alkisg>
The problem is that some things can't be done client-side
18:08
E.g. suppose that the sysadmin needs to do load balancing based on available server ram
18:08
<vagrantc>
sure
18:09
you don't think any processing should be done client-side?
18:09
<alkisg>
I think both options are needed
18:09
<vagrantc>
ok, good :)
18:09
<alkisg>
And each script should go wherever it belongs best...
18:10* alkisg would like to have ltspd ready enough for debconf, in order to commit it in trunk there
18:11
<alkisg>
I think it can easily support reading lts.conf from tftp if we do want to use it with ltsp 5 too...
18:12
Btw, I was checking "vagrant" today, it sounds like a good way to create ltsp "chroots", but I haven't yet tested it
18:13
<awei>
alkisg: Hi... so, for whatever reason, i need the nbdroot. i added the port: nbdroot=192.168.9.10,10809 and i get "Negotiation .Error: It looks like you're trying to connect to a newstyle server with a the oldstyle protocol.
18:13
<alkisg>
Yes that's not a correct syntax
18:13
<awei>
oh ok... n.m...
18:14
<alkisg>
Try nbdroot=10.168.9.10:/opt/ltsp/i386
18:14
<awei>
k
18:14
<alkisg>
But you should check why you need it
18:14
E.g. by removing it, putting break=mount, and running `cat /run/net-eth0.conf` in the initramfs
18:14
<awei>
ok, i'll try that too.
18:16
so, adding the file directly worked... i get ubuntu gui now!
18:16
lemme check on the networking issue
18:17yomama has left IRC (yomama!0c3020c5@gateway/web/freenode/ip.12.48.32.197, Ping timeout: 246 seconds)
18:18
<vagrantc>
alkisg: yeah, if we start using "vagrant" that'll get pretty confusing. :)
18:18
<alkisg>
:D
18:18
<vagrantc>
alkisg: i've also wondered about puppet, chef, propellor, etc.
18:19
<alkisg>
I only care enough about that part in order to "remove it" from ltsp, the documentation and the code on how to build a vm
18:19
If we could just link to some tools it'd be great
18:19
And leave our own part to the ltsp-client package
18:19
<vagrantc>
so killing off ltsp-build-client entirely?
18:20
should be feasible, i guess.
18:20
<awei>
alkisg: so, i think the issue is the ROOTSERVER='192.168.9.1'. where doe s that get configured?
18:20
<alkisg>
awei: if your host doesn't have that IP, then it's your virtualbox's dhcp server talking there
18:20
<vagrantc>
alkisg: the only thing i would worry about is more inconsistancy if it's just "install package foo"
18:21
alkisg: a lot of tools add random cruft
18:21
<alkisg>
vagrantc: I saw that vagrant support installing e.g. centos anywhere, we don't have scripts for that now
18:21
And if it supports kvm too, maybe it has an rpi "box" as well?
18:21
<vagrantc>
alkisg: there would still need to be ltsp-client packages
18:21
<alkisg>
Yes, of course
18:22
Ah, you mean that we would need instructions to "launch the vm and install ltsp-client"?
18:22
I think that'd be trivial...
18:22
<vagrantc>
wait, you're talking about building a vm and then generating the image out of that?
18:23
<alkisg>
E.g. `vagrant init ubuntu/precise32', 'vagrant up', "install ltsp-client there", then just run ltsp-update-image by pointing to the .vdi file
18:24
We can easily export the .vdi directly if we prefer, but that's a thought for later on, it will work great with btrfs snapshots
18:25
<vagrantc>
doesn't vagrant have hooks so we could install ltsp-client automatically?
18:25
<alkisg>
I haven't looked, it probably does. Maybe it's specific to each box, some use puppet, some chef...
18:26
From the ltsp side, we only care about the last 2 parts, we don't even care if the users are using vagrant or vbox or kvm or chroots...
18:26
<vagrantc>
do we end up with extra dependencies in the image?
18:26
<alkisg>
I can't comment much on vagrant, I haven't run it yet :)
18:26
I don't think so though
18:27
<vagrantc>
i guess i just want to make sure there's a way to install that's only running a single command, rather than "build a vm with X, log into the vm, install Y Z"
18:28
<alkisg>
One may also use lxc to maintain his chroots
18:28
<vagrantc>
alkisg: i presume you're not planning on abandoning the "ltsp-update-image /" ltsp-pnp method?
18:29
<alkisg>
It won't make any difference, the code will be there, running it upon a .vdi or upon / is small difference
18:29
(or upon a chroot)
18:29
<vagrantc>
right
18:29
<alkisg>
The preparations for this, i.e. init-ltsp.d, were the significant part...
18:29
<vagrantc>
i've also wondered about updating an existing image with an aufs/overlayfs mount of the old image
18:30* vagrantc nods
18:30
<vagrantc>
would make cross-distro images easier to maintain
18:37alkisg is now known as work_alkisg
19:01
<vagrantc>
eesh. ltsp-docs is really out of date
19:03
<awei>
work_alkisg: fwiw, i restarted my vms and did not need the nbdroot command anymore. thanks for all your help.
19:24gbaman has joined IRC (gbaman!~gbaman@members.unit1.farsetlabs.org.uk)
19:44awei has left IRC (awei!4b44c5f9@gateway/web/freenode/ip.75.68.197.249, Ping timeout: 246 seconds)
19:59cliebow has left IRC (cliebow!~cliebow@gw-rsu24-co.rsu24.org, Quit: Ex-Chat)
20:39Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
20:44gbaman has left IRC (gbaman!~gbaman@members.unit1.farsetlabs.org.uk, Remote host closed the connection)
21:44khildin has left IRC (khildin!~khildin@ip-83-134-135-161.dsl.scarlet.be, Remote host closed the connection)
21:45telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
21:46telex has joined IRC (telex!teletype@freeshell.de)
22:00vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 256 seconds)
22:03ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 256 seconds)
22:30gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
22:34gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 250 seconds)
23:22ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
23:42Markus_123 has left IRC (Markus_123!~Markus123@192-164-48-118.adsl.highway.telekom.at, Quit: Leaving)