I think for the case of Cambodia with many small deployments
(educational NGOs got XOs donated from G1G1/OLPC or other donors), no
signed builds probably means that the XOs don't get updated anymore.
Are you trying to say that the Cambodian OLPC recipients don't have
any serious chance of
On Wed, Dec 2, 2009 at 8:49 AM, Philipp Kocher philipp.koc...@gmx.net wrote:
What is the plan for the Fedora 11 build for XO-1, will OLPC sign such a
build or is 802 the last build signed by OLPC?
I think the F11 images will follow the policy I outlined: no more signed builds.
I don't think
Philipp -
I would prefer not to speculate about what is happening or not happening in
various locations; if small XO situations want updates they can obtain
developer keys for them. I'm not aware of any requests from Cambodia for
software updates they don't have, or for signed builds. It's
- It won't be signed by OLPC. You have to be on an unlocked XO, or be
a deployment signing your own builds.
Is there a reason why 8.2.2 doesn't get signed by OLPC?
I do understand that the main target group are big deployments which can
sign the build, but why are others excluded?
In the
On Tue, Dec 1, 2009 at 10:14 AM, Philipp Kocher philipp.koc...@gmx.net wrote:
- It won't be signed by OLPC. You have to be on an unlocked XO, or be
a deployment signing your own builds.
Is there a reason why 8.2.2 doesn't get signed by OLPC?
I do understand that the main target group are big
Philipp -
An OS image signed by OLPC can be booted by any XO-1.0 laptop in the world,
except for those which have been reconfigured by a deployment to only respect
software signed by other security keys. That implies a higher level of testing
and certification than an image that can be
Hi Ed, Martin
What is the plan for the Fedora 11 build for XO-1, will OLPC sign such a
build or is 802 the last build signed by OLPC?
I don't think one of the two options is a good solution for small
deployments without a tech team.
I think for the case of Cambodia with many small deployments
On 30.11.2009, at 12:30, Martin Langhoff wrote:
On Mon, Nov 30, 2009 at 12:11 PM, Bert Freudenberg b...@freudenbergs.de
wrote:
What's the 8.2.2 schedule? What is changing?
Very succintly:
- It won't be signed by OLPC. You have to be on an unlocked XO, or be
a deployment signing your
On Mon, Nov 30, 2009 at 12:43 PM, Bert Freudenberg b...@freudenbergs.de wrote:
So a deployment could customize the image-builder script to include a newer
RPM, e.g. if they wanted a more recent version of Etoys.
Bingo. It actually supports an rpms dir. Drop something there and go.
And I am
On Mon, Nov 30, 2009 at 1:32 PM, Martin Langhoff
martin.langh...@gmail.comwrote:
On Mon, Nov 30, 2009 at 12:43 PM, Bert Freudenberg b...@freudenbergs.de
wrote:
So a deployment could customize the image-builder script to include a
newer RPM, e.g. if they wanted a more recent version of Etoys.
10 matches
Mail list logo