The one problem with extended attributes is that almost everything touching and/or archiving the files needs to be aware of them. Some utilities may lack this functionality, and others have to be told to actively back these up. By means of example, XO laptops have to work around the fact that the ping command in Fedora gets the permissions it needs via extended attributes for the past several years. The XO imaging solution is not extended attribute aware, and at the time it was developed ping was still commonly set setuid root. <div class="gmail_quote">On May 22, 2016 9:52 AM, "Sebastian Silva" <<a href="mailto:sebastian@fuentelibre.org">sebastian@fuentelibre.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div bgcolor="#FFFFFF" text="#000000"> Hi Utkarsh, Perhaps this is an area for improvement in Sugar. The journal datastore was designed to be more than it is now (see the git backend discussion). I always found very silly how Sugar tries very hard to hide files (even from the command line) when, in fact, it stores journal objects as files. It should be relatively simple to modify the Journal to save its objects as regular files, and store the metadata in "filesystem extended attributes" (please look that up). I believe this would relieve a lot of confusion (in the ground) around the journal (like you are having). Perhaps Tony and the community can be convinced this is a good idea to implement. Please read in detail the Sugar Human Interface Guidelines, which describe the Sugar design in detail. Also read James Simmons Make-Your-Own-Sugar-Activities which describes a good attempt to make sense of the implementation from a Sugar Activity developer perspective. With regards to the Documents directory, use the source, look up in the journal code exactly how it decides. A good, standards compliant implementation would use the result of the `<tt>xdg-user-dir DOCUMENTS</tt>` command. Are you using system Sugar packages or sugar-build? sugar-build probably overrides this. Regards, Sebastian <div>El 22/05/16 a las 05:55, Tony Anderson escribió: </div> <blockquote type="cite">Hi, Utkarsh I may not be able to help. I am testing on an XO. However, the object is not to use direct paths which may vary between SOAS and Sugar on an XO. Documents should be ~/Documents. Journal objects are stored in ~/.sugar/default/datastore. However, if you only reference the datastore with the datastore class -that shouldn't be important. So you can write them with datastore to the Journal. For Documents, I use ~/Documents but there is a way to change the 'mount' in the datastore to use the Documents folder (or to use a USB key). Tony On 05/22/2016 12:27 PM, Ütkarsh Tiwari wrote: <blockquote type="cite">Hi, I am unable to find the location where the sugar-build stores the Documents and Journal objects. I would also like to know how to copy the external files (.html, .txt, .png, .zip files - outside sugar-build) to Journal or Documents. P.S- I am on Ubuntu 15.04 Thanks, Utkarsh Tiwari _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote> _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote> </div> _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div>