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


Channel log from 29 March 2010   (all times are UTC)

01:04alexqwesa has quit IRC
01:04alexqwesa has joined #ltsp
01:16Appiah has quit IRC
01:16AndyGraybeal has quit IRC
01:16Patina has quit IRC
01:16highvoltage has quit IRC
01:16yanu has quit IRC
01:16vlt has quit IRC
01:16daya has quit IRC
01:16pem725 has quit IRC
01:16abeehc has quit IRC
01:16jhutchins_lt has quit IRC
01:16jimcooncat has quit IRC
01:16jbrett- has quit IRC
01:16vbundi has quit IRC
01:16moldy has quit IRC
01:16knipwim_ has quit IRC
01:16Shingoshi has quit IRC
01:35Shingoshi has joined #ltsp
01:35daya has joined #ltsp
01:35highvoltage has joined #ltsp
01:35jimcooncat has joined #ltsp
01:35yanu has joined #ltsp
01:35jbrett- has joined #ltsp
01:35pem725 has joined #ltsp
01:35abeehc has joined #ltsp
01:35jhutchins_lt has joined #ltsp
01:35vbundi has joined #ltsp
01:35Appiah has joined #ltsp
01:35moldy has joined #ltsp
01:35knipwim_ has joined #ltsp
01:35AndyGraybeal has joined #ltsp
01:35Patina has joined #ltsp
01:35vlt has joined #ltsp
01:35try2free has joined #ltsp
01:55F-GT has joined #ltsp
01:57vagrantc has quit IRC
02:02F-GT has quit IRC
02:04japerry has joined #ltsp
02:18F-GT has joined #ltsp
02:33F-GT has quit IRC
02:51mikkel has joined #ltsp
02:53F-GT has joined #ltsp
03:32leio has quit IRC
03:35leio has joined #ltsp
03:51F-GT has quit IRC
04:07F-GT has joined #ltsp
05:26alkisg has quit IRC
05:41highvoltage has quit IRC
05:43highvoltage has joined #ltsp
06:02jimcooncat has quit IRC
06:04hersonls has joined #ltsp
06:18Selveste1 has quit IRC
06:22daya has quit IRC
06:28alkisg has joined #ltsp
06:29pmatulis has joined #ltsp
06:49moldy has quit IRC
06:50moldy has joined #ltsp
06:55highvoltage has quit IRC
06:57highvoltage has joined #ltsp
07:27cliebow has joined #ltsp
07:31vvinet has joined #ltsp
07:34windmill has joined #ltsp
07:40
<_UsUrPeR_>
morning all
07:42
<vvinet>
good morning
07:45
<_UsUrPeR_>
I'm trying to figure out how to get all the open office variations (word processor, spreadsheet, etc...) to be known by the server/client as localapps. Right now, I have "ooffice" under LOCAL_APPS_MENU_ITEMS, but it's not creating an xprop command for OOo.
07:45
I have realized that instead of separate office executables, openoffice is opened by the same executable along with an option (i.e. -calc, -write, etc...) is anybody familiar with getting the menu items working?
07:48
<alkisg>
_UsUrPeR_: are you looking for the "normal" way, i.e. by opening them from the gnome menus, or are you looking for something special, e.g. a command line way?
07:49
Because for the "normal" way you just need to enable the local apps menu, you don't need to speficy any items...
07:49
LOCAL_APPS_MENU=True
08:28
<highvoltage>
hey alkisg
08:28
<alkisg>
Hi highvoltage
08:28
<highvoltage>
alkisg: since you're always on top of things, have you tested ltsp installation with the new ldm-server package and have you had it hang on installation again?
08:29
alkisg: mine still does and I have the newest package, which is weird.
08:30
<alkisg>
highvoltage: no, this week I'm programming an inetd-based bash server & a bash client to remote control ltsp clients, so I haven't tried anything new
08:30
<highvoltage>
alkisg: sounds like fun :)
08:30vbundi has quit IRC
08:30
<alkisg>
highvoltage: if it succeeds, I'll have no more use for italc, tcm, controlaula etc :)
08:31* alkisg is able to send text commands and receive text output both on thin + fat clients, and is working on getting binary data e.g. for screenshots..
08:31
<alkisg>
highvoltage: but do comment your experience on the bug report...
08:36
<highvoltage>
alkisg: yep! will try out. do you implement ssl as well?
08:36
<alkisg>
highvoltage: no, it's working over the existing ssh connection
08:36
So no need for authorization / encryption or whatever
08:36
(that's for fat clients)
08:36
<highvoltage>
alkisg: ah ok
08:36
<alkisg>
For thin clients, it's working directly on the server, so again no encryption is necessary
08:37
..and as a side-effect, I get automatic notifications of when clients boot / users logon / logoff etc...
08:37
The client is just a bash script, so it can run in 64mb as well.
08:38
<highvoltage>
alkisg: nice
08:39
alkisg: do you plan to make it something that could be included by default in ltsp one day?
08:39
<alkisg>
I'm trying to, e.g. I put lts.conf variables for clients that one might not want to control etc,
08:40
but for Lucid it's just going to be part of my "sch-scripts" project, which due to time constrains is greek only,
08:40
...but I'd like to internationalize it in the summer, if any native english speaker is interested on proofreading it
08:52
Yey! Binary transfers working :)
08:52
<cliebow>
8~)
08:59windmill has quit IRC
09:00litlebuda has joined #ltsp
09:00mikkel has quit IRC
09:03
<litlebuda>
hi all I am trying to enable nbdswap on ubuntu 9.10 but i cant find /var/lib/tftpboot/ltsp/i386/lts.conf should I instead edit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default ?
09:05slidesinger has joined #ltsp
09:10
<alkisg>
litlebuda: no, you need to create lts.conf
09:10
<litlebuda>
ok thanks alkisg
09:10
will try it out
09:20alexqwesa has quit IRC
09:20alexqwesa has joined #ltsp
09:46
<alkisg>
highvoltage, and anyone else that might be interested: I have two scripts ready, `sch-server` which runs from inetd on the ltsp server, and `sch-client` which runs both on the thin client as root and on the user session from /etc/xdg/autostart.
09:46
Now I'm creating the third and final script, `sch-send`, which will be used by the sysadmin to send commands to the clients and/or users, and I'd like some feedback on what its parameters should be.
09:46
I'm thinking: sch-send [-h] hostname | [-u] username | [-i] ip | [-m] mac-address command [params]
09:46
E.g. `sch-send ltsp123 poweroff`, or `sch-send ltsp123 firefox`.
09:46
The problem is that `poweroff` should be executed by the root sch-client (daemon), while `firefox` should be executed by the user sch-client.
09:46
So in order for that simple syntax to work, I'd need to list some specific commands (get-client-info, poweroff, reboot), to be executed by root, while all the others by the user sch-client. Is that acceptable? Any other commands that you'd need to run as roots on the clients?
09:49
(and alternative would for an additional [-r] parameter that would specify that the command should be executed by the root daemon)
09:51mikkel has joined #ltsp
09:59The_Code has joined #ltsp
10:30staffencasa has joined #ltsp
10:44Faithful has quit IRC
10:46reynolds has joined #ltsp
10:47
<reynolds>
can anyone help me get video running on my clients? whenever I play a video It displays black. I have VLC installed in the chroot.
10:58
<abeehc>
could have something to do with the client video card
10:58
vlc can be pretty verbose if run in terminal with like -vv
10:59Faithful has joined #ltsp
11:36windmill has joined #ltsp
11:37Gadi has joined #ltsp
11:44
<alkisg>
Yey! bash tcp sockets can transfer files from the client session (=localhost) to the server at 14 Mbyte/sec in my laptop!
11:50F-GT has quit IRC
11:57litlebuda has quit IRC
12:06F-GT has joined #ltsp
12:14
<moldy>
alkisg: nice :)
12:15
alkisg: i would prefer the extra switch solution, i think
12:16
<alkisg>
moldy: thanks, another teacher told me the same, so I'll implement that.
12:16
So far it seems stable; I transfered a whole .iso without problems
12:17
I think I'll have the framework ready in 2-3 days, so if anyone wants to package it separately from sch-scripts, it'll be very nice
12:19
bbiab
12:19reynolds has quit IRC
12:36staffencasa has quit IRC
12:40Lns has joined #ltsp
12:57Jinux has joined #ltsp
12:57Jinux has left #ltsp
12:58
<moldy>
alkisg: nice. i will take a look as soon as i find the time to
13:00ogra_cmpc has quit IRC
13:01jammcq has joined #ltsp
13:01
<jammcq>
hey kids
13:01ogra_cmpc has joined #ltsp
13:06
<Lns>
daddy!
13:06* Lns hugs jammcq
13:10staffencasa has joined #ltsp
13:21mgariepy has joined #ltsp
13:21ogra_cmpc has quit IRC
13:28vaix has joined #ltsp
13:28
<vaix>
is there CentOS integration on LTSP server side? Are there any best practices/concerns around using mixed distros? All our linxu servers today are CentOS. We have several stand-alone workstations running ubuntu
13:29
<Appiah>
should be no concerns regards different dists..
13:30
K12Linux = LTSP on Centos I think
13:31
<vaix>
Appiah: thanks.
13:31
LTSP work in combo w/ LVS - so I can have an HA/DR config for LTSP?
13:31
<Appiah>
I dont know what LVS is
13:31
and HA/DR either
13:32
<vaix>
LVS = linux virtual server. HA = High Availability, DR = Disaster Recovery
13:32
<Appiah>
LVS , yes
13:32
HA/DR Well there is ltsp-cluster
13:32
check that out and how you can put that togheter with your HA config today
13:33
<vaix>
thanks - will look there
13:35ogra_cmpc has joined #ltsp
13:48alkisg has quit IRC
13:51alkisg has joined #ltsp
14:08din_os has joined #ltsp
14:36arx has joined #ltsp
14:39din_os has quit IRC
14:48leio has quit IRC
14:52leio has joined #ltsp
14:53vagrantc has joined #ltsp
14:55cliebow has quit IRC
14:57pmatulis has quit IRC
15:02
<vaix>
perhaps I am dense... but is there a way to get LTSP w/out using the ISO ditributions? Can I download the source and compile/configure directly? Are RPM/deb files available?
15:04
<alkisg>
What .iso distributions?
15:04din_os has joined #ltsp
15:04
<alkisg>
E.g. in ubuntu you can get it with apt-get install ltsp-server, or apt-get source ltsp-server if you want the source, or aptitude download ltsp-server if you want the .deb...
15:04arauto has joined #ltsp
15:05
<vagrantc>
vaix: yes, you can install debian, ubuntu or fedora and then install the ltsp-server packages and then use ltsp-build-client to build the ltsp environment
15:05din_os has quit IRC
15:05
<alkisg>
vagrantc: does debian support tcp sockets in bash? E.g. exec 3<>/dev/tcp/localhost/22 ?
15:06
<vagrantc>
alkisg: i think i played with that back in 2001...
15:06
so i'm guessing so
15:06
<alkisg>
vagrantc: I got 3 scripts almost ready, 2 in bash and one in python, to send commands to ltsp clients
15:07
They reuse the ssh channel to transfer the commands
15:07
Do you think they'd belong upstream, given enough care of course?
15:08
The server script uses openbsd-inet + bash
15:08
The client script only bash ==> works in 64 MB ram clients,
15:08
<vagrantc>
possibly...
15:08
<alkisg>
and the command-send script python, so that it can be used as a module
15:09
Right now I'm tailoring them to my needs, but if there's a possibility to get them upstream, maybe I should give them more generic names... (e.g. now I'm calling them sch-server, sch-client and sch-send...)
15:10
http://bazaar.launchpad.net/~sch-devs/sch-scripts/trunk/revision/109
15:10
<vagrantc>
alkisg: and what sorts of things are you planning on doing with them that couldn't be done easily before?
15:11
<alkisg>
vagrantc: in /var/run/sch-server/* I have a list of sockets with mac/ip/user/host, so I can easily detect which user/host is on
15:11
<vagrantc>
oooh.
15:11
<alkisg>
I can send a poweroff to the clients or run cron jobs on them from the server
15:11
(no authentication needed)
15:11
I can send commands to the user sessions, be it on thin or fat clients
15:11
<vagrantc>
a restricted (or restrictable) set of commands?
15:11
<alkisg>
E.g. "sch-send user123 firefox"
15:11
<vagrantc>
sounds pretty cool.
15:11
<alkisg>
The root commands are restricted currently
15:12
(to poweroff, reboot, exit and sch-info)
15:12
The user commands are not restricted on purpose
15:12
The root commands are unencrypted, but they're using reverse connections, so they cannot be easily exploited
15:12
The user commands use the ssh channel, so they're encrypted
15:12
<vagrantc>
unencrrypted?
15:13
<alkisg>
poweroff/reboot => do they need encryption?
15:13
<vagrantc>
just curious how you implement them unencrypted if the communication channel is already encrypted
15:13
<alkisg>
There are 2 daemons per terminal, one that runs as root (always), and one that runs inside the user session
15:13
The one that runs as root is executed before ldm starts
15:14
So it connects to server:9570 on an unencrypted channel
15:14
<vagrantc>
ah.
15:14
<alkisg>
The other one is using ssh port forwarding, so it uses encryption
15:14
<vagrantc>
got it
15:14
<Gadi>
sounds like a system bus and a session bus
15:14
<alkisg>
(and connects to the same port)
15:14
<Gadi>
:)
15:15
<alkisg>
Each connection is only using one bash on the clients, so it needs minimum ram
15:15
And I've already started implementing some lts.conf options for not starting some of them...
15:15
(e.g. we might not want to run them in some hosts)
15:16
If you guys are interested, I should change the names to more generic ones, get rid of the sch-* prefix
15:16
...and we'll see in the future if it's worth to be put upstream.
15:17
Gadi, right, nice metaphor :)
15:18
<Gadi>
just something I was doodling on the side of my notebook while the professor waas teaching ;)
15:20* Gadi cheers alkisg on - and hopes he doesn't get sidetracked from this effort when people start talking about tubes and dbus over ssh and unicrons and all the other "correct" approaches to things
15:20
<Gadi>
:)
15:20
*unicorns
15:20
<alkisg>
Gadi, I've wasted 2 weeks on those :)
15:20
<vagrantc>
the one true cron
15:20
<alkisg>
...and another one on twisted :)
15:20
<vagrantc>
twisted?
15:20* vagrantc cringes
15:21
<alkisg>
BASH_ROCKS!
15:21
<Gadi>
Linux is a bizarre beast aint it? I mean what other OS can you have a twisted gimp talking to an oaf through a tube on dbus?
15:21
honestly
15:22
<alkisg>
Hehe
15:22
<Gadi>
it just sounds ridiculous
15:22
<vagrantc>
next hackfefst, we should play illuminati
15:23
<Gadi>
I'm waiting to sweep the nation with a project called Poopie
15:23
<vagrantc>
Gadi: speaking of hackfests, you register for debconf10?
15:24
<Gadi>
I have not
15:24
<vagrantc>
alkisg: i spent 6 hours writing up a debian/copyright file for gPXE ... probably roughly 30-40% done.
15:24
<alkisg>
Yey!
15:24* Gadi has been in a cave under a rock for two weeks
15:24
<vagrantc>
it's brutal
15:25
Gadi: well, you know, i *Expect* you to be there. :P
15:25
<Gadi>
hehe - can you email me the info?
15:25
I will never remember to do it otherwise
15:25* alkisg hopes he'll have gpxe as a boot option in debian/ubuntu cds pretty soon... :)
15:25
<Gadi>
I am rushing today to get everything I need done before the holiday
15:25
then, its back under a rock for me...
15:25
:P
15:26
<vagrantc>
ah, rocks.
15:31
<dba>
.oO(speaking about rocks.. vagrantc rocks too :)
15:31vbundi has joined #ltsp
15:33
<vbundi>
hey is Stephane's PPA meant to be used for both the chroot and the ltsp server?
15:33
<vaix>
is v5.199+ development public? It looks like the sourceforge repository only has 4.x product?
15:33
<alkisg>
vbundi: yes, if you're gonna use it, use it on both
15:34
!ltsp-source
15:34
<ltspbot`>
alkisg: "ltsp-source" :: at http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/files
15:34
<alkisg>
vaix: ^^^
15:34
<vaix>
tnx
15:34
<vbundi>
alright, thanks
15:35
<vagrantc>
vaix: ltsp 5.x is very different than ltsp 4.x, in the sense that you don't compile or download anything other than standard distribution packages now.
15:35
<alkisg>
!docs
15:35
<ltspbot`>
alkisg: "docs" :: For the most current documentation, see https://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
15:35
<alkisg>
vaix: ^^^
15:36
<vagrantc>
unless you're looking to port it to a new linux distro, just downloading the source isn't probably very usefull.
15:36
!ldm-source
15:36
<ltspbot`>
vagrantc: "ldm-source" :: at http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/files
15:36
<vagrantc>
heh.
15:36
<vaix>
I was very motivated a few hours ago to run this on CentOS.... but the more i read - it seems like rolling-my-own is bordering on lunacy and I should use a pre-supported distro...
15:36* alkisg did a throughout job on factoids ;)
15:37
<jammcq>
vaix: or convince a Redhat or Centos developer to get involved
15:37
<vaix>
jammcq: haha - if i had that pull i would. As is - be better spending my time doing the port myself then trying to convince ppl!
15:40windmill has quit IRC
15:41vaix is now known as vaix_afk
15:42
<vbundi>
after looking at both my amd64 and i386 chroot... I see that my /etc/apt/sources.list files are quite different... my i386 one is only 3 lines...
15:43
is the amd64 one a mirror of the local system vs i386 which is generated?
15:43
<vagrantc>
depends on how it was created
15:44
there's an option that copies the sources.list file from the server into the chroot
15:45
<vbundi>
well unless it is default when running the install from the alternate CD, I didn't choose any option afaik
15:45Gadi has left #ltsp
15:45
<vagrantc>
probably is a different default
15:46
but not knowing ubuntu too well, i can't say for sure.
15:47mathesis__ has joined #ltsp
15:47litlebuda has joined #ltsp
15:49
<Lns>
alkisg, I am also behind you 100% with what you're doing, I'm really happy this kind of functionality is starting to see the light of day... it's going to be a real killer feature of ltsp deployments
15:49
kind of makes ltsp terminals more 'lucid' (no pun intended)
15:49
<alkisg>
Thank you Lns... now I'm only missing some good program/variable names :D
15:49
<vbundi>
when updating my chroot... is the procedure, chroot /opt/ltsp/i386/ sudo apt-get update && sudo apt-get upgrade; ltsp-update-image --arch i386 ?
15:50
<Lns>
alkisg: i can help with that if you want =)
15:50mathesis_ has quit IRC
15:51
<alkisg>
Lns, ok, I got "sch-server", "sch-client" and "sch-send" the one that is used to send the commands
15:51
<Lns>
sch = ?
15:51
<alkisg>
...and I probably need to ditch the sch- in front... (school)
15:52
<Lns>
ah
15:52
<alkisg>
(the greek schools domain is sch.gr)
15:52
<Lns>
yeah, I dunno, my personal perspective is that ltsp != schools so we should keep that separate
15:52
<alkisg>
Sure, if it is to go upstream sometime, it'll need something with ltsp* in front
15:52ogra_cmpc has quit IRC
15:52
<Lns>
The basic idea of the programs are to gain control of terminals from the server/admin workstation, no?
15:53
<alkisg>
Yes
15:53
<Lns>
well, one name i had for my little project that went nowhere was "LNS" (yeah i know =p) but it stood for 'lucid node system'
15:53
kind of a strange name but i dunno, it does make the 'nodes' more 'lucid'
15:54
<alkisg>
Heh
15:54
<Lns>
I really liked "ltsp-manager" from ogra a while back
15:54
and it obviously doesn't leave anything to question about its functionality
15:54ogra_cmpc has joined #ltsp
15:54
<Lns>
lol, speak of the devil
15:54
<alkisg>
Hmmm that sounds good
15:55
ogra_cmpc: could we reuse the "ltsp-manager" name for a different, but similar project?
16:02hersonls has quit IRC
16:08_UsUrPeR_ has left #ltsp
16:18windmill has joined #ltsp
16:29vvinet has quit IRC
16:35mikkel has quit IRC
16:36pmatulis has joined #ltsp
16:43mgariepy has quit IRC
16:45alkisg has quit IRC
16:49Selveste1 has joined #ltsp
17:02jammcq has quit IRC
17:08Lns has quit IRC
17:15arx has quit IRC
18:07windmill has quit IRC
18:36ogra_cmpc has quit IRC
18:37ogra_cmpc has joined #ltsp
18:40mathesis_ has joined #ltsp
18:42mathesis__ has quit IRC
18:45staffencasa has quit IRC
19:03litlebuda has quit IRC
20:21try2free has joined #ltsp
20:26try2free has left #ltsp
20:28mgariepy has joined #ltsp
20:48pmatulis has quit IRC
21:25mgariepy has quit IRC
21:27mathesis_ has quit IRC
22:18arauto has quit IRC
22:40vagrantc has quit IRC
22:49daya has joined #ltsp
22:51alkisg has joined #ltsp
22:53vagrantc has joined #ltsp
22:55* alkisg renames sch-server, sch-client and sch-send to lcmd-server, lcmd-client and lcmd-send (Ltsp CoMmanD), and hopes that's acceptable...
23:25Egyptian[Home] has quit IRC
23:34tstafford has quit IRC
23:45ogra_cmpc has quit IRC
23:46ogra_cmpc has joined #ltsp