Sugar Labs - User contributions [en]

Google Code In 2016

2016-11-10T19:16:09Z

Julio Daniel Reyes: /* Mentors */

<noinclude>[[Category:Trac Reference]][[Category:Idea]]
[[Category: GCI2015]]</noinclude>

This is the project page for the Sugar Labs application to [https://developers.google.com/open-source/gci/ Google Code In 2016]. Sugar Labs community members: please feel free to add tasks below. We'll do an edit before final applications are due the first week of November 2016.

== Message to potential participants ==

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

https://developers.google.com/open-source/gci/resources/contest-rules

Please see the Contest Rules for Eligibility and Registration process.

https://developers.google.com/open-source/gci/resources/contest-rules

'''Details regarding the required forms and paperwork are here: [[Google Code In 2015/Participate#Students]].'''

Also, you will likely need to set up the Sugar development environment. See http://developer.sugarlabs.org/dev-environment.md.html for details. Further information about contributing to the project can be found here: http://developer.sugarlabs.org/

Please don't hesitate to ask questions on our irc channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org

== Why we are participating ==

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

== Some background from GCI ==

[See https://developers.google.com/open-source/gci/resources/getting-started]

===Open Source Fundamentals ===

You can contribute without being a coder!
You do not have to be a coder to contribute to open source. There are many different skill sets needed to help an open source community thrive:
;Documentation: If you are a good writer and enjoy attention to detail then you might want to contribute by writing or editing documentation. Documentation is a huge part of a successful open source project. Organizations need documentation to help attract new contributors as it helps them see what the codebase looks like and where things are and what the plan is for the project.
;Research: An organization may need help crunching numbers or sorting through pages of documents to better understand what the users want or need. There are many different types of tasks that students could work on that are very important to the health of the project.
;Outreach: If you have an outgoing personality and like being around and talking to people, take a look at the outreach tasks. Outreach tasks often include hosting meetups in your local community or creating a plan on how people around the globe can host a meetup about the project in their local communities.
;Training: You could create a YouTube video discussing a new feature of the project or maybe some basics on what the project does so people who haven’t heard about it can understand the project and get involved.
;User Interface: User interface can include many types of tasks including designing new aspects of a webpage or creating a new logo for the project. It may also include various accessibility opportunities to help make the project easier for people who are blind.
;Other: If you have an idea that may help an organization, reach out to them and let them know! Sometimes the best task is one that the organization hasn’t even considered yet.
=== Collaboration===
Open source is not just about coding but working with other people to find the best solution. Being a part of the community is an essential part of success in Google Code-in. Mentors tell us every year that their best students were the ones who worked hard on their projects but also participated on IRC and helped answer questions other students had. Collaborate with the community and mentors on the #sugar channel in the irc.freenode.net network.

=== Quality over Quantity ===

It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.

== Some basics about Sugar Labs ==

For some basics about the project, see [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

=== Getting started with coding ===

Sugar development is in either Python or Javascript.

* You will need knowledge of Python and GTK (See http://python-gtk-3-tutorial.readthedocs.org/en/latest/);
* or Javascript/HTML5;
* and then the basic of Sugar development (See http://www.flossmanuals.net/make-your-own-sugar-activities/);
* and to have a Sugar development environment running (See http://developer.sugarlabs.org).

Please note that you must run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and pyflakes on your code ''before'' submitting your patches.

=== Getting started with GIT ===

Some knowledge of git is important as your work will be submitted to our git repository (https://github.com/sugarlabs). The basic mechanism is a pull request (PR), which is detailed in [http://developer.sugarlabs.org/contributing.md.html].

GitHub provides a tutorial (See https://try.github.io/levels/1/challenges/1), although there are many others as well.

Note that our bug tracker is http:bugs.sugarlabs.org.

=== Getting started with Sugarizer ===

Sugar Web Framework is the JavaScript Framework for Sugar [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md]. Sugarizer [http://sugarizer.org] is a subset of Sugar that allow runing activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.

== This is a stub for 25+ example tasks new for GCI 2016. ==

# Investigate Google Fuzzing tool (Research)
# Decimal places in Calculate activity (Code: Pyhton)
# Music Blocks examples (Documentation/Training)
# Space team activity (Code: Python)
# Bugzilla clean up (QA)
# Teach me how to draw activity (Code: Python)
# Manage order of blocks in Turtle plugins (Code: Javascript)
# Plugin manager for Turtle JS (Code: Javascript)
# Refactor pitch-time matrix code (Code: Javascript)
# Fix scrolling problem with pitch-time matrix (Code: Javascript)
# Refactor Training activity to be non-specific to Australia (Code: Python)
# Refactor Turtle graphics to adopt look of Javascript version (Code: Python)
# Improvements to Lilypond interface (Code: Javascript)
# Add drum icons in Music Blocks (Design)
# Add more synths/sound fonts to Music Blocks (Research)
# Add ABC import to Music Blocks (Code: Javascript)
# Add ABC export to Music Blocks (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Refactor Planet server for Turtle Blocks (Code: Python)
# Research graphics caching in Turtle (Research)
# Wiki cleanup (Documentation)
# Make trash areas smaller on Turtle (Code: Javascript)
# Write a Turtle plugin (Code: Javascript)
# Write a Pinetrest plugin for the Sugar Journal (Code: Python)
# Investigate CSound/Python version of Music Blocks (Code: Python)
# Add synth lab widget to Music Blocks (Code: Javascript)
# Backport a web plugin from Turtle Blocks JS to Python (Code: Python)
# Turtle write directly to the canvas instead of using Easel (Code: Javascript)
# Visualize turtle movements in Pitch-Time Matrix (Code: Javascript)
# Visualize turtle pitch in Music Blocks project (Code: Music Blocks)
# Visualize turtle pitch in Music Blocks widget (Code: Javascript)
# Synonym-Antonym activity to lassify them correctly (Code: Javascript)
# Create a zoo activity - Differentiate between animals, birds, reptiles etc (Code: Javascript)
# Laser mirror reflection game activity



===Beginner Tasks===
We have several tasks that are targeting people new to Sugar and Sugar development. You are only allowed to complete two beginner tasks.
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
|Install the Sugar development environment||Following the instruction at [http://developer.sugarlabs.org/dev-environment.md.html], set up the Sugar development environment. Submit a screen-shot of the development environment running to complete this task. You can get help on our irc channel should you run into any difficulties.|| 48 || all || beginner
|-
|Install Sugar in a virtual machine||If your intention is to focus on documentation and training or outreach, then you may want to install Sugar in a virtual machine. Following the instructions at [http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Tutorials][http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Virtual_machines][http://wiki.sugarlabs.org/go/Downloads#Virtual_Machines_on_all_platforms], set up the Sugar development environment. Submit a screen-shot of the development environment running to complete this task. You can get help on our irc channel should you run into any difficulties.|| 48 || all || beginner
|-
|Create an example program in Turtle Blocks||We distribute examples with the Turtle Blocks programming environment. Create your example -- some art, some geometry, some multimedia, a simple game -- to be included with the package. Deliverable is a Turtle Blocks project file to be reviewed by Sugar Labs designers and educators. (Use either the Python version bundled with Sugar or the Javascript version at [http://turtle.sugarlabs.org Turtle Blocks JS]) One source of inspiration might be [https://www.pinterest.com/walterbender/turtle-art/]. || 48 || all || beginner
|-
|Create an example program in Music Blocks||We distribute examples with the [http://walterbender.github.io/musicblocks Music Blocks] programming environment. Create your example -- some music (and art) -- to be included with the package. Deliverable is a Music Blocks project file to be reviewed by Sugar Labs designers and educators. || 48 || all || beginner
|-
|Create a simple machine in Physics||We distribute examples with the [http://activities.sugarlabs.org/en-US/sugar/addon/4193 Physics Activity]. Create a simple machine we can include in the examples collection -- some interesting mechanical device. Deliverable is a Physics activity project file to be reviewed by Sugar Labs designers and educators. || 48 || all || beginner
|}

===Documentation/Training===
Tasks related to creating/editing documents and helping others learn more

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
|Update the Sugar Labs entry in Wikipedia|| The Sugar Labs entry in Wikipedia could use some TLC. Please bring it up to date. || 48 || Walter || Documentation
|-
|Update the Sugar Labs wiki page on git||The [[Activity Team/Git Tutorial]] is out of date: we have migrated to GitHub. Please update the page to reflect the GitHub workflow. See http://developer.sugarlabs.org/contributing.md.html for more details || 48 || Walter || Documentation
|-
|Turtle Blocks Programming Guide 1|| Add live examples missing from the [https://github.com/walterbender/turtleblocksjs/blob/master/guide/README.md Guide to Programming with Turtle Blocks]. || 48 || Walter || Documentation
|-
|Turtle Blocks Programming Guide 2|| Extend the [https://github.com/walterbender/turtleblocksjs/blob/master/guide/README.md Guide to Programming with Turtle Blocks] to include more examples. || 48 || Walter || Documentation
|-
|Music Blocks Programming Guide|| Extend the [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide to Programming with Music Blocks] to include more examples. || 48 || Walter || Documentation
|-
|Turtle Blocks Classroom Guide||Write a guide on how to use Turtle Blocks in the classroom -- a manual for teachers who might want to engage in programming. Please consult with a classroom teacher when creating the guide.|| 96 || Walter || Documentation
|-
|Music Blocks Classroom Guide||Write a guide on how to use Music Blocks in the classroom -- a manual for teachers who might want to engage in programming with Music. Please consult with a music teacher when creating the guide.|| 96 || Walter || Documentation
|-
|Sugarizer Server API Documentation||Write a documentation for the REST API for Sugarizer Server. Include some GET/POST/DELETE sample inside || 48|| Lionel || Documentation
|-
|Sugarizer Server Collaboration Tutorial||Write a tutorial on how to connect a Sugarizer Client to a Sugarizer Server and how to use it to do Journal sharing and collaboration || 24 || Lionel || Documentation
|-
|Sugarizer wiki page||Write a Sugarizer page in the SugarLabs wiki || 24 || Lionel || Documentation
|}

For information about how to create help pages for activities

http://wiki.sugarlabs.org/go/Activities/Help/Contribute

https://github.com/godiard/help-activity/blob/master/source/restructuredtext.rst

https://github.com/godiard/help-activity/blob/master/source/collaborating.rst

===Outreach/Research===
Tasks related to community management, outreach/marketing, or studying problems and recommending solutions

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
|Turtle Art Day||Organize a Turtle Art Day in your community. Details at [http://people.sugarlabs.org/walter/Guia_Ingles_10-08-2013.pdf]||96||Walter||Outreach
|-
|Promo Video||Create a 60 second promotional video on Sugar and its community.||96||Mariah||Outreach
|-
|Hangout Q&A||Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. Invite friends, family, peers, as well as academic and community leaders.||96||Mariah||Outreach
|-
|Local Lab Wiki||Create/update a "Local Lab" page for your area/country. Fill in the page with information on the Sugar community in your area. This could include contact information, mailing lists, events and any other information that may be relevant. ||96||Mariah||Research
|-
|How-To Guide||Create a guide for how to host your own DIY Sugar on a Stick party. The guide should include at least two promotional item designs (like a sticker, brochure, flyer). Feel free to change the name to something else. ||96||Mariah||Outreach
|-
|DIY Sugar on a Stick||Organize and host a Sugar on a Stick party where you show people how to make their own Sugar on a Stick. Then, hold a workshop on the basics of using Sugar. Take pictures to document the experience. Post a blog about it.||96||Mariah||Outreach
|-
|Potential Users||Gather information on who could benefit from using or knowing about Sugar. Look at non-profit organizations, academic institutions, the home-school community. Build a database including contact information, website URLS, social media profiles, and any other relevant information.||96||Mariah||Research
|-
|Sugar Tools & Resources||Find the resources that people are using throughout the world to learn about or teach Sugar Activities. This can include manuals, teacher guides, YouTube videos, blogs, etc. Document what type of resource it is, the URL for the resource, the target audience of the resource and whether it is up-to-date.||96||Mariah||Research
|-
|Introduce Yourself||Write a blog post about why you are participating in Google Code-In, what you hope to learn from the GCI and how Sugar Labs can help you. Include a picture. Share blog post through social media.||48||Mariah||Outreach
|-
|Interview a GCI Peer||Interview another Sugar Labs GCI participant. Ask them questions about how they are selecting/completing tasks, any successes/struggles they are having, etc. Post on participant blog. Share blog post through social media.||48||Mariah||Outreach
|--
|Interview an Educator||Find an educator who is using open-source educational software to teach. Interview the educator about their experience as an educator and why they are using open-source software to teach. Post about it on the blog, include a picture. Share the blog post through social media and with the educator.||48||Mariah||Outreach|
|-
|Review an Activity||Write a review about an Activity in Sugar. Explain how you use it, what kind of project you could do with it, any bugs it might have, etc. Post your review. The review can be a video review or a written review with screenshots. Share the blog post through social media.||48||Mariah||Outreach
|-
|Women in the Sugar Community||Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. Write a blog post about what you learned when making this presentation and include a link to the presentation.||48||Mariah||Outreach
|-
|Wrap-Up||Write a blog post about your experience as a GCI participant for Sugar Labs. Share your thoughts on what was successful and what can be improved for next year's participants. Feel free to include pictures, videos, links to work that you are most proud of. Share the post through social media.||48||Mariah||Outreach
|}

===User Interface===
Tasks related to user experience research or user interface design and interaction

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
|Icon design for Music Blocks||The icons used for the main toolbar in Music Block don't "sing" to me. This task is to design better icons both in terms of expressing the intention of the button and visual engagement of the user. || 72 || Walter, Devin || UI, design
|-
|Classroom collaboration|| Sugar provides tools for sharing and collaborating among students, e.g., peer editing of texts, chat, group programming, etc. Survey the list of collaboration-enabled activities and categorize them by whether they are learning utilities, classroom management utilities, communication, games, etc. || 72 || Walter || UI, pedagogy
|-
|Classroom management 1|| Sugar provides only a few tools for classroom management, e.g., the Share With Teacher webservice. Survey classroom services that run either as web services or native in desktop environments.|| 72 || Walter || UI, pedagogy
|-
|Classroom management 2|| Sugar provides only a few tools for classroom management, e.g., the Share With Teacher webservice. Which of the results from the Classroom management 1 task would be useful to incorporate into the Sugar ecosystem? Evaluation should include s description of the service and a sketch of how the user interaction would work. || 72 || Walter || UI, pedagogy
|-
|Sugar on a small screen|| Sugar was originally designed as a desktop environment for small computers. But these days, many children have access to smart phones rather than computers. This task is to make some sketches as to how Sugar might be redesigned for a smart phone form-factor. A series of annotated sketches should be made as part of completing this task. || 72 || Walter || UI
|-
|Programming on a small screen|| We put an emphasis on programming in Sugar. One popular programming environment is Turtle Blocks. Recently we made a Javascript version that can run in a browser (and hence on a smart phone). How should the UI change to accommodate that form-factor? A series of annotated sketches should be made as part of completing this task. || 72 || Walter || UI
|-
|End-user customization||We try to encourage our users to re-imagine Sugar as they'd like it. Users can change the icon layout, the background screen, and the XO avatar. What else should be made easier to customize with minimal programming? || 72 || Walter || UI
|-
|Sugarizer marketing web page||Create a marketing web page to explain what is Sugarizer and replace the [http://sugarizer.org current one] || 40 || Lionel || UI
|}

===Quality Assurance===
Tasks related to testing and ensuring code is of high quality.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
|Behavior diff for Turtle Blocks JS|| [https://turtle.sugarlabs.org Turtle Blocks JS] is a Javascript port from the Python version of the activity. The goal of this task is to document any differences in behavior between the two versions.||72||Walter||QA
|-
|Unit tests for JS activities||We have no unit tests for our Javascript activities. This task is to investigate approaches to unit testing in Javascript||72||Walter||QA
|-
|Test Sugar on a Stick || Help test the latest Sugar on a Stick on Fedora (F24). See https://wiki.sugarlabs.org/go/Fedora_24#fedora_24, [http://dl.fedoraproject.org/pub/alt/unofficial/releases/24/ #fedora-qa (freenode IRC). Deliverable is a report of the major Sugar features, e.g., desktop, journal, collaboration, and the core activities, e.g., Write, Browse, Turtle, Chat, Speak, etc. || 48 || Satellit || QA, SoaS
|-
|fix f25 Soas|f25 Soas currently does not login to liveuser.|| see: https://bugzilla.redhat.com/show_bug.cgi?id=1363915, https://qa.fedoraproject.org/blockerbugs/milestone/25/final/buglist], Task is to fix this bug||72|| || QA
|-
|Interview a teacher|| Ultimately the quality of our work is determined by our end users. Interview a classroom teacher who is using Sugar and solicit feedback about what works, what doesn't. || 72 || Walter || QA
|-
|Interview a student|| Ultimately the quality of our work is determined by our end users. Interview a student who is using Sugar in school and solicit feedback about what works, what doesn't. || 72 || Walter || QA
|}





== Mentors ==
;NOTES TO MENTORS:
:Please refer to [[Google Code In 2016/Participate#Mentors]] for details regarding enrolling as a mentor.
:Please add yourself to the list below.
:Feel free to add new tasks to the table above.

Depending on the project, we will assign multiple mentors from our various development and support teams.

* Walter Bender - also org admin for GCI
* Sam Parkinson
* Ignacio Rodriguez
* Lionel Laské
* Batchu Venkat Vishal
* Ibiam Chihurumnaya
* Utkarsh Tiwari
* Abhijit Patel
* Julio Reyes

User:Daksh Shah

2015-12-08T01:48:18Z

Julio Daniel Reyes: /* Google Code-in */

== Google Code-in ==
{| class="wikitable"
|-
! Task
! Task Page Link
|-
| Install the Sugarizer Client development environment
| https://codein.withgoogle.com/dashboard/task-instances/5091163702820864/
|-
| Second Task
| And his link
|}

Google Code In 2015

2015-10-24T14:48:04Z

Julio Daniel Reyes: /* Mentors */

<noinclude>[[Category:Trac Reference]][[Category:Idea]]
[[Category: GCI2015]]</noinclude>
This is the project page for the Sugar Labs application to [http://www.google-melange.com/gci/homepage/google/gci2015 Google Code In 2015]. Sugar Labs community members: please feel free to add tasks below. We'll do an edit before final applications are due the first week of November 2015.

== Message to potential participants ==

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

https://developers.google.com/open-source/gci/resources/contest-rules

Please see the Contest Rules for Eligibility and Registration process.

https://developers.google.com/open-source/gci/resources/contest-rules

'''Details regarding the required forms and paperwork are here: [[Google Code In 2015/Participate#Students]].'''

Also, you will likely need to set up the Sugar development environment. See http://developer.sugarlabs.org/dev-environment.md.html for details. Further information about contributing to the project can be found here: http://developer.sugarlabs.org/

Please don't hesitate to ask questions on our irc channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org

== Why we are participating ==

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

== Some background from GCI ==

[See https://developers.google.com/open-source/gci/resources/getting-started]

===Open Source Fundamentals ===

You can contribute without being a coder!
You do not have to be a coder to contribute to open source. There are many different skill sets needed to help an open source community thrive:
;Documentation: If you are a good writer and enjoy attention to detail then you might want to contribute by writing or editing documentation. Documentation is a huge part of a successful open source project. Organizations need documentation to help attract new contributors as it helps them see what the codebase looks like and where things are and what the plan is for the project.
;Research: An organization may need help crunching numbers or sorting through pages of documents to better understand what the users want or need. There are many different types of tasks that students could work on that are very important to the health of the project.
;Outreach: If you have an outgoing personality and like being around and talking to people, take a look at the outreach tasks. Outreach tasks often include hosting meetups in your local community or creating a plan on how people around the globe can host a meetup about the project in their local communities.
;Training: You could create a YouTube video discussing a new feature of the project or maybe some basics on what the project does so people who haven’t heard about it can understand the project and get involved.
;User Interface: User interface can include many types of tasks including designing new aspects of a webpage or creating a new logo for the project. It may also include various accessibility opportunities to help make the project easier for people who are blind.
;Other: If you have an idea that may help an organization, reach out to them and let them know! Sometimes the best task is one that the organization hasn’t even considered yet.
=== Collaboration===
Open source is not just about coding but working with other people to find the best solution. Being a part of the community is an essential part of success in Google Code-in. Mentors tell us every year that their best students were the ones who worked hard on their projects but also participated on IRC and helped answer questions other students had.

=== Quality over Quantity ===

It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.

== Some basics about Sugar Labs ==

For some basics about the project, see [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

=== Getting started with coding ===

Sugar development is in either Python or Javascript.

* You will need knowledge of Python and GTK (See http://python-gtk-3-tutorial.readthedocs.org/en/latest/);
* or Javascript/HTML5;
* and then the basic of Sugar development (See http://www.flossmanuals.net/make-your-own-sugar-activities/);
* and to have a Sugar development environment running (See http://developer.sugarlabs.org).

Please note that you must run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and pyflakes on your code ''before'' submitting your patches.

=== Getting started with GIT ===

Some knowledge of git is important as your work will be submitted to our git repository (https://github.com/sugarlabs). The basic mechanism is a pull request (PR), which is detailed in [http://developer.sugarlabs.org/contributing.md.html].

GitHub provides a tutorial (See https://try.github.io/levels/1/challenges/1), although there are many others as well.

Note that our bug tracker is http:bugs.sugarlabs.org.

== Tasks ==
'''Note:''' This is our preliminary list of tasks. We can add more as the contest progresses.

Mentors: please feel free to add more tasks and/or add yourself as a potential mentor to an existing task.

Tasks must fall within one of these five categories: [[#Documentation/Training]]; [[#Outreach/Research]]; [[#User Interface]]; [[#Quality Assurance]]; and [[#Code]].

===Beginner Tasks===
We have several tasks that are targeting people new to Sugar and Sugar development. You are only allowed to complete two beginner tasks.
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
|Install the Sugar development environment||Following the instruction at [http://developer.sugarlabs.org/dev-environment.md.html], set up the Sugar development environment. Submit a screen-shot of the development environment running to complete this task. You can get help on our irc channel should you run into any difficulties.|| 48 || all || beginner
|-
|Install Sugar in a virtual machine||If your intention is to focus on documentation and training or outreach, then you may want to install Sugar in a virtual machine. Following the instructions at [http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Tutorials][http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Virtual_machines][http://wiki.sugarlabs.org/go/Downloads#Virtual_Machines_on_all_platforms], set up the Sugar development environment. Submit a screen-shot of the development environment running to complete this task. You can get help on our irc channel should you run into any difficulties.|| 48 || all || beginner
|-
|Create an example program in Turtle Blocks||We distribute examples with the Turtle Blocks programming environment. Create your example -- some art, some geometry, some multimedia, a simple game -- to be included with the package. Deliverable is a Turtle Blocks project file to be reviewed by Sugar Labs designers and educators. (Use either the Python version bundled with Sugar or the Javascript version at [http://turtle.sugarlabs.org Turtle Blocks JS]) || 48 || all || beginner
|-
|Create an example program in Music Blocks||We distribute examples with the [http://walterbender.github.io/musicblocks Music Blocks] programming environment. Create your example -- some music (and art) -- to be included with the package. Deliverable is a Music Blocks project file to be reviewed by Sugar Labs designers and educators. || 48 || all || beginner
|-
|Create a simple machine in Physics||We distribute examples with the [http://activities.sugarlabs.org/en-US/sugar/addon/4193 Physics Activity]. Create a simple machine we can include in the examples collection -- some interesting mechanical device. Deliverable is a Physics activity project file to be reviewed by Sugar Labs designers and educators. || 48 || all || beginner
|}

===Documentation/Training===
Tasks related to creating/editing documents and helping others learn more

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
|Update the Sugar Labs entry in Wikipedia|| The Sugar Labs entry in Wikipedia could use some TLC. Please bring it up to date. || 48 || Walter || Documentation
|-
|Update the Sugar Labs wiki page on git||The [[Activity Team/Git Tutorial]] is out of date: we have migrated to GitHub. Please update the page to reflect the GitHub workflow. See http://developer.sugarlabs.org/contributing.md.html for more details || 48 || Walter || Documentation
|-
|Turtle Blocks Programming Guide|| Extend the [https://github.com/walterbender/turtleblocksjs/blob/master/guide/README.md Guide to Programming with Turtle Blocks] to include more examples. || 48 || Walter || Documentation
|-
|Music Blocks Programming Guide|| Extend the [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide to Programming with Music Blocks] to include more examples. || 48 || Walter || Documentation
|-
|Turtle Blocks Classroom Guide||Write a guide on how to use Turtle Blocks in the classroom -- a manual for teachers who might want to engage in programming. Please consult with a classroom teacher when creating the guide.|| 96 || Walter || Documentation
|-
|Music Blocks Classroom Guide||Write a guide on how to use Music Blocks in the classroom -- a manual for teachers who might want to engage in programming with Music. Please consult with a music teacher when creating the guide.|| 96 || Walter || Documentation
|}

For information about how to create help pages for activities

http://wiki.sugarlabs.org/go/Activities/Help/Contribute

https://github.com/godiard/help-activity/blob/master/source/restructuredtext.rst

https://github.com/godiard/help-activity/blob/master/source/collaborating.rst

===Outreach/Research===
Tasks related to community management, outreach/marketing, or studying problems and recommending solutions

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
|Turtle Art Day||Organize a Turtle Art Day in your community. Details at [http://people.sugarlabs.org/walter/Guia_Ingles_10-08-2013.pdf]||96||Walter||Outreach
|-
|Promo Video||Create a 60 second promotional video on Sugar and its community.||96||Mariah||Outreach
|-
|Hangout Q&A||Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. Invite friends, family, peers, as well as academic and community leaders.||96||Mariah||Outreach
|-
|Local Lab Wiki||Create/update a "Local Lab" page for your area/country. Fill in the page with information on the Sugar community in your area. This could include contact information, mailing lists, events and any other information that may be relevant. ||96||Mariah||Research
|-
|How-To Guide||Create a guide for how to host your own DIY Sugar on a Stick party. The guide should include at least two promotional item designs (like a sticker, brochure, flyer). Feel free to change the name to something else. ||96||Mariah||Outreach
|-
|DIY Sugar on a Stick||Organize and host a Sugar on a Stick party where you show people how to make their own Sugar on a Stick. Then, hold a workshop on the basics of using Sugar. Take pictures to document the experience. Post a blog about it.||96||Mariah||Outreach
|-
|Potential Users||Gather information on who could benefit from using or knowing about Sugar. Look at non-profit organizations, academic institutions, the home-school community. Build a database including contact information, website URLS, social media profiles, and any other relevant information.||96||Mariah||Research
|-
|Sugar Tools & Resources||Find the resources that people are using throughout the world to learn about or teach Sugar Activities. This can include manuals, teacher guides, YouTube videos, blogs, etc. Document what type of resource it is, the URL for the resource, the target audience of the resource and whether it is up-to-date.||96||Mariah||Research
|-
|Introduce Yourself||Write a blog post about why you are participating in Google Code-In, what you hope to learn from the GCI and how Sugar Labs can help you. Include a picture. Share blog post through social media.||48||Mariah||Outreach
|-
|Interview a GCI Peer||Interview another Sugar Labs GCI participant. Ask them questions about how they are selecting/completing tasks, any successes/struggles they are having, etc. Post on participant blog. Share blog post through social media.||48||Mariah||Outreach
|--
|Interview an Educator||Find an educator who is using open-source educational software to teach. Interview the educator about their experience as an educator and why they are using open-source software to teach. Post about it on the blog, include a picture. Share the blog post through social media and with the educator.||48||Mariah||Outreach|
|-
|Review an Activity||Write a review about an Activity in Sugar. Explain how you use it, what kind of project you could do with it, any bugs it might have, etc. Post your review. The review can be a video review or a written review with screenshots. Share the blog post through social media.||48||Mariah||Outreach
|-
|Women in the Sugar Community||Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. Write a blog post about what you learned when making this presentation and include a link to the presentation.||48||Mariah||Outreach
|-
|Wrap-Up||Write a blog post about your experience as a GCI participant for Sugar Labs. Share your thoughts on what was successful and what can be improved for next year's participants. Feel free to include pictures, videos, links to work that you are most proud of. Share the post through social media.||48||Mariah||Outreach
|}

===User Interface===
Tasks related to user experience research or user interface design and interaction

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
|Icon design for Music Blocks||The icons used for the main toolbar in Music Block don't "sing" to me. This task is to design better icons both in terms of expressing the intention of the button and visual engagement of the user. || 72 || Walter || UI, design
|-
|Save file design for Music Blocks||Since Music Blocks programs don't always create artwork, when you save the project, there may be no corresponding image to associate with it. This task is to design a default graphic to use in such cases. || 72 || Walter || UI, design
|-
|Classroom collaboration|| Sugar provides tools for sharing and collaborating among students, e.g., peer editing of texts, chat, group programming, etc. Survey the list of collaboration-enabled activities and categorize them by whether they are learning utilities, classroom management utilities, communication, games, etc. || 72 || Walter || UI, pedagogy
|-
|Classroom management 1|| Sugar provides only a few tools for classroom management, e.g., the Share With Teacher webservice. Survey classroom services that run either as web services or native in desktop environments.|| 72 || Walter || UI, pedagogy
|-
|Classroom management 2|| Sugar provides only a few tools for classroom management, e.g., the Share With Teacher webservice. Which of the results from the Classroom management 1 task would be useful to incorporate into the Sugar ecosystem? Evaluation should include s description of the service and a sketch of how the user interaction would work. || 72 || Walter || UI, pedagogy
|-
|Sugar on a small screen|| Sugar was originally designed as a desktop environment for small computers. But these days, many children have access to smart phones rather than computers. This task is to make some sketches as to how Sugar might be redesigned for a smart phone form-factor. A series of annotated sketches should be made as part of completing this task. || 72 || Walter || UI
|-
|Programming on a small screen|| We put an emphasis on programming in Sugar. One popular programming environment is Turtle Blocks. Recently we made a Javascript version that can run in a browser (and hence on a smart phone). How should the UI change to accommodate that form-factor? A series of annotated sketches should be made as part of completing this task. || 72 || Walter || UI
|-
|End-user customization||We try to encourage our users to re-imagine Sugar as they'd like it. Users can change the icon layout, the background screen, and the XO avatar. What else should be made easier to customize with minimal programming? || 72 || Walter || UI
|}

===Quality Assurance===
Tasks related to testing and ensuring code is of high quality.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
|Behavior diff for Turtle Blocks JS|| [https://turtle.sugarlabs.org Turtle Blocks JS] is a Javascript port from the Python version of the activity. The goal of this task is to document any differences in behavior between the two versions.||72||Walter||QA
|-
|Unit tests for JS activities||We have no unit tests for our Javascript activities. This task is to investigate approaches to unit testing in Javascript||72||Walter||QA
|-
|Test Sugar on a Stick || Help test the latest Sugar on a Stick on Fedora (F21). See [http://dl.fedoraproject.org/pub/alt/stage/21_Beta_RC4/], [https://fedoraproject.org/wiki/Test_Results:Fedora_21_Beta_RC4_Desktop#Sugar_.28non-blocking.2C_all_arches.29] #fedora-qa (freenode IRC). Deliverable is a report of the major Sugar features, e.g., desktop, journal, collaboration, and the core activities, e.g., Write, Browse, Turtle, Chat, Speak, etc. || 48 || Satellit || QA, SoaS
|-
|Interview a teacher|| Ultimately the quality of our work is determined by our end users. Interview a classroom teacher who is using Sugar and solicit feedback about what works, what doesn't. || 72 || Walter || QA
|-
|Interview a student|| Ultimately the quality of our work is determined by our end users. Interview a student who is using Sugar in school and solicit feedback about what works, what doesn't. || 72 || Walter || QA
|}

===Code===
Tasks related to writing or refactoring code

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Tag
|-
| Sugar Bug 3921 Journal palette is not updated|| [https://bugs.sugarlabs.org/ticket/3921 Ticket 3921] Journal palette is not updated when I stay in the same column || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 4172 Set color of insensitive buttons || [https://bugs.sugarlabs.org/ticket/4172 Ticket 4172] The greyed-out "Next" button on the intro screen comes up with the text in the same colour as the background, i.e. you cant see it. || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 4461 "Volume busy" dialog appear in Sugar || [https://bugs.sugarlabs.org/ticket/4461 Ticket 4461] Trying to unmount a pendrive, a "Volume is busy" dialog appear. || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 4613 Neighborhood view should respect max_participants limit || [https://bugs.sugarlabs.org/ticket/4613 Ticket 4613] max_participants should limit the number of joiners. If the maximum has been reached, joining should be disabled and some feedback given to the user. It would also be nice if the icon indicated (with a badge, perhaps) the maximum. || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 4894 Frame settings doesn't allow option other that edge delay = 0 || [https://bugs.sugarlabs.org/ticket/4894 Ticket 4894] || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 381 Neighbourhood view icons should be placed in a spatially repeatable way || [https://bugs.sugarlabs.org/ticket/381 Ticket 381] Right now the neighbourhood view is disappointingly random || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 2478 Buttons unresponsive when launching Sugar || [https://bugs.sugarlabs.org/ticket/2478 Ticket 2478] Buttons unresponsive when launching Sugar until Journal appears on Home View || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 3006 Ad-hoc network icon mixup || [https://bugs.sugarlabs.org/ticket/3006 Ticket 3006] || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 3119 Check if the connection has been established || [https://bugs.sugarlabs.org/ticket/3119 Ticket 3119] || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 3143 Remove icon-slicer dependency || [https://bugs.sugarlabs.org/ticket/3143 Ticket 3143] || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 3708 Sugar doesn't DHCP connecting to ad-hoc wifi point || [https://bugs.sugarlabs.org/ticket/3708 Ticket 3708] || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 3831 Frame animation has regressed || [https://bugs.sugarlabs.org/ticket/3831 Ticket 3831] || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 4449 Language names are not translated || [https://bugs.sugarlabs.org/ticket/4449 Ticket 4449] "Spanish" and other language names are not translated in My Settings language section || 72 || Martin Abente || Code, Python
|-
| Sugar Bug 4693 Send to friend not working || [https://bugs.sugarlabs.org/ticket/4693 Ticket 4693] || 72 || Martin Abente || Code, Python
|-
| Turtle Confusion in Javascript || [http://activities.sugarlabs.org/en-US/sugar/addon/4450 Turtle Confusion] presents 40 shape challenges to the learner that must be completed using basic Logo-blocks. The challenges as based on Barry Newell's 1988 book, Turtle Confusion: Logo Puzzles and Riddles. This task is to implement Turtle Confusion within the framework of the [http://turtle.sugarlabs.org JavaScript version of Turtle Blocks].|| 72 || Walter || Code, JavaScript
|-
| Music Blocks Play Backwards Feature || [https://github.com/walterbender/musicblocks/issues/58 Issue 58] describes a new feature: play the notes backward. || 72 || Walter || Code, JavaScript
|-
| Music Blocks Export Matrix as HTML file Feature || [https://github.com/walterbender/musicblocks/issues/57 Issue 57] describes a new feature: export the note selection matrix as HTML. || 72 || Walter || Code, JavaScript
|-
| Music Blocks Matrix highlight Bug || [https://github.com/walterbender/musicblocks/issues/56 Issue 56] describes a bug regarding highlighting the matrix || 72 || Walter || Code, JavaScript
|-
| Music Blocks Lilypond output || [https://github.com/walterbender/musicblocks/issues/55 Issue 55] More Robust Aggregation for LilyPond output design enhancement lilypond || 72 || Walter || Code, JavaScript
|-
| Music Blocks Parsing voices || [https://github.com/walterbender/musicblocks/issues/53 Issue 53] Enhancement to Lilypond output: parsing voices when note values are simultaneous || 72 || Walter || Code, JavaScript
|-
| Music Blocks Default Tempo enhancement || [https://github.com/walterbender/musicblocks/issues/52 Issue 52] Reset tempo on clear || 72 || Walter || Code, JavaScript
|-
| Music Blocks Android || [https://github.com/walterbender/musicblocks/issues/51 Issue 51] does Tonejs work on Android? is there an alternative? || 72 || Walter || Code, JavaScript
|-
| Music Blocks Lilypond Save Button || [https://github.com/walterbender/musicblocks/issues/50 Issue 50] Save to Lilypond button design enhancement || 72 || Walter || Code, JavaScript
|-
| Music Blocks timing drifts || [https://github.com/walterbender/musicblocks/issues/49 Issue 49] We need a realtime clock || 72 || Walter || Code, JavaScript
|-
| Music Blocks Planet graphics || [https://github.com/walterbender/musicblocks/issues/44 Issue 44] Add some graphic for the planet upload/download || 72 || Walter || Code, JavaScript
|-
| Music Blocks Safari download || [https://github.com/walterbender/musicblocks/issues/37 Issue 37] Safari does not "download" the .tb files, it just opens a new window with the code in it. || 72 || Walter || Code, JavaScript
|-
| Music Blocks block highlighting is inconsistent || [https://github.com/walterbender/musicblocks/issues/32 Issue 32] Notes stay lit up during debug mode. || 72 || Walter || Code, JavaScript
|-
| Music Blocks Invert Pitches Feature || [https://github.com/walterbender/musicblocks/issues/30 Issue 30] Invert pitches clamp based on pitch interval|| 72 || Walter || Code, JavaScript
|-
| Music Blocks Skip Feature || [https://github.com/walterbender/musicblocks/issues/29 Issue 29] Play every nth note enhancement || 72 || Walter || Code, JavaScript
|-
| Music Blocks Transposition by Ratio || [https://github.com/walterbender/musicblocks/issues/28 Issue 28] Transposition by Ratio || 72 || Walter || Code, JavaScript
|-
| Music Block Matrix enhancements || [https://github.com/walterbender/musicblocks/issues/27 Issue 27] User Interaction for Matrix Improvement design enhancement || 72 || Walter || Code, JavaScript
|-
| Music Blocks playback notes slowly || [https://github.com/walterbender/musicblocks/issues/22 Issue 22] Add slow playback step-by-step mode|| 72 || Walter || Code, JavaScript
|-
| Music Blocks Synth selection || [https://github.com/walterbender/musicblocks/issues/19 Issue 19] Add support for voices/instruments/synths || 72 || Walter || Code, JavaScript
|-
| Music Blocks Build Newton's color scheme demo || [https://github.com/walterbender/musicblocks/issues/17 Issue 17] Program a demo of Newton's Color/Music dualilty|| 72 || Walter || Code, JavaScript
|-
| Music Blocks Volume enhancement || [https://github.com/walterbender/musicblocks/issues/15 Issue 15] Make volume logarithmic || 72 || Walter || Code, JavaScript
|-
| Music Blocks Restore matrix || [https://github.com/walterbender/musicblocks/issues/13 Issue 13] Restore selected blocks in Matrix || 72 || Walter || Code, JavaScript
|}

== Unsorted tasks ==
=== Sugar enhancements from bugs.sugarlabs.org ===
Each of these open tickets is potential task-worthy.
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Ticket !! Description !! Type !! Component
|-
| [http://bugs.sugarlabs.org/ticket/1646 1646] || No way to force-close (kill) an activity || enhancement || Sugar
|}

=== Sugar bugs from bugs.sugarlabs.org ===
Each of these open tickets is potential task-worthy.
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Ticket !! Description !! Type !! Component
|-
| [http://bugs.sugarlabs.org/ticket/4307 4307] || clipboard.set_with_data/set_with_owner is not introspectable || defect || Sugar
|}

=== Activity enhancements from bugs.sugarlabs.org ===
Each of these open tickets is potential task-worthy.
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Ticket !! Description !! Component
|-
| [http://bugs.sugarlabs.org/ticket/758 758] || Port to new tube API || Read
|}

== Mentors ==
;NOTES TO MENTORS:
:Please refer to [[Google Code In 2015/Participate#Mentors]] for details regarding enrolling as a mentor.
:Please add yourself to the list below.
:Feel free to add new tasks to the table above.

Depending on the project, we will assign multiple mentors from our various development and support teams.

* Walter Bender - also org admin for GCI
* Sam Parkinson
* Ignacio Rodriguez
* German
* Amit
* Martin Abente
* Mariah Noelle Villarreal
* Gary Servin Cardozo
* Rajul Srivastava
* Julio Daniel Reyes

JukyParaguay/trabajos2013/xoos

2013-05-10T14:47:26Z

Julio Daniel Reyes: /* Week 3-4. QEMU XO-1.75 arm architecture 15/04/13 - 26/04/13 */

= Journal =

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

====Links de interes:====
*[http://wiki.sugarlabs.org/index.php?title=JukyParaguay Informacion sobre el proyecto]
*[http://wiki.sugarlabs.org/go/CursoSugar2013 Curso base de Sugar]
*[http://wiki.laptop.org/ Wiki de OLPC, official releases]
*[https://sugardextrose.org/projects/dextrose/wiki/Wiki Wiki de Dextrose]
*[http://198.27.75.136/DX4/UY/latest/ Descargas Dextrose]
*[http://wiki.laptop.org/go/Firmware Informacion de firmware]
*[http://wiki.laptop.org/go/Releases Instalacion official]
*[https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation Instalacion dextrose develop]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

====Links de interes:====

*[http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686 Fedora 17]
*[http://wiki.laptop.org/go/OS_Builder Wiki OSBuilder]
*[https://git.sugarlabs.org/dx-activities-server dx-activities-server]

== ''Week 3-4. QEMU XO-1.75 arm'' 15/04/13 - 26/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

'''[http://wiki.sugarlabs.org/go/JukyParaguay/trabajos2013/xoos/qemu_tutorial Tutorial QEMU]'''

== ''Week 5-6. Inicio de juky-os'' 29/04/13 - 10/04/13 ==

Empieza el proyecto [https://git.sugarlabs.org/juky-os juky-os].

JukyParaguay/trabajos2013/xoos

2013-05-10T14:46:56Z

Julio Daniel Reyes: /* Week 5-6. Actualizacion de Actividades y Repositorios 29/04/13 - 10/04/13 */

= Journal =

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

====Links de interes:====
*[http://wiki.sugarlabs.org/index.php?title=JukyParaguay Informacion sobre el proyecto]
*[http://wiki.sugarlabs.org/go/CursoSugar2013 Curso base de Sugar]
*[http://wiki.laptop.org/ Wiki de OLPC, official releases]
*[https://sugardextrose.org/projects/dextrose/wiki/Wiki Wiki de Dextrose]
*[http://198.27.75.136/DX4/UY/latest/ Descargas Dextrose]
*[http://wiki.laptop.org/go/Firmware Informacion de firmware]
*[http://wiki.laptop.org/go/Releases Instalacion official]
*[https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation Instalacion dextrose develop]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

====Links de interes:====

*[http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686 Fedora 17]
*[http://wiki.laptop.org/go/OS_Builder Wiki OSBuilder]
*[https://git.sugarlabs.org/dx-activities-server dx-activities-server]

== ''Week 3-4. QEMU XO-1.75 arm architecture'' 15/04/13 - 26/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

'''[http://wiki.sugarlabs.org/go/JukyParaguay/trabajos2013/xoos/qemu_tutorial Tutorial QEMU]'''

== ''Week 5-6. Inicio de juky-os'' 29/04/13 - 10/04/13 ==

Empieza el proyecto [https://git.sugarlabs.org/juky-os juky-os].

JukyParaguay/trabajos2013/xoos

2013-05-10T14:45:55Z

Julio Daniel Reyes: /* juky-os */

= Journal =

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

====Links de interes:====
*[http://wiki.sugarlabs.org/index.php?title=JukyParaguay Informacion sobre el proyecto]
*[http://wiki.sugarlabs.org/go/CursoSugar2013 Curso base de Sugar]
*[http://wiki.laptop.org/ Wiki de OLPC, official releases]
*[https://sugardextrose.org/projects/dextrose/wiki/Wiki Wiki de Dextrose]
*[http://198.27.75.136/DX4/UY/latest/ Descargas Dextrose]
*[http://wiki.laptop.org/go/Firmware Informacion de firmware]
*[http://wiki.laptop.org/go/Releases Instalacion official]
*[https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation Instalacion dextrose develop]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

====Links de interes:====

*[http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686 Fedora 17]
*[http://wiki.laptop.org/go/OS_Builder Wiki OSBuilder]
*[https://git.sugarlabs.org/dx-activities-server dx-activities-server]

== ''Week 3-4. QEMU XO-1.75 arm architecture'' 15/04/13 - 26/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

'''[http://wiki.sugarlabs.org/go/JukyParaguay/trabajos2013/xoos/qemu_tutorial Tutorial QEMU]'''

== ''Week 5-6. Actualizacion de Actividades y Repositorios'' 29/04/13 - 10/04/13 ==

Empieza el proyecto [https://git.sugarlabs.org/juky-os juky-os].

JukyParaguay/trabajos2013/xoos/qemu tutorial

2013-04-26T01:51:39Z

Julio Daniel Reyes:

= Instalación y configuración de Qemu=
Esta sección es una compilación de Tutoriales para la instalación de fedora con arquitectura arm en qemu.
==Primeros pasos.==
Lo primero<ref name="Qemu-install">[https://fedoraproject.org/wiki/Architectures/ARM/Versatile_Express#Versatile_Express]Tutorial ARM/Versatile Express</ref> que necesitamos es instalar Qemu. Lo podemos hacer con el gestor de paquetes.
Para fedora:
#yum install qemu
Para otras distribuciones otra alternativa es bajar la [http://wiki.qemu.org/Download ultima version] de Qemu y compilarla.
Una vez termine nos aseguramos que lo tenemos instalado
$qemu-system-arm --version
QEMU emulator version 1.4.1, Copyright (c) 2003-2008 Fabrice Bellard

El siguiente paso es descargar una imagen de Fedora arm que podemos conseguir en su [http://fedoraproject.org/ Pagina Oficial].
Para este tutorial usamos estas:
*[http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz Img]
*[http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz Kernel]
Necesitamos la imagen .img y el kernel.tar de Versatile Express<ref name="vexpress">[http://www.arm.com/products/tools/development-boards/versatile-express/index.php]Informacion sobre Versatile Express.</ref>
Luego las descomprimimos con el comando unxz. por Ejemplo:
$unxz Fedora-17-armhfp-vexpress-mmcblk0.img.xz
$unxz Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz
y obtendremos los siguientes archivos:
:Fedora-17-armhfp-vexpress-mmcblk0.img
:Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Extraemos el tar:
$tar -x Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Accedemos a la carpeta boot del paquete del kernel
$cd armhfp-vexpress-mmcblk0/boot
y ejecutamos el script ''boot-vexpress'' o ''boot-vexpress+x'' el cual recibe 3 parametros:
#El kernel. (contenida en la carpeta boot)
#La imagen de Ram inicial. (contenida en la carpeta boot)
#La imagen de Fedora que descargamos.
Por ejemplo:
$sudo boot-vexpress vmlinuz-3.4.2-3.fc17.armv7hl initramfs-3.4.2-3.fc17.armv7hl.img /<path>/<to-image>/Fedora-17-armhfp-vexpress-mmcblk0.img
En este momento deberiamos tener la vm corriendo nuestro fedora arm.

==Redimensionar imagen==
Al correr la vm nos damos cuenta que la imagen que descargamos solo tiene unos 600 MB libres aproximadamente, lo que para nuestro proposito no es suficiente.
Vemos las particiones con fdisk:
$ fdisk Fedora-17-armhfp-vexpress-mmcblk0.img
Welcome to fdisk (util-linux 2.21.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk Fedora-17-armhfp-vexpress-mmcblk0.img: 1888 MB, 1888485376 bytes
255 heads, 63 sectors/track, 229 cylinders, total 3688448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
Fedora-17-armhfp-vexpress-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA)
Fedora-17-armhfp-vexpress-mmcblk0.img2 1044225 3688447 1322111+ 83 Linux

Para eso tenemos varias opciones. Para este tutorial vamos a redimensionar la partición principal<ref name="resize-fs">[http://askubuntu.com/questions/107228/how-to-resize-virtual-machine-disk]How to resize virtual machine disk.</ref>.
La imagen ''Fedora-17-armhfp-vexpress-mmcblk0.img'' descomprimida ocupa aproximadamente 1.8G
Para redimensionar la imagen podemos usar el comando '''qemu-img resize <filename> [+ | -]<size>'''. (La VM no debe estar activa!)
Pero primero crearemos un backup de esta imagen, un simple cp basta.
$ cp Fedora-17-armhfp-vexpress-mmcblk0.img backup.img
Luego redimensionamos la imagen, por ejemplo si queremos agregarle 5GB escribimos ''+5G''.
$ qemu-img resize Fedora-17-armhfp-vexpress-mmcblk0.img +5G
Image resized.
Ya tenemos mas espacio, y la vm puede verlo, pero todavía tenemos las viejas particiones.
Con '''fdisk''' vamos a hacer lo siguiente:
*Escribimos ''p'' para mostrar la tabla de particiones.
$ fdisk Fedora-17-armhfp-vexpress-mmcblk0.img
Welcome to fdisk (util-linux 2.21.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk Fedora-17-armhfp-vexpress-mmcblk0.img: 7257 MB, 7257194496 bytes
255 heads, 63 sectors/track, 882 cylinders, total 14174208 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
Fedora-17-armhfp-vexpress-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA)
Fedora-17-armhfp-vexpress-mmcblk0.img2 1044225 3688447 1322111+ 83 Linux
Vemos como la segunda partición empieza en el sector 1044225. Lo que vamos a hacer es borrar esa partición de la tabla de particiones y creamos una nueva que empieza en el mismo sector pero termina en otro mucho después. Luego la partición va contener un sistema de archivos valido.
*Escribimos ''d'' (delete) y elegimos la 2da partición
Command (m for help): d
Partition number (1-4): 2
Partition 2 is deleted
*Escribimos ''n'' (new) y elegimos partición primaria, la partición 2, el sector de inicio y fin. (en este caso podemos dejar los valores por defecto)
Command (m for help): n
Partition type:
p primary (1 primary, 0 extended, 3 free)
e extended
Select (default p): p
Partition number (1-4, default 2):
Using default value 2
First sector (1044225-14174207, default 1044225):
Using default value 1044225
Last sector, +sectors or +size{K,M,G} (1044225-14174207, default 14174207):
Using default value 14174207
Partition 2 of type Linux and of size 6.3 GiB is set
*Escribimos ''w'' para guardar los cambios al disco y salir de fdisk.
Command (m for help): w
The partition table has been altered!

Syncing disks.
Ahora debemos redimensionar el filesystem, Para esto necesitamos la posición de la partición en el filesystem (el offset).
Para eso usamos '''parted''' con la imagen y los argumentos ''u'' ''b'' ("unit bytes") y ''p'' ("print").
$ sudo parted Fedora-17-armhfp-vexpress-mmcblk0.img u b p
Model: (file)
Disk /<path of>/<file>/Fedora-17-armhfp-vexpress-mmcblk0.img: 7257194496B
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 32256B 534643199B 534610944B primary boot, lba
2 534643200B 7257194495B 6722551296B primary ext4
Ahora que tenemos donde empieza (534643200), creamos un ''loopback block device''<ref name="lofi">[http://en.wikipedia.org/wiki/Loop_device]Loopback block devices</ref> con el comando '''losetup -f --show -o <start block> <filedisk>'''
$ sudo losetup -f --show -o 534643200 Fedora-17-armhfp-vexpress-mmcblk0.img
/dev/loop0
''losetup'' te informa que dispositivo eligió (en este caso /dev/loop0).
ahora podemos verificar el filesystem y luego cambiar su tamaño con '''e2fsck -f /dev/loop0''' y '''resize2fs /dev/loop0'''

$ sudo e2fsck -f /dev/loop0
e2fsck 1.42.3 (14-May-2012)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs: 18715/82720 files (0.1% non-contiguous), 137245/330527 blocks

$ sudo resize2fs /dev/loop0
resize2fs 1.42.3 (14-May-2012)
Resizing the filesystem on /dev/loop0 to 1641247 (4k) blocks.
The filesystem on /dev/loop0 is now 1641247 blocks long.

Y borramos el loopback al terminar.
$ sudo losetup -d /dev/loop0

==Configurar red y ssh==
Por defecto el script que vino con el kernel que descargamos ya tiene la configuración suficiente para poder acceder a internet en modo usuario.<ref name="user-mode">[http://en.wikibooks.org/wiki/QEMU/Networking#User_mode_networking]Modo Usuario</ref>. Pero bloquea todo trafico entrante, por lo que conectarse a través de ssh, no seria posible.
La opción mas simple seria redirigir algún puerto del host, al puerto 22 de la VM <ref name="port-redirect">[http://en.wikibooks.org/wiki/QEMU/Networking#Redirecting_ports]Redireccionar Puertos</ref> con el argumento '''-redir [tcp|udp]:[hostaddr]:hostport-[guestaddr]:guestport'''
Entonces para ssh agregamos '''-redir tcp:2222::22''' al script ''boot-vexpress''.
y nos conectamos a la VM de esta forma:
$ ssh root@localhost -p 2222

==Referencias==
<references />

JukyParaguay/trabajos2013/xoos/qemu tutorial

2013-04-26T01:46:13Z

Julio Daniel Reyes:

=Instalacion y configuracion de Qemu=
Esta seccion es una compilacion de Tutoriales para la instalacion de fedora con arquitectura arm en qemu.
==Primeros pasos.==
Lo primero<ref name="Qemu-install">[https://fedoraproject.org/wiki/Architectures/ARM/Versatile_Express#Versatile_Express]Tutorial ARM/Versatile Express</ref> que necesitamos es instalar Qemu. Lo podemos hacer con el gestor de paquetes.
Para fedora:
#yum install qemu
Para otras distribuciones otra alternativa es bajar la [http://wiki.qemu.org/Download ultima version] de Qemu y compilarla.
Una vez termine nos aseguramos que lo tenemos instalado
$qemu-system-arm --version
QEMU emulator version 1.4.1, Copyright (c) 2003-2008 Fabrice Bellard

El siguiente paso es descargar una imagen de Fedora arm que podemos conseguir en su [http://fedoraproject.org/ Pagina Oficial].
Para este tutorial usamos estas:
*[http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz Img]
*[http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz Kernel]
Necesitamos la imagen .img y el kernel.tar de Versatile Express<ref name="vexpress">[http://www.arm.com/products/tools/development-boards/versatile-express/index.php]Informacion sobre Versatile Express.</ref>
Luego las descomprimimos con el comando unxz. por Ejemplo:
$unxz Fedora-17-armhfp-vexpress-mmcblk0.img.xz
$unxz Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz
y obtendremos los siguientes archivos:
:Fedora-17-armhfp-vexpress-mmcblk0.img
:Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Extraemos el tar:
$tar -x Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Accedemos a la carpeta boot del paquete del kernel
$cd armhfp-vexpress-mmcblk0/boot
y ejecutamos el script ''boot-vexpress'' o ''boot-vexpress+x'' el cual recibe 3 parametros:
#El kernel. (contenida en la carpeta boot)
#La imagen de Ram inicial. (contenida en la carpeta boot)
#La imagen de Fedora que descargamos.
Por ejemplo:
$sudo boot-vexpress vmlinuz-3.4.2-3.fc17.armv7hl initramfs-3.4.2-3.fc17.armv7hl.img /<path>/<to-image>/Fedora-17-armhfp-vexpress-mmcblk0.img
En este momento deberiamos tener la vm corriendo nuestro fedora arm.

==Redimensionar imagen==
Al correr la vm nos damos cuenta que la imagen que descargamos solo tiene unos 600 MB libres aproximadamente, lo que para nuestro proposito no es suficiente.
Vemos las particiones con fdisk:
$ fdisk Fedora-17-armhfp-vexpress-mmcblk0.img
Welcome to fdisk (util-linux 2.21.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk Fedora-17-armhfp-vexpress-mmcblk0.img: 1888 MB, 1888485376 bytes
255 heads, 63 sectors/track, 229 cylinders, total 3688448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
Fedora-17-armhfp-vexpress-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA)
Fedora-17-armhfp-vexpress-mmcblk0.img2 1044225 3688447 1322111+ 83 Linux

Para eso tenemos varias opciones. Para este tutorial vamos a redimencionar la particion principal<ref name="resize-fs">[http://askubuntu.com/questions/107228/how-to-resize-virtual-machine-disk]How to resize virtual machine disk.</ref>.
La imagen ''Fedora-17-armhfp-vexpress-mmcblk0.img'' descomprimida ocupa aproximadamente 1.8G
Para redimencionar la imagen podemos usar el comando '''qemu-img resize <filename> [+ | -]<size>'''. (La VM no debe estar activa!)
Pero primero crearemos un backup de esta imagen, un simple cp basta.
$ cp Fedora-17-armhfp-vexpress-mmcblk0.img backup.img
Luego redimencionamos la imagen, por ejemplo si queremos agregarle 5GB escribimos ''+5G''.
$ qemu-img resize Fedora-17-armhfp-vexpress-mmcblk0.img +5G
Image resized.
Ya tenemos mas espacio, y la vm puede verlo, pero todavia tenemos las viejas particiones.
Con '''fdisk''' vamos a hacer lo siguiente:
*Escribimos ''p'' para mostrar la tabla de particiones.
$ fdisk Fedora-17-armhfp-vexpress-mmcblk0.img
Welcome to fdisk (util-linux 2.21.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk Fedora-17-armhfp-vexpress-mmcblk0.img: 7257 MB, 7257194496 bytes
255 heads, 63 sectors/track, 882 cylinders, total 14174208 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
Fedora-17-armhfp-vexpress-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA)
Fedora-17-armhfp-vexpress-mmcblk0.img2 1044225 3688447 1322111+ 83 Linux
Vemos como la segunda particion empieza en el sector 1044225. Lo que vamos a hacer es borrar esa particion de la tabla de particiones y creamos una nueva que empieza en el mismo sector pero termina en otro mucho despues. Luego la particion va contener un sistema de archivos valido.
*Escribimos ''d'' (delete) y elegimos la 2da particion
Command (m for help): d
Partition number (1-4): 2
Partition 2 is deleted
*Escribimos ''n'' (new) y elegimos particion primaria, la particion 2, el sector de inicio y fin. (en este caso podemos dejar los valores por defecto)
Command (m for help): n
Partition type:
p primary (1 primary, 0 extended, 3 free)
e extended
Select (default p): p
Partition number (1-4, default 2):
Using default value 2
First sector (1044225-14174207, default 1044225):
Using default value 1044225
Last sector, +sectors or +size{K,M,G} (1044225-14174207, default 14174207):
Using default value 14174207
Partition 2 of type Linux and of size 6.3 GiB is set
*Escribimos ''w'' para guardar los cambios al disco y salir de fdisk.
Command (m for help): w
The partition table has been altered!

Syncing disks.
Ahora debemos redimencionar el filesystem, Para esto necesitamos la posicion de la particion en el filesystem (el offset).
Para eso usamos '''parted''' con la imagen y los argumentos ''u'' ''b'' ("unit bytes") y ''p'' ("print").
$ sudo parted Fedora-17-armhfp-vexpress-mmcblk0.img u b p
Model: (file)
Disk /<path of>/<file>/Fedora-17-armhfp-vexpress-mmcblk0.img: 7257194496B
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 32256B 534643199B 534610944B primary boot, lba
2 534643200B 7257194495B 6722551296B primary ext4
Ahora que tenemos donde empieza (534643200), creamos un ''loopback block device''<ref name="lofi">[http://en.wikipedia.org/wiki/Loop_device]Loopback block devices</ref> con el comando '''losetup -f --show -o <start block> <filedisk>'''
$ sudo losetup -f --show -o 534643200 Fedora-17-armhfp-vexpress-mmcblk0.img
/dev/loop0
''losetup'' te informa que dispositivo eligio (en este caso /dev/loop0).
ahora podemos verificar el filesystem y luego cambiar su tamaño con '''e2fsck -f /dev/loop0''' y '''resize2fs /dev/loop0'''

$ sudo e2fsck -f /dev/loop0
e2fsck 1.42.3 (14-May-2012)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs: 18715/82720 files (0.1% non-contiguous), 137245/330527 blocks

$ sudo resize2fs /dev/loop0
resize2fs 1.42.3 (14-May-2012)
Resizing the filesystem on /dev/loop0 to 1641247 (4k) blocks.
The filesystem on /dev/loop0 is now 1641247 blocks long.

Y borramos el loopback al terminar.
$ sudo losetup -d /dev/loop0

==Configurar red y ssh==
Por defecto el script que vino con el kernel que descargamos ya tiene la configuracion suficiente para poder acceder a internet en modo usuario.<ref name="user-mode">[http://en.wikibooks.org/wiki/QEMU/Networking#User_mode_networking]Modo Usuario</ref>. Pero bloquea todo trafico entrante, por lo que conectarse a travez de ssh, no seria posible.
La opcion mas simple seria redirigir algun puerto del host, al puerto 22 de la VM <ref name="port-redirect">[http://en.wikibooks.org/wiki/QEMU/Networking#Redirecting_ports]Redireccionar Puertos</ref> con el argumento '''-redir [tcp|udp]:[hostaddr]:hostport-[guestaddr]:guestport'''
Entonces para ssh agregamos '''-redir tcp:2222::22''' al script ''boot-vexpress''.
y nos conectamos a la VM de esta forma:
$ ssh root@localhost -p 2222

==Referencias==
<references />

JukyParaguay/trabajos2013/xoos/qemu tutorial

2013-04-25T19:53:25Z

Julio Daniel Reyes:

=Instalacion y configuracion de Qemu=
Esta seccion es una compilacion de Tutoriales para la instalacion de fedora con arquitectura arm en qemu.
==Primeros pasos.==
Lo primero<ref name="Qemu-install">[https://fedoraproject.org/wiki/Architectures/ARM/Versatile_Express#Versatile_Express]Tutorial ARM/Versatile Express</ref> que necesitamos es instalar Qemu. Lo podemos hacer con el gestor de paquetes.
Para fedora:
#yum install qemu
Para otras distribuciones otra alternativa es bajar la [http://wiki.qemu.org/Download ultima version] de Qemu y compilarla.
Una vez termine nos aseguramos que lo tenemos instalado
$qemu-system-arm --version
QEMU emulator version 1.4.1, Copyright (c) 2003-2008 Fabrice Bellard

El siguiente paso es descargar una imagen de Fedora arm que podemos conseguir en su [http://fedoraproject.org/ Pagina Oficial].
Para este tutorial usamos estas:
*[http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz Img]
*[http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz Kernel]
Necesitamos la imagen .img y el kernel.tar de Versatile Express<ref name="vexpress">[http://www.arm.com/products/tools/development-boards/versatile-express/index.php]Informacion sobre Versatile Express.</ref>
Luego las descomprimimos con el comando unxz. por Ejemplo:
$unxz Fedora-17-armhfp-vexpress-mmcblk0.img.xz
$unxz Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz
y obtendremos los siguientes archivos:
:Fedora-17-armhfp-vexpress-mmcblk0.img
:Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Extraemos el tar:
$tar -x Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Accedemos a la carpeta boot del paquete del kernel
$cd armhfp-vexpress-mmcblk0/boot
y ejecutamos el script ''boot-vexpress'' o ''boot-vexpress+x'' el cual recibe 3 parametros:
#El kernel. (contenida en la carpeta boot)
#La imagen de Ram inicial. (contenida en la carpeta boot)
#La imagen de Fedora que descargamos.
Por ejemplo:
$sudo boot-vexpress vmlinuz-3.4.2-3.fc17.armv7hl initramfs-3.4.2-3.fc17.armv7hl.img /<path>/<to-image>/Fedora-17-armhfp-vexpress-mmcblk0.img
En este momento deberiamos tener la vm corriendo nuestro fedora arm.

==Redimensionar imagen==
Al correr la vm nos damos cuenta que la imagen que descargamos solo tiene unos 600 MB libres aproximadamente, lo que para nuestro proposito no es suficiente.
Vemos las particiones con fdisk:
$ fdisk Fedora-17-armhfp-vexpress-mmcblk0.img
Welcome to fdisk (util-linux 2.21.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk Fedora-17-armhfp-vexpress-mmcblk0.img: 1888 MB, 1888485376 bytes
255 heads, 63 sectors/track, 229 cylinders, total 3688448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
Fedora-17-armhfp-vexpress-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA)
Fedora-17-armhfp-vexpress-mmcblk0.img2 1044225 3688447 1322111+ 83 Linux

Para eso tenemos varias opciones. Para este tutorial vamos a redimencionar la particion principal<ref name="resize-fs">[http://askubuntu.com/questions/107228/how-to-resize-virtual-machine-disk]How to resize virtual machine disk.</ref>.
La imagen ''Fedora-17-armhfp-vexpress-mmcblk0.img'' descomprimida ocupa aproximadamente 1.8G
Para redimencionar la imagen podemos usar el comando '''qemu-img resize <filename> [+ | -]<size>'''. (La VM no debe estar activa!)
Pero primero crearemos un backup de esta imagen, un simple cp basta.
$ cp Fedora-17-armhfp-vexpress-mmcblk0.img backup.img
Luego redimencionamos la imagen, por ejemplo si queremos agregarle 5GB escribimos ''+5G''.
$ qemu-img resize Fedora-17-armhfp-vexpress-mmcblk0.img +5G
Image resized.
Ya tenemos mas espacio, y la vm puede verlo, pero todavia tenemos las viejas particiones.
Con '''fdisk''' vamos a hacer lo siguiente:
*Escribimos ''p'' para mostrar la tabla de particiones.
$ fdisk Fedora-17-armhfp-vexpress-mmcblk0.img
Welcome to fdisk (util-linux 2.21.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk Fedora-17-armhfp-vexpress-mmcblk0.img: 7257 MB, 7257194496 bytes
255 heads, 63 sectors/track, 882 cylinders, total 14174208 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
Fedora-17-armhfp-vexpress-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA)
Fedora-17-armhfp-vexpress-mmcblk0.img2 1044225 3688447 1322111+ 83 Linux
Vemos como la segunda particion empieza en el sector 1044225. Lo que vamos a hacer es borrar esa particion de la tabla de particiones y creamos una nueva que empieza en el mismo sector pero termina en otro mucho despues. Luego la particion va contener un sistema de archivos valido.
*Escribimos ''d'' (delete) y elegimos la 2da particion
Command (m for help): d
Partition number (1-4): 2
Partition 2 is deleted
*Escribimos ''n'' (new) y elegimos particion primaria, la particion 2, el sector de inicio y fin. (en este caso podemos dejar los valores por defecto)
Command (m for help): n
Partition type:
p primary (1 primary, 0 extended, 3 free)
e extended
Select (default p): p
Partition number (1-4, default 2):
Using default value 2
First sector (1044225-14174207, default 1044225):
Using default value 1044225
Last sector, +sectors or +size{K,M,G} (1044225-14174207, default 14174207):
Using default value 14174207
Partition 2 of type Linux and of size 6.3 GiB is set
*Escribimos ''w'' para guardar los cambios al disco y salir de fdisk.
Command (m for help): w
The partition table has been altered!

Syncing disks.
Ahora debemos redimencionar el filesystem, Para esto necesitamos la posicion de la particion en el filesystem (el offset).
Para eso usamos '''parted''' con la imagen y los argumentos ''u'' ''b'' ("unit bytes") y ''p'' ("print").
$ sudo parted Fedora-17-armhfp-vexpress-mmcblk0.img u b p
Model: (file)
Disk /<path of>/<file>/Fedora-17-armhfp-vexpress-mmcblk0.img: 7257194496B
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 32256B 534643199B 534610944B primary boot, lba
2 534643200B 7257194495B 6722551296B primary ext4
Ahora que tenemos donde empieza (534643200), creamos un ''loopback block device''<ref name="lofi">[http://en.wikipedia.org/wiki/Device_file_system#Block_devices]Loopback block devices</ref> con el comando '''losetup -f --show -o <start block> <filedisk>'''
$ sudo losetup -f --show -o 534643200 Fedora-17-armhfp-vexpress-mmcblk0.img
/dev/loop0
''losetup'' te informa que dispositivo eligio (en este caso /dev/loop0).
ahora podemos verificar el filesystem y luego cambiar su tamaño con '''e2fsck -f /dev/loop0''' y '''resize2fs /dev/loop0'''

$ sudo e2fsck -f /dev/loop0
e2fsck 1.42.3 (14-May-2012)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs: 18715/82720 files (0.1% non-contiguous), 137245/330527 blocks

$ sudo resize2fs /dev/loop0
resize2fs 1.42.3 (14-May-2012)
Resizing the filesystem on /dev/loop0 to 1641247 (4k) blocks.
The filesystem on /dev/loop0 is now 1641247 blocks long.

Y borramos el loopback al terminar.
$ sudo losetup -d /dev/loop0

==Configurar red y ssh==
Por defecto el script que vino con el kernel que descargamos ya tiene la configuracion suficiente para poder acceder a internet en modo usuario.<ref name="user-mode">[http://en.wikibooks.org/wiki/QEMU/Networking#User_mode_networking]Modo Usuario</ref>. Pero bloquea todo trafico entrante, por lo que conectarse a travez de ssh, no seria posible.
La opcion mas simple seria redirigir algun puerto del host, al puerto 22 de la VM <ref name="port-redirect">[http://en.wikibooks.org/wiki/QEMU/Networking#Redirecting_ports]Redireccionar Puertos</ref> con el argumento '''-redir [tcp|udp]:[hostaddr]:hostport-[guestaddr]:guestport'''
Entonces para ssh agregamos '''-redir tcp:2222::22''' al script ''boot-vexpress''.
y nos conectamos a la VM de esta forma:
$ ssh root@localhost -p 2222

==Referencias==
<references />

JukyParaguay/trabajos2013/xoos/qemu tutorial

2013-04-25T18:27:08Z

Julio Daniel Reyes: /* Redimensionar imagen */

=Instalacion y configuracion de Qemu=
Esta seccion es una compilacion de Tutoriales para la instalacion de fedora con arquitectura arm en qemu.
==Primeros pasos.==
Lo primero<ref name="Qemu-install">[https://fedoraproject.org/wiki/Architectures/ARM/Versatile_Express#Versatile_Express], Tutorial ARM/Versatile Express</ref> que necesitamos es instalar Qemu. Lo podemos hacer con el gestor de paquetes.
Para fedora:
#yum install qemu
Para otras distribuciones otra alternativa es bajar la [http://wiki.qemu.org/Download ultima version] de Qemu y compilarla.
Una vez termine nos aseguramos que lo tenemos instalado
$qemu-system-arm --version
QEMU emulator version 1.4.1, Copyright (c) 2003-2008 Fabrice Bellard

El siguiente paso es descargar una imagen de Fedora arm que podemos conseguir en su [http://fedoraproject.org/ Pagina Oficial].
Para este tutorial usamos estas:
*[http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz Img]
*[http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz Kernel]
Necesitamos la imagen .img y el kernel.tar de Versatile Express<ref name="vexpress">[http://www.arm.com/products/tools/development-boards/versatile-express/index.php] Informacion sobre Versatile Express.</ref>
Luego las descomprimimos con el comando unxz. por Ejemplo:
$unxz Fedora-17-armhfp-vexpress-mmcblk0.img.xz
$unxz Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz
y obtendremos los siguientes archivos:
:Fedora-17-armhfp-vexpress-mmcblk0.img
:Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Extraemos el tar:
$tar -x Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Accedemos a la carpeta boot del paquete del kernel
$cd armhfp-vexpress-mmcblk0/boot
y ejecutamos el script ''boot-vexpress'' o ''boot-vexpress+x'' el cual recibe 3 parametros:
#El kernel. (contenida en la carpeta boot)
#La imagen de Ram inicial. (contenida en la carpeta boot)
#La imagen de Fedora que descargamos.
Por ejemplo:
$sudo boot-vexpress vmlinuz-3.4.2-3.fc17.armv7hl initramfs-3.4.2-3.fc17.armv7hl.img /<path>/<to-image>/Fedora-17-armhfp-vexpress-mmcblk0.img
En este momento deberiamos tener la vm corriendo nuestro fedora arm.

==Redimensionar imagen==
Al correr la vm nos damos cuenta que la imagen que descargamos solo tiene unos 600 MB libres aproximadamente, lo que para nuestro proposito no es suficiente.
Vemos las particiones con fdisk:
$ fdisk Fedora-17-armhfp-vexpress-mmcblk0.img
Welcome to fdisk (util-linux 2.21.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk Fedora-17-armhfp-vexpress-mmcblk0.img: 1888 MB, 1888485376 bytes
255 heads, 63 sectors/track, 229 cylinders, total 3688448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
Fedora-17-armhfp-vexpress-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA)
Fedora-17-armhfp-vexpress-mmcblk0.img2 1044225 3688447 1322111+ 83 Linux

Para eso tenemos varias opciones. Para este tutorial vamos a redimencionar la particion principal<ref name="resize-fs">[http://askubuntu.com/questions/107228/how-to-resize-virtual-machine-disk] How to resize virtual machine disk.</ref>.
La imagen ''Fedora-17-armhfp-vexpress-mmcblk0.img'' descomprimida ocupa aproximadamente 1.8G
Para redimencionar la imagen podemos usar el comando '''qemu-img resize <filename> [+ | -]<size>'''. (La VM no debe estar activa!)
Pero primero crearemos un backup de esta imagen, un simple cp basta.
$ cp Fedora-17-armhfp-vexpress-mmcblk0.img backup.img
Luego redimencionamos la imagen, por ejemplo si queremos agregarle 5GB escribimos ''+5G''.
$ qemu-img resize Fedora-17-armhfp-vexpress-mmcblk0.img +5G
Image resized.
Ya tenemos mas espacio, y la vm puede verlo, pero todavia tenemos las viejas particiones.
Con '''fdisk''' vamos a hacer lo siguiente:
*Escribimos ''p'' para mostrar la tabla de particiones.
$ fdisk Fedora-17-armhfp-vexpress-mmcblk0.img
Welcome to fdisk (util-linux 2.21.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk Fedora-17-armhfp-vexpress-mmcblk0.img: 7257 MB, 7257194496 bytes
255 heads, 63 sectors/track, 882 cylinders, total 14174208 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
Fedora-17-armhfp-vexpress-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA)
Fedora-17-armhfp-vexpress-mmcblk0.img2 1044225 3688447 1322111+ 83 Linux
Vemos como la segunda particion empieza en el sector 1044225. Lo que vamos a hacer es borrar esa particion de la tabla de particiones y creamos una nueva que empieza en el mismo sector pero termina en otro mucho despues. Luego la particion va contener un sistema de archivos valido.
*Escribimos ''d'' (delete) y elegimos la 2da particion
Command (m for help): d
Partition number (1-4): 2
Partition 2 is deleted
*Escribimos ''n'' (new) y elegimos particion primaria, la particion 2, el sector de inicio y fin. (en este caso podemos dejar los valores por defecto)
Command (m for help): n
Partition type:
p primary (1 primary, 0 extended, 3 free)
e extended
Select (default p): p
Partition number (1-4, default 2):
Using default value 2
First sector (1044225-14174207, default 1044225):
Using default value 1044225
Last sector, +sectors or +size{K,M,G} (1044225-14174207, default 14174207):
Using default value 14174207
Partition 2 of type Linux and of size 6.3 GiB is set
*Escribimos ''w'' para guardar los cambios al disco y salir de fdisk.
Command (m for help): w
The partition table has been altered!

Syncing disks.
Ahora debemos redimencionar el filesystem.
{En construccion}

==Configurar red y ssh==
{En construccion}
==Referencias==
<references />

JukyParaguay/trabajos2013/xoos/qemu tutorial

2013-04-25T18:24:13Z

Julio Daniel Reyes: /* Redimensionar imagen */

=Instalacion y configuracion de Qemu=
Esta seccion es una compilacion de Tutoriales para la instalacion de fedora con arquitectura arm en qemu.
==Primeros pasos.==
Lo primero<ref name="Qemu-install">[https://fedoraproject.org/wiki/Architectures/ARM/Versatile_Express#Versatile_Express], Tutorial ARM/Versatile Express</ref> que necesitamos es instalar Qemu. Lo podemos hacer con el gestor de paquetes.
Para fedora:
#yum install qemu
Para otras distribuciones otra alternativa es bajar la [http://wiki.qemu.org/Download ultima version] de Qemu y compilarla.
Una vez termine nos aseguramos que lo tenemos instalado
$qemu-system-arm --version
QEMU emulator version 1.4.1, Copyright (c) 2003-2008 Fabrice Bellard

El siguiente paso es descargar una imagen de Fedora arm que podemos conseguir en su [http://fedoraproject.org/ Pagina Oficial].
Para este tutorial usamos estas:
*[http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz Img]
*[http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz Kernel]
Necesitamos la imagen .img y el kernel.tar de Versatile Express<ref name="vexpress">[http://www.arm.com/products/tools/development-boards/versatile-express/index.php] Informacion sobre Versatile Express.</ref>
Luego las descomprimimos con el comando unxz. por Ejemplo:
$unxz Fedora-17-armhfp-vexpress-mmcblk0.img.xz
$unxz Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz
y obtendremos los siguientes archivos:
:Fedora-17-armhfp-vexpress-mmcblk0.img
:Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Extraemos el tar:
$tar -x Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Accedemos a la carpeta boot del paquete del kernel
$cd armhfp-vexpress-mmcblk0/boot
y ejecutamos el script ''boot-vexpress'' o ''boot-vexpress+x'' el cual recibe 3 parametros:
#El kernel. (contenida en la carpeta boot)
#La imagen de Ram inicial. (contenida en la carpeta boot)
#La imagen de Fedora que descargamos.
Por ejemplo:
$sudo boot-vexpress vmlinuz-3.4.2-3.fc17.armv7hl initramfs-3.4.2-3.fc17.armv7hl.img /<path>/<to-image>/Fedora-17-armhfp-vexpress-mmcblk0.img
En este momento deberiamos tener la vm corriendo nuestro fedora arm.

==Redimensionar imagen==
Al correr la vm nos damos cuenta que la imagen que descargamos solo tiene unos 600 MB libres aproximadamente, lo que para nuestro proposito no es suficiente.
Vemos las particiones con fdisk:
$ fdisk Fedora-17-armhfp-vexpress-mmcblk0.img
Welcome to fdisk (util-linux 2.21.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk Fedora-17-armhfp-vexpress-mmcblk0.img: 1888 MB, 1888485376 bytes
255 heads, 63 sectors/track, 229 cylinders, total 3688448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
Fedora-17-armhfp-vexpress-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA)
Fedora-17-armhfp-vexpress-mmcblk0.img2 1044225 3688447 1322111+ 83 Linux

Para eso tenemos varias opciones. Para este tutorial vamos a redimencionar la particion principal<ref name="resize-fs">[http://askubuntu.com/questions/107228/how-to-resize-virtual-machine-disk] How to resize virtual machine disk.</ref>.
La imagen ''Fedora-17-armhfp-vexpress-mmcblk0.img'' descomprimida ocupa aproximadamente 1.8G
Para redimencionar la imagen podemos usar el comando '''qemu-img resize <filename> [+ | -]<size>'''. (La VM no debe estar activa!)
Pero primero crearemos un backup de esta imagen, un simple cp basta.
$ cp Fedora-17-armhfp-vexpress-mmcblk0.img backup.img
Luego redimencionamos la imagen, por ejemplo le agregamos 20G
$ qemu-img resize Fedora-17-armhfp-vexpress-mmcblk0.img +20G
Image resized.
Ya tenemos mas espacio, y la vm puede verlo, pero todavia tenemos las viejas particiones.
Con '''fdisk''' vamos a hacer lo siguiente:
*Escribimos ''p'' para mostrar la tabla de particiones.
$ fdisk Fedora-17-armhfp-vexpress-mmcblk0.img
Welcome to fdisk (util-linux 2.21.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk Fedora-17-armhfp-vexpress-mmcblk0.img: 7257 MB, 7257194496 bytes
255 heads, 63 sectors/track, 882 cylinders, total 14174208 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
Fedora-17-armhfp-vexpress-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA)
Fedora-17-armhfp-vexpress-mmcblk0.img2 1044225 3688447 1322111+ 83 Linux
Vemos como la segunda particion empieza en el sector 1044225. Lo que vamos a hacer es borrar esa particion de la tabla de particiones y creamos una nueva que empieza en el mismo sector pero termina en otro mucho despues. Luego la particion va contener un sistema de archivos valido.
*Escribimos ''d'' (delete) y elegimos la 2da particion
Command (m for help): d
Partition number (1-4): 2
Partition 2 is deleted
*Escribimos ''n'' (new) y elegimos particion primaria, la particion 2, el sector de inicio y fin. (en este caso podemos dejar los valores por defecto)
Command (m for help): n
Partition type:
p primary (1 primary, 0 extended, 3 free)
e extended
Select (default p): p
Partition number (1-4, default 2):
Using default value 2
First sector (1044225-14174207, default 1044225):
Using default value 1044225
Last sector, +sectors or +size{K,M,G} (1044225-14174207, default 14174207):
Using default value 14174207
Partition 2 of type Linux and of size 6.3 GiB is set
*Escribimos ''w'' para guardar los cambios al disco y salir de fdisk.
Command (m for help): w
The partition table has been altered!

Syncing disks.
Ahora debemos redimencionar el filesystem.
{En construccion}

==Configurar red y ssh==
{En construccion}
==Referencias==
<references />

JukyParaguay/trabajos2013/xoos/qemu tutorial

2013-04-25T14:35:12Z

Julio Daniel Reyes:

JukyParaguay/trabajos2013/xoos

2013-04-25T14:18:41Z

Julio Daniel Reyes: /* Week 3. QEMU XO-1.75 arm architecture 15/04/13 - 19/04/13 */

= Journal =

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

====Links de interes:====
*[http://wiki.sugarlabs.org/index.php?title=JukyParaguay Informacion sobre el proyecto]
*[http://wiki.sugarlabs.org/go/CursoSugar2013 Curso base de Sugar]
*[http://wiki.laptop.org/ Wiki de OLPC, official releases]
*[https://sugardextrose.org/projects/dextrose/wiki/Wiki Wiki de Dextrose]
*[http://198.27.75.136/DX4/UY/latest/ Descargas Dextrose]
*[http://wiki.laptop.org/go/Firmware Informacion de firmware]
*[http://wiki.laptop.org/go/Releases Instalacion official]
*[https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation Instalacion dextrose develop]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

====Links de interes:====

*[http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686 Fedora 17]
*[http://wiki.laptop.org/go/OS_Builder Wiki OSBuilder]
*[https://git.sugarlabs.org/dx-activities-server dx-activities-server]

== ''Week 3-4. QEMU XO-1.75 arm architecture'' 15/04/13 - 25/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

'''[http://wiki.sugarlabs.org/go/JukyParaguay/trabajos2013/xoos/qemu_tutorial Tutorial QEMU]'''

JukyParaguay/trabajos2013/xoos/qemu tutorial

2013-04-25T14:16:15Z

Julio Daniel Reyes:

=Instalacion y configuracion de Qemu=
Esta seccion es una compilacion de Tutoriales para la instalacion de fedora con arquitectura arm en qemu.
==Primeros pasos.<ref name="Qemu-install">[https://fedoraproject.org/wiki/Architectures/ARM/Versatile_Express#Versatile_Express], Tutorial ARM/Versatile Express</ref>==
Lo primero que necesitamos es instalar Qemu. Lo podemos hacer con el gestor de paquetes.
Para fedora:
#yum install qemu
O bien:
#yum install qemu-system-arm
Para otras distribuciones otra alternativa es bajar la [http://wiki.qemu.org/Download ultima version] de Qemu y compilarla.
Una vez termine nos aseguramos que lo tenemos instalado
$qemu-system-arm --version

El siguiente paso es descargar una imagen de Fedora arm que podemos conseguir en su [http://fedoraproject.org/ Pagina Oficial].
Al momento de hacer el tutorial estaban alojadas [http://mirrors.kernel.org/fedora-secondary/releases/17/Images/armhfp/ aqui].
Necesitamos la imagen .img y el kernel.tar de Versatile Express<ref name="vexpress">[http://www.arm.com/products/tools/development-boards/versatile-express/index.php] Informacion sobre Versatile Express.</ref>
Luego las descomprimimos con el comando unxz. por Ejemplo:
$unxz Fedora-17-armhfp-vexpress-mmcblk0.img.xz
$unxz Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz
y obtendremos los siguientes archivos:
:Fedora-17-armhfp-vexpress-mmcblk0.img
:Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Extraemos el tar:
$tar -x Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar
Accedemos a la carpeta boot del paquete del kernel
$cd armhfp-vexpress-mmcblk0/boot
y ejecutamos el script ''boot-vexpress'' o ''boot-vexpress+x'' el cual recibe 3 parametros:
#El kernel. (contenida en la carpeta boot)
#La imagen de Ram inicial. (contenida en la carpeta boot)
#La imagen de Fedora que descargamos.
Por ejemplo:
$sudo boot-vexpress vmlinuz-3.4.2-3.fc17.armv7hl initramfs-3.4.2-3.fc17.armv7hl.img /<path>/<to-image>/Fedora-17-armhfp-vexpress-mmcblk0.img
En este momento deberiamos tener la vm corriendo nuestro fedora arm.

==Redimensionar imagen==
{En construccion}
==Configurar red y ssh==
{En construccion}
==Referencias==
<references />

JukyParaguay/trabajos2013/xoos/qemu tutorial

2013-04-18T15:48:14Z

Julio Daniel Reyes:

=Instalacion y configuracion de QEMU=
{En construccion}

JukyParaguay/trabajos2013/xoos/qemu tutorial

2013-04-18T15:43:49Z

Julio Daniel Reyes: Created page with "=Instalacion y configuracion de QEMU="

=Instalacion y configuracion de QEMU=

JukyParaguay/trabajos2013/xoos

2013-04-18T15:42:41Z

Julio Daniel Reyes:

= Journal =

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

====Links de interes:====
*[http://wiki.sugarlabs.org/index.php?title=JukyParaguay Informacion sobre el proyecto]
*[http://wiki.sugarlabs.org/go/CursoSugar2013 Curso base de Sugar]
*[http://wiki.laptop.org/ Wiki de OLPC, official releases]
*[https://sugardextrose.org/projects/dextrose/wiki/Wiki Wiki de Dextrose]
*[http://198.27.75.136/DX4/UY/latest/ Descargas Dextrose]
*[http://wiki.laptop.org/go/Firmware Informacion de firmware]
*[http://wiki.laptop.org/go/Releases Instalacion official]
*[https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation Instalacion dextrose develop]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

====Links de interes:====

*[http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686 Fedora 17]
*[http://wiki.laptop.org/go/OS_Builder Wiki OSBuilder]
*[https://git.sugarlabs.org/dx-activities-server dx-activities-server]

== ''Week 3. QEMU XO-1.75 arm architecture'' 15/04/13 - 19/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

'''[http://wiki.sugarlabs.org/go/JukyParaguay/trabajos2013/xoos/qemu_tutorial Tutorial QEMU]'''

JukyParaguay/trabajos2013/xoos

2013-04-18T15:33:37Z

Julio Daniel Reyes: /* Journal */

= Journal =

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

====Links de interes:====
[http://wiki.sugarlabs.org/index.php?title=JukyParaguay Informacion sobre el proyecto]

[http://wiki.sugarlabs.org/go/CursoSugar2013 Curso base de Sugar]

[http://wiki.laptop.org/ Wiki de OLPC, official releases]

[https://sugardextrose.org/projects/dextrose/wiki/Wiki Wiki de Dextrose]

[http://198.27.75.136/DX4/UY/latest/ Descargas Dextrose]

[http://wiki.laptop.org/go/Firmware Informacion de firmware]

[http://wiki.laptop.org/go/Releases Instalacion official]

[https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation Instalacion dextrose develop]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

====Links de interes:====

[http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686 Fedora 17]

[http://wiki.laptop.org/go/OS_Builder Wiki OSBuilder]

[https://git.sugarlabs.org/dx-activities-server dx-activities-server]

== ''Week 3. QEMU XO-1.75 arm architecture'' 15/04/13 - 19/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

JukyParaguay/trabajos2013/xoos

2013-04-18T15:33:10Z

Julio Daniel Reyes: /* Week 1. Investigacion 01/04/13 - 05/04/13 */

== Journal ==

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

====Links de interes:====
[http://wiki.sugarlabs.org/index.php?title=JukyParaguay Informacion sobre el proyecto]

[http://wiki.sugarlabs.org/go/CursoSugar2013 Curso base de Sugar]

[http://wiki.laptop.org/ Wiki de OLPC, official releases]

[https://sugardextrose.org/projects/dextrose/wiki/Wiki Wiki de Dextrose]

[http://198.27.75.136/DX4/UY/latest/ Descargas Dextrose]

[http://wiki.laptop.org/go/Firmware Informacion de firmware]

[http://wiki.laptop.org/go/Releases Instalacion official]

[https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation Instalacion dextrose develop]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

====Links de interes:====

[http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686 Fedora 17]

[http://wiki.laptop.org/go/OS_Builder Wiki OSBuilder]

[https://git.sugarlabs.org/dx-activities-server dx-activities-server]

== ''Week 3. QEMU XO-1.75 arm architecture'' 15/04/13 - 19/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

JukyParaguay/trabajos2013/xoos

2013-04-18T15:32:24Z

Julio Daniel Reyes: /* Week 2. OSbuilder 08/04/13 - 12/04/13 */

== Journal ==

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

'''Links de interes:'''
----
[http://wiki.sugarlabs.org/index.php?title=JukyParaguay Informacion sobre el proyecto]

[http://wiki.sugarlabs.org/go/CursoSugar2013 Curso base de Sugar]

[http://wiki.laptop.org/ Wiki de OLPC, official releases]

[https://sugardextrose.org/projects/dextrose/wiki/Wiki Wiki de Dextrose]

[http://198.27.75.136/DX4/UY/latest/ Descargas Dextrose]

[http://wiki.laptop.org/go/Firmware Informacion de firmware]

[http://wiki.laptop.org/go/Releases Instalacion official]

[https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation Instalacion dextrose develop]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

====Links de interes:====

[http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686 Fedora 17]

[http://wiki.laptop.org/go/OS_Builder Wiki OSBuilder]

[https://git.sugarlabs.org/dx-activities-server dx-activities-server]

== ''Week 3. QEMU XO-1.75 arm architecture'' 15/04/13 - 19/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

JukyParaguay/trabajos2013/xoos

2013-04-18T15:28:44Z

Julio Daniel Reyes: /* Week 1. Investigacion 01/04/13 - 05/04/13 */

== Journal ==

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

'''Links de interes:'''
----
[http://wiki.sugarlabs.org/index.php?title=JukyParaguay Informacion sobre el proyecto]

[http://wiki.sugarlabs.org/go/CursoSugar2013 Curso base de Sugar]

[http://wiki.laptop.org/ Wiki de OLPC, official releases]

[https://sugardextrose.org/projects/dextrose/wiki/Wiki Wiki de Dextrose]

[http://198.27.75.136/DX4/UY/latest/ Descargas Dextrose]

[http://wiki.laptop.org/go/Firmware Informacion de firmware]

[http://wiki.laptop.org/go/Releases Instalacion official]

[https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation Instalacion dextrose develop]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

'''Links de interes:'''
----

Fedora 17: [http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686]

Wiki OSBuilder: [http://wiki.laptop.org/go/OS_Builder]

dx-activities-server: [https://git.sugarlabs.org/dx-activities-server]

== ''Week 3. QEMU XO-1.75 arm architecture'' 15/04/13 - 19/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

JukyParaguay/trabajos2013/xoos

2013-04-17T12:15:44Z

Julio Daniel Reyes: /* Week 3. QEMU XO-1.75 arm arquitecture 15/04/13 - 19/04/13 */

== Journal ==

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

'''Links de interes:'''
----

Informacion sobre el proyecto: [[http://wiki.sugarlabs.org/index.php?title=JukyParaguay]]

Curso base de Sugar: [[http://wiki.sugarlabs.org/go/CursoSugar2013]]

Wiki de OLPC, official releases: [http://wiki.laptop.org/]

Wiki de Dextrose: [https://sugardextrose.org/projects/dextrose/wiki/Wiki]

Descargas Dextrose: [http://198.27.75.136/DX4/UY/latest/]

Informacion de firmware: [http://wiki.laptop.org/go/Firmware]

Instalacion official: [http://wiki.laptop.org/go/Releases]

Instalacion dextrose develop: [https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

'''Links de interes:'''
----

Fedora 17: [http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686]

Wiki OSBuilder: [http://wiki.laptop.org/go/OS_Builder]

dx-activities-server: [https://git.sugarlabs.org/dx-activities-server]

== ''Week 3. QEMU XO-1.75 arm architecture'' 15/04/13 - 19/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

JukyParaguay/trabajos2013/xoos

2013-04-17T12:14:31Z

Julio Daniel Reyes:

== Journal ==

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' 01/04/13 - 05/04/13 ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

'''Links de interes:'''
----

Informacion sobre el proyecto: [[http://wiki.sugarlabs.org/index.php?title=JukyParaguay]]

Curso base de Sugar: [[http://wiki.sugarlabs.org/go/CursoSugar2013]]

Wiki de OLPC, official releases: [http://wiki.laptop.org/]

Wiki de Dextrose: [https://sugardextrose.org/projects/dextrose/wiki/Wiki]

Descargas Dextrose: [http://198.27.75.136/DX4/UY/latest/]

Informacion de firmware: [http://wiki.laptop.org/go/Firmware]

Instalacion official: [http://wiki.laptop.org/go/Releases]

Instalacion dextrose develop: [https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation]

== ''Week 2. OSbuilder'' 08/04/13 - 12/04/13 ==
Resumen de la semana: Instalacion de Fedora 17, OSbuilder y dx-activities-server. Build del SO official para XO-1 y XO-1.5.

'''Links de interes:'''
----

Fedora 17: [http://fedora.c3sl.ufpr.br/linux/releases/17/Live/i686]

Wiki OSBuilder: [http://wiki.laptop.org/go/OS_Builder]

dx-activities-server: [https://git.sugarlabs.org/dx-activities-server]

== ''Week 3. QEMU XO-1.75 arm arquitecture'' 15/04/13 - 19/04/13 ==

Resumen de la semana: Instalacion y configuracion de la VM QEMU arm.

JukyParaguay/trabajos2013/xoos

2013-04-08T12:28:18Z

Julio Daniel Reyes: /* Week 1. Investigacion */

JukyParaguay/trabajos2013/xoos

2013-04-05T15:33:14Z

Julio Daniel Reyes: /* Week 1. Investigacion */

== Journal ==

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' ==
Resumen de la semana: Investigacion sobre el proyecto. Instalacion y comparacion del official release y Dextrose 4 en XO-1, XO-1.5, XO-1.75.

'''Links de interes:'''
----

Informacion sobre el proyecto: [[http://wiki.sugarlabs.org/index.php?title=JukyParaguay]]

Curso base de Sugar: [[http://wiki.sugarlabs.org/go/CursoSugar2013]]

Wiki de OLPC, official releases: [http://wiki.laptop.org/]

Wiki de Dextrose: [https://sugardextrose.org/projects/dextrose/wiki/Wiki]

Descargas Dextrose: [http://198.27.75.136/DX4/UY/latest/]

Informacion de firmware: [http://wiki.laptop.org/go/Firmware]

Instalacion official: [http://wiki.laptop.org/go/Releases]

Instalacion dextrose develop: [https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation]

JukyParaguay/trabajos2013/xoos

2013-04-05T15:06:41Z

Julio Daniel Reyes: Created page with " == Journal == Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe == ''Week 1. Investigacion'' == '''Links ..."

== Journal ==

Esta seccion contiene las actividades realizadas para la construccion y actualizacion del SO de las XO en Caacupe

== ''Week 1. Investigacion'' ==

'''Links de interes:'''
----

Informacion sobre el proyecto: [[http://wiki.sugarlabs.org/index.php?title=JukyParaguay]]

Curso base de Sugar: [[http://wiki.sugarlabs.org/go/CursoSugar2013]]

Wiki de OLPC, official releases: [http://wiki.laptop.org/]

Wiki de Dextrose: [https://sugardextrose.org/projects/dextrose/wiki/Wiki]

Descargas Dextrose: [http://198.27.75.136/DX4/UY/latest/]

Informacion de firmware: [http://wiki.laptop.org/go/Firmware]

Instalacion official: [http://wiki.laptop.org/go/Releases]

Instalacion dextrose develop: [https://sugardextrose.org/projects/dextrose/wiki/Dextrose_installation]