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
On 03/24/2013 09:38 AM, devel-requ...@lists.laptop.org wrote:
It's true, we need learn new tricks, but does not have sense have a service
not needed on every xo, if we can do it in a better way.
Does this logic apply generally?
12.1.0 has a control panel entry 'Modem configuration'. How many
Ok. Ive done it.
Is it possible to have an auto install? i.e. without need to type command
from the prompt.
Lionel.
De : Samuel Greenfeld [mailto:greenf...@laptop.org]
Envoyé : dimanche 24 mars 2013 14:40
À : lio...@olpc-france.org
Cc : devel@lists.laptop.org
Objet :
Hi all,
Ive seen that the « langs= » property in the .ini for OS Builder allow to
choose the language sets installed on the image.
I wonder if there is a way to specify the default language (FR instead of EN
for example).
Do I need to use a custom script for that?
Thanks in advance for
On Sun, Mar 24, 2013 at 11:29 AM, Tony Anderson tony_ander...@usa.netwrote:
On 03/24/2013 09:38 AM, devel-requ...@lists.laptop.org wrote:
It's true, we need learn new tricks, but does not have sense have a
service
not needed on every xo, if we can do it in a better way.
Does this logic
i think the point john (gilmore) was making is that it's a bad
precedent that simply because a) systemd offers a second-rate API for
scheduling events, and b) we only have a couple of uses for an event
scheduler, that we should therefore switch from a well-established API
to a lousy API. instead,
On Sun, 2013-03-24 at 21:33 +0100, lio...@olpc-france.org wrote:
Ok. I’ve done it.
Is it possible to have an auto install? i.e. without need to type
command from the prompt.
Yes, you would need to have your security keys installed in the XOs, but
that is difficult when the XO's have
Hi Paul,
On Sun, Mar 24, 2013 at 6:34 PM, Paul Fox p...@laptop.org wrote:
but when systemd falls out of favor in a year or two we'll just have
to change things again -- either to something new, or back to cron
Not sure whether you're stating that straight or facetiously.
Systemd has some
On Sun, 2013-03-24 at 23:02 +0100, lio...@olpc-france.org wrote:
Hi all,
I’ve seen that the « langs= » property in the .ini for OS Builder
allow to choose the language sets installed on the image.
I wonder if there is a way to specify the default language (FR instead
of EN for
Hi Lionel,
the right way for this is to have the correct language set in the
manufacturing data in the XO laptops. If you have this set right (and
you probably do already), then just include french in the build, and
on first boot the laptop will pick up the right default.
Boot one of your XOs,
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
IMHO, if we can speed up the startup time a litle,
the change worth it.
We are talking of end users systems, how many kids will add a cron task?
And who propose the change is dsd, we know him and is
a conservative guy, does not do change without reason.
We did this in the same way the last 30
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
martin wrote:
Hi Paul,
On Sun, Mar 24, 2013 at 6:34 PM, Paul Fox p...@laptop.org wrote:
but when systemd falls out of favor in a year or two we'll just have
to change things again -- either to something new, or back to cron
Not sure whether you're stating that straight or
If you change the LO tag for a laptop before the first boot of an image,
its value will get picked up and used.
- Stop a boot in OFW by pressing the ESC key.
- fs-update (or copy-image) the new image into place
- Change the manufacturing tag:
change-tag LO fr_FR.UTF-8 / only works if the same
16 matches
Mail list logo
