We have a building with 25 LTSP clients. We will open another location
across town. I need to choose to design the network.
A few topologies come to mind:
(1) to keep servers in building A and login from building B. However,
if there is a problem with the Internet, then all the computers in
> Below are what was shown on terminal during tail –f /var/log/messages.
>
> Jun 14 11:10:23 k12ltsp dhcpd: DHCPDISCOVER from 00:1a:92:93:1b:7f via eth0
> Jun 14 11:10:23 k12ltsp dhcpd: DHCPOFFER on 192.168.0.131 to
> 00:1a:92:93:1b:7f via eth0
> Jun 14 11:10:27 k12ltsp dhcpd: DHCPREQUEST for 19
I need to have sound on clients with flashplayer 9 (kde + iceweasel)
I tried to follow the instructions on wiki
(http://wiki.ltsp.org/twiki/bin/view/Ltsp/Sound#Adobe_Flash_9) , but I
didn't have results.
Did someone test this feature on Debian etch with success ?
Tank you
Lucas
---
Sudev Barar kirjoitti:
> What are server specs?
>
Both servers are Xeon Dual Core with 6G memory and scsi hard discs. They
are both same model, identical, less than year old.
So each server should have 60 clients at maximum. There will be 8
classrooms, 15 clients per classroom. But you know
I put together a set containing the files we use for our laptop boot installs.
This install gets a laptop to the stage of having a kernel, getting a DHCP
lease (which would be the second DHCP request in an PXE or Etherboot LTSP
setup) and doing the root pivot. It's for laptops where the option t
