https://wiki.sugarlabs.org/api.php?action=feedcontributions&feedformat=atom&user=MstoneSugar Labs - User contributions [en]2026-05-30T20:58:07ZUser contributionsMediaWiki 1.43.0https://wiki.sugarlabs.org/index.php?title=User:Mstone&diff=60691User:Mstone2011-01-10T00:07:16Z<p>Mstone: </p>
<hr />
<div>See http://wiki.laptop.org/go/Profiles/mstone<br />
<br />
'''Notes:'''<br />
<br />
[[User:Mstone/Notes/D-Bus|D-Bus]]<br />
<br />
'''Queries:'''<br />
<br />
[http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&group=priority&order=changetime&desc=1&max=1000&col=id&col=summary&col=owner&col=changetime&col=component&component=sugar sugar]<br />
<br />
[http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&group=priority&order=changetime&desc=1&max=1000&col=id&col=summary&col=owner&col=changetime&col=component&component=sugar-toolkit sugar-toolkit]<br />
<br />
[http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&group=priority&order=changetime&desc=1&max=1000&col=id&col=summary&col=owner&col=changetime&col=component&component=journal journal]</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=User:Mstone&diff=60528User:Mstone2011-01-02T00:12:05Z<p>Mstone: </p>
<hr />
<div>See http://wiki.laptop.org/go/Profiles/mstone<br />
<br />
<br />
Notes:<br />
<br />
[[User:Mstone/Notes/D-Bus|D-Bus]]</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=User:Mstone/Notes/D-Bus&diff=60527User:Mstone/Notes/D-Bus2011-01-02T00:04:17Z<p>Mstone: Created page with "=== DataStore === m:create(profs, file_path, transfer_ownership) s:Created(uid) (null) m:update(uid, props, file_path, transfer_ownership) s:Updated(uid) m:find(query,..."</p>
<hr />
<div>=== DataStore ===<br />
<br />
m:create(profs, file_path, transfer_ownership)<br />
s:Created(uid) (null)<br />
m:update(uid, props, file_path, transfer_ownership)<br />
s:Updated(uid)<br />
m:find(query, properties) -> entries, count<br />
m:get_filename(uid, sender) -> path<br />
m:get_properties(uid) -> dict<br />
m:get_uniquevaluesfor(propertyname, query) -> [string]<br />
m:delete(uid)<br />
s:Deleted(uid) (null)<br />
s:Stopped() (null)<br />
m:mount(uri, options) -> ''<br />
m:mounts() -> [{'id':1}]<br />
m:unmount(mountpoint_id) -> (null)<br />
s:Mounted(descriptor) (null)<br />
s:Unmounted(descriptor) (null)<br />
<br />
other users:<br />
copy-to-journal<br />
copy-from-journal<br />
<br />
=== Presence ===<br />
<br />
oy. (invites)<br />
<br />
=== Journal (object-chooser) ===<br />
<br />
m:ShowObject(object_id)<br />
m:ChooseObject(parent_xid, what_filter) -> chooser_id<br />
s:ObjectChooserResponse(chooser_id, object_id)<br />
s:ObjectChooserCancelled(chooser_id)<br />
<br />
=== ActivityService (view source) ===<br />
<br />
m:SetActive(active)<br />
m:InviteContact(account_path, contact_id)<br />
m:HandleViewSource()<br />
m:GetDocumentPath()<br />
<br />
=== Speech ===<br />
<br />
m:SayText(text)<br />
<br />
=== Shell (UIService) ===<br />
<br />
m:GetBundlePath(bundle_id) -> path<br />
m:ActivateActivity(activity_id) -> (real-activity-not-launcher : bool)<br />
m:NotifyLaunch(bundle_id, activity_id)<br />
m:NotifyLaunchFailure(activity_id)<br />
<br />
=== Misc ===<br />
<br />
nm key dialog ...<br />
network view<br />
cp-power<br />
cp-network</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Mentors&diff=50103Summer of Code/Mentors2010-03-20T16:22:54Z<p>Mstone: /* Michael */</p>
<hr />
<div>{{TOCright}}<br />
==Mentors==<br />
Our most important need right now is for quality mentors. If you (or someone you know) would make a good mentor, please nominate yourself (or them), both here on the ML (iaep AT sl.o) and on the wiki (if you can't handle a little redundant paperwork, you're probably not a good candidate :). Include relevant information such as:<br />
<br />
*Name/contact<br />
*Timezone<br />
*What kind of projects could/would you mentor?<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
*What relevant mentoring (or related) experience do you have?<br />
*Anything else you think is relevant.<br />
<br />
Please also add this page to your watchlist. We will probably later do some kind of "community interview" process where we ask you questions on this page.<br />
<br />
=== Jameson ===<br />
<br />
*Name/contact<br />
<br />
Jameson.Quinn at gmail<br />
<br />
*Timezone<br />
<br />
US Central / Central America (UTC-6)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements, especially interested in language or developer tools.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week. If we are short on mentors and I find project(s) that are an especially good match, I could do 8 hrs (double duty). Over the summer, I hope to be helping to work on an XO deployment, hopefully on a paid basis, but am currently unemployed.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Develop activity, have done some tinkering with Sugar, I've been involved for over a year.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I have several years' experience as a full-time teacher.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== [[User:Nrp|Nrp]] ===<br />
<br />
* Name/contact<br />
<br />
Nirav Patel nrpatel at gmail<br />
<br />
* Timezone<br />
<br />
UTC-5<br />
<br />
* What kind of projects could/would you mentor?<br />
<br />
Pygame or PyGTK based Activities<br />
<br />
* How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Graduating and no job prospects, so it is likely I will have quite a<br />
bit of free time as of early May. 5 hours a week is certainly doable.<br />
<br />
* What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Some Pygame/PyGTK Activity development and a module for Pygame.<br />
<br />
* What relevant mentoring (or related) experience do you have?<br />
<br />
Teaching Assistant and miscellaneous mentoring experiences at school.<br />
<br />
* Anything else you think is relevant.<br />
<br />
I survived GSoC on the student end of things in 2008.<br />
<br />
=== Tomeu ===<br />
<br />
*Name/contact<br />
<br />
[[User:Tomeu | Tomeu Vizoso]]<br />
<br />
*Timezone<br />
<br />
Central European Time<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Coded activities and for the sugar shell for more than two years now.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Last year mentored one intern at OLPC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== [[User:Bobbyp|Bobby]] ===<br />
<br />
*Name/contact<br />
<br />
firstnamelastname at gmail, nteon on IRC<br />
<br />
*Timezone<br />
<br />
US Eastern Standard Time (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, lower level stuff.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Probably 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Model activity, have done some tinkering with Sugar/Rainbow, rewrote boot-animation. Fairly confident with C/Python/Linux, have been involved with OLPC for about a year (although have been mostly lurking on the sugar side of things for a few months).<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Summer camp counselor for a number of years, OLPC intern summer '08.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I'm a few months behind on Sugar development, but think its a fabulous project. Let me know what you need of me.<br />
<br />
=== [[User:Sebastian|Sebastian]] ===<br />
<br />
*Name/contact<br />
<br />
Sebastian Silva (sebastian at fuentelibre.org), (gmail alternative: sebatustra)<br />
<br />
icarito on IRC<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, especially "social" activities.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am helping a teacher group this (northern summer), that leaves me enough time to commit to this (at least 4-6 hours a week, more if needed). It also is a great chance for some user feedback.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities, led workshops. Confident in python and GNU. Worked professionally in programming for some years.<br />
<br />
=== [[User:Wade|Wade]] ===<br />
<br />
*Name/contact<br />
<br />
Wade Brainerd (wadetb at gmail dot com) <br />
<br />
wadeb on IRC<br />
<br />
*Timezone<br />
<br />
Portland, Maine (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
New activities, Games, Updates to/refreshes of existing activities, Frameworks for creating activities in new languages (Flash, Ajax, Mono)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I will be available for a single mentorship this year. I work full time as a programmer but have a flexible schedule.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities. Experienced in Python, C++, others. 11 years as a professional programmer, including 5 as a technical director and team lead.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was closely involved in the 2007 OLPC GSoC project, reviewing applications and communicating with students. I mentored two students informally during 2007 after their GSoC projects were not funded. Both projects were completed with my help.<br />
<br />
*Anything else you think is relevant.<br />
<br />
As the Sugar Labs Activity Team coordinator, I have plenty of access to deployments. This gives me a good handle on what student projects will most effectively advance Sugar Labs' goals in the community. <br />
<br />
As a volunteer activity developer, I have also developed many new activities myself, and overhauled existing ones.<br />
<br />
=== [[User:Lglira|Lglira]] ===<br />
<br />
*Name/contact<br />
<br />
Luis Gustavo Lira, BSc, MSc lira.lg at pucp.edu.pe<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Networking, Hardware Projects, Python, Activities (science, math, entrepreneurship).<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could mentor 1 o 2 students.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Engineer 10 years working experience, CIO and Executive level since 2006.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Consultant for big telecomms, systems integrators, etc.<br />
Lecturer at University undergraduate and graduate level.<br />
GSoC 2007, 2008 and 2009 Mentor for OpenMoko<br />
GSoC 2008 for OLPC but my student was not funded<br />
<br />
*Anything else you think is relevant.<br />
<br />
Fellow of Lemelson Foundation RAMP-Peru, Social Entrepreneur, Free Culture activist, Appropriate Technology developer, Teaching Science, Math and Entrepeneurship in rural terciary schools.<br />
<br />
=== [[User:benlau|Ben Lau]] ===<br />
<br />
*Name/contact<br />
xbenlau at gmail.com<br />
<br />
*Timezone<br />
UTC+8<br />
<br />
*What kind of projects could/would you mentor?<br />
Video , Computer Vision , Speech Processing , Python, Activities (Educational software , Chinese language learning)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
I could commit up to 4-5 hours a week, able to mentor 1 student.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
10 years Linux development experience , include kernel porting (ARM), Linux driver , GTK+ , opencv , GStreamer , C/C++ , python<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
I have led two teams of university students to join an embedded system contest called Intel Cup (China) in 2006. The teams got a first prize and a second prize award finally.<br />
<br />
*Anything else you think is relevant.<br />
I am leading a team of volunteers on technical side for OLPC APAC division.<br />
<br />
=== [[User:SayaminduDasgupta|Sayamindu]] ===<br />
<br />
*Name/contact<br />
<br />
Sayamindu Dasgupta (sayamindu at gmail)<br />
<br />
unmadindu on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530) (I normally work on European timezones)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Activities, l10n/i18n related projects.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am working a contractor for OLPC for the next few months. However, I think I can commit around 4-5 hours per week for the work.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Wrote the Imageviewer activity, maintainer of Terminal, in the process of implementing largish features to Read. Familiar with GTK+, Python, Gstreamer, etc.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was a mentor during SoC 2008 for the Translate toolkit project (my student worked successfully on enhancing the Pootle featureset). I have also experience informally mentoring/guiding students and volunteers for a number of Free Software projects (mostly i18n/l10n related).<br />
<br />
*Anything else you think is relevant.<br />
<br />
I was a successful student participant in Summer of Code 2007 under Federico Mena-Quintero for the GNOME project. I also helped in the rating of applications for OLPC as a mentoring organisation during 2008's SoC.<br />
<br />
<br />
<br />
=== [[User:Assim|Assim Deodia]] ===<br />
<br />
*Name/contact<br />
<br />
Assim Deodia (assim.deodia at gmail dot com)<br />
<br />
assimd on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
[[Activities/Listen Spell|Listen Spell]], Activities related to speech synthesis<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I can comfortably devote 4-5 hrs a week. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I have developed speech server in SoCon for OLPC [http://wiki.laptop.org/go/Speech_Server| Speech Server], Deducto for OLPC and have also developed Listen Spell for OLPC in GSoC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I have successful completed Summer of Code 2008 under Dafydd Harries for the OLPC. I have also developed a low cost OMR processing application which is hosted on sourceforge [http://sourceforge.net/projects/omr-ai/| OMR AI]<br />
<br />
<br />
<br />
<br />
<br />
=== [[User:Aa|aa]] ===<br />
<br />
*Name/contact<br />
<br />
andresambrois at gmail<br />
<br />
*Timezone<br />
<br />
America/Montevideo (UTC-3)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities and Sugar projects, especially in collaboration and networking. <br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
5-6 hours a week. Currently unemployed, but studying computer engineering. I devote most of my time to free software projects and Ceibal-related volunteering. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I maintain the PlayGo activity, one of the developers of the [http://wiki.laptop.org/go/Educational_Blogger_Project| EduBlog project], written a couple of patches for sugar and currently working on some improvements. Familiar with Python, PHP, Tcl, Shell Scripting and (some) C. <br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I've given technical talks and workshops, and was a math tutor years ago. <br />
<br />
*Anything else you think is relevant.<br />
<br />
I fear velociraptors.<br />
<br />
=== Alfonsodg ===<br />
<br />
*Name/contact<br />
<br />
[[User:Alfonsodg | Alfonso de la Guarda]]<br />
<br />
*Timezone<br />
<br />
GMT -5<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Sugar activities based on python, gtk, glade and some electronical enhancements<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4 to 6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Coded multiple python apps since 2001, including some XO activities<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Lead Technology Consultor for the Peruvian Army with 7 projects based all on FLOSS<br />
<br />
*Anything else you think is relevant.<br />
<br />
Love technology and wanna that some of my activities could be better with the help of many people<br />
<br />
=== Alex Levenson ===<br />
<br />
*Name/contact<br />
**Alex Levenson<br />
**alev742@gwu.edu<br />
<br />
*Timezone<br />
**Eastern Time during the school year, Pacific Time during the summer<br />
<br />
*What kind of projects could/would you mentor?<br />
**Anything physics engine related<br />
**Anything related to games, pygame, olpcgames, graphics, etc<br />
<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
**I'll be working for Google in San Francisco this summer.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
**I wrote a couple of physics simulation activities for OLPC last summer. I am a computer science major and have experience as a software developer. Resume: http://student.seas.gwu.edu/~alev742/resume.php<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
**I am a computer science tutor here at The George Washington University.<br />
<br />
*What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty)<br />
**I would be glad to provide any kind of support I can, from high level software design strategy to code reviews. I would like to focus on keeping the code not only functional but elegant, readable, and scalable - something that's very important as this platform moves forward.<br />
<br />
*Anything else you think is relevant.<br />
**Please check out my resume: http://student.seas.gwu.edu/~alev742/resume.php<br />
**And also my olpc userpage: http://wiki.laptop.org/go/User:Alexlevenson<br />
<br />
=== Guillaume Desmottes ===<br />
<br />
*Name/contact: [[User:Cassidy|Guillaume Desmottes]]<br />
<br />
*Timezone: GMT+1 (UK)<br />
<br />
*What kind of projects could/would you mentor? Telepathy related<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
** If possible I'd prefer co-mentoring so I would focus on the Telepathy part and a Sugar guy on the UI/integration one. I'll work this summer but my [http://www.collabora.co.uk/ employer] would probably let me allocate some time on mentoring if needed. I could maybe have another soc student on the GNOME front too.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
** I hack on Telepathy as my job. Did lot of the Telepathy integration in Sugar.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
** Never mentored soc projects but regularly help people on #telepathy and #sugar.<br />
<br />
*What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty)<br />
** My main goal is to ensure than proposed projects are did the right way. I want to avoid that student did the code on his own without any input from relevant person and so is finally never merged because it was just the wrong approach.<br />
<br />
===[[User:BryanWB|Bryan W Berry]]===<br />
<br />
*Name: [[User:BryanWB|Bryan W Berry]]<br />
*Timezone : GMT+5:45 (Nepal)<br />
*What kind of projects could/would you mentor?<br />
Using Web technologies to create Sugar activities, like [[Karma]]<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
<br />
I can probably only mentor one person. I think I can contribute 10 hours per week for 3 months.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
For the past two years I have led a team of 10 full-time software developers creating open-source educational learning activities. <br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I have mentored 12 Nepali interns at OLE Nepal over the last 12 months.<br />
<br />
What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty) <br />
<br />
There is a lot to creating learning activities that is not technical but procedure. I am particularly interested in making it easier for programmers to create learning activities.<br />
<br />
===[[User:Walter|Walter]]===<br />
*Name/contact<br />
<br />
Walter Bender / (walter AT sl.o)<br />
<br />
*Timezone<br />
<br />
EST (UTC+4)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Activities, and some Sugar UI-related projects (anything relevant to daily life in the classroom.)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
<br />
Not sure what a "double mentor" is, but I could put in 10 hours/week...<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I have been with the Sugar project since the beginning and have been making the occasional Sugar patch; I have written and maintain a half-dozen activities.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was a GSoC coordinator and mentor in 2009. I have supervised hundreds of MIT undergraduate research projects and 50+ graduate-level (MS&PhD) thesis projects.<br />
<br />
*Anything else you think is relevant.<br />
<br />
You learn through doing, so I will roll up my sleeves along side whomever I mentor, because I want to keep learning.<br />
<br />
===[[User:Mstone|Michael]]===<br />
*Name/contact<br />
:: Michael Stone / michael@laptop.org<br />
*Timezone<br />
:: EDT (UTC-4)<br />
*What kind of projects could/would you mentor?<br />
:: One project<br />
*How much time could you devote to mentoring?<br />
:: 5-10 hr/week<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
:: I am the author of [http://wiki.laptop.org/go/Rainbow rainbow]. I also am intimately familiar with Sugar's architecture, design, and code base.<br />
*What relevant mentoring (or related) experience do you have?<br />
:: I analyze, critique, and improve software professionally, often working with less experienced coders. I also managed the release of a small operating system ([http://wiki.laptop.org/go/Release_notes/8.2.0 OLPC's 8.2.0 OS release]) in which I helped to fold the work of many contributors, both new and old, into a successful and coherent software development experience.<br />
*Anything else you think is relevant.<br />
:: My entrée into professional software development, which I love, was an internship not unlike the ones you're applying for here.<br />
<br />
[[Category:GSoC]]</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Mentors&diff=50102Summer of Code/Mentors2010-03-20T16:15:35Z<p>Mstone: /* Michael */</p>
<hr />
<div>{{TOCright}}<br />
==Mentors==<br />
Our most important need right now is for quality mentors. If you (or someone you know) would make a good mentor, please nominate yourself (or them), both here on the ML (iaep AT sl.o) and on the wiki (if you can't handle a little redundant paperwork, you're probably not a good candidate :). Include relevant information such as:<br />
<br />
*Name/contact<br />
*Timezone<br />
*What kind of projects could/would you mentor?<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
*What relevant mentoring (or related) experience do you have?<br />
*Anything else you think is relevant.<br />
<br />
Please also add this page to your watchlist. We will probably later do some kind of "community interview" process where we ask you questions on this page.<br />
<br />
=== Jameson ===<br />
<br />
*Name/contact<br />
<br />
Jameson.Quinn at gmail<br />
<br />
*Timezone<br />
<br />
US Central / Central America (UTC-6)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements, especially interested in language or developer tools.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week. If we are short on mentors and I find project(s) that are an especially good match, I could do 8 hrs (double duty). Over the summer, I hope to be helping to work on an XO deployment, hopefully on a paid basis, but am currently unemployed.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Develop activity, have done some tinkering with Sugar, I've been involved for over a year.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I have several years' experience as a full-time teacher.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== [[User:Nrp|Nrp]] ===<br />
<br />
* Name/contact<br />
<br />
Nirav Patel nrpatel at gmail<br />
<br />
* Timezone<br />
<br />
UTC-5<br />
<br />
* What kind of projects could/would you mentor?<br />
<br />
Pygame or PyGTK based Activities<br />
<br />
* How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Graduating and no job prospects, so it is likely I will have quite a<br />
bit of free time as of early May. 5 hours a week is certainly doable.<br />
<br />
* What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Some Pygame/PyGTK Activity development and a module for Pygame.<br />
<br />
* What relevant mentoring (or related) experience do you have?<br />
<br />
Teaching Assistant and miscellaneous mentoring experiences at school.<br />
<br />
* Anything else you think is relevant.<br />
<br />
I survived GSoC on the student end of things in 2008.<br />
<br />
=== Tomeu ===<br />
<br />
*Name/contact<br />
<br />
[[User:Tomeu | Tomeu Vizoso]]<br />
<br />
*Timezone<br />
<br />
Central European Time<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Coded activities and for the sugar shell for more than two years now.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Last year mentored one intern at OLPC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== [[User:Bobbyp|Bobby]] ===<br />
<br />
*Name/contact<br />
<br />
firstnamelastname at gmail, nteon on IRC<br />
<br />
*Timezone<br />
<br />
US Eastern Standard Time (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, lower level stuff.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Probably 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Model activity, have done some tinkering with Sugar/Rainbow, rewrote boot-animation. Fairly confident with C/Python/Linux, have been involved with OLPC for about a year (although have been mostly lurking on the sugar side of things for a few months).<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Summer camp counselor for a number of years, OLPC intern summer '08.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I'm a few months behind on Sugar development, but think its a fabulous project. Let me know what you need of me.<br />
<br />
=== [[User:Sebastian|Sebastian]] ===<br />
<br />
*Name/contact<br />
<br />
Sebastian Silva (sebastian at fuentelibre.org), (gmail alternative: sebatustra)<br />
<br />
icarito on IRC<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, especially "social" activities.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am helping a teacher group this (northern summer), that leaves me enough time to commit to this (at least 4-6 hours a week, more if needed). It also is a great chance for some user feedback.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities, led workshops. Confident in python and GNU. Worked professionally in programming for some years.<br />
<br />
=== [[User:Wade|Wade]] ===<br />
<br />
*Name/contact<br />
<br />
Wade Brainerd (wadetb at gmail dot com) <br />
<br />
wadeb on IRC<br />
<br />
*Timezone<br />
<br />
Portland, Maine (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
New activities, Games, Updates to/refreshes of existing activities, Frameworks for creating activities in new languages (Flash, Ajax, Mono)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I will be available for a single mentorship this year. I work full time as a programmer but have a flexible schedule.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities. Experienced in Python, C++, others. 11 years as a professional programmer, including 5 as a technical director and team lead.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was closely involved in the 2007 OLPC GSoC project, reviewing applications and communicating with students. I mentored two students informally during 2007 after their GSoC projects were not funded. Both projects were completed with my help.<br />
<br />
*Anything else you think is relevant.<br />
<br />
As the Sugar Labs Activity Team coordinator, I have plenty of access to deployments. This gives me a good handle on what student projects will most effectively advance Sugar Labs' goals in the community. <br />
<br />
As a volunteer activity developer, I have also developed many new activities myself, and overhauled existing ones.<br />
<br />
=== [[User:Lglira|Lglira]] ===<br />
<br />
*Name/contact<br />
<br />
Luis Gustavo Lira, BSc, MSc lira.lg at pucp.edu.pe<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Networking, Hardware Projects, Python, Activities (science, math, entrepreneurship).<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could mentor 1 o 2 students.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Engineer 10 years working experience, CIO and Executive level since 2006.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Consultant for big telecomms, systems integrators, etc.<br />
Lecturer at University undergraduate and graduate level.<br />
GSoC 2007, 2008 and 2009 Mentor for OpenMoko<br />
GSoC 2008 for OLPC but my student was not funded<br />
<br />
*Anything else you think is relevant.<br />
<br />
Fellow of Lemelson Foundation RAMP-Peru, Social Entrepreneur, Free Culture activist, Appropriate Technology developer, Teaching Science, Math and Entrepeneurship in rural terciary schools.<br />
<br />
=== [[User:benlau|Ben Lau]] ===<br />
<br />
*Name/contact<br />
xbenlau at gmail.com<br />
<br />
*Timezone<br />
UTC+8<br />
<br />
*What kind of projects could/would you mentor?<br />
Video , Computer Vision , Speech Processing , Python, Activities (Educational software , Chinese language learning)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
I could commit up to 4-5 hours a week, able to mentor 1 student.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
10 years Linux development experience , include kernel porting (ARM), Linux driver , GTK+ , opencv , GStreamer , C/C++ , python<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
I have led two teams of university students to join an embedded system contest called Intel Cup (China) in 2006. The teams got a first prize and a second prize award finally.<br />
<br />
*Anything else you think is relevant.<br />
I am leading a team of volunteers on technical side for OLPC APAC division.<br />
<br />
=== [[User:SayaminduDasgupta|Sayamindu]] ===<br />
<br />
*Name/contact<br />
<br />
Sayamindu Dasgupta (sayamindu at gmail)<br />
<br />
unmadindu on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530) (I normally work on European timezones)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Activities, l10n/i18n related projects.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am working a contractor for OLPC for the next few months. However, I think I can commit around 4-5 hours per week for the work.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Wrote the Imageviewer activity, maintainer of Terminal, in the process of implementing largish features to Read. Familiar with GTK+, Python, Gstreamer, etc.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was a mentor during SoC 2008 for the Translate toolkit project (my student worked successfully on enhancing the Pootle featureset). I have also experience informally mentoring/guiding students and volunteers for a number of Free Software projects (mostly i18n/l10n related).<br />
<br />
*Anything else you think is relevant.<br />
<br />
I was a successful student participant in Summer of Code 2007 under Federico Mena-Quintero for the GNOME project. I also helped in the rating of applications for OLPC as a mentoring organisation during 2008's SoC.<br />
<br />
<br />
<br />
=== [[User:Assim|Assim Deodia]] ===<br />
<br />
*Name/contact<br />
<br />
Assim Deodia (assim.deodia at gmail dot com)<br />
<br />
assimd on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
[[Activities/Listen Spell|Listen Spell]], Activities related to speech synthesis<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I can comfortably devote 4-5 hrs a week. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I have developed speech server in SoCon for OLPC [http://wiki.laptop.org/go/Speech_Server| Speech Server], Deducto for OLPC and have also developed Listen Spell for OLPC in GSoC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I have successful completed Summer of Code 2008 under Dafydd Harries for the OLPC. I have also developed a low cost OMR processing application which is hosted on sourceforge [http://sourceforge.net/projects/omr-ai/| OMR AI]<br />
<br />
<br />
<br />
<br />
<br />
=== [[User:Aa|aa]] ===<br />
<br />
*Name/contact<br />
<br />
andresambrois at gmail<br />
<br />
*Timezone<br />
<br />
America/Montevideo (UTC-3)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities and Sugar projects, especially in collaboration and networking. <br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
5-6 hours a week. Currently unemployed, but studying computer engineering. I devote most of my time to free software projects and Ceibal-related volunteering. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I maintain the PlayGo activity, one of the developers of the [http://wiki.laptop.org/go/Educational_Blogger_Project| EduBlog project], written a couple of patches for sugar and currently working on some improvements. Familiar with Python, PHP, Tcl, Shell Scripting and (some) C. <br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I've given technical talks and workshops, and was a math tutor years ago. <br />
<br />
*Anything else you think is relevant.<br />
<br />
I fear velociraptors.<br />
<br />
=== Alfonsodg ===<br />
<br />
*Name/contact<br />
<br />
[[User:Alfonsodg | Alfonso de la Guarda]]<br />
<br />
*Timezone<br />
<br />
GMT -5<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Sugar activities based on python, gtk, glade and some electronical enhancements<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4 to 6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Coded multiple python apps since 2001, including some XO activities<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Lead Technology Consultor for the Peruvian Army with 7 projects based all on FLOSS<br />
<br />
*Anything else you think is relevant.<br />
<br />
Love technology and wanna that some of my activities could be better with the help of many people<br />
<br />
=== Alex Levenson ===<br />
<br />
*Name/contact<br />
**Alex Levenson<br />
**alev742@gwu.edu<br />
<br />
*Timezone<br />
**Eastern Time during the school year, Pacific Time during the summer<br />
<br />
*What kind of projects could/would you mentor?<br />
**Anything physics engine related<br />
**Anything related to games, pygame, olpcgames, graphics, etc<br />
<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
**I'll be working for Google in San Francisco this summer.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
**I wrote a couple of physics simulation activities for OLPC last summer. I am a computer science major and have experience as a software developer. Resume: http://student.seas.gwu.edu/~alev742/resume.php<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
**I am a computer science tutor here at The George Washington University.<br />
<br />
*What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty)<br />
**I would be glad to provide any kind of support I can, from high level software design strategy to code reviews. I would like to focus on keeping the code not only functional but elegant, readable, and scalable - something that's very important as this platform moves forward.<br />
<br />
*Anything else you think is relevant.<br />
**Please check out my resume: http://student.seas.gwu.edu/~alev742/resume.php<br />
**And also my olpc userpage: http://wiki.laptop.org/go/User:Alexlevenson<br />
<br />
=== Guillaume Desmottes ===<br />
<br />
*Name/contact: [[User:Cassidy|Guillaume Desmottes]]<br />
<br />
*Timezone: GMT+1 (UK)<br />
<br />
*What kind of projects could/would you mentor? Telepathy related<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
** If possible I'd prefer co-mentoring so I would focus on the Telepathy part and a Sugar guy on the UI/integration one. I'll work this summer but my [http://www.collabora.co.uk/ employer] would probably let me allocate some time on mentoring if needed. I could maybe have another soc student on the GNOME front too.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
** I hack on Telepathy as my job. Did lot of the Telepathy integration in Sugar.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
** Never mentored soc projects but regularly help people on #telepathy and #sugar.<br />
<br />
*What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty)<br />
** My main goal is to ensure than proposed projects are did the right way. I want to avoid that student did the code on his own without any input from relevant person and so is finally never merged because it was just the wrong approach.<br />
<br />
===[[User:BryanWB|Bryan W Berry]]===<br />
<br />
*Name: [[User:BryanWB|Bryan W Berry]]<br />
*Timezone : GMT+5:45 (Nepal)<br />
*What kind of projects could/would you mentor?<br />
Using Web technologies to create Sugar activities, like [[Karma]]<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
<br />
I can probably only mentor one person. I think I can contribute 10 hours per week for 3 months.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
For the past two years I have led a team of 10 full-time software developers creating open-source educational learning activities. <br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I have mentored 12 Nepali interns at OLE Nepal over the last 12 months.<br />
<br />
What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty) <br />
<br />
There is a lot to creating learning activities that is not technical but procedure. I am particularly interested in making it easier for programmers to create learning activities.<br />
<br />
===[[User:Walter|Walter]]===<br />
*Name/contact<br />
<br />
Walter Bender / (walter AT sl.o)<br />
<br />
*Timezone<br />
<br />
EST (UTC+4)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Activities, and some Sugar UI-related projects (anything relevant to daily life in the classroom.)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
<br />
Not sure what a "double mentor" is, but I could put in 10 hours/week...<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I have been with the Sugar project since the beginning and have been making the occasional Sugar patch; I have written and maintain a half-dozen activities.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was a GSoC coordinator and mentor in 2009. I have supervised hundreds of MIT undergraduate research projects and 50+ graduate-level (MS&PhD) thesis projects.<br />
<br />
*Anything else you think is relevant.<br />
<br />
You learn through doing, so I will roll up my sleeves along side whomever I mentor, because I want to keep learning.<br />
<br />
===[[User:Mstone|Michael]]===<br />
*Name/contact<br />
:: Michael Stone / michael@laptop.org<br />
*Timezone<br />
:: EDT (UTC-4)<br />
*What kind of projects could/would you mentor?<br />
:: One project<br />
*How much time could you devote to mentoring?<br />
:: 5-10 hr/week<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
:: I am the author of [http://wiki.laptop.org/go/Rainbow rainbow]. I also am intimately familiar with Sugar's architecture, design, and code base.<br />
*What relevant mentoring (or related) experience do you have?<br />
:: I analyze, critique, and improve software professionally, often working with less experienced coders. I also managed the release of a small operating system ([http://wiki.laptop.org/go/Release_notes/8.2.0 OLPC's 8.2.0 OS release]) in which I helped to fold the work of many contributors, both new and old, into a successful and coherent software development experience.<br />
*Anything else you think is relevant.<br />
:: My entrée into professional software development, [http://wiki.laptop.org/go/Rainbow rainbow], was begun in an internship not unlike the ones you're applying for here. Now it's time for me to "pay it forward".<br />
<br />
[[Category:GSoC]]</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Mentors&diff=50101Summer of Code/Mentors2010-03-20T16:15:10Z<p>Mstone: /* Michael */</p>
<hr />
<div>{{TOCright}}<br />
==Mentors==<br />
Our most important need right now is for quality mentors. If you (or someone you know) would make a good mentor, please nominate yourself (or them), both here on the ML (iaep AT sl.o) and on the wiki (if you can't handle a little redundant paperwork, you're probably not a good candidate :). Include relevant information such as:<br />
<br />
*Name/contact<br />
*Timezone<br />
*What kind of projects could/would you mentor?<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
*What relevant mentoring (or related) experience do you have?<br />
*Anything else you think is relevant.<br />
<br />
Please also add this page to your watchlist. We will probably later do some kind of "community interview" process where we ask you questions on this page.<br />
<br />
=== Jameson ===<br />
<br />
*Name/contact<br />
<br />
Jameson.Quinn at gmail<br />
<br />
*Timezone<br />
<br />
US Central / Central America (UTC-6)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements, especially interested in language or developer tools.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week. If we are short on mentors and I find project(s) that are an especially good match, I could do 8 hrs (double duty). Over the summer, I hope to be helping to work on an XO deployment, hopefully on a paid basis, but am currently unemployed.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Develop activity, have done some tinkering with Sugar, I've been involved for over a year.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I have several years' experience as a full-time teacher.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== [[User:Nrp|Nrp]] ===<br />
<br />
* Name/contact<br />
<br />
Nirav Patel nrpatel at gmail<br />
<br />
* Timezone<br />
<br />
UTC-5<br />
<br />
* What kind of projects could/would you mentor?<br />
<br />
Pygame or PyGTK based Activities<br />
<br />
* How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Graduating and no job prospects, so it is likely I will have quite a<br />
bit of free time as of early May. 5 hours a week is certainly doable.<br />
<br />
* What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Some Pygame/PyGTK Activity development and a module for Pygame.<br />
<br />
* What relevant mentoring (or related) experience do you have?<br />
<br />
Teaching Assistant and miscellaneous mentoring experiences at school.<br />
<br />
* Anything else you think is relevant.<br />
<br />
I survived GSoC on the student end of things in 2008.<br />
<br />
=== Tomeu ===<br />
<br />
*Name/contact<br />
<br />
[[User:Tomeu | Tomeu Vizoso]]<br />
<br />
*Timezone<br />
<br />
Central European Time<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Coded activities and for the sugar shell for more than two years now.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Last year mentored one intern at OLPC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== [[User:Bobbyp|Bobby]] ===<br />
<br />
*Name/contact<br />
<br />
firstnamelastname at gmail, nteon on IRC<br />
<br />
*Timezone<br />
<br />
US Eastern Standard Time (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, lower level stuff.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Probably 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Model activity, have done some tinkering with Sugar/Rainbow, rewrote boot-animation. Fairly confident with C/Python/Linux, have been involved with OLPC for about a year (although have been mostly lurking on the sugar side of things for a few months).<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Summer camp counselor for a number of years, OLPC intern summer '08.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I'm a few months behind on Sugar development, but think its a fabulous project. Let me know what you need of me.<br />
<br />
=== [[User:Sebastian|Sebastian]] ===<br />
<br />
*Name/contact<br />
<br />
Sebastian Silva (sebastian at fuentelibre.org), (gmail alternative: sebatustra)<br />
<br />
icarito on IRC<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, especially "social" activities.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am helping a teacher group this (northern summer), that leaves me enough time to commit to this (at least 4-6 hours a week, more if needed). It also is a great chance for some user feedback.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities, led workshops. Confident in python and GNU. Worked professionally in programming for some years.<br />
<br />
=== [[User:Wade|Wade]] ===<br />
<br />
*Name/contact<br />
<br />
Wade Brainerd (wadetb at gmail dot com) <br />
<br />
wadeb on IRC<br />
<br />
*Timezone<br />
<br />
Portland, Maine (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
New activities, Games, Updates to/refreshes of existing activities, Frameworks for creating activities in new languages (Flash, Ajax, Mono)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I will be available for a single mentorship this year. I work full time as a programmer but have a flexible schedule.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities. Experienced in Python, C++, others. 11 years as a professional programmer, including 5 as a technical director and team lead.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was closely involved in the 2007 OLPC GSoC project, reviewing applications and communicating with students. I mentored two students informally during 2007 after their GSoC projects were not funded. Both projects were completed with my help.<br />
<br />
*Anything else you think is relevant.<br />
<br />
As the Sugar Labs Activity Team coordinator, I have plenty of access to deployments. This gives me a good handle on what student projects will most effectively advance Sugar Labs' goals in the community. <br />
<br />
As a volunteer activity developer, I have also developed many new activities myself, and overhauled existing ones.<br />
<br />
=== [[User:Lglira|Lglira]] ===<br />
<br />
*Name/contact<br />
<br />
Luis Gustavo Lira, BSc, MSc lira.lg at pucp.edu.pe<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Networking, Hardware Projects, Python, Activities (science, math, entrepreneurship).<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could mentor 1 o 2 students.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Engineer 10 years working experience, CIO and Executive level since 2006.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Consultant for big telecomms, systems integrators, etc.<br />
Lecturer at University undergraduate and graduate level.<br />
GSoC 2007, 2008 and 2009 Mentor for OpenMoko<br />
GSoC 2008 for OLPC but my student was not funded<br />
<br />
*Anything else you think is relevant.<br />
<br />
Fellow of Lemelson Foundation RAMP-Peru, Social Entrepreneur, Free Culture activist, Appropriate Technology developer, Teaching Science, Math and Entrepeneurship in rural terciary schools.<br />
<br />
=== [[User:benlau|Ben Lau]] ===<br />
<br />
*Name/contact<br />
xbenlau at gmail.com<br />
<br />
*Timezone<br />
UTC+8<br />
<br />
*What kind of projects could/would you mentor?<br />
Video , Computer Vision , Speech Processing , Python, Activities (Educational software , Chinese language learning)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
I could commit up to 4-5 hours a week, able to mentor 1 student.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
10 years Linux development experience , include kernel porting (ARM), Linux driver , GTK+ , opencv , GStreamer , C/C++ , python<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
I have led two teams of university students to join an embedded system contest called Intel Cup (China) in 2006. The teams got a first prize and a second prize award finally.<br />
<br />
*Anything else you think is relevant.<br />
I am leading a team of volunteers on technical side for OLPC APAC division.<br />
<br />
=== [[User:SayaminduDasgupta|Sayamindu]] ===<br />
<br />
*Name/contact<br />
<br />
Sayamindu Dasgupta (sayamindu at gmail)<br />
<br />
unmadindu on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530) (I normally work on European timezones)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Activities, l10n/i18n related projects.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am working a contractor for OLPC for the next few months. However, I think I can commit around 4-5 hours per week for the work.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Wrote the Imageviewer activity, maintainer of Terminal, in the process of implementing largish features to Read. Familiar with GTK+, Python, Gstreamer, etc.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was a mentor during SoC 2008 for the Translate toolkit project (my student worked successfully on enhancing the Pootle featureset). I have also experience informally mentoring/guiding students and volunteers for a number of Free Software projects (mostly i18n/l10n related).<br />
<br />
*Anything else you think is relevant.<br />
<br />
I was a successful student participant in Summer of Code 2007 under Federico Mena-Quintero for the GNOME project. I also helped in the rating of applications for OLPC as a mentoring organisation during 2008's SoC.<br />
<br />
<br />
<br />
=== [[User:Assim|Assim Deodia]] ===<br />
<br />
*Name/contact<br />
<br />
Assim Deodia (assim.deodia at gmail dot com)<br />
<br />
assimd on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
[[Activities/Listen Spell|Listen Spell]], Activities related to speech synthesis<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I can comfortably devote 4-5 hrs a week. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I have developed speech server in SoCon for OLPC [http://wiki.laptop.org/go/Speech_Server| Speech Server], Deducto for OLPC and have also developed Listen Spell for OLPC in GSoC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I have successful completed Summer of Code 2008 under Dafydd Harries for the OLPC. I have also developed a low cost OMR processing application which is hosted on sourceforge [http://sourceforge.net/projects/omr-ai/| OMR AI]<br />
<br />
<br />
<br />
<br />
<br />
=== [[User:Aa|aa]] ===<br />
<br />
*Name/contact<br />
<br />
andresambrois at gmail<br />
<br />
*Timezone<br />
<br />
America/Montevideo (UTC-3)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities and Sugar projects, especially in collaboration and networking. <br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
5-6 hours a week. Currently unemployed, but studying computer engineering. I devote most of my time to free software projects and Ceibal-related volunteering. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I maintain the PlayGo activity, one of the developers of the [http://wiki.laptop.org/go/Educational_Blogger_Project| EduBlog project], written a couple of patches for sugar and currently working on some improvements. Familiar with Python, PHP, Tcl, Shell Scripting and (some) C. <br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I've given technical talks and workshops, and was a math tutor years ago. <br />
<br />
*Anything else you think is relevant.<br />
<br />
I fear velociraptors.<br />
<br />
=== Alfonsodg ===<br />
<br />
*Name/contact<br />
<br />
[[User:Alfonsodg | Alfonso de la Guarda]]<br />
<br />
*Timezone<br />
<br />
GMT -5<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Sugar activities based on python, gtk, glade and some electronical enhancements<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4 to 6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Coded multiple python apps since 2001, including some XO activities<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Lead Technology Consultor for the Peruvian Army with 7 projects based all on FLOSS<br />
<br />
*Anything else you think is relevant.<br />
<br />
Love technology and wanna that some of my activities could be better with the help of many people<br />
<br />
=== Alex Levenson ===<br />
<br />
*Name/contact<br />
**Alex Levenson<br />
**alev742@gwu.edu<br />
<br />
*Timezone<br />
**Eastern Time during the school year, Pacific Time during the summer<br />
<br />
*What kind of projects could/would you mentor?<br />
**Anything physics engine related<br />
**Anything related to games, pygame, olpcgames, graphics, etc<br />
<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
**I'll be working for Google in San Francisco this summer.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
**I wrote a couple of physics simulation activities for OLPC last summer. I am a computer science major and have experience as a software developer. Resume: http://student.seas.gwu.edu/~alev742/resume.php<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
**I am a computer science tutor here at The George Washington University.<br />
<br />
*What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty)<br />
**I would be glad to provide any kind of support I can, from high level software design strategy to code reviews. I would like to focus on keeping the code not only functional but elegant, readable, and scalable - something that's very important as this platform moves forward.<br />
<br />
*Anything else you think is relevant.<br />
**Please check out my resume: http://student.seas.gwu.edu/~alev742/resume.php<br />
**And also my olpc userpage: http://wiki.laptop.org/go/User:Alexlevenson<br />
<br />
=== Guillaume Desmottes ===<br />
<br />
*Name/contact: [[User:Cassidy|Guillaume Desmottes]]<br />
<br />
*Timezone: GMT+1 (UK)<br />
<br />
*What kind of projects could/would you mentor? Telepathy related<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
** If possible I'd prefer co-mentoring so I would focus on the Telepathy part and a Sugar guy on the UI/integration one. I'll work this summer but my [http://www.collabora.co.uk/ employer] would probably let me allocate some time on mentoring if needed. I could maybe have another soc student on the GNOME front too.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
** I hack on Telepathy as my job. Did lot of the Telepathy integration in Sugar.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
** Never mentored soc projects but regularly help people on #telepathy and #sugar.<br />
<br />
*What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty)<br />
** My main goal is to ensure than proposed projects are did the right way. I want to avoid that student did the code on his own without any input from relevant person and so is finally never merged because it was just the wrong approach.<br />
<br />
===[[User:BryanWB|Bryan W Berry]]===<br />
<br />
*Name: [[User:BryanWB|Bryan W Berry]]<br />
*Timezone : GMT+5:45 (Nepal)<br />
*What kind of projects could/would you mentor?<br />
Using Web technologies to create Sugar activities, like [[Karma]]<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
<br />
I can probably only mentor one person. I think I can contribute 10 hours per week for 3 months.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
For the past two years I have led a team of 10 full-time software developers creating open-source educational learning activities. <br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I have mentored 12 Nepali interns at OLE Nepal over the last 12 months.<br />
<br />
What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty) <br />
<br />
There is a lot to creating learning activities that is not technical but procedure. I am particularly interested in making it easier for programmers to create learning activities.<br />
<br />
===[[User:Walter|Walter]]===<br />
*Name/contact<br />
<br />
Walter Bender / (walter AT sl.o)<br />
<br />
*Timezone<br />
<br />
EST (UTC+4)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Activities, and some Sugar UI-related projects (anything relevant to daily life in the classroom.)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
<br />
Not sure what a "double mentor" is, but I could put in 10 hours/week...<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I have been with the Sugar project since the beginning and have been making the occasional Sugar patch; I have written and maintain a half-dozen activities.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was a GSoC coordinator and mentor in 2009. I have supervised hundreds of MIT undergraduate research projects and 50+ graduate-level (MS&PhD) thesis projects.<br />
<br />
*Anything else you think is relevant.<br />
<br />
You learn through doing, so I will roll up my sleeves along side whomever I mentor, because I want to keep learning.<br />
<br />
===[[User:Mstone|Michael]]===<br />
*Name/contact<br />
:: Michael Stone / michael@laptop.org<br />
*Timezone<br />
:: EDT (UTC-4)<br />
*What kind of projects could/would you mentor?<br />
:: One project<br />
*How much time could you devote to mentoring?<br />
:: 5-10 hr/week<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
:: I am the author of [http://wiki.laptop.org/go/Rainbow rainbow]. I also am intimately familiar with Sugar's architecture, design, and code base.<br />
*What relevant mentoring (or related) experience do you have?<br />
:: I analyze, critique, and improve software professionally, often working with less experienced coders. I also managed the release of a small operating system ([http://wiki.laptop.org/go/Release_notes/8.2.0 OLPC's 8.2.0 OS release]) in which I helped to fold the work of many contributors, both large and small, into a successful and coherent software development experience.<br />
*Anything else you think is relevant.<br />
:: My entrée into professional software development, [http://wiki.laptop.org/go/Rainbow rainbow], was begun in an internship not unlike the ones you're applying for here. Now it's time for me to "pay it forward".<br />
<br />
[[Category:GSoC]]</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Mentors&diff=50100Summer of Code/Mentors2010-03-20T16:14:06Z<p>Mstone: </p>
<hr />
<div>{{TOCright}}<br />
==Mentors==<br />
Our most important need right now is for quality mentors. If you (or someone you know) would make a good mentor, please nominate yourself (or them), both here on the ML (iaep AT sl.o) and on the wiki (if you can't handle a little redundant paperwork, you're probably not a good candidate :). Include relevant information such as:<br />
<br />
*Name/contact<br />
*Timezone<br />
*What kind of projects could/would you mentor?<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
*What relevant mentoring (or related) experience do you have?<br />
*Anything else you think is relevant.<br />
<br />
Please also add this page to your watchlist. We will probably later do some kind of "community interview" process where we ask you questions on this page.<br />
<br />
=== Jameson ===<br />
<br />
*Name/contact<br />
<br />
Jameson.Quinn at gmail<br />
<br />
*Timezone<br />
<br />
US Central / Central America (UTC-6)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements, especially interested in language or developer tools.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week. If we are short on mentors and I find project(s) that are an especially good match, I could do 8 hrs (double duty). Over the summer, I hope to be helping to work on an XO deployment, hopefully on a paid basis, but am currently unemployed.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Develop activity, have done some tinkering with Sugar, I've been involved for over a year.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I have several years' experience as a full-time teacher.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== [[User:Nrp|Nrp]] ===<br />
<br />
* Name/contact<br />
<br />
Nirav Patel nrpatel at gmail<br />
<br />
* Timezone<br />
<br />
UTC-5<br />
<br />
* What kind of projects could/would you mentor?<br />
<br />
Pygame or PyGTK based Activities<br />
<br />
* How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Graduating and no job prospects, so it is likely I will have quite a<br />
bit of free time as of early May. 5 hours a week is certainly doable.<br />
<br />
* What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Some Pygame/PyGTK Activity development and a module for Pygame.<br />
<br />
* What relevant mentoring (or related) experience do you have?<br />
<br />
Teaching Assistant and miscellaneous mentoring experiences at school.<br />
<br />
* Anything else you think is relevant.<br />
<br />
I survived GSoC on the student end of things in 2008.<br />
<br />
=== Tomeu ===<br />
<br />
*Name/contact<br />
<br />
[[User:Tomeu | Tomeu Vizoso]]<br />
<br />
*Timezone<br />
<br />
Central European Time<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Coded activities and for the sugar shell for more than two years now.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Last year mentored one intern at OLPC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== [[User:Bobbyp|Bobby]] ===<br />
<br />
*Name/contact<br />
<br />
firstnamelastname at gmail, nteon on IRC<br />
<br />
*Timezone<br />
<br />
US Eastern Standard Time (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, lower level stuff.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Probably 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Model activity, have done some tinkering with Sugar/Rainbow, rewrote boot-animation. Fairly confident with C/Python/Linux, have been involved with OLPC for about a year (although have been mostly lurking on the sugar side of things for a few months).<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Summer camp counselor for a number of years, OLPC intern summer '08.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I'm a few months behind on Sugar development, but think its a fabulous project. Let me know what you need of me.<br />
<br />
=== [[User:Sebastian|Sebastian]] ===<br />
<br />
*Name/contact<br />
<br />
Sebastian Silva (sebastian at fuentelibre.org), (gmail alternative: sebatustra)<br />
<br />
icarito on IRC<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, especially "social" activities.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am helping a teacher group this (northern summer), that leaves me enough time to commit to this (at least 4-6 hours a week, more if needed). It also is a great chance for some user feedback.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities, led workshops. Confident in python and GNU. Worked professionally in programming for some years.<br />
<br />
=== [[User:Wade|Wade]] ===<br />
<br />
*Name/contact<br />
<br />
Wade Brainerd (wadetb at gmail dot com) <br />
<br />
wadeb on IRC<br />
<br />
*Timezone<br />
<br />
Portland, Maine (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
New activities, Games, Updates to/refreshes of existing activities, Frameworks for creating activities in new languages (Flash, Ajax, Mono)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I will be available for a single mentorship this year. I work full time as a programmer but have a flexible schedule.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities. Experienced in Python, C++, others. 11 years as a professional programmer, including 5 as a technical director and team lead.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was closely involved in the 2007 OLPC GSoC project, reviewing applications and communicating with students. I mentored two students informally during 2007 after their GSoC projects were not funded. Both projects were completed with my help.<br />
<br />
*Anything else you think is relevant.<br />
<br />
As the Sugar Labs Activity Team coordinator, I have plenty of access to deployments. This gives me a good handle on what student projects will most effectively advance Sugar Labs' goals in the community. <br />
<br />
As a volunteer activity developer, I have also developed many new activities myself, and overhauled existing ones.<br />
<br />
=== [[User:Lglira|Lglira]] ===<br />
<br />
*Name/contact<br />
<br />
Luis Gustavo Lira, BSc, MSc lira.lg at pucp.edu.pe<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Networking, Hardware Projects, Python, Activities (science, math, entrepreneurship).<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could mentor 1 o 2 students.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Engineer 10 years working experience, CIO and Executive level since 2006.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Consultant for big telecomms, systems integrators, etc.<br />
Lecturer at University undergraduate and graduate level.<br />
GSoC 2007, 2008 and 2009 Mentor for OpenMoko<br />
GSoC 2008 for OLPC but my student was not funded<br />
<br />
*Anything else you think is relevant.<br />
<br />
Fellow of Lemelson Foundation RAMP-Peru, Social Entrepreneur, Free Culture activist, Appropriate Technology developer, Teaching Science, Math and Entrepeneurship in rural terciary schools.<br />
<br />
=== [[User:benlau|Ben Lau]] ===<br />
<br />
*Name/contact<br />
xbenlau at gmail.com<br />
<br />
*Timezone<br />
UTC+8<br />
<br />
*What kind of projects could/would you mentor?<br />
Video , Computer Vision , Speech Processing , Python, Activities (Educational software , Chinese language learning)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
I could commit up to 4-5 hours a week, able to mentor 1 student.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
10 years Linux development experience , include kernel porting (ARM), Linux driver , GTK+ , opencv , GStreamer , C/C++ , python<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
I have led two teams of university students to join an embedded system contest called Intel Cup (China) in 2006. The teams got a first prize and a second prize award finally.<br />
<br />
*Anything else you think is relevant.<br />
I am leading a team of volunteers on technical side for OLPC APAC division.<br />
<br />
=== [[User:SayaminduDasgupta|Sayamindu]] ===<br />
<br />
*Name/contact<br />
<br />
Sayamindu Dasgupta (sayamindu at gmail)<br />
<br />
unmadindu on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530) (I normally work on European timezones)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Activities, l10n/i18n related projects.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am working a contractor for OLPC for the next few months. However, I think I can commit around 4-5 hours per week for the work.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Wrote the Imageviewer activity, maintainer of Terminal, in the process of implementing largish features to Read. Familiar with GTK+, Python, Gstreamer, etc.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was a mentor during SoC 2008 for the Translate toolkit project (my student worked successfully on enhancing the Pootle featureset). I have also experience informally mentoring/guiding students and volunteers for a number of Free Software projects (mostly i18n/l10n related).<br />
<br />
*Anything else you think is relevant.<br />
<br />
I was a successful student participant in Summer of Code 2007 under Federico Mena-Quintero for the GNOME project. I also helped in the rating of applications for OLPC as a mentoring organisation during 2008's SoC.<br />
<br />
<br />
<br />
=== [[User:Assim|Assim Deodia]] ===<br />
<br />
*Name/contact<br />
<br />
Assim Deodia (assim.deodia at gmail dot com)<br />
<br />
assimd on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
[[Activities/Listen Spell|Listen Spell]], Activities related to speech synthesis<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I can comfortably devote 4-5 hrs a week. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I have developed speech server in SoCon for OLPC [http://wiki.laptop.org/go/Speech_Server| Speech Server], Deducto for OLPC and have also developed Listen Spell for OLPC in GSoC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I have successful completed Summer of Code 2008 under Dafydd Harries for the OLPC. I have also developed a low cost OMR processing application which is hosted on sourceforge [http://sourceforge.net/projects/omr-ai/| OMR AI]<br />
<br />
<br />
<br />
<br />
<br />
=== [[User:Aa|aa]] ===<br />
<br />
*Name/contact<br />
<br />
andresambrois at gmail<br />
<br />
*Timezone<br />
<br />
America/Montevideo (UTC-3)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities and Sugar projects, especially in collaboration and networking. <br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
5-6 hours a week. Currently unemployed, but studying computer engineering. I devote most of my time to free software projects and Ceibal-related volunteering. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I maintain the PlayGo activity, one of the developers of the [http://wiki.laptop.org/go/Educational_Blogger_Project| EduBlog project], written a couple of patches for sugar and currently working on some improvements. Familiar with Python, PHP, Tcl, Shell Scripting and (some) C. <br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I've given technical talks and workshops, and was a math tutor years ago. <br />
<br />
*Anything else you think is relevant.<br />
<br />
I fear velociraptors.<br />
<br />
=== Alfonsodg ===<br />
<br />
*Name/contact<br />
<br />
[[User:Alfonsodg | Alfonso de la Guarda]]<br />
<br />
*Timezone<br />
<br />
GMT -5<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Sugar activities based on python, gtk, glade and some electronical enhancements<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4 to 6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Coded multiple python apps since 2001, including some XO activities<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Lead Technology Consultor for the Peruvian Army with 7 projects based all on FLOSS<br />
<br />
*Anything else you think is relevant.<br />
<br />
Love technology and wanna that some of my activities could be better with the help of many people<br />
<br />
=== Alex Levenson ===<br />
<br />
*Name/contact<br />
**Alex Levenson<br />
**alev742@gwu.edu<br />
<br />
*Timezone<br />
**Eastern Time during the school year, Pacific Time during the summer<br />
<br />
*What kind of projects could/would you mentor?<br />
**Anything physics engine related<br />
**Anything related to games, pygame, olpcgames, graphics, etc<br />
<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
**I'll be working for Google in San Francisco this summer.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
**I wrote a couple of physics simulation activities for OLPC last summer. I am a computer science major and have experience as a software developer. Resume: http://student.seas.gwu.edu/~alev742/resume.php<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
**I am a computer science tutor here at The George Washington University.<br />
<br />
*What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty)<br />
**I would be glad to provide any kind of support I can, from high level software design strategy to code reviews. I would like to focus on keeping the code not only functional but elegant, readable, and scalable - something that's very important as this platform moves forward.<br />
<br />
*Anything else you think is relevant.<br />
**Please check out my resume: http://student.seas.gwu.edu/~alev742/resume.php<br />
**And also my olpc userpage: http://wiki.laptop.org/go/User:Alexlevenson<br />
<br />
=== Guillaume Desmottes ===<br />
<br />
*Name/contact: [[User:Cassidy|Guillaume Desmottes]]<br />
<br />
*Timezone: GMT+1 (UK)<br />
<br />
*What kind of projects could/would you mentor? Telepathy related<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
** If possible I'd prefer co-mentoring so I would focus on the Telepathy part and a Sugar guy on the UI/integration one. I'll work this summer but my [http://www.collabora.co.uk/ employer] would probably let me allocate some time on mentoring if needed. I could maybe have another soc student on the GNOME front too.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
** I hack on Telepathy as my job. Did lot of the Telepathy integration in Sugar.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
** Never mentored soc projects but regularly help people on #telepathy and #sugar.<br />
<br />
*What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty)<br />
** My main goal is to ensure than proposed projects are did the right way. I want to avoid that student did the code on his own without any input from relevant person and so is finally never merged because it was just the wrong approach.<br />
<br />
===[[User:BryanWB|Bryan W Berry]]===<br />
<br />
*Name: [[User:BryanWB|Bryan W Berry]]<br />
*Timezone : GMT+5:45 (Nepal)<br />
*What kind of projects could/would you mentor?<br />
Using Web technologies to create Sugar activities, like [[Karma]]<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
<br />
I can probably only mentor one person. I think I can contribute 10 hours per week for 3 months.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
For the past two years I have led a team of 10 full-time software developers creating open-source educational learning activities. <br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I have mentored 12 Nepali interns at OLE Nepal over the last 12 months.<br />
<br />
What do you think your role as a mentor would involve? How would you fill it, and why? (3-5 sentences is plenty) <br />
<br />
There is a lot to creating learning activities that is not technical but procedure. I am particularly interested in making it easier for programmers to create learning activities.<br />
<br />
===[[User:Walter|Walter]]===<br />
*Name/contact<br />
<br />
Walter Bender / (walter AT sl.o)<br />
<br />
*Timezone<br />
<br />
EST (UTC+4)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Activities, and some Sugar UI-related projects (anything relevant to daily life in the classroom.)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
<br />
Not sure what a "double mentor" is, but I could put in 10 hours/week...<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I have been with the Sugar project since the beginning and have been making the occasional Sugar patch; I have written and maintain a half-dozen activities.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was a GSoC coordinator and mentor in 2009. I have supervised hundreds of MIT undergraduate research projects and 50+ graduate-level (MS&PhD) thesis projects.<br />
<br />
*Anything else you think is relevant.<br />
<br />
You learn through doing, so I will roll up my sleeves along side whomever I mentor, because I want to keep learning.<br />
<br />
===[[User:Mstone|Michael]]===<br />
*Name/contact<br />
:: Michael Stone / michael@laptop.org<br />
*Timezone<br />
:: EDT (UTC-4)<br />
*What kind of projects could/would you mentor?<br />
:: One project<br />
*How much time could you devote to mentoring?<br />
:: 5-10 hr/week<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
:: I am the author of [http://wiki.laptop.org/go/Rainbow rainbow]. I also am intimately familiar with Sugar's architecture, design, and code base.<br />
*What relevant mentoring (or related) experience do you have?<br />
:: I analyze, critique, and improve software professionally, often working with less experienced coders. I also managed the release of a large software distribution ([http://wiki.laptop.org/go/Release_notes/8.2.0 OLPC's 8.2.0 OS release]) in which I helped to fold the work of many contributors, both large and small, into a successful and coherent software development experience.<br />
*Anything else you think is relevant.<br />
:: My entrée into professional software development, [http://wiki.laptop.org/go/Rainbow rainbow], was begun in an internship not unlike the ones you're applying for here. Now it's time for me to "pay it forward".<br />
<br />
[[Category:GSoC]]</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=43470Development Team/Chroot2010-01-23T19:10:02Z<p>Mstone: </p>
<hr />
<div>=== Status ===<br />
<br />
* sugar-chroot-0.1 released: see [http://dev.laptop.org/git/users/mstone/sugar-chroot sugar-chroot]<br />
<br />
=== Purpose ===<br />
<br />
''You want to hack sugar. You don't want to fuss around. '''You want sugar-chroot.'''''<br />
<br />
=== Usage ===<br />
<br />
As excerpted from the '''[http://dev.laptop.org/git/users/mstone/sugar-chroot/plain/README README]''':<br />
<br />
sugar-chroot consists of simple scripts. Download and unpack them like so:<br />
<br />
NV=sugar-chroot-0.1<br />
curl http://dev.laptop.org/~mstone/releases/SOURCES/$NV.tar.xz | tar Zxf $NV.tar.xz<br />
cd $NV<br />
<br />
To use them, pick a supported distro:<br />
<br />
DISTRO=debian<br />
DISTRO=fedora<br />
<br />
To configure:<br />
<br />
echo $DISTRO > conf/distro<br />
$EDITOR conf/$DISTRO.mk<br />
<br />
Then run<br />
<br />
sudo make r/distro<br />
<br />
to install your chroot.<br />
<br />
=== History ===<br />
<br />
See http://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&oldid=36911 for the manual instructions which sugar-chroot automates.</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=43469Development Team/Chroot2010-01-23T19:07:06Z<p>Mstone: </p>
<hr />
<div>=== Status ===<br />
<br />
* sugar-chroot-0.1 released: see [http://dev.laptop.org/git/users/mstone/sugar-chroot sugar-chroot]<br />
<br />
=== Purpose ===<br />
<br />
You want to hack sugar.<br />
<br />
You don't want to fuss around.<br />
<br />
'''You want sugar-chroot.'''<br />
<br />
=== Usage ===<br />
<br />
As excerpted from the '''[http://dev.laptop.org/git/users/mstone/sugar-chroot/plain/README README]''':<br />
<br />
sugar-chroot consists of simple scripts. Download and unpack them like so:<br />
<br />
NV=sugar-chroot-0.1<br />
curl http://dev.laptop.org/~mstone/releases/SOURCES/$NV.tar.xz | tar Zxf $NV.tar.xz<br />
cd $NV<br />
<br />
To use them, pick a supported distro:<br />
<br />
DISTRO=debian<br />
DISTRO=fedora<br />
<br />
To configure:<br />
<br />
echo $DISTRO > conf/distro<br />
$EDITOR conf/$DISTRO.mk<br />
<br />
Then run<br />
<br />
sudo make r/distro<br />
<br />
to install your chroot.<br />
<br />
=== History ===<br />
<br />
See http://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&oldid=36911 for the manual instructions which sugar-chroot automates.</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=43468Development Team/Chroot2010-01-23T19:06:14Z<p>Mstone: </p>
<hr />
<div>=== Status ===<br />
<br />
* sugar-chroot-0.1 released: see [http://dev.laptop.org/git/users/mstone/sugar-chroot sugar-chroot]<br />
<br />
=== Purpose ===<br />
<br />
You want to '''hack sugar'''.<br />
<br />
You want '''clean, reproducible environments'''. <br />
<br />
'''You want sugar-chroot.'''<br />
<br />
=== Usage ===<br />
<br />
As excerpted from the '''[http://dev.laptop.org/git/users/mstone/sugar-chroot/plain/README README]''':<br />
<br />
sugar-chroot consists of simple scripts. Download and unpack them like so:<br />
<br />
NV=sugar-chroot-0.1<br />
curl http://dev.laptop.org/~mstone/releases/SOURCES/$NV.tar.xz | tar Zxf $NV.tar.xz<br />
cd $NV<br />
<br />
To use them, pick a supported distro:<br />
<br />
DISTRO=debian<br />
DISTRO=fedora<br />
<br />
To configure:<br />
<br />
echo $DISTRO > conf/distro<br />
$EDITOR conf/$DISTRO.mk<br />
<br />
Then run<br />
<br />
sudo make r/distro<br />
<br />
to install your chroot.<br />
<br />
=== History ===<br />
<br />
See http://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&oldid=36911 for the manual instructions which sugar-chroot automates.</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=43467Development Team/Chroot2010-01-23T19:02:15Z<p>Mstone: </p>
<hr />
<div>=== Status ===<br />
<br />
* sugar-chroot-0.1 released: see [http://dev.laptop.org/git/users/mstone/sugar-chroot sugar-chroot]<br />
<br />
=== Purpose ===<br />
<br />
You want to '''test sugar''', sugar patches, sugar packages, or sugar hacks. <br />
<br />
You want '''clean, reproducible environments'''. <br />
<br />
'''You want sugar-chroot.'''<br />
<br />
=== Usage ===<br />
<br />
As excerpted from the '''[http://dev.laptop.org/git/users/mstone/sugar-chroot/plain/README README]''':<br />
<br />
sugar-chroot consists of simple scripts. Download and unpack them like so:<br />
<br />
NV=sugar-chroot-0.1<br />
curl http://dev.laptop.org/~mstone/releases/SOURCES/$NV.tar.xz | tar Zxf $NV.tar.xz<br />
cd $NV<br />
<br />
To use them, pick a supported distro:<br />
<br />
DISTRO=debian<br />
DISTRO=fedora<br />
<br />
To configure:<br />
<br />
echo $DISTRO > conf/distro<br />
$EDITOR conf/$DISTRO.mk<br />
<br />
Then run<br />
<br />
sudo make r/distro<br />
<br />
to install your chroot.<br />
<br />
=== History ===<br />
<br />
See http://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&oldid=36911 for the manual instructions which sugar-chroot automates.</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=43466Development Team/Chroot2010-01-23T19:01:18Z<p>Mstone: </p>
<hr />
<div>=== Status ===<br />
<br />
* sugar-chroot-0.1 released: see [http://dev.laptop.org/git/users/mstone/sugar-chroot sugar-chroot]<br />
<br />
=== Purpose ===<br />
<br />
You want to test sugar, sugar patches, sugar packages, or sugar hacks. You want clean, reproducible environments. You want sugar-chroot.<br />
<br />
=== Usage ===<br />
<br />
As excerpted from the '''[http://dev.laptop.org/git/users/mstone/sugar-chroot/plain/README README]''':<br />
<br />
sugar-chroot consists of simple scripts. Download and unpack them like so:<br />
<br />
NV=sugar-chroot-0.1<br />
curl http://dev.laptop.org/~mstone/releases/SOURCES/$NV.tar.xz | tar Zxf $NV.tar.xz<br />
cd $NV<br />
<br />
To use them, pick a supported distro:<br />
<br />
DISTRO=debian<br />
DISTRO=fedora<br />
<br />
To configure:<br />
<br />
echo $DISTRO > conf/distro<br />
$EDITOR conf/$DISTRO.mk<br />
<br />
Then run<br />
<br />
sudo make r/distro<br />
<br />
to install your chroot.<br />
<br />
=== History ===<br />
<br />
See http://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&oldid=36911 for the manual instructions which sugar-chroot automates.</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=36911Development Team/Chroot2009-09-07T15:23:52Z<p>Mstone: /* Fedora rawhide chroot */</p>
<hr />
<div>=== Status ===<br />
<br />
* Debian chroot construction has been automated: see [http://dev.laptop.org/git/users/mstone/puritan/snapshot/puritan-sugar.tar.bz2 puritan-sugar.tar.bz2] and its [http://dev.laptop.org/git/users/mstone/puritan/tree/README?h=sugar README] -- [[User:Mstone|Michael Stone]] 20:33, 1 August 2009 (UTC)<br />
* Sugar continues to run happily in Squeeze chroots. --[[User:Mstone|Michael Stone]] 16:30, 3 July 2009 (UTC)<br />
* Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
# and to enter the chroot<br />
sudo chroot $CHROOT /bin/bash -l<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
==== Fedora rawhide chroot ====<br />
<br />
We will use <tt>febootstrap</tt> to construct our Fedora chroot. Install it with:<br />
<br />
yum install febootstrap # or<br />
apt-get install febootstrap<br />
<br />
: ''(Note for Debian users -- Fedora 11 and up require versions of <tt>rpm</tt> built with fancy features. I have successfully run these instructions with rpm_4.7.1-4_i386, which, at the time, I built from sources in Debian Experimental.)''<br />
<br />
Then run it like so:<br />
<br />
export CHROOT=`pwd`/f11<br />
sudo febootstrap fedora-11 $CHROOT # sugar-0.84<br />
<br />
or <br />
<br />
export CHROOT=`pwd`/f12<br />
sudo febootstrap fedora-12 $CHROOT # sugar-0.85.5, at the time of writing<br />
<br />
Finally, as with Debian:<br />
<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
# and to enter the chroot<br />
sudo chroot $CHROOT /bin/bash -l<br />
<br />
==== Gentoo chroot ====<br />
<br />
Well, if you are familiar with regular Gentoo installation process(by using [http://www.gentoo.org/doc/en/handbook/ Handbook] instead of GUI stuff) you should know how to setup Gentoo chtoot :). Otherwise use these instructions.<br />
<br />
* Firstly, you need Gentoo stage tarball. You can borrow it from any [http://www.gentoo.org/main/en/mirrolrs2.xml mirror] (use releases/<platform>/current sub directory).<br />
<br />
* Lets think you are using stage3-i686-20090623.tar.bz2, then:<br />
<br />
mkdir chroot-gentoo<br />
tar xjpf stage3-i686-20090623.tar.bz2 -C chroot-gentoo<br />
mount -o bind /dev chroot-gentoo/dev<br />
mount -o bind /proc chroot-gentoo/proc<br />
chroot chroot-gentoo /bin/bash<br />
<br />
* To install sugar, use [[Community/Distributions/Gentoo|sugar-overlay]] or setup [[Development_Team/Jhbuild|sugar-jhbuild]] environment(with [[Community/Distributions/Gentoo#Packages|sugar-overlay]] you can install git packages as well).<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar sugar-0.84<br />
<br />
# install your development tools here<br />
<br />
==== f12 chroot ====<br />
<br />
yum groupinstall sugar-desktop<br />
<br />
<br />
==== f11 chroot ====<br />
<br />
yum groupinstall sugar-desktop<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
cd ~<br />
ulimit -c unlimited<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=36910Development Team/Chroot2009-09-07T15:23:18Z<p>Mstone: /* Debian squeeze chroot */</p>
<hr />
<div>=== Status ===<br />
<br />
* Debian chroot construction has been automated: see [http://dev.laptop.org/git/users/mstone/puritan/snapshot/puritan-sugar.tar.bz2 puritan-sugar.tar.bz2] and its [http://dev.laptop.org/git/users/mstone/puritan/tree/README?h=sugar README] -- [[User:Mstone|Michael Stone]] 20:33, 1 August 2009 (UTC)<br />
* Sugar continues to run happily in Squeeze chroots. --[[User:Mstone|Michael Stone]] 16:30, 3 July 2009 (UTC)<br />
* Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
# and to enter the chroot<br />
sudo chroot $CHROOT /bin/bash -l<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
==== Fedora rawhide chroot ====<br />
<br />
We will use <tt>febootstrap</tt> to construct our Fedora chroot. Install it with:<br />
<br />
yum install febootstrap # or<br />
apt-get install febootstrap<br />
<br />
: ''(Note for Debian users -- Fedora 11 and up require versions of <tt>rpm</tt> built with fancy features. I have successfully run these instructions with rpm_4.7.1-4_i386, which, at the time, I built from sources in Debian Experimental.)''<br />
<br />
Then run it like so:<br />
<br />
export CHROOT=`pwd`/f11<br />
sudo febootstrap fedora-11 $CHROOT # sugar-0.84<br />
<br />
or <br />
<br />
export CHROOT=`pwd`/f12<br />
sudo febootstrap fedora-12 $CHROOT # sugar-0.85.5, at the time of writing<br />
<br />
==== Gentoo chroot ====<br />
<br />
Well, if you are familiar with regular Gentoo installation process(by using [http://www.gentoo.org/doc/en/handbook/ Handbook] instead of GUI stuff) you should know how to setup Gentoo chtoot :). Otherwise use these instructions.<br />
<br />
* Firstly, you need Gentoo stage tarball. You can borrow it from any [http://www.gentoo.org/main/en/mirrolrs2.xml mirror] (use releases/<platform>/current sub directory).<br />
<br />
* Lets think you are using stage3-i686-20090623.tar.bz2, then:<br />
<br />
mkdir chroot-gentoo<br />
tar xjpf stage3-i686-20090623.tar.bz2 -C chroot-gentoo<br />
mount -o bind /dev chroot-gentoo/dev<br />
mount -o bind /proc chroot-gentoo/proc<br />
chroot chroot-gentoo /bin/bash<br />
<br />
* To install sugar, use [[Community/Distributions/Gentoo|sugar-overlay]] or setup [[Development_Team/Jhbuild|sugar-jhbuild]] environment(with [[Community/Distributions/Gentoo#Packages|sugar-overlay]] you can install git packages as well).<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar sugar-0.84<br />
<br />
# install your development tools here<br />
<br />
==== f12 chroot ====<br />
<br />
yum groupinstall sugar-desktop<br />
<br />
<br />
==== f11 chroot ====<br />
<br />
yum groupinstall sugar-desktop<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
cd ~<br />
ulimit -c unlimited<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=36909Development Team/Chroot2009-09-07T15:21:22Z<p>Mstone: /* Sugar Installation */</p>
<hr />
<div>=== Status ===<br />
<br />
* Debian chroot construction has been automated: see [http://dev.laptop.org/git/users/mstone/puritan/snapshot/puritan-sugar.tar.bz2 puritan-sugar.tar.bz2] and its [http://dev.laptop.org/git/users/mstone/puritan/tree/README?h=sugar README] -- [[User:Mstone|Michael Stone]] 20:33, 1 August 2009 (UTC)<br />
* Sugar continues to run happily in Squeeze chroots. --[[User:Mstone|Michael Stone]] 16:30, 3 July 2009 (UTC)<br />
* Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
<br />
==== Fedora rawhide chroot ====<br />
<br />
We will use <tt>febootstrap</tt> to construct our Fedora chroot. Install it with:<br />
<br />
yum install febootstrap # or<br />
apt-get install febootstrap<br />
<br />
: ''(Note for Debian users -- Fedora 11 and up require versions of <tt>rpm</tt> built with fancy features. I have successfully run these instructions with rpm_4.7.1-4_i386, which, at the time, I built from sources in Debian Experimental.)''<br />
<br />
Then run it like so:<br />
<br />
export CHROOT=`pwd`/f11<br />
sudo febootstrap fedora-11 $CHROOT # sugar-0.84<br />
<br />
or <br />
<br />
export CHROOT=`pwd`/f12<br />
sudo febootstrap fedora-12 $CHROOT # sugar-0.85.5, at the time of writing<br />
<br />
==== Gentoo chroot ====<br />
<br />
Well, if you are familiar with regular Gentoo installation process(by using [http://www.gentoo.org/doc/en/handbook/ Handbook] instead of GUI stuff) you should know how to setup Gentoo chtoot :). Otherwise use these instructions.<br />
<br />
* Firstly, you need Gentoo stage tarball. You can borrow it from any [http://www.gentoo.org/main/en/mirrolrs2.xml mirror] (use releases/<platform>/current sub directory).<br />
<br />
* Lets think you are using stage3-i686-20090623.tar.bz2, then:<br />
<br />
mkdir chroot-gentoo<br />
tar xjpf stage3-i686-20090623.tar.bz2 -C chroot-gentoo<br />
mount -o bind /dev chroot-gentoo/dev<br />
mount -o bind /proc chroot-gentoo/proc<br />
chroot chroot-gentoo /bin/bash<br />
<br />
* To install sugar, use [[Community/Distributions/Gentoo|sugar-overlay]] or setup [[Development_Team/Jhbuild|sugar-jhbuild]] environment(with [[Community/Distributions/Gentoo#Packages|sugar-overlay]] you can install git packages as well).<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar sugar-0.84<br />
<br />
# install your development tools here<br />
<br />
==== f12 chroot ====<br />
<br />
yum groupinstall sugar-desktop<br />
<br />
<br />
==== f11 chroot ====<br />
<br />
yum groupinstall sugar-desktop<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
cd ~<br />
ulimit -c unlimited<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=36908Development Team/Chroot2009-09-07T15:19:32Z<p>Mstone: /* Fedora rawhide chroot */</p>
<hr />
<div>=== Status ===<br />
<br />
* Debian chroot construction has been automated: see [http://dev.laptop.org/git/users/mstone/puritan/snapshot/puritan-sugar.tar.bz2 puritan-sugar.tar.bz2] and its [http://dev.laptop.org/git/users/mstone/puritan/tree/README?h=sugar README] -- [[User:Mstone|Michael Stone]] 20:33, 1 August 2009 (UTC)<br />
* Sugar continues to run happily in Squeeze chroots. --[[User:Mstone|Michael Stone]] 16:30, 3 July 2009 (UTC)<br />
* Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
<br />
==== Fedora rawhide chroot ====<br />
<br />
We will use <tt>febootstrap</tt> to construct our Fedora chroot. Install it with:<br />
<br />
yum install febootstrap # or<br />
apt-get install febootstrap<br />
<br />
: ''(Note for Debian users -- Fedora 11 and up require versions of <tt>rpm</tt> built with fancy features. I have successfully run these instructions with rpm_4.7.1-4_i386, which, at the time, I built from sources in Debian Experimental.)''<br />
<br />
Then run it like so:<br />
<br />
export CHROOT=`pwd`/f11<br />
sudo febootstrap fedora-11 $CHROOT # sugar-0.84<br />
<br />
or <br />
<br />
export CHROOT=`pwd`/f12<br />
sudo febootstrap fedora-12 $CHROOT # sugar-0.85.5, at the time of writing<br />
<br />
==== Gentoo chroot ====<br />
<br />
Well, if you are familiar with regular Gentoo installation process(by using [http://www.gentoo.org/doc/en/handbook/ Handbook] instead of GUI stuff) you should know how to setup Gentoo chtoot :). Otherwise use these instructions.<br />
<br />
* Firstly, you need Gentoo stage tarball. You can borrow it from any [http://www.gentoo.org/main/en/mirrolrs2.xml mirror] (use releases/<platform>/current sub directory).<br />
<br />
* Lets think you are using stage3-i686-20090623.tar.bz2, then:<br />
<br />
mkdir chroot-gentoo<br />
tar xjpf stage3-i686-20090623.tar.bz2 -C chroot-gentoo<br />
mount -o bind /dev chroot-gentoo/dev<br />
mount -o bind /proc chroot-gentoo/proc<br />
chroot chroot-gentoo /bin/bash<br />
<br />
* To install sugar, use [[Community/Distributions/Gentoo|sugar-overlay]] or setup [[Development_Team/Jhbuild|sugar-jhbuild]] environment(with [[Community/Distributions/Gentoo#Packages|sugar-overlay]] you can install git packages as well).<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
# fix broken hippocanvas (Debian bug#522231)<br />
echo "deb-src http://debian.lcs.mit.edu/debian squeeze main" >> /etc/apt/sources.list<br />
# echo "deb-src http://localhost:9999/debian squeeze main" >> /etc/apt/sources.list<br />
apt-get update<br />
apt-get install apt-src devscripts<br />
apt-src install python-hippocanvas<br />
cd *hippo*<br />
DEB_BUILD_OPTIONS=nostrip debuild -us -uc<br />
cd ..<br />
dpkg -i *hippo*.deb<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
cd ~<br />
ulimit -c unlimited<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=36907Development Team/Chroot2009-09-07T15:17:57Z<p>Mstone: /* Fedora rawhide chroot */</p>
<hr />
<div>=== Status ===<br />
<br />
* Debian chroot construction has been automated: see [http://dev.laptop.org/git/users/mstone/puritan/snapshot/puritan-sugar.tar.bz2 puritan-sugar.tar.bz2] and its [http://dev.laptop.org/git/users/mstone/puritan/tree/README?h=sugar README] -- [[User:Mstone|Michael Stone]] 20:33, 1 August 2009 (UTC)<br />
* Sugar continues to run happily in Squeeze chroots. --[[User:Mstone|Michael Stone]] 16:30, 3 July 2009 (UTC)<br />
* Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
<br />
==== Fedora rawhide chroot ====<br />
<br />
We will use <tt>febootstrap</tt> to construct our Fedora chroot. Install it with:<br />
<br />
yum install febootstrap # or<br />
apt-get install febootstrap<br />
<br />
: ''(Note for Debian users -- Fedora 11 and up require versions of <tt>rpm</tt> built with fancy features. I have successfully run these instructions with rpm_4.7.1-4_i386, which, at the time, I built from sources in Debian Experimental.)''<br />
<br />
Then run it like so:<br />
<br />
sudo febootstrap fedora-11 ./f11 -- sugar-0.84<br />
sudo febootstrap fedora-12 ./f12 -- sugar-0.85.5, at the time of writing<br />
<br />
==== Gentoo chroot ====<br />
<br />
Well, if you are familiar with regular Gentoo installation process(by using [http://www.gentoo.org/doc/en/handbook/ Handbook] instead of GUI stuff) you should know how to setup Gentoo chtoot :). Otherwise use these instructions.<br />
<br />
* Firstly, you need Gentoo stage tarball. You can borrow it from any [http://www.gentoo.org/main/en/mirrolrs2.xml mirror] (use releases/<platform>/current sub directory).<br />
<br />
* Lets think you are using stage3-i686-20090623.tar.bz2, then:<br />
<br />
mkdir chroot-gentoo<br />
tar xjpf stage3-i686-20090623.tar.bz2 -C chroot-gentoo<br />
mount -o bind /dev chroot-gentoo/dev<br />
mount -o bind /proc chroot-gentoo/proc<br />
chroot chroot-gentoo /bin/bash<br />
<br />
* To install sugar, use [[Community/Distributions/Gentoo|sugar-overlay]] or setup [[Development_Team/Jhbuild|sugar-jhbuild]] environment(with [[Community/Distributions/Gentoo#Packages|sugar-overlay]] you can install git packages as well).<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
# fix broken hippocanvas (Debian bug#522231)<br />
echo "deb-src http://debian.lcs.mit.edu/debian squeeze main" >> /etc/apt/sources.list<br />
# echo "deb-src http://localhost:9999/debian squeeze main" >> /etc/apt/sources.list<br />
apt-get update<br />
apt-get install apt-src devscripts<br />
apt-src install python-hippocanvas<br />
cd *hippo*<br />
DEB_BUILD_OPTIONS=nostrip debuild -us -uc<br />
cd ..<br />
dpkg -i *hippo*.deb<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
cd ~<br />
ulimit -c unlimited<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=34470Development Team/Chroot2009-08-01T20:33:44Z<p>Mstone: </p>
<hr />
<div>=== Status ===<br />
<br />
* Debian chroot construction has been automated: see [http://dev.laptop.org/git/users/mstone/puritan/snapshot/puritan-sugar.tar.bz2 puritan-sugar.tar.bz2] and its [http://dev.laptop.org/git/users/mstone/puritan/tree/README?h=sugar README] -- [[User:Mstone|Michael Stone]] 20:33, 1 August 2009 (UTC)<br />
* Sugar continues to run happily in Squeeze chroots. --[[User:Mstone|Michael Stone]] 16:30, 3 July 2009 (UTC)<br />
* Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --install yum<br />
mock -r fedora-devel-i386 --shell<br />
<br />
==== Gentoo chroot ====<br />
<br />
Well, if you are familiar with regular Gentoo installation process(by using [http://www.gentoo.org/doc/en/handbook/ Handbook] instead of GUI stuff) you should know how to setup Gentoo chtoot :). Otherwise use these instructions.<br />
<br />
* Firstly, you need Gentoo stage tarball. You can borrow it from any [http://www.gentoo.org/main/en/mirrolrs2.xml mirror] (use releases/<platform>/current sub directory).<br />
<br />
* Lets think you are using stage3-i686-20090623.tar.bz2, then:<br />
<br />
mkdir chroot-gentoo<br />
tar xjpf stage3-i686-20090623.tar.bz2 -C chroot-gentoo<br />
mount -o bind /dev chroot-gentoo/dev<br />
mount -o bind /proc chroot-gentoo/proc<br />
chroot chroot-gentoo /bin/bash<br />
<br />
* To install sugar, use [[Community/Distributions/Gentoo|sugar-overlay]] or setup [[Development_Team/Jhbuild|sugar-jhbuild]] environment(with [[Community/Distributions/Gentoo#Packages|sugar-overlay]] you can install git packages as well).<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
# fix broken hippocanvas (Debian bug#522231)<br />
echo "deb-src http://debian.lcs.mit.edu/debian squeeze main" >> /etc/apt/sources.list<br />
# echo "deb-src http://localhost:9999/debian squeeze main" >> /etc/apt/sources.list<br />
apt-get update<br />
apt-get install apt-src devscripts<br />
apt-src install python-hippocanvas<br />
cd *hippo*<br />
DEB_BUILD_OPTIONS=nostrip debuild -us -uc<br />
cd ..<br />
dpkg -i *hippo*.deb<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
cd ~<br />
ulimit -c unlimited<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=34469Development Team/Chroot2009-08-01T20:33:26Z<p>Mstone: </p>
<hr />
<div>=== Status ===<br />
<br />
* Debian chroot construction has been automated: see [http://dev.laptop.org/git/users/mstone/puritan/snapshot/puritan-sugar.tar.bz2|puritan-sugar.tar.bz2] and its [http://dev.laptop.org/git/users/mstone/puritan/tree/README?h=sugar README] -- [[User:Mstone|Michael Stone]] 20:33, 1 August 2009 (UTC)<br />
* Sugar continues to run happily in Squeeze chroots. --[[User:Mstone|Michael Stone]] 16:30, 3 July 2009 (UTC)<br />
* Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --install yum<br />
mock -r fedora-devel-i386 --shell<br />
<br />
==== Gentoo chroot ====<br />
<br />
Well, if you are familiar with regular Gentoo installation process(by using [http://www.gentoo.org/doc/en/handbook/ Handbook] instead of GUI stuff) you should know how to setup Gentoo chtoot :). Otherwise use these instructions.<br />
<br />
* Firstly, you need Gentoo stage tarball. You can borrow it from any [http://www.gentoo.org/main/en/mirrolrs2.xml mirror] (use releases/<platform>/current sub directory).<br />
<br />
* Lets think you are using stage3-i686-20090623.tar.bz2, then:<br />
<br />
mkdir chroot-gentoo<br />
tar xjpf stage3-i686-20090623.tar.bz2 -C chroot-gentoo<br />
mount -o bind /dev chroot-gentoo/dev<br />
mount -o bind /proc chroot-gentoo/proc<br />
chroot chroot-gentoo /bin/bash<br />
<br />
* To install sugar, use [[Community/Distributions/Gentoo|sugar-overlay]] or setup [[Development_Team/Jhbuild|sugar-jhbuild]] environment(with [[Community/Distributions/Gentoo#Packages|sugar-overlay]] you can install git packages as well).<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
# fix broken hippocanvas (Debian bug#522231)<br />
echo "deb-src http://debian.lcs.mit.edu/debian squeeze main" >> /etc/apt/sources.list<br />
# echo "deb-src http://localhost:9999/debian squeeze main" >> /etc/apt/sources.list<br />
apt-get update<br />
apt-get install apt-src devscripts<br />
apt-src install python-hippocanvas<br />
cd *hippo*<br />
DEB_BUILD_OPTIONS=nostrip debuild -us -uc<br />
cd ..<br />
dpkg -i *hippo*.deb<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
cd ~<br />
ulimit -c unlimited<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=34454Development Team/Chroot2009-08-01T18:30:03Z<p>Mstone: </p>
<hr />
<div>=== Status ===<br />
<br />
* Sugar continues to run happily in Squeeze chroots. --[[User:Mstone|Michael Stone]] 16:30, 3 July 2009 (UTC)<br />
* Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --install yum<br />
mock -r fedora-devel-i386 --shell<br />
<br />
==== Gentoo chroot ====<br />
<br />
Well, if you are familiar with regular Gentoo installation process(by using [http://www.gentoo.org/doc/en/handbook/ Handbook] instead of GUI stuff) you should know how to setup Gentoo chtoot :). Otherwise use these instructions.<br />
<br />
* Firstly, you need Gentoo stage tarball. You can borrow it from any [http://www.gentoo.org/main/en/mirrolrs2.xml mirror] (use releases/<platform>/current sub directory).<br />
<br />
* Lets think you are using stage3-i686-20090623.tar.bz2, then:<br />
<br />
mkdir chroot-gentoo<br />
tar xjpf stage3-i686-20090623.tar.bz2 -C chroot-gentoo<br />
mount -o bind /dev chroot-gentoo/dev<br />
mount -o bind /proc chroot-gentoo/proc<br />
chroot chroot-gentoo /bin/bash<br />
<br />
* To install sugar, use [[Community/Distributions/Gentoo|sugar-overlay]] or setup [[Development_Team/Jhbuild|sugar-jhbuild]] environment(with [[Community/Distributions/Gentoo#Packages|sugar-overlay]] you can install git packages as well).<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
# fix broken hippocanvas (Debian bug#522231)<br />
echo "deb-src http://debian.lcs.mit.edu/debian squeeze main" >> /etc/apt/sources.list<br />
# echo "deb-src http://localhost:9999/debian squeeze main" >> /etc/apt/sources.list<br />
apt-get update<br />
apt-get install apt-src devscripts<br />
apt-src install python-hippocanvas<br />
cd *hippo*<br />
DEB_BUILD_OPTIONS=nostrip debuild -us -uc<br />
cd ..<br />
dpkg -i *hippo*.deb<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
cd ~<br />
ulimit -c unlimited<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=31845Development Team/Chroot2009-07-03T16:30:34Z<p>Mstone: </p>
<hr />
<div>=== Status ===<br />
<br />
* Sugar continues to run happily in Squeeze chroots. --[[User:Mstone|Michael Stone]] 16:30, 3 July 2009 (UTC)<br />
* Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --install yum<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
# fix broken hippocanvas<br />
echo "deb-src http://debian.lcs.mit.edu/debian squeeze main" >> /etc/apt/sources.list<br />
# echo "deb-src http://localhost:9999/debian squeeze main" >> /etc/apt/sources.list<br />
apt-get update<br />
apt-get install apt-src devscripts<br />
apt-src install python-hippocanvas<br />
cd *hippo*<br />
DEB_BUILD_OPTIONS=nostrip debuild -us -uc<br />
cd ..<br />
dpkg -i *hippo*.deb<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=31619Development Team/Chroot2009-07-03T00:14:40Z<p>Mstone: /* squeeze chroot */</p>
<hr />
<div>Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --install yum<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
# fix broken hippocanvas<br />
echo "deb-src http://debian.lcs.mit.edu/debian squeeze main" >> /etc/apt/sources.list<br />
# echo "deb-src http://localhost:9999/debian squeeze main" >> /etc/apt/sources.list<br />
apt-get update<br />
apt-get install apt-src devscripts<br />
apt-src install python-hippocanvas<br />
cd *hippo*<br />
DEB_BUILD_OPTIONS=nostrip debuild -us -uc<br />
cd ..<br />
dpkg -i *hippo*.deb<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=31618Development Team/Chroot2009-07-02T23:19:46Z<p>Mstone: </p>
<hr />
<div>Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
''Note'': you can use approx to cache packages across multiple runs for faster testing:<br />
<br />
apt-get install approx<br />
echo 'debian http://debian.lcs.mit.edu/debian' >> /etc/approx/approx.conf<br />
/etc/init.d/approx restart<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://localhost:9999/debian<br />
<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --install yum<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
# fix broken hippocanvas<br />
echo "deb-src http://debian.lcs.mit.edu/debian squeeze main" >> /etc/apt/sources.list<br />
apt-get update<br />
apt-get install apt-src devscripts<br />
apt-src install python-hippocanvas<br />
cd *hippo*<br />
DEB_BUILD_OPTIONS=nostrip debuild -us -uc<br />
cd ..<br />
dpkg -i *hippo*.deb<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29674Development Team/Chroot2009-05-23T22:21:07Z<p>Mstone: </p>
<hr />
<div>Sugar is now somewhat runnable from chroots. Jaunty and Squeeze have been tested recently; Fedora has not. --[[User:Mstone|Michael Stone]] 22:21, 23 May 2009 (UTC)<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --install yum<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
# fix broken hippocanvas<br />
echo "deb-src http://debian.lcs.mit.edu/debian squeeze main" >> /etc/apt/sources.list<br />
apt-get update<br />
apt-get install apt-src devscripts<br />
apt-src install python-hippocanvas<br />
cd *hippo*<br />
DEB_BUILD_OPTIONS=nostrip debuild -us -uc<br />
cd ..<br />
dpkg -i *hippo*.deb<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29673Development Team/Chroot2009-05-23T22:10:04Z<p>Mstone: </p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian squeeze chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 squeeze $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t tmpfs tmpfs $CHROOT/tmp<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --install yum<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== squeeze chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
# edit /etc/hosts<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
# fix broken hippocanvas<br />
echo "deb-src http://debian.lcs.mit.edu/debian squeeze main" >> /etc/apt/sources.list<br />
apt-get update<br />
apt-get install apt-src devscripts<br />
apt-src install python-hippocanvas<br />
cd *hippo*<br />
DEB_BUILD_OPTIONS=nostrip debuild -us -uc<br />
cd ..<br />
dpkg -i *hippo*.deb<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24 # 1024x768x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=localhost:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
sudo killall -u sugar<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
umount $CHROOT/tmp<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29667Development Team/Chroot2009-05-23T17:05:34Z<p>Mstone: /* sid chroot */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --install yum<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== sid chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
dpkg-reconfigure locales<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29666Development Team/Chroot2009-05-23T16:47:16Z<p>Mstone: /* Fedora rawhide chroot */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --install yum<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== sid chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29665Development Team/Chroot2009-05-23T16:45:29Z<p>Mstone: /* Sugar Installation */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
==== sid chroot ====<br />
<br />
apt-get update<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
<br />
apt-get install education-desktop-sugar<br />
<br />
# install your development tools here<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29664Development Team/Chroot2009-05-23T16:32:43Z<p>Mstone: </p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!<br />
<br />
=== Cleaning Up ===<br />
<br />
To correctly delete a chroot that you no longer need, kill all processes running in the chroot, and<br />
<br />
export CHROOT=/path/to/my/chroot # important!<br />
umount $CHROOT/var/run/dbus<br />
umount $CHROOT/proc<br />
umount $CHROOT/dev/pts<br />
rm -rf $CHROOT</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29663Development Team/Chroot2009-05-23T16:28:27Z<p>Mstone: /* jaunty chroot */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29662Development Team/Chroot2009-05-23T16:27:50Z<p>Mstone: /* jaunty chroot */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
<br />
apt-get install locales<br />
locale-gen "$LANG"<br />
dpkg-reconfigure tzdata<br />
<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29661Development Team/Chroot2009-05-23T16:20:44Z<p>Mstone: /* Running Sugar */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
Then pull up the frame, switch to the home view, and launch some activities!</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29660Development Team/Chroot2009-05-23T16:20:00Z<p>Mstone: /* X11 */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 -screen 800x600x24<br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29659Development Team/Chroot2009-05-23T16:18:21Z<p>Mstone: /* jaunty chroot */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
<br />
# install your development tools here<br />
<br />
# patch (hopefully temporary) bugs<br />
sed -ie '114i\\ if not favorites_settings.layout: favorites_settings.layout = favoriteslayout.RingLayout.key' /usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 <br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29658Development Team/Chroot2009-05-23T16:10:40Z<p>Mstone: </p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
# install your development tools here<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 <br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29657Development Team/Chroot2009-05-23T16:10:13Z<p>Mstone: /* D-Bus */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
# install your development tools here<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 <br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29656Development Team/Chroot2009-05-23T16:09:51Z<p>Mstone: /* User Accounts */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
# install your development tools here<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 <br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29655Development Team/Chroot2009-05-23T16:06:32Z<p>Mstone: </p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
# install your development tools here<br />
<br />
=== User Accounts ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 <br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== Running Sugar ===<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
sudo chroot $CHROOT /bin/bash -l<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29654Development Team/Chroot2009-05-23T16:04:43Z<p>Mstone: /* User Account */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
# install your development tools here<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 <br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== User Account ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, ''as root'', run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29653Development Team/Chroot2009-05-23T16:04:17Z<p>Mstone: /* D-Bus */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
# install your development tools here<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 <br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, ''outside the chroot'', we need to<br />
<br />
sudo mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== User Account ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Talk:Development_Team/Chroot&diff=29652Talk:Development Team/Chroot2009-05-23T16:03:00Z<p>Mstone: </p>
<hr />
<div>== Restricting Xephyr connections ==<br />
Most X11 servers are configured to disable TCP connections. This means that in order to get a working X connection we can:<br />
<br />
# bind-mount the X unix socket into the chroot.<br />
# ssh ''into'' the chroot with X11-forwarding enabled.<br />
# Enable TCP on an X server, e.g. a nested Xephyr.<br />
<br />
In the main walk-through, we chose to use an open Xephyr like so:<br />
<br />
Xephyr -ac :1<br />
<br />
However, we might instead try:<br />
<br />
# ''outside chroot''<br />
DISP=:1 # adjust to suit your configuration<br />
COOKIE=$(mcookie)<br />
AUTH=$(mktemp)<br />
echo "add $DISP . $COOKIE" | xauth -f "$AUTH"<br />
echo "add these commands to clients:"<br />
echo "export DISPLAY=\"localhost$DISP\""<br />
echo "export XAUTHORITY=\"$AUTH\""<br />
Xephyr -auth "$AUTH" -reset -terminate "$DISP" && rm "$AUTH"<br />
<br />
And, ''inside'' the chroot, set the <tt>DISPLAY</tt> and <tt>XAUTHORITY</tt> variables as directed by the setup script and copy the <tt>"$AUTH"</tt> file from outside the chroot into the chroot to the path assigned to <tt>"$XAUTHORITY"</tt>.<br />
<br />
== as_person script, when PAM is misconfigured ==<br />
cat > as_person <<EOF<br />
#!/usr/bin/env python<br />
from os import environ, chdir, setgroups, setgid, setuid, execve<br />
from sys import argv<br />
from pwd import getpwnam<br />
user = getpwnam(argv[1])<br />
environ['HOME'] = user.pw_dir<br />
environ['USER'] = user.pw_name<br />
chdir(user.pw_dir)<br />
setgroups([user.pw_gid])<br />
setgid(user.pw_gid)<br />
setuid(user.pw_uid)<br />
execve(argv[2], argv[2:], environ)<br />
EOF<br />
chmod a+x as_person<br />
./as_person sugar /usr/bin/sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29651Development Team/Chroot2009-05-23T16:02:03Z<p>Mstone: /* X11 */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
# install your development tools here<br />
<br />
=== X11 ===<br />
<br />
We need to point Sugar at an X server. One easy (but insecure) way to do this is to make a nested X server like so, ''outside the chroot'':<br />
<br />
Xephyr -ac :1 <br />
<br />
See the talk page for more secure alternatives.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, we need to bind-mount<br />
<br />
mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== User Account ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29650Development Team/Chroot2009-05-23T15:59:17Z<p>Mstone: /* jaunty chroot */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
apt-get update<br />
apt-get install sugar sugar-activities<br />
# install your development tools here<br />
<br />
=== X11 ===<br />
<br />
Most X11 servers are configured to disable TCP connections. This means that in order to get a working X connection we can:<br />
<br />
# bind-mount the X unix socket into the chroot.<br />
# ssh ''into'' the chroot with X11-forwarding enabled.<br />
# Enable TCP on an X server, e.g. a nested Xephyr.<br />
<br />
We're going to try option (3) first:<br />
<br />
Xephyr -ac :1 <br />
<br />
And, ''inside'' the chroot, set the <tt>DISPLAY</tt> to <tt>localhost:1</tt>.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, we need to bind-mount<br />
<br />
mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== User Account ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29649Development Team/Chroot2009-05-23T15:56:06Z<p>Mstone: </p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== Sugar Installation ===<br />
<br />
==== jaunty chroot ====<br />
<br />
sed -ie "s/main/main universe/" /etc/apt/sources.list<br />
<br />
=== X11 ===<br />
<br />
Most X11 servers are configured to disable TCP connections. This means that in order to get a working X connection we can:<br />
<br />
# bind-mount the X unix socket into the chroot.<br />
# ssh ''into'' the chroot with X11-forwarding enabled.<br />
# Enable TCP on an X server, e.g. a nested Xephyr.<br />
<br />
We're going to try option (3) first:<br />
<br />
Xephyr -ac :1 <br />
<br />
And, ''inside'' the chroot, set the <tt>DISPLAY</tt> to <tt>localhost:1</tt>.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, we need to bind-mount<br />
<br />
mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== User Account ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29648Development Team/Chroot2009-05-23T15:55:02Z<p>Mstone: </p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
Here are some ideas to help you get started:<br />
<br />
==== Ubuntu jaunty chroot ====<br />
With ''recent'' versions of debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/jaunty-root<br />
sudo debootstrap --arch i386 jaunty $CHROOT http://ubuntu.media.mit.edu/ubuntu/<br />
sudo chroot $CHROOT /bin/bash -l<br />
mount -t proc proc /proc<br />
mount -t devpts devpts /dev/pts<br />
<br />
==== Debian sid chroot ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== Fedora rawhide chroot ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== X11 ===<br />
<br />
Most X11 servers are configured to disable TCP connections. This means that in order to get a working X connection we can:<br />
<br />
# bind-mount the X unix socket into the chroot.<br />
# ssh ''into'' the chroot with X11-forwarding enabled.<br />
# Enable TCP on an X server, e.g. a nested Xephyr.<br />
<br />
We're going to try option (3) first:<br />
<br />
Xephyr -ac :1 <br />
<br />
And, ''inside'' the chroot, set the <tt>DISPLAY</tt> to <tt>localhost:1</tt>.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, we need to bind-mount<br />
<br />
mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== User Account ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29647Development Team/Chroot2009-05-23T15:51:51Z<p>Mstone: </p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
==== debootstrap ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== mock ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== X11 ===<br />
<br />
Most X11 servers are configured to disable TCP connections. This means that in order to get a working X connection we can:<br />
<br />
# bind-mount the X unix socket into the chroot.<br />
# ssh ''into'' the chroot with X11-forwarding enabled.<br />
# Enable TCP on an X server, e.g. a nested Xephyr.<br />
<br />
We're going to try option (3) first:<br />
<br />
Xephyr -ac :1 <br />
<br />
And, ''inside'' the chroot, set the <tt>DISPLAY</tt> to <tt>localhost:1</tt>.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, we need to bind-mount<br />
<br />
mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== User Account ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29646Development Team/Chroot2009-05-23T15:51:18Z<p>Mstone: /* D-Bus */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
==== debootstrap ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== mock ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== X11 ===<br />
<br />
Most X11 servers are configured to disable TCP connections. This means that in order to get a working X connection we can:<br />
<br />
# bind-mount the X unix socket into the chroot.<br />
# ssh ''into'' the chroot with X11-forwarding enabled.<br />
# Enable TCP on an X server, e.g. a nested Xephyr.<br />
<br />
We're going to try option (3) first:<br />
<br />
Xephyr -ac :1 <br />
<br />
And, ''inside'' the chroot, set the <tt>DISPLAY</tt> to <tt>localhost:1</tt>.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, we need to bind-mount<br />
<br />
mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
=== User Account ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
== Jhbuild ==<br />
<br />
After, you can also build sugar inside your chroot without compromising your ''main'' system.<br />
<br />
*[[Development Team/Jhbuild]]</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Talk:Development_Team/Chroot&diff=29645Talk:Development Team/Chroot2009-05-23T15:50:48Z<p>Mstone: </p>
<hr />
<div>== Restricting Xephyr connections ==<br />
# ''outside chroot''<br />
DISP=:1 # adjust to suit your configuration<br />
COOKIE=$(mcookie)<br />
AUTH=$(mktemp)<br />
echo "add $DISP . $COOKIE" | xauth -f "$AUTH"<br />
echo "add these commands to clients:"<br />
echo "export DISPLAY=\"localhost$DISP\""<br />
echo "export XAUTHORITY=\"$AUTH\""<br />
Xephyr -auth "$AUTH" -reset -terminate "$DISP" && rm "$AUTH"<br />
<br />
And, ''inside'' the chroot, set the <tt>DISPLAY</tt> and <tt>XAUTHORITY</tt> variables as directed by the setup script and copy the <tt>"$AUTH"</tt> file from outside the chroot into the chroot to the path assigned to <tt>"$XAUTHORITY"</tt>.<br />
<br />
== as_person script, when PAM is misconfigured ==<br />
cat > as_person <<EOF<br />
#!/usr/bin/env python<br />
from os import environ, chdir, setgroups, setgid, setuid, execve<br />
from sys import argv<br />
from pwd import getpwnam<br />
user = getpwnam(argv[1])<br />
environ['HOME'] = user.pw_dir<br />
environ['USER'] = user.pw_name<br />
chdir(user.pw_dir)<br />
setgroups([user.pw_gid])<br />
setgid(user.pw_gid)<br />
setuid(user.pw_uid)<br />
execve(argv[2], argv[2:], environ)<br />
EOF<br />
chmod a+x as_person<br />
./as_person sugar /usr/bin/sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Talk:Development_Team/Chroot&diff=29644Talk:Development Team/Chroot2009-05-23T15:50:22Z<p>Mstone: </p>
<hr />
<div>== Restricting Xephyr connections ==<br />
# ''outside chroot''<br />
DISP=:1 # adjust to suit your configuration<br />
COOKIE=$(mcookie)<br />
AUTH=$(mktemp)<br />
echo "add $DISP . $COOKIE" | xauth -f "$AUTH"<br />
echo "add these commands to clients:"<br />
echo "export DISPLAY=\"localhost$DISP\""<br />
echo "export XAUTHORITY=\"$AUTH\""<br />
Xephyr -auth "$AUTH" -reset -terminate "$DISP" && rm "$AUTH"<br />
<br />
And, ''inside'' the chroot, set the <tt>DISPLAY</tt> and <tt>XAUTHORITY</tt> variables as directed by the setup script and copy the <tt>"$AUTH"</tt> file from outside the chroot into the chroot to the path assigned to <tt>"$XAUTHORITY"</tt>.<br />
<br />
== as_person script, when PAM is misconfigured ==<br />
cat > as_person <<EOF<br />
#!/usr/bin/env python<br />
from os import environ, chdir, setgroups, setgid, setuid, execve<br />
from sys import argv<br />
from pwd import getpwnam<br />
user = getpwnam(argv[1])<br />
environ['HOME'] = user.pw_dir<br />
environ['USER'] = user.pw_name<br />
chdir(user.pw_dir)<br />
setgroups([user.pw_gid])<br />
setgid(user.pw_gid)<br />
setuid(user.pw_uid)<br />
execve(argv[2], argv[2:], environ)<br />
EOF<br />
chmod a+x as_person<br />
./as_person sugar /usr/bin/sugar</div>Mstonehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Chroot&diff=29643Development Team/Chroot2009-05-23T15:49:09Z<p>Mstone: /* User Account */</p>
<hr />
<div>Sugar ought to be easy to run from chroots. For a variety of silly reasons, this isn't yet the case, but it might be soon. Ping [[User:Mstone|Michael]] with questions.<br />
<br />
=== Chroot Construction ===<br />
<br />
There are lots of ways to create appropriate chroots; e.g. by hand, with debootstrap, with mock, etc.<br />
<br />
==== debootstrap ====<br />
With debootstrap, in order to get a working chroot, you want something like: <br />
<br />
export CHROOT=`pwd`/sid-root<br />
sudo debootstrap --arch i386 sid $CHROOT http://debian.lcs.mit.edu/debian<br />
sudo chroot $CHROOT /bin/bash -l<br />
# and some of the following:<br />
mount -t proc proc $CHROOT/proc<br />
mount -t devpts devpts $CHROOT/dev/pts<br />
mount -t selinuxfs selinux $CHROOT/selinux<br />
<br />
''Reference: http://www.debian.org/doc/manuals/reference/ch-tips.en.html ''<br />
<br />
==== mock ====<br />
With mock, it would be more like:<br />
<br />
mock -r fedora-devel-i386 --init<br />
mock -r fedora-devel-i386 --shell<br />
<br />
=== X11 ===<br />
<br />
Most X11 servers are configured to disable TCP connections. This means that in order to get a working X connection we can:<br />
<br />
# bind-mount the X unix socket into the chroot.<br />
# ssh ''into'' the chroot with X11-forwarding enabled.<br />
# Enable TCP on an X server, e.g. a nested Xephyr.<br />
<br />
We're going to try option (3) first:<br />
<br />
Xephyr -ac :1 <br />
<br />
And, ''inside'' the chroot, set the <tt>DISPLAY</tt> to <tt>localhost:1</tt>.<br />
<br />
=== D-Bus ===<br />
<br />
Sugar wants to be able to use global state stored in both HAL and NetworkManager, both of which live on the system bus. Consequently, we need to bind-mount<br />
<br />
mount --bind /var/run/dbus $CHROOT/var/run/dbus<br />
<br />
before entering the chroot. (Mock uses unshare() to enter a new mount-point namespace since this makes garbage collection of mountpoints much easier.)<br />
<br />
It also wants to have a session bus so, ''inside'' the chroot, as user <tt>sugar</tt>:<br />
<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
<br />
=== User Account ===<br />
<br />
For stupid reasons, it's necessary that Sugar run under a uid inside the chroot which exists as a real account outside the chroot. (Talk to the DBus people.)<br />
<br />
Consequently, run something like this ''both'' inside and outside the chroot:<br />
<br />
groupadd -g 64002 sugar<br />
useradd -m -u 64002 -g sugar -s /bin/bash sugar<br />
<br />
Then, inside the chroot, you can happily run sugar as user 'sugar' with something like<br />
<br />
su sugar -<br />
export DISPLAY=:1<br />
export DBUS_SESSION_BUS_ADDRESS=$(dbus-daemon --session --print-address --fork)<br />
sugar<br />
<br />
== Jhbuild ==<br />
<br />
After, you can also build sugar inside your chroot without compromising your ''main'' system.<br />
<br />
*[[Development Team/Jhbuild]]</div>Mstone