[Sugar-devel] [IAEP] Getting data about the upgrading older machines and SoaS responsiveness.

[David Van Assche]

That's a good point, and I understand the thinking behind it, as if you are
not 'changing' anything in an existing setup, people are less afraid that
things might go terribly wrong. That's the reason we have ltsp on a usb
stick... because you can stick in a server, and test it without installing
anything. Think of it as SoaS server with beaurocratic advantages included
(taking care of networking, providing Sugar images, setting up user
accounts, providng collaboration if necessary. It is by no means the XS
server, nor should it try to be that, its just the desktop environment part
with ejabberd, if needed.. of course, it only works in wired environments.

kind Regards,
David (nubae) Van Assche

On Sun, Jun 7, 2009 at 8:19 PM, David Farning <dfarning at sugarlabs.org>wrote:

> On Sun, Jun 7, 2009 at 12:24 PM, David Van Assche<dvanassche at gmail.com>
> wrote:
> > When it come to older pcs, it really makes sense to try and use LTSP. We
> > have created a kiwi-ltsp usb stick for openSUSE, which gives a portable
> ltsp
> > server wherever u plug it in. In most cases it would make sense for this
> to
> > be the most powerful computer. It is as easy as installing the sugar and
> > sugar activities meta packages on this usb image and the users on the
> ltsp
> > network then have access to Sugar from any computer in the network, and
> they
> > are bound to load faster than from a usb image. The advantage is u need
> one
> > usb stick per network, as opposed to one for each terminal... that saves
> > costs, and time. Also, u dont need any of the old hardware, such as cdrom
> > drives, hard drives, etc. Networking and internet is also no issue as if
> it
> > works on the server, it has to work on each of the terminals too...
>
> SoaS is also working on a slightly different issue.
>
> I didn't understand it until Caroline explained it for about the 100th
> time yesterday:)
>
> In addition to all the technical hurdles.  Sugar on a Stick is
> tackling the _bureaucratic_ issue of installing and running Sugar (or
> any software) on systems which one doesn't have admin access.
>
> In many schools it can be difficult to get the authority to install
> software or modify the configuration on their computers.  SoaS
> circumvents that problem by replacing  'install a new OS' with 'insert
> the stick and turn it on.'
>
> The piece that I was _misunderstanding_ was that all of the
> technically hurdles that SoaS introduces are worth the ability to
> circumvent the bureaucratic hurdles.
>
> FWIW, at least in developed nations.... Once you get the bureaucratic
> permission to 'install' Sugar, a client-server configuration is most
> palatable to the existing generation of elementary school sysadmins.
>
> david
>
> > kind Regards,
> > David (nubae) Van Assche
> >
> > On Sun, Jun 7, 2009 at 5:27 PM, Frederick Grose <fgrose at gmail.com>
> wrote:
> >>
> >> On Sun, Jun 7, 2009 at 10:07 AM, Caroline Meeks
> >> <caroline at solutiongrove.com> wrote:
> >>>
> >>> Let me echo Caryl's question. Do we have a page with tasks for new
> >>> volunteers?
> >>
> >> http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO has been restored
> and
> >> is ready to be updated, perhaps restructured to cover this need.
> >>
> >>          --Fred
> >>
> >> _______________________________________________
> >> IAEP -- It's An Education Project (not a laptop project!)
> >> IAEP at lists.sugarlabs.org
> >> http://lists.sugarlabs.org/listinfo/iaep
> >
> >
> > _______________________________________________
> > IAEP -- It's An Education Project (not a laptop project!)
> > IAEP at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/iaep
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/archive/sugar-devel/attachments/20090607/221627f9/attachment.htm