|00:43||alkisg has joined #ltsp|
|00:49||cyberorg has joined #ltsp|
|01:14||pmatulis has quit IRC|
|01:50||Ahmuck has quit IRC|
|02:33||Ryan52 has quit IRC|
|02:47||lucascoala has joined #ltsp|
|03:01||Ryan52 has joined #ltsp|
|03:19||nubae1 has joined #ltsp|
|03:20||nubae has quit IRC|
|04:22||Remaille has joined #ltsp|
|04:44||F-GT has quit IRC|
|04:47||F-GT has joined #ltsp|
|05:04||alkisg has quit IRC|
|05:16||pmatulis has joined #ltsp|
|05:23||Remaille has quit IRC|
|05:47||yoshi__ has quit IRC|
|06:49||nubae1 is now known as Nubae|
|06:58||F-GT has quit IRC|
|07:00||F-GT has joined #ltsp|
|07:01||lucascoala has joined #ltsp|
|07:05||bobby_C has joined #ltsp|
|07:26||alkisg has joined #ltsp|
|08:09||F-GT has quit IRC|
|08:32||F-GT has joined #ltsp|
|08:57||alkisg has quit IRC|
|09:01||hanthana has joined #ltsp|
|09:06||Egyptian[Home] has quit IRC|
|09:17||Egyptian[Home] has joined #ltsp|
|09:28||nubae1 has joined #ltsp|
|09:29||Nubae has quit IRC|
|09:45||ogra has joined #ltsp|
|09:52||nubae1 is now known as Nubae|
|10:21||alkisg has joined #ltsp|
|10:50||vagrantc has joined #ltsp|
|11:09||Nubae has quit IRC|
|11:24||nubae has joined #ltsp|
|11:37||F-GT has quit IRC|
|11:40||F-GT has joined #ltsp|
|11:50||pasmen has joined #ltsp|
|12:13||F-GT has quit IRC|
|12:15||F-GT has joined #ltsp|
|12:17||nubae has quit IRC|
|12:19||nubae has joined #ltsp|
|12:59||Remaille has joined #ltsp|
|13:09||alkisg has quit IRC|
|13:09||alkisg has joined #ltsp|
|13:23||F-GT has quit IRC|
|13:26||F-GT has joined #ltsp|
|13:40||Squideshi has joined #ltsp|
Can anyone help be understand what LTSP provides that can not already be done with X remotely?
Squideshi: depends. define "X remotely"
Can't you just setup a server (the X client) and multiple workstations (the X servers) and connect that way?
For example, if I had a bunch of X terminals, couldn't they all just connect to the server (X client)>
|13:52||pasmen has quit IRC|
Squideshi: see the ltsp docs. E.g. network booting, sound, local devices (usb sticks, cd roms), encrypted communication etc
I've been reading through the docs, but I thought that these were already all possible with an X terminal (Except for maybe network booting, which I don't think is needed with an X terminal.)
Remote sound with an x-terminal? Local devices? I don't think so...
Hmmm... That may be where my confusion was then.
The docs talk about network booting, but don't some thin clients have the X server already embedded in hardware?
Network booting = central updates. I don't know if/how X-terminals are upgrated, but in LTSP an apt-get update in the chroot is all it takes.
|14:05||Remaille has quit IRC|
I guess I just assumed that the X terminals with X servers embedded in hardware just don't get updated.
|14:14||F-GT has quit IRC|
|14:16||F-GT has joined #ltsp|
|14:24||dmc has quit IRC|
disklessworkstations.com sells a few "DLW" terminals with Linux "embedded". Am I correct in understanding that this does not get updated?
|14:40||dmc has joined #ltsp|
|14:42||litlebuda has joined #ltsp|
|14:42||otavio has quit IRC|
Squideshi: probably not without manual intervention.
|14:55||hanthana has quit IRC|
I am thinking about setting up a LTSP server in a central location with remote terminal/clients offsite, connected via either DSL or cable modem. Do I need a router at the terminal/client side to route PXE booting, or is there another scenario?
DSL remote booting will be slow
hmm pxe over vpn?
Squideshi: I think its an unrealistic setup, its been spoken about before
I believe someone wanted to set up a LTSP server on an Amazon cloud
|15:21||litlebuda has quit IRC|
OK. LTSP doesn't require PXE booting. Are there thin clients with LTSP embedded or already installed (so they don't have to be pulled down over the network for boot)?
pulling down over the network is rearely a problem
you could build such a thing yourself if you really wanted to
it's the actual running that is a problem
since all the programs run over the network
I thought that all the programs would run on the LTSP server and only X11 would be sent over the network.
Isn't that the purpose?
Squideshi: so if you so ssh -X some_pc_over_a_dsl, are you satisfied with the results?
Squideshi, X11 is heavy..
I haven't tried that. I thought that X11 was designed to allow remote terminals.
otherwise you wouldn't be able to do what you're doing
OK, so what I think I hear you saying is that X11 may work over a DSL connection; but it won't work well.
|15:36||bobby_C has quit IRC|
for how many clients?
|15:36||litlebuda has joined #ltsp|
Usually one per DSL connection.
oh each client got its own connection?
Yes--they're branch offices.
Small branch offices.
with just 1 client?
What about this NX thing I just found?
Does that work with LTSP?
well , doesnt sound impossible but cant gurantee it will be smooth
there is nx support
This might be for what I am looking.
yes.. that will help mucho
but you won't get all the benefits of ltsp iirc
i'm trying to remember.. others here would know better
Seems like NX is a better protocol than X11 in general. I wonder why more people aren't using NX instead of X11, if X11 really is that "heavy".
I mean, if it compresses things and works well over a limited bandwidth connection, surely it would also reduce local network traffic if used strictly over a LAN, right?
sure.. at the cost of higher resources
plus.. the original implementation is not open
Oh, NX is not FOSS?
I thought it was. My bad.
i think freenx is
FreeNX is Free :D
still version 0.7.3
about 1 year since last release
Hmmm... Maybe I can use FreeNX with LTSP.
the NX implementations have code copies from older versions of X, and are getting outdated and buggy and security ridden
NX was a great idea, but implemented in a way that isn't long-term viable.
|16:19||alkisg has quit IRC|
|16:54||Ahmuck has joined #ltsp|
|17:16||otavio has joined #ltsp|
|17:31||johnny has left #ltsp|
|17:54||johnny has joined #ltsp|
|18:09||vagrantc has quit IRC|
|18:12||Squideshi has quit IRC|
|18:39||litlebuda has quit IRC|
|18:52||petre has joined #ltsp|
What causes the problem of a usb flash drive plugged into the server causing an icon to appear on all client desktops? Or is it a case of 'it depends'?
hey jammcq !
petre, usually because your users aren't in their own group
as their primary
ah, as in putting all users into, say, group 'students' for their primary group?
their primary group should be themselves
and everyone should be in the 'fuse' group, meaning secondary, for local device access, right?
if they are already
I have a script for that
|20:32||nubae has quit IRC|
|20:33||nubae has joined #ltsp|
|20:34||grimboy_ has joined #ltsp|
|20:44||johnny has left #ltsp|
|20:47||grimboy has quit IRC|
|20:56||Faithful has joined #ltsp|
I think Ive got all the woodtics off me now :)
|21:33||F-GT has quit IRC|
|21:36||F-GT has joined #ltsp|
|21:54||petre has quit IRC|
|22:18||nubae1 has joined #ltsp|
|22:18||nubae has quit IRC|
|22:18||nubae1 is now known as Nubae|
|22:32||pmatulis has quit IRC|
|22:32||alkisg has joined #ltsp|
|22:56||hanthana has joined #ltsp|
|23:10||alkisg has quit IRC|
|23:13||nubae1 has joined #ltsp|
|23:14||Nubae has quit IRC|
|23:36||try2free has joined #ltsp|