Hi,
If I understand this:
1. Get a developer key for each laptop in the school.
2. Use the developer key to unlock each laptop.
3. Do a normal install of the build image.
4. Relock the laptop by removing the developer key on the XO
Still a bit complex, but should be usable.
Tony
On 11/15/2012 08:02 PM, James Cameron wrote:
Thanks. Your understanding is adequate, but possibly incomplete.
Any deployment can unlock their laptops, add a deployment key, and
then relock them. This deployment key can then be used in the
preparation of signed builds. The capability is publically available,
and I'm aware of more than one deployment using it.
On Thu, Nov 15, 2012 at 07:16:04PM -0500, Tony Anderson wrote:
Hi,
As I understand it, if you make your own build, it cannot be
installed on a 'locked' laptop unless you have local signing
capability. It is also my understanding that this capability is only
available to one deployment.
Tony
On 11/15/2012 05:54 PM, James Cameron wrote:
On Thu, Nov 15, 2012 at 12:34:32PM -0500, Tony Anderson wrote:
Hi,
One alternative is to write a simple script to do this using
sugar-install-bundle.
I put the activities to be installed on the stick.
An example,
#run as olpc
cd /run/media/olpc/xxx #so relative paths work
#remove unwanted activity
rm -rf /home/olpc/Activities/someactivity.activity
#rm activity even if not installed just to ensure clean install
rm -rf /home/olpc/Activities/newactivity.activity
#install new activity
sugar-install-bundle newactivity-1.xo
sudo poweroff #ensures xo will be restarted to register activities
This also avoids the 'signing' issues in building a custom image.
Could you be more specific about these issues?
_______________________________________________
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
