gutsy kiosk mode

[Michael Redmond]

Reiner Schmid wrote:
> Hello Michael
> 
> 
> 
>>In my case, I do have a firewall. In order to get the browser to work, I 
>>needed to use the firefox Edit->preferences->advanced->network->settings 
>>gui to set my proxies. 
> 
> 
> in Feisty kioskmode it was not necessary to change something in the setting s of firefox

If you manually set a proxy through your server, can you make it work? 
If so, some global settings may have gotten lost in the update to gutsy. 
   Again, since I never used the kiosk plugin with feisty, I have 
nothing to compare it to. If I understand things correctly, normally, 
the thin client would not need proxy settings since ltsp typically runs 
it's applications, like firefox, on the server. The network is directly 
available to that application. When you run the kiosk, firefox is 
running locally on the thin client, and only has access to the subnet 
that was defined for it on the server (typically 192.168.0.XXX--assuming 
you use the 2 port solution--it turns out that I do not do that--my thin 
clients are on the same net as my server). So it can only see the 
outside world net through the server (I assume). So maybe set the proxy 
to something like server "name" 192.168.0.254 (typical), and port  80 or 
8080 (I am not sure what is used or if it is automatically set up with 
edubuntu). Sorry to be so tentative, but I have not dealt directly with 
this issue...

> 
> 
...
> 
> 
> The problem is the unionfs of gutsy, so you have to use the following command after each change of .xsession or of any other file in /opt/ltsp or /opt/ltsp-kiosk
> 
> sudo ltsp-update-image -b /opt/ltsp-kiosk
> 
> 
Thanks for this. It made things function, though the image update 
process takes a long time. feisty was a lot quicker for testing. Now I 
can start on the harder parts...
> 
> 
> 
> 
>>This is generally beyond what you probably want to do, but you may run 
>>into the same problem if you try modifying the firefox command line. And 
>>if you find a fix or if you don't run into it, please let me know.
>>
>>Thanks
>>Mike
>>---
>>