|00:20||mistik1 has quit IRC|
|00:24||mistik1 has joined #ltsp|
|00:25||alkisg has joined #ltsp|
|00:34||topslakr has quit IRC|
|00:34||babyhuey has quit IRC|
|00:34||GiantPickle has quit IRC|
|00:34||babyhuey has joined #ltsp|
|00:34||topslakr has joined #ltsp|
|00:34||GiantPickle has joined #ltsp|
|01:28||rcy` has joined #ltsp|
|01:28||rcy has quit IRC|
|01:29||juanpaul has quit IRC|
|01:40||rcy` has quit IRC|
|01:40||rcy has joined #ltsp|
|01:49||indradg has quit IRC|
|01:49||indradg has joined #ltsp|
|02:03||rxd has joined #ltsp|
|02:10||GiantPickle has quit IRC|
|02:14||Egyptian[Home] has quit IRC|
|02:30||vagrantc_ has quit IRC|
|02:31||Egyptian[Home] has joined #ltsp|
|02:33||rxd has quit IRC|
|03:04||Egyptian[Home] has quit IRC|
|03:22||Q-FUNK has joined #ltsp|
|03:25||shandflm has joined #ltsp|
|03:26||rcy has quit IRC|
|03:26||pfwsmbkwt has joined #ltsp|
|03:27||alkisg has quit IRC|
|03:36||Q-FUNK has quit IRC|
|03:38||Egyptian[Home] has joined #ltsp|
|03:49||alkisg has joined #ltsp|
|04:12||alkisg has left #ltsp|
|04:16||Egyptian[Home] has quit IRC|
|04:26||warren has joined #ltsp|
|04:58||radoeka has joined #ltsp|
|05:06||X0d_of_N0d has quit IRC|
|05:11||X0d_of_N0d has joined #ltsp|
|05:12||radoeka has quit IRC|
|05:19||alkisg has joined #ltsp|
|05:20||Egyptian[Home] has joined #ltsp|
|05:21||Nubae has joined #ltsp|
|05:27||topslakr has quit IRC|
|05:27||babyhuey has quit IRC|
|05:28||babyhuey has joined #ltsp|
|05:28||topslakr has joined #ltsp|
|05:30||monteslu has quit IRC|
|06:37||radoeka has joined #ltsp|
|07:07||alekibango has quit IRC|
|07:15||kleewyck has joined #ltsp|
|07:37||warren has quit IRC|
|07:39||warren has joined #ltsp|
|07:42||mikkel has joined #ltsp|
|08:26||powerfox has joined #ltsp|
Hi! Did some one run configuration "Win-server + linux thin clients"? I've read in the mailing list that somebody has tried it with Samba.
|08:28||radoeka has quit IRC|
|08:44||radoeka has joined #ltsp|
|08:54||Q-FUNK has joined #ltsp|
powerfox, what do you mean? how are the clients going to boot?
alkisg: mainly if I can do such configuration and what should I read (Samba, etc)
So you want windows to be the only server in your setup?
No Linux server for the thin clients to boot from?
|09:09||Q-FUNK has quit IRC|
|09:30||Q-FUNK has joined #ltsp|
|09:39||alkisg has left #ltsp|
|09:45||DonSilver has joined #ltsp|
Oops, sorry unfortunately they made me aw. But too late =(
I will have just windows server
|09:51||sepski has joined #ltsp|
why are you here ?
you need a linux server if you want linux thin clients
altho.. you you can serve windows to linux thin clients..
if you had the proper virtual machines, and licenses
or a completely seperate windows server
|10:02||GiantPickle has joined #ltsp|
|10:02||gonzaloaf_laptop has quit IRC|
johnny: I just need linux thin clients with windows server
It's great my boss agreed to use linux thin clients. But it can be hard to make my boss agree with linux-server.
how did you expect that to work?
you would need to install linux in a virtual machine
on the windows server
it's usually better the other way around tho
windows in a virtual machine in the linux server
johnny: it will be slower
you need linux to serve up the proper files
u could try running ltsp under cygwin... would that work?
is there an nfs server for windows?
or nbd ?
if you could serve nbd.. you could probably make the image on ubuntu
copy it to windows
it requires X
powerfox, you're still gonna need linux
yeah, seems stupid to be running thin clients without linux
powerfox, virtual machine is your only option
usually a linux server is an easier sell than linux thin clients
without adding a seperate physical server
Nubae: as I understand I just need the way to send boot image to them
powerfox, they still boot off the remote linux server and use X and the remote window manager
no, then u misunderstand what is meant by thin client
and client manager, and apps manager
johnny: I can use Qt embedded
then that will not be ltsp
u need a full linux distro to run ltsp
that will be something else popey
Nubae, johny: ok, thanks folks. Have to read documentation.
I'm new to terminals :)
u can do fat clients the way u describe
that would just serve netbooted terminals
They don't have any hdd
right... thats why I said netbooted
Oh, I thought thin clients are the same as netbooted terminals
no, not at all
first, what are the specs of your terminals?
Don't have any now. Will try to ckeck mail archive
u'd have to build the image on a linux machine
and then move the image to windows
and serve via nbd
that will work
but as far as I know, thats new terrain... and not really ltsp at all anymore, other than u use ltsp to build the image
|10:30||keithclark has joined #ltsp|
|10:31||GiantPickle has quit IRC|
|10:31||powerfox has quit IRC|
|10:31||indradg has quit IRC|
|10:31||leio has quit IRC|
|10:32||GiantPickle has joined #ltsp|
|10:32||powerfox has joined #ltsp|
|10:32||indradg has joined #ltsp|
|10:32||leio has joined #ltsp|
|10:32||powerfox has left #ltsp|
|10:32||powerfox has joined #ltsp|
Nubae: got specification. Intel eligrick 2 or somethink like this. Will check intel site. Celeron on the motherboard and the same server but with hdd
cant find eligrick 2 on google
Nubae: me too. Ok, it's a small motherboard with integrated Celeron. It has DDR-2.
|10:41||Q-FUNK has quit IRC|
which mhz, how much ram?
Nubae: he didn't tell me. Just that it can be a netbooted system (before I came it had windows embedded) and should make 60FPS
well, we need to know the ram and cpu speed.... when u turn on the computer, those details should be mentioned, as well as in the bios
I don't have client now :) I'm doing research if we can use linux
well then find out the exact name of the client
It should be Onboard Intel® Mobile Celeron® processor 600MHz with 0K L2 cache.
AFAIK 256-512 RAM
well that will run ok, but not great with netbooted linux
I understand it's stupid to ask without specs :(
But should be faster, than Windows embedded, right?
depends what windows
than vista, sure
|10:54||keithclark has quit IRC|
well, it will be more usable yeah and more secure... but probably not that much faster
Nubae: So LTSP can help me right?
LTSP means Linux server and linux thin terminals
but what u are looking for is netbooted clients (if u intend to run a windows server with linux clients)
|10:58||Q-FUNK has joined #ltsp|
Nubae: ok, will read both. Thanks a lot for your help :)
|11:09||bobby_C has joined #ltsp|
|11:09||bobby_C has quit IRC|
|11:10||mikkel has quit IRC|
|11:20||ogra has quit IRC|
|11:23||ogra has joined #ltsp|
|11:30||mistik1 has quit IRC|
|11:41||sepski has quit IRC|
|11:44||powerfox has quit IRC|
|11:44||leio has quit IRC|
|11:44||GiantPickle has quit IRC|
|11:44||indradg has quit IRC|
|11:45||alkisg has joined #ltsp|
|11:45||powerfox has joined #ltsp|
|11:45||GiantPickle has joined #ltsp|
|11:45||indradg has joined #ltsp|
|11:45||leio has joined #ltsp|
|11:46||mistik1 has joined #ltsp|
|11:55||keithclark has joined #ltsp|
|12:12||powerfox has left #ltsp|
|12:15||jhutchins has quit IRC|
|12:16||keithclark has quit IRC|
|12:38||roshan08 has joined #ltsp|
|12:39||roshan08 has left #ltsp|
|12:54||alkisg has quit IRC|
|12:57||alkisg has joined #ltsp|
|13:12||sepski has joined #ltsp|
|13:46||gonzaloaf_laptop has joined #ltsp|
|14:16||gonzaloaf_laptop has quit IRC|
|14:28||warren has quit IRC|
|14:37||ogra has quit IRC|
|14:51||johnny has left #ltsp|
|14:52||ogra has joined #ltsp|
|15:08||vagrantc has joined #ltsp|
|15:13||johnny has joined #ltsp|
|15:14||keithclark has joined #ltsp|
|15:33||keithclark has quit IRC|
|15:48||* stgraber is working on auto-generated localapp menu|
the menu generation scripts seem to work correctly, I just now need to define a configuration file to define what's in the menu
stgraber, is there a way to hijack what loads to desktop files to prefix them with the app launcher
well, in my case I'll just to another menu for localapps, but yes you can overwrite the existing desktop files with some using localapps
the xdg menu, first apply the system menus, then the ones in .local/ and .config/
|15:53||sepski has quit IRC|
so if you have the same entry in the system menu (let's say firefox.desktop) and another in the user's home directory for the same entry, the one from the user will overwrite the system one
xdg menus are pretty cool stuff
|15:56||indradg_ has joined #ltsp|
|16:05||X0d_of_N0d has quit IRC|
|16:14||indradg has quit IRC|
johnny, maybe you could add a /usr/share/mime-info/something.keys file, to specify that all .desktop files open with app-launcher, and in app-launcher check if the app is local or not and run it accordingly
|16:29||alkisg has quit IRC|
|16:33||alkisg has joined #ltsp|
here you go, menu generator
I just need to write two ldm rc.d scripts and that'll work
|16:59||artista_frustrad has joined #ltsp|
stgraber: nice :-)
Nubae: yeah, for now we did it on the application server side which was far from perfect as we also have some NX users that don't want to see the menu.
Nubae: the only thing I haven't solved yet is when the software is in the chroot but not on the application server. In this case, the icon will be missing ...
so depending on the user's group they see or dont see the local app menu?
well, that script will run on the thin client, so if boolean_is_true LOCALAPP, the menu will be generated
and removed on session logout
oh, even better
so only thin client users with localapps enabled will have it
and you'll only see the .desktop that are in /etc/ltsp/localapps-menu/ in the chroot
ah u did say above it was on the app server to begin with.. didnt read properly
ltsp is starting to run out of needed implementations... it really seems like it does everything now
|17:08||radoeka has quit IRC|
|17:16||alkisg has left #ltsp|
Nubae: i think LTSP's biggest challenge now will be to ensure that Linux's mad push to become a Desktop OS doesn't forget that it's also a networked OS (i.e. the network-transparency of X).
|17:54||artista_frustrad has quit IRC|
|17:55||X0d_of_N0d has joined #ltsp|
vagrantc: yeah indeed
hey vagrantc, now that you're here, I've been asked by the sugar team to be part of the "core for the server side development of the Sugar Learning Platform" whatever that means... but its in response to me posting the sugar on ltsp, which they got very excited about, and wanted to me see how to do this with other distros, most notably debian and skoledu....
as far as I know u are the skoledu, debian guy... and ejabberd (collaboration side) seems to be packaged for debian... what would be the best way to present something like a 'sugar for ltsp' package or script?
Nubae: we (Revolution Linux) also have some interest in offering sugar as a desktop environment for our very young LTSP users, be that as a localapp (I think we can do that in most cases) or as an alternative desktop manager on the server side
(it's on my roadmap for 1.5 (investigating it) and 2.0 (ready for production))
1.5 being December, 2.0 being March/April
ok, cool, I'll keep that in mind, and if u need something specific from sugar, let me know so I can tell the team, as they are now actively trying to integrate it seamlessly in other distros than fedora
revolution linux is totally ubuntu based right?
we have some very old Mandriva systems at some customers but they'll be updated to Ubuntu
though ltsp-cluster isn't really Ubuntu-specific, we keep the packaging separated so another distro may package it
Nubae: there's frequently discussion on firstname.lastname@example.org about sugar... there's also a sugar packaging team ... sugar is available in debian ... what sort of things are you wondering?
I hope to be able to deploy ltsp-cluster, just need a big enough school, heh
well this is sugar coupled together with ejabberd, basically it needs some tweaking to work with ltsp
sugar by itself is kinda useless, it really needs collaboration to be useful
Nubae: i'm not really familiar with sugar and related technologies...
Nubae: having sugar + ejabberd installed in the chroot (+ some configuration) should do the trick no ?
do u think skoledu would be interested in offering it to primary users?
stgraber: nah, everything on the server, nothing needed in the chroot
Nubae: debian-edu or skolelinux :)
heh, yeah get that confused
Nubae: well, in our case we'd like to have it in the chroot, our thin clients are way too powerful to need a server in this case :)
right... then its just running a script
which I've got almost working... for some reason I get an X with a black screen on startup
not sure whats causing it... but I'll figure it out soon enough
Nubae: when starting sugar ? I also had that last time I tried IIRC
stgraber: in your case u need ejabberd on the server and sugar in the chroot
yeah I think the reason is sugar doesnt really have a real session manager
anyway, I'll get quite a few new atom-based thin clients/netbooks next week so I'll then have a good test lab :)
yeah the new dual core atoms must be cool
prefect as fat clients
sugar as thin client technology though, flies... its so much faster than gnome
I tried a standard 1.6Ghz + hyperthreading with 1Gig of RAM two weeks ago
these things are really fast and shouldn't be called thin clients anymore :)
that's a good deal more capable than my laptop :P)
|18:19||* vagrantc stumbles over emoticons|
well, it was almost as fast as the server :)
(in fact it had more RAM than our test server)
one thing that will be interesting is doing wireless ltsp fat based with sugar
|18:34||X0d_of_N0d has quit IRC|
|18:40||X0d_of_N0d has joined #ltsp|
|19:12||warren has joined #ltsp|
|19:45||warren has quit IRC|
|19:49||kleewyck has left #ltsp|
|20:01||warren has joined #ltsp|
|20:04||warren has quit IRC|
|20:14||DonSilver has quit IRC|
|20:26||moquist has quit IRC|
|20:45||shogunx has joined #ltsp|
|20:49||alekibango has joined #ltsp|
|21:11||Nubae has quit IRC|
|21:11||johnny has left #ltsp|
|22:02||CaScAdE^FarAway has joined #ltsp|
|22:09||CaScAdE^1arAway has quit IRC|
who's inviting the ltsp lists to twitter?
and how can we cause them undue harm?
don't know, I clicked opt-out but someone did it before me :)
|22:26||Ryan_52 has joined #ltsp|
on both lists?
opt-out is kind of... nasty.
i.e. it's exactly the sort of behavior spammers want people to do.
but well, it's twitter (I checked the URL before clicking) ... still they shouldn't let someone invite email@example.com
(or anything that includes "list" in the url)
|22:32||vagrantc has quit IRC|
|22:35||Ryan_52 has quit IRC|
|23:01||CaScAdE^1arAway has joined #ltsp|
|23:04||CaScAdE^FarAway has quit IRC|
sbalneav: http://ubuntu.pastebin.com/f718884da + 2 ldm rc scripts and you're done
then you get a shiny localapp menu showing when the user is logged on a thin client, and you don't get it if it's on a standard desktop
Glad I added the LDM rc subsystem. Knew it would come in handy
|23:16||johnny has joined #ltsp|
sbalneav: hehe, I already have three things using it :) italc, ltsp-cluster session manager and the menu generator
I need to get the bugfix I came up with pushed through for hardy. Fixes most of the "hung processes after logout", plus does a proper logout so people relying on pam stuff are happy
|23:20||vagrantc has joined #ltsp|
sbalneav: that fix is already in Intrepid right ?
Not sure. I don't think so.
so you'll need a SRU for both
try saying shru :)
why does ltsp in ubuntu depend on pulseaudio?
because ltsp uses pulseaudio for the audio part
ok. looks like I'll have to put this back together in a while
|23:55||alkisg has joined #ltsp|
kc8pxy_, ubuntu uses pulseaudio in general anyways
kc8pxy_, i use pulseaudio in gentoo too..
it is wonderful to be able to play sound out of my computer with the good speakers.. from my laptop
johnny: I'm trying to play a few games to demo what linux/ubuntu can do, for a few visitors. and the wine folk say pulseaudio is geting in the way.
that's their fault for not using a pulse driver :)
don't they have an esd driver?
the esd driver should be compatible with pulse