Re: an anecdote from Bhagmalpur

[Rogelio Mita]

=)

2013/6/20 Sameer Verma 

> An interesting anecdote from Bhagmalpur, India
> (http://bhagmalpur.wordpress.com)
>
> We just turned on the Internet two weeks ago (thx to Anish Mangal and
> Kartik Perisetla), but power has been largely missing. The server and
> Wi-Fi paraphernalia lives at my uncle's house. The kids miss the
> access a lot. So, eventually they pooled money, bought a liter of
> Diesel and showed up at my Uncle's house, asking him to run the
> generator, so that they could get on the Internet!
>
> What have we done! :-)
>
> cheers,
> Sameer
> --
> Sameer Verma, Ph.D.
> Professor, Information Systems
> San Francisco State University
> http://verma.sfsu.edu/
> http://commons.sfsu.edu/
> http://olpcsf.org/
> http://olpcjamaica.org.jm/
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>



-- 
Roger

Activity Central 
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: trouble making actrd with dracut

[Rogelio Mita]

openssl-dev???

2013/3/1 Esteban Bordón 

> I'm having a problem trying to import httplib:
>
> ImportError: No module named hashlib
>
>
>
> 2013/2/26 Daniel Drake 
>
>> On Tue, Feb 26, 2013 at 11:41 AM, Esteban Bordón
>>  wrote:
>> > Hi all,
>> >
>> > I'm trying to make a new actrd in XO 1.75-F18 and I'm having some
>> errors:
>> >
>> > bash-4.2# dracut --force --conf /etc/dracut-olpc-actrd.conf actrd.img
>> > dracut-install: ERROR: installing
>> > '/usr/lib/python2.7/lib-dynload/_md5module.so'
>> > E: /usr/lib/dracut/dracut-install -D /var/tmp/initramfs.2kIhBe
>> > /usr/lib/python2.7/lib-dynload/_md5module.so
>> > dracut-install: ERROR: installing
>> > '/usr/lib/python2.7/lib-dynload/Python-2.7.2-py2.7.egg-info'
>> > E: /usr/lib/dracut/dracut-install -D /var/tmp/initramfs.2kIhBe
>> > /usr/lib/python2.7/lib-dynload/Python-2.7.2-py2.7.egg-info
>> > dracut-install: ERROR: installing
>> > '/usr/lib/python2.7/lib-dynload/_sha256module.so'
>> > E: /usr/lib/dracut/dracut-install -D /var/tmp/initramfs.2kIhBe
>> > /usr/lib/python2.7/lib-dynload/_sha256module.so
>> > dracut-install: ERROR: installing
>> > '/usr/lib/python2.7/lib-dynload/_sha512module.so'
>> > E: /usr/lib/dracut/dracut-install -D /var/tmp/initramfs.2kIhBe
>> > /usr/lib/python2.7/lib-dynload/_sha512module.so
>> > dracut-install: ERROR: installing
>> > '/usr/lib/python2.7/lib-dynload/_shamodule.so'
>> > E: /usr/lib/dracut/dracut-install -D /var/tmp/initramfs.2kIhBe
>> > /usr/lib/python2.7/lib-dynload/_shamodule.so
>> > WARNING: could not open
>> >
>> /var/tmp/initramfs.2kIhBe/lib/modules/3.0.19_xo1.75-20121216.0813.olpc.1765a82/modules.order:
>> > No such file or directory
>> > WARNING: could not open
>> >
>> /var/tmp/initramfs.2kIhBe/lib/modules/3.0.19_xo1.75-20121216.0813.olpc.1765a82/modules.builtin:
>> > No such file or directory
>>
>> I expect these errors aren't really important, and that it produces an
>> initramfs for you anyway. What is the problem you are seeing?
>>
>> Daniel
>>
>
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
>


-- 
Roger

Activity Central 
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: OOB + signature

[Rogelio Mita]

Hi all!

2013/2/8 Rogelio Mita 

> Thanks a lot Martín!.
>
> Perfect the answer!, then... we understand that the contents manifest file
> that is the result of build (ussualy .toc, that is used to update method,
> olpc-update) will also be affected by this process, is this right?.
> Because we no found place to verify this assertion in some documentation,
> only the specification of contents manifest, but found nothing about it,
> only the following lines that do not answer to our question:
>
> A contents manifest is just a convenience object for bundling a number of
>> related directory objects; it should not be directly signed. Instead, the
>> root directory object in the contents manifest should be the element which
>> receives a signature.
>
> http://wiki.laptop.org/go/Contents_manifest_specification
>
> Thanks again!
>
> Regards!
>
2013/2/8 Martin Langhoff 
>
>> On Thu, Feb 7, 2013 at 9:45 AM, Rafael Ortiz 
>> wrote:
>> > and how its resulting files are signed (for instance the content
>> manifest
>> > file, specifically for the upgrade files), OOB uses some method when the
>> > signature module is activated ?, you have to sing them in an special
>> way?.
>>
>> If you have the signing keys in the build machine, it's really easy.
>> Set the .ini file to use the signing modules, tell it where the keys
>> are, and it'll do it automagically for you.
>>
>> Any suggestions on this =) ? Thanks!


>  See in OOB sources, modules/signing/README. Skip the "external signing"
>> section.
>>
>> hth,
>>
>>
>>
>> m
>> --
>>  martin.langh...@gmail.com
>>  mar...@laptop.org -- Software Architect - OLPC
>>  - ask interesting questions
>>  - don't get distracted with shiny stuff  - working code first
>>  - http://wiki.laptop.org/go/User:Martinlanghoff
>>
>
>
>
> --
> Roger
>
> Activity Central <http://activitycentral.com/>
>



-- 
Roger

Activity Central <http://activitycentral.com/>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: OOB + signature

[Rogelio Mita]

Thanks a lot Martín!.

Perfect the answer!, then... we understand that the contents manifest file
that is the result of build (ussualy .toc, that is used to update method,
olpc-update) will also be affected by this process, is this right?.
Because we no found place to verify this assertion in some documentation,
only the specification of contents manifest, but found nothing about it,
only the following lines that do not answer to our question:

A contents manifest is just a convenience object for bundling a number of
> related directory objects; it should not be directly signed. Instead, the
> root directory object in the contents manifest should be the element which
> receives a signature.

http://wiki.laptop.org/go/Contents_manifest_specification

Thanks again!

Regards!

2013/2/8 Martin Langhoff 

> On Thu, Feb 7, 2013 at 9:45 AM, Rafael Ortiz 
> wrote:
> > and how its resulting files are signed (for instance the content manifest
> > file, specifically for the upgrade files), OOB uses some method when the
> > signature module is activated ?, you have to sing them in an special
> way?.
>
> If you have the signing keys in the build machine, it's really easy.
> Set the .ini file to use the signing modules, tell it where the keys
> are, and it'll do it automagically for you.
>
> See in OOB sources, modules/signing/README. Skip the "external signing"
> section.
>
> hth,
>
>
>
> m
> --
>  martin.langh...@gmail.com
>  mar...@laptop.org -- Software Architect - OLPC
>  - ask interesting questions
>  - don't get distracted with shiny stuff  - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff
>



-- 
Roger.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: OOB + signature

[Rogelio Mita]

Thanks a lot Martín!.

Perfect the answer!, then... we understand that the contents manifest file
that is the result of build (ussualy .toc, that is used to update method,
olpc-update) will also be affected by this process, is this right?.
Because we no found place to verify this assertion in some documentation,
only the specification of contents manifest, but found nothing about it,
only the following lines that do not answer to our question:

A contents manifest is just a convenience object for bundling a number of
> related directory objects; it should not be directly signed. Instead, the
> root directory object in the contents manifest should be the element which
> receives a signature.

http://wiki.laptop.org/go/Contents_manifest_specification

Thanks again!

Regards!

2013/2/8 Martin Langhoff 

> On Thu, Feb 7, 2013 at 9:45 AM, Rafael Ortiz 
> wrote:
> > and how its resulting files are signed (for instance the content manifest
> > file, specifically for the upgrade files), OOB uses some method when the
> > signature module is activated ?, you have to sing them in an special
> way?.
>
> If you have the signing keys in the build machine, it's really easy.
> Set the .ini file to use the signing modules, tell it where the keys
> are, and it'll do it automagically for you.
>
> See in OOB sources, modules/signing/README. Skip the "external signing"
> section.
>
> hth,
>
>
>
> m
> --
>  martin.langh...@gmail.com
>  mar...@laptop.org -- Software Architect - OLPC
>  - ask interesting questions
>  - don't get distracted with shiny stuff  - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff
>



-- 
Roger

Activity Central 
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel