|01:04||alexqwesa has quit IRC|
|01:04||alexqwesa has joined #ltsp|
|01:16||Appiah has quit IRC|
|01:16||AndyGraybeal has quit IRC|
|01:16||Patina has quit IRC|
|01:16||highvoltage has quit IRC|
|01:16||yanu has quit IRC|
|01:16||vlt has quit IRC|
|01:16||daya has quit IRC|
|01:16||pem725 has quit IRC|
|01:16||abeehc has quit IRC|
|01:16||jhutchins_lt has quit IRC|
|01:16||jimcooncat has quit IRC|
|01:16||jbrett- has quit IRC|
|01:16||vbundi has quit IRC|
|01:16||moldy has quit IRC|
|01:16||knipwim_ has quit IRC|
|01:16||Shingoshi has quit IRC|
|01:35||Shingoshi has joined #ltsp|
|01:35||daya has joined #ltsp|
|01:35||highvoltage has joined #ltsp|
|01:35||jimcooncat has joined #ltsp|
|01:35||yanu has joined #ltsp|
|01:35||jbrett- has joined #ltsp|
|01:35||pem725 has joined #ltsp|
|01:35||abeehc has joined #ltsp|
|01:35||jhutchins_lt has joined #ltsp|
|01:35||vbundi has joined #ltsp|
|01:35||Appiah has joined #ltsp|
|01:35||moldy has joined #ltsp|
|01:35||knipwim_ has joined #ltsp|
|01:35||AndyGraybeal has joined #ltsp|
|01:35||Patina has joined #ltsp|
|01:35||vlt has joined #ltsp|
|01:35||try2free has joined #ltsp|
|01:55||F-GT has joined #ltsp|
|01:57||vagrantc has quit IRC|
|02:02||F-GT has quit IRC|
|02:04||japerry has joined #ltsp|
|02:18||F-GT has joined #ltsp|
|02:33||F-GT has quit IRC|
|02:51||mikkel has joined #ltsp|
|02:53||F-GT has joined #ltsp|
|03:32||leio has quit IRC|
|03:35||leio has joined #ltsp|
|03:51||F-GT has quit IRC|
|04:07||F-GT has joined #ltsp|
|05:26||alkisg has quit IRC|
|05:41||highvoltage has quit IRC|
|05:43||highvoltage has joined #ltsp|
|06:02||jimcooncat has quit IRC|
|06:04||hersonls has joined #ltsp|
|06:18||Selveste1 has quit IRC|
|06:22||daya has quit IRC|
|06:28||alkisg has joined #ltsp|
|06:29||pmatulis has joined #ltsp|
|06:49||moldy has quit IRC|
|06:50||moldy has joined #ltsp|
|06:55||highvoltage has quit IRC|
|06:57||highvoltage has joined #ltsp|
|07:27||cliebow has joined #ltsp|
|07:31||vvinet has joined #ltsp|
|07:34||windmill has joined #ltsp|
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.
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?
_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?
Because for the "normal" way you just need to enable the local apps menu, you don't need to speficy any items...
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?
alkisg: mine still does and I have the newest package, which is weird.
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
alkisg: sounds like fun :)
|08:30||vbundi has quit IRC|
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..|
highvoltage: but do comment your experience on the bug report...
alkisg: yep! will try out. do you implement ssl as well?
highvoltage: no, it's working over the existing ssh connection
So no need for authorization / encryption or whatever
(that's for fat clients)
alkisg: ah ok
For thin clients, it's working directly on the server, so again no encryption is necessary
..and as a side-effect, I get automatic notifications of when clients boot / users logon / logoff etc...
The client is just a bash script, so it can run in 64mb as well.
alkisg: do you plan to make it something that could be included by default in ltsp one day?
I'm trying to, e.g. I put lts.conf variables for clients that one might not want to control etc,
but for Lucid it's just going to be part of my "sch-scripts" project, which due to time constrains is greek only,
...but I'd like to internationalize it in the summer, if any native english speaker is interested on proofreading it
Yey! Binary transfers working :)
|08:59||windmill has quit IRC|
|09:00||litlebuda has joined #ltsp|
|09:00||mikkel has quit IRC|
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:05||slidesinger has joined #ltsp|
litlebuda: no, you need to create lts.conf
ok thanks alkisg
will try it out
|09:20||alexqwesa has quit IRC|
|09:20||alexqwesa has joined #ltsp|
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.
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.
I'm thinking: sch-send [-h] hostname | [-u] username | [-i] ip | [-m] mac-address command [params]
E.g. `sch-send ltsp123 poweroff`, or `sch-send ltsp123 firefox`.
The problem is that `poweroff` should be executed by the root sch-client (daemon), while `firefox` should be executed by the user sch-client.
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?
(and alternative would for an additional [-r] parameter that would specify that the command should be executed by the root daemon)
|09:51||mikkel has joined #ltsp|
|09:59||The_Code has joined #ltsp|
|10:30||staffencasa has joined #ltsp|
|10:44||Faithful has quit IRC|
|10:46||reynolds has joined #ltsp|
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.
could have something to do with the client video card
vlc can be pretty verbose if run in terminal with like -vv
|10:59||Faithful has joined #ltsp|
|11:36||windmill has joined #ltsp|
|11:37||Gadi has joined #ltsp|
Yey! bash tcp sockets can transfer files from the client session (=localhost) to the server at 14 Mbyte/sec in my laptop!
|11:50||F-GT has quit IRC|
|11:57||litlebuda has quit IRC|
|12:06||F-GT has joined #ltsp|
alkisg: nice :)
alkisg: i would prefer the extra switch solution, i think
moldy: thanks, another teacher told me the same, so I'll implement that.
So far it seems stable; I transfered a whole .iso without problems
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||reynolds has quit IRC|
|12:36||staffencasa has quit IRC|
|12:40||Lns has joined #ltsp|
|12:57||Jinux has joined #ltsp|
|12:57||Jinux has left #ltsp|
alkisg: nice. i will take a look as soon as i find the time to
|13:00||ogra_cmpc has quit IRC|
|13:01||jammcq has joined #ltsp|
|13:01||ogra_cmpc has joined #ltsp|
|13:06||* Lns hugs jammcq|
|13:10||staffencasa has joined #ltsp|
|13:21||mgariepy has joined #ltsp|
|13:21||ogra_cmpc has quit IRC|
|13:28||vaix has joined #ltsp|
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
should be no concerns regards different dists..
K12Linux = LTSP on Centos I think
LTSP work in combo w/ LVS - so I can have an HA/DR config for LTSP?
I dont know what LVS is
and HA/DR either
LVS = linux virtual server. HA = High Availability, DR = Disaster Recovery
LVS , yes
HA/DR Well there is ltsp-cluster
check that out and how you can put that togheter with your HA config today
thanks - will look there
|13:35||ogra_cmpc has joined #ltsp|
|13:48||alkisg has quit IRC|
|13:51||alkisg has joined #ltsp|
|14:08||din_os has joined #ltsp|
|14:36||arx has joined #ltsp|
|14:39||din_os has quit IRC|
|14:48||leio has quit IRC|
|14:52||leio has joined #ltsp|
|14:53||vagrantc has joined #ltsp|
|14:55||cliebow has quit IRC|
|14:57||pmatulis has quit IRC|
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?
What .iso distributions?
|15:04||din_os has joined #ltsp|
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:04||arauto has joined #ltsp|
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:05||din_os has quit IRC|
vagrantc: does debian support tcp sockets in bash? E.g. exec 3<>/dev/tcp/localhost/22 ?
alkisg: i think i played with that back in 2001...
so i'm guessing so
vagrantc: I got 3 scripts almost ready, 2 in bash and one in python, to send commands to ltsp clients
They reuse the ssh channel to transfer the commands
Do you think they'd belong upstream, given enough care of course?
The server script uses openbsd-inet + bash
The client script only bash ==> works in 64 MB ram clients,
and the command-send script python, so that it can be used as a module
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...)
alkisg: and what sorts of things are you planning on doing with them that couldn't be done easily before?
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
I can send a poweroff to the clients or run cron jobs on them from the server
(no authentication needed)
I can send commands to the user sessions, be it on thin or fat clients
a restricted (or restrictable) set of commands?
E.g. "sch-send user123 firefox"
sounds pretty cool.
The root commands are restricted currently
(to poweroff, reboot, exit and sch-info)
The user commands are not restricted on purpose
The root commands are unencrypted, but they're using reverse connections, so they cannot be easily exploited
The user commands use the ssh channel, so they're encrypted
poweroff/reboot => do they need encryption?
just curious how you implement them unencrypted if the communication channel is already encrypted
There are 2 daemons per terminal, one that runs as root (always), and one that runs inside the user session
The one that runs as root is executed before ldm starts
So it connects to server:9570 on an unencrypted channel
The other one is using ssh port forwarding, so it uses encryption
sounds like a system bus and a session bus
(and connects to the same port)
Each connection is only using one bash on the clients, so it needs minimum ram
And I've already started implementing some lts.conf options for not starting some of them...
(e.g. we might not want to run them in some hosts)
If you guys are interested, I should change the names to more generic ones, get rid of the sch-* prefix
...and we'll see in the future if it's worth to be put upstream.
Gadi, right, nice metaphor :)
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|
Gadi, I've wasted 2 weeks on those :)
the one true cron
...and another one on twisted :)
|15:20||* vagrantc cringes|
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?
it just sounds ridiculous
next hackfefst, we should play illuminati
I'm waiting to sweep the nation with a project called Poopie
Gadi: speaking of hackfests, you register for debconf10?
I have not
alkisg: i spent 6 hours writing up a debian/copyright file for gPXE ... probably roughly 30-40% done.
|15:24||* Gadi has been in a cave under a rock for two weeks|
Gadi: well, you know, i *Expect* you to be there. :P
hehe - can you email me the info?
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... :)|
I am rushing today to get everything I need done before the holiday
then, its back under a rock for me...
.oO(speaking about rocks.. vagrantc rocks too :)
|15:31||vbundi has joined #ltsp|
hey is Stephane's PPA meant to be used for both the chroot and the ltsp server?
is v5.199+ development public? It looks like the sourceforge repository only has 4.x product?
vbundi: yes, if you're gonna use it, use it on both
alkisg: "ltsp-source" :: at http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/files
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.
alkisg: "docs" :: For the most current documentation, see https://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
unless you're looking to port it to a new linux distro, just downloading the source isn't probably very usefull.
vagrantc: "ldm-source" :: at http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/files
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 ;)|
vaix: or convince a Redhat or Centos developer to get involved
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:40||windmill has quit IRC|
|15:41||vaix is now known as vaix_afk|
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...
is the amd64 one a mirror of the local system vs i386 which is generated?
depends on how it was created
there's an option that copies the sources.list file from the server into the chroot
well unless it is default when running the install from the alternate CD, I didn't choose any option afaik
|15:45||Gadi has left #ltsp|
probably is a different default
but not knowing ubuntu too well, i can't say for sure.
|15:47||mathesis__ has joined #ltsp|
|15:47||litlebuda has joined #ltsp|
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
kind of makes ltsp terminals more 'lucid' (no pun intended)
Thank you Lns... now I'm only missing some good program/variable names :D
when updating my chroot... is the procedure, chroot /opt/ltsp/i386/ sudo apt-get update && sudo apt-get upgrade; ltsp-update-image --arch i386 ?
alkisg: i can help with that if you want =)
|15:50||mathesis_ has quit IRC|
Lns, ok, I got "sch-server", "sch-client" and "sch-send" the one that is used to send the commands
sch = ?
...and I probably need to ditch the sch- in front... (school)
(the greek schools domain is sch.gr)
yeah, I dunno, my personal perspective is that ltsp != schools so we should keep that separate
Sure, if it is to go upstream sometime, it'll need something with ltsp* in front
|15:52||ogra_cmpc has quit IRC|
The basic idea of the programs are to gain control of terminals from the server/admin workstation, no?
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'
kind of a strange name but i dunno, it does make the 'nodes' more 'lucid'
I really liked "ltsp-manager" from ogra a while back
and it obviously doesn't leave anything to question about its functionality
|15:54||ogra_cmpc has joined #ltsp|
lol, speak of the devil
Hmmm that sounds good
ogra_cmpc: could we reuse the "ltsp-manager" name for a different, but similar project?
|16:02||hersonls has quit IRC|
|16:08||_UsUrPeR_ has left #ltsp|
|16:18||windmill has joined #ltsp|
|16:29||vvinet has quit IRC|
|16:35||mikkel has quit IRC|
|16:36||pmatulis has joined #ltsp|
|16:43||mgariepy has quit IRC|
|16:45||alkisg has quit IRC|
|16:49||Selveste1 has joined #ltsp|
|17:02||jammcq has quit IRC|
|17:08||Lns has quit IRC|
|17:15||arx has quit IRC|
|18:07||windmill has quit IRC|
|18:36||ogra_cmpc has quit IRC|
|18:37||ogra_cmpc has joined #ltsp|
|18:40||mathesis_ has joined #ltsp|
|18:42||mathesis__ has quit IRC|
|18:45||staffencasa has quit IRC|
|19:03||litlebuda has quit IRC|
|20:21||try2free has joined #ltsp|
|20:26||try2free has left #ltsp|
|20:28||mgariepy has joined #ltsp|
|20:48||pmatulis has quit IRC|
|21:25||mgariepy has quit IRC|
|21:27||mathesis_ has quit IRC|
|22:18||arauto has quit IRC|
|22:40||vagrantc has quit IRC|
|22:49||daya has joined #ltsp|
|22:51||alkisg has joined #ltsp|
|22:53||vagrantc 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:25||Egyptian[Home] has quit IRC|
|23:34||tstafford has quit IRC|
|23:45||ogra_cmpc has quit IRC|
|23:46||ogra_cmpc has joined #ltsp|