19:16 < gloin> hey jammcq_laptop I've got an idea I've been wanting to bounce
off you
19:17 < jammcq_laptop> k
19:17 -!- hesco [n=hesco@S010600119536d264.wk.shawcable.net] has joined #ltsp
19:17 < gloin> I'm running LTSP on SuSE 10... and it breaks with some
frequency. The thing I'm finding to be the common breakage is
the whole netboot/tftp stack
19:18 < gloin> usually something like a change in the config file during one
update or another
19:18 < hesco> I'm back. Lost my desktop here.
19:18 < gloin> we have another lab at work which for grant purposes runs RDP
client to a windows server, and I'm using thinstation to connect
the sessions
19:18 < gloin> thing about thinstation is, I can set it to turn TFTP off, which
cuts out that entire layer of complexity
19:19 < gloin> What I'm wondering is, what about a simpler approach, where I
just use a regular linux box serving XDMCP and using thinstation
on the client machines?
19:20 < gloin> in our case, we already have DHCP etc working just fine, the
network is currently a /16 with plenty of spare addresses... I
just can't see the need to fight with netbooting if I don't have
to
19:21 < hesco> Did I misss any clues on trouble shooting my esd sound on remote
client issue.
19:21 -!- Skarmeth [n=Skarmeth@201008231125.user.veloxzone.com.br] has quit
["Fui embora"]
19:21 < gloin> hesco: nope
19:22 < gloin> what I'm asking is what the benefit is in netbooting and having
the ltsp server provide a whole seperate environment for the
thinclients
19:24 -!- jammcq_laptop [n=jam@207.219.199.245] has quit [Remote closed the
connection]
19:24 -!- jammcq_laptop [n=jam@207.219.199.245] has joined #ltsp
19:24 < gloin> rehi jammcq_laptop