Thanks to all. It works perfectly now.
Following is my script for other beginners like me :-)
Lionel.
\ automatic installer
unfreeze
visible
: wait-for-enter
begin key h# d = until
;
: ask-remove
. Remove the key and type enter to finish cr
wait-for-enter
;
: installer
Let us know if you have any further questions ... I expect some from
every new Forth user. ;-)
--
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Here is a screen capture from the XO-1 I'm using to test the procedure:
http://laske.fr/tmp/SHF8080270B.jpg
You appear to be using a developer key. If you are going to be
installing a custom build on all the laptops I would encourage you to
disable the security system altogether as the last
Hi all,
Thanks for your answer.
Let us know if you have any further questions ... I expect some from every
new Forth user. ;-)
You're right, it's hard to enter in Forth language :-{
I've added a olpc.fth file in the boot directory of my key with following
commands:
copy-nand
Hi Richard,
You appear to be using a developer key. If you are going to be installing
a custom build on all the laptops I would encourage you to disable the
security
system altogether as the last step in your olpc.fth step with
'disable-security'. Then some of the gotchas that occur with
Yes, add a comment line to the start of file, so that the file is
recognised. I also suggest encoding the work as a program
definition. So the file might be:
\ automatic installer by lio...@olpc-france.org
: installer
copy-nand u:\21007xx0.img eval
change-tag LO fr_FR.UTF-8 eval
;
On Mon, Mar 25, 2013 at 5:20 PM, lio...@olpc-france.org wrote:
Hi Richard,
You appear to be using a developer key. If you are going to be installing
a custom build on all the laptops I would encourage you to disable the
security
system altogether as the last step in your olpc.fth step
Yes, add a comment line to the start of file, so that the file is
recognised. I also suggest encoding the work as a program definition. So
the file might be:
YEES It works !
You're my new Forth Hero !
Lionel.
___
Devel mailing
Well for one you have to have those keys present for your installed os to
run either on that stick or by copying the developer key to the XO.
But then you have to make sure that the developer key is re-installed
anytime you reflash the XO. Also if for some other reason the dev keys are
removed
On Mon, Mar 25, 2013 at 11:23:39PM +0100, lio...@olpc-france.org wrote:
Hmmm. Change-tag without reboot ? Is there any way to do that ?
Yes, it is possible. For XO-4 it is easy. For XO-1 it disables
keyboard during the actions. If you have a bug in the code at this
time, you have to remove
On Mon, Mar 25, 2013 at 7:07 PM, James Cameron qu...@laptop.org wrote:
On Mon, Mar 25, 2013 at 06:50:00PM -0400, Richard Smith wrote:
But maybe you don't need to do that, if you are only changing one tag?
How many tags are you changing? If one, then finish the script with
the tag change.
special command to reboot without the lock. No way around it as you
can only unlock with a reboot. I suppose you could do the security
disable first and then when you see that its 'ww' rather than 'wp'
continue on with the re-flash and then the LO change as the last step.
I had a vague
I thought you should set the dk manufacturing tag, but I
just noticed that is only supported on XO-1 and 1.5!
wp and ww are different tags, you can't just change the
tag value with change-tag.
wad
On Mar 25, 2013, at 7:07 PM, James Cameron wrote:
On Mon, Mar 25, 2013 at 06:50:00PM -0400,
Hi all,
Thanks to the nice documentation on the Wiki, Ive successfully created my
first OS Build.
For the moment, its just a 12.1.0 without any customization but Im very
proud of this first step! :-)
Now I want to deploy it on my unlock XO-1 but Im slightly disappointed by
the output of
The fs0.zip file would only appear if you configured everything to make a
signed build. You would only be able to make a signed build if you had a
copy of the private keys for the deployment you are making the signed build
for. Only OLPC has the keys to make a signed build that pretty much any
: Re: OS Builder output img ?
The fs0.zip file would only appear if you configured everything to make a
signed build. You would only be able to make a signed build if you had a
copy of the private keys for the deployment you are making the signed build
for. Only OLPC has the keys to make
-france.org
Cc : devel@lists.laptop.org
Objet : Re: OS Builder output img ?
The fs0.zip file would only appear if you configured everything to
make a signed build. You would only be able to make a signed build if
you had a copy of the private keys for the deployment you are making
the signed
An auto install for an unlocked laptop does not need keys or signing.
Just place the Open Firmware commands that you want to run in a file
olpc.fth in the folder boot on the USB drive.
Sometimes the commands may need careful writing to avoid certain
features of Open Firmware.
There is no action
Hi Lionel,
your questions in recent emails lack some background -- specifically,
on how the XOs are configured. Without that info, we can give you many
different answers because it all depends on how the XOs are
configured.
Can you tell us the output of .mfg-data for the laptops you are
19 matches
Mail list logo
