[Sugar-devel] Sugar-Server enhancement

[Tony Anderson]

Jerry,

I apologize for the word absurd. That was emotional. I should have used 
the 24 hour rule.

The backup capability is limited to the XO since it is based on its 
serial-number. If may become applicable to SOAS by providing a generated 
serial-number for non-XO platforms.

"Please tell me that this is not being deployed, and you are just 
comparing old versions."

My point was only to show that ds_backup has been a part of Sugar since 
before SugarLabs, but yes it is being deployed.

Of course, I am free to 'roll' my own images. However, I use what I have 
from Sugarlabs (currently 13.2.5), adding capabilities that I believe 
are needed by deployments. This same process applies to xsce (currently 
xsce6) as well.

Tony


On 04/18/2016 10:59 AM, Jerry Vonau wrote:
> Hi Tony,
>
>> On April 17, 2016 at 9:06 PM Tony Anderson <tony_anderson at usa.net> wrote:
>>
>>
>> Hi, Dave
>>
>> It is absurd for reasons I have specified the first time James made this
>> statement.
> Please don't use language such as 'absurd' please, I would personally find
> that offensive if it were directed towards me or my ideas. You are not
> gaining anything by doing that, just cutting down a skilled developer.
>
>
>> The two scripts are in /usr/bin. They are invoked by the
>> installed Sugar image.
> That 'sugar' image was assembled by somebody who used the OLPC supplied
> rpms, and are only available on the XOs, not on SoaS or to my knowledge
> anywhere else.
>
>> The scripts are enabled by
>> /usr/lib/python2.7/site-packages/jarabe/The status is specified in
>> /home/olpc/.sugar/defaults. I have in front of me an XO-1 with Build 85
>> (Sugar 0.82.1). If has the two scripts in /usr/bin.
>>
>      ^^^^^^^^
> Please tell me that this is not being deployed, and you are just comparing
> old versions.
>   
>> This version used a file config in /home/olpc/.sugar/default (pre-dating
>> gconf, let alone gsetting). This file contains:
>>
>> [Server]
>> backup1 = SHC84201B0A at schoolserver.linuxtag:backup .
>>
>> The real problem is not the absurdity of claiming that ds_backup is not
>> part of Sugar but that the statement attempts to close community
>> discussion. I grant it may not be a capability important to James, but
>> it is to me. I have great respect for James Cameron's technical
>> capabilities. I can also understand if he does not feel that this
>> feature scratches his itch (or serves the needs of his employer).
>> However, this does not entitle him to impose his judgment on the
>> community.
>>
> You are always free to roll your own image or alter preexisting images in
> the fashion that you do now to add that functionality back if it
> disappears. OSBuilder is your friend.
>
> Jerry
>
>   
>> Tony
>>
>> On 04/18/2016 08:54 AM, Dave Crossland wrote:
>>> Hi Tony
>>>
>>> On 14 April 2016 at 04:43, Tony Anderson <tony_anderson at usa.net
>>> <mailto:tony_anderson at usa.net>> wrote:
>>>
>>>      However this is the second time he has claimed that the backup
>>>      does not have anything to do with Sugar. An absurd position.
>>>
>>>
>>> Perhaps, but as a fellow newbie, it is not obvious to me why this
>>> position is absurd. Since it seems important for people to understand,
>>> perhaps you could explain it on the wiki or developer documentation
>>> somewhere? :)
>>>
>>>      James is excellent technically, but very new to the community and
>>>      with limited understanding of the history or field use of the
>>>      systems.
>>>
>>>
>>> That's also my impression
>>>
>>>      He probably is not aware that OLPC before the Sugar splinter
>>>      proposed to actually build a hardware school server.
>>>
>>>
>>> Since I was very marginally involved in the OLPC community in 2007 I
>>> do remember this, and I see the https://github.com/XSCE/xsce codebase
>>> is very actively recently :)
>>>
>>> -- 
>>> Cheers
>>> Dave
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
> .
>