[Sugar-devel] [FEATURES][DESIGN] Network proxy configuration
jvonau at shaw.ca
Tue Jan 24 12:33:37 EST 2012
On Tue, 2012-01-24 at 13:02 +0100, Simon Schampijer wrote:
> On 01/23/2012 03:05 AM, Sridhar Dhanapalan wrote:
> > On 23 January 2012 13:02, Gary Martin<garycmartin at googlemail.com> wrote:
> >> Hi Sridhar,
> >> On 23 Jan 2012, at 01:08, Sridhar Dhanapalan<sridhar at laptop.org.au> wrote:
> >>> On 19 January 2012 21:16, Simon Schampijer<simon at schampijer.de> wrote:
> >>>> If OLPC-AU has been telling their users to set the proxy via GNOME before
> >>>> that is useful information. Other deployments might have set a proxy in the
> >>>> build itself?
> >>> To confirm, we do tell users to configure their proxy using the GNOME
> >>> tool (gnome-network-properties). Switching to GNOME just to do this is
> >>> tiresome, so we have a Sugar activity launcher for it. This is a
> >>> workaround, and we would prefer a native Sugar CP applet.
> >> Do you think this functionality could be folded into the Network CP UI or are there a heap of inputs? We could make better use of Network CP horizontal space regarding text blocks, and gain some vertical space to reduce potential scrolling overflows for adding an extra field with text description.
> > I think it could be folded, provided that no features are lost. We
> > need the entire feature set of gnome-network-properties to be
> > available, with the possible exception of the Location picker
> > (although that would be nice too).
> > Sridhar
> Hi Sridhar and Jarry,
> can you give a bit of inside on the usage of that Feature in the field?
> So far I am clear that you did use the gnome-network section to set the
> proxy. To make it easier the option should now be as well available in
> the CP in Sugar.
Yes, both tools can set the same gconf settings.
> - who does set the proxy for each XO, the learner or an administrator?
That depends on the exact school deployment. I can see both occurring,
("OK class open my settings then click on proxy, enter these
settings...."), pre-populate the gconf settings at image creation
time(we can create an image for a large user base), or alter these
settings via a customization key routine that we have developed.
> - what is the scope of the proxy? does each school has another one, is
> it per district, deployment...
> - what type of proxy do you set, per url or manually?
Here again, depends on the school location. All this is really
meaningless unless the proxy info is exported as an environment variable
for sugar-update-control and populate yum.conf to allow these to work
through the proxy. That's in a different patch to sugar-session. Anish
where is the patch for sugar-session?
More information about the Sugar-devel