1,764
edits
Changes
Jump to navigation
Jump to search
Line 33:
Line 33: − + Line 45:
Line 45: − + − I'm currently publishing selected builds in [http://oficina.paraguayeduca.org/~bernie/f11-xo1-py/ my public html folder].+ − − − ([http://wiki.laptop.org/go/Antitheft_HowTo OATS]). Signing does − − − − * TODO: We don't have a place for publishing official images yet − − * TODO: We don't have a procedure for releasing builds to field technicians (we may use repo.paraguayeduca.org in the future) − − * TODO: We don't keep release notes for our builds (we should probably use the wiki) − + − + + + Line 97:
Line 88: − + − +
no edit summary
== Signing ==
== Signing ==
* Put the 4 signing keys somewhere in your home:
* Put the 3 signing keys somewhere:
bernie@robbie:~$ ll src/olpc/keys/
bernie@robbie:~$ ll src/olpc/keys/
* Make sure the keys are '''NOT''' world-readable
* Make sure the keys are '''NOT''' world-readable
* Edit the paths in the <tt>[signing]</tt> section of <tt>examples/f11-xo1-py.ini</tt>
* Edit the paths in the <tt>[signing]</tt> section of your ini file (e.g. <tt>examples/f11-0.88-xo1-py.ini</tt>
== Publishing the images ==
== Publishing the images ==
Signed builds should be published only if they correctly implement the [http://wiki.laptop.org/go/Antitheft_HowTo OLPC anti-theft system]). Signing does not have anything to do with quality or endorsement (i.e. signed builds are not necessarily bug-free or supported).
Signed builds should be published only if they implement the OLPC anti-theft system
not have anything to do with quality or endorsement (i.e. signed builds are not
necessarily bug-free).
== Customizing the build ==
== Customizing the build ==
The topic of is too vast to discuss in detail here. Start by reading http://git.paraguayeduca.org/gitweb/users/bernie/olpc-os-builder.git/blob_plain/HEAD:/doc/README README] in the olpc-os-builder tree. Then, as needed, read the various <tt>README</tt>
The topic of is too vast to discuss in detail here. Start by reading
files contained in the [http://git.paraguayeduca.org/gitweb/users/bernie/olpc-os-builder.git/tree/HEAD:/modules modules] directory.
[http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/doc/README README]
in the olpc-os-builder tree. Then, as needed, read the various <tt>README</tt> files contained in the
[http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/modules modules] directory.
Being a Build Master involves knowledge of many workflows, including:
Being a Build Master involves knowledge of many workflows, including:
git log olpc/master
git log olpc/master
== Building custom kernels ==
== Building custom OLPC kernels ==
$ git clone git://git.paraguayeduca.org/users/bernie/olpc-2.6
$ git clone http://dev.laptop.org/git/olpc-2.6/
$ cd olpc-2.6
$ cd olpc-2.6
$ setarch i386 make ARCH=i386 xo_1-kernel-rpm
$ setarch i386 make ARCH=i386 xo_1-kernel-rpm