Customizing NAND images/lang-es: Difference between revisions

From OLPC
Jump to navigation Jump to search
(sync'ed version = 63810)
(Undo revision 196615 by 88.233.117.177 (Talk) - spam!)
 
(5 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{OLPC}}
{{OLPC}}
{{Translation | lang = es | source = Customizing NAND images | version = 63810}}
{{Translation | lang = es | source = Customizing NAND images | version = 63821}}
{{TOCright}}
{{TOCright}}


Line 6: Line 6:
{{ Translated text |
{{ Translated text |
This document describes how to create a jffs2 image from a laptop's internal NAND, producing an image that can be flashed onto a different XO. The laptop that is being backed up is the "host" laptop, and the laptop receiving the contents of the host laptop is the "target" laptop.
This document describes how to create a jffs2 image from a laptop's internal NAND, producing an image that can be flashed onto a different XO. The laptop that is being backed up is the "host" laptop, and the laptop receiving the contents of the host laptop is the "target" laptop.
| display = block }}
| display = none }}


{{anchor|Basic Procedure}}
{{anchor|Basic Procedure}}
Line 30: Line 30:


* Cambiando y sobre a la laptop "destino", inserte el disco USB. Nuevamente, interrumpa en el "ok" prompt y tipee "<tt>copy-nand disk:\nand.img</tt>". Esto copiará <tt>nand.img</tt> a la NAND interna. Cuando vuelva al "ok" prompt, apague, extraiga el disco USB y prenda de nuevo para cargar a partir de la nueva imagen NAND.
* Cambiando y sobre a la laptop "destino", inserte el disco USB. Nuevamente, interrumpa en el "ok" prompt y tipee "<tt>copy-nand disk:\nand.img</tt>". Esto copiará <tt>nand.img</tt> a la NAND interna. Cuando vuelva al "ok" prompt, apague, extraiga el disco USB y prenda de nuevo para cargar a partir de la nueva imagen NAND.

{{ Translated text |
{{ Translated text |
Steps:
Steps:
Line 35: Line 36:
* Make the modifications on the host laptop that you want to be present in the generated image. If you've logged into Sugar and want the user to see the welcome/login prompt again, see the Section [[#Forcing Sugar to reprompt for name and colors]]. If you plan to use the image in laptops with different languages and keyboard layouts, you should delete also the file <tt>/.olpc-configured</tt>. This will force the system to run the olpc-configure script in the next boot.
* Make the modifications on the host laptop that you want to be present in the generated image. If you've logged into Sugar and want the user to see the welcome/login prompt again, see the Section [[#Forcing Sugar to reprompt for name and colors]]. If you plan to use the image in laptops with different languages and keyboard layouts, you should delete also the file <tt>/.olpc-configured</tt>. This will force the system to run the olpc-configure script in the next boot.


* IMPORTANT: Make sure you delete these files in /etc/ssh:
* IMPORTANT: Make sure you delete these files in <tt>/etc/ssh</tt>:
ssh_host_dsa_key
ssh_host_dsa_key
ssh_host_dsa_key.pub
ssh_host_dsa_key.pub
Line 45: Line 46:
* Insert a Windows-formatted (VFAT) USB disk into the host laptop, and reboot.
* Insert a Windows-formatted (VFAT) USB disk into the host laptop, and reboot.


* At the "Type any key to interrupt automatic startup" key, press a key. At the "ok" prompt, type "save-nand disk:\nand.img" and press return. The contents of the NAND will be backed up to the nand.img file on the USB disk. The "ok" prompt will return when the copy has finished, and you can then power the laptop off with the power button.
* At the "Type any key to interrupt automatic startup" key, press a key. At the "ok" prompt, type "<tt>save-nand disk:\nand.img</tt>" and press return. The contents of the NAND will be backed up to the <tt>nand.img</tt> file on the USB disk. The "ok" prompt will return when the copy has finished, and you can then power the laptop off with the power button.


* Since build 406, you need a checksum file to successfully upgrade the system. To create the CRC file see the Section [[#Creating CRC file]].
* Since build 406, you need a checksum file to successfully upgrade the system. To create the CRC file see the Section [[#Creating CRC file]].


* Move to the "target" laptop, and insert the USB disk. Again, interrupt at the prompt, and at the ok prompt type "copy-nand disk:\nand.img". This will copy from nand.img to the internal NAND. When back at the ok prompt, power off, remove the USB disk, and power on again to load from the new NAND image.
* Move to the "target" laptop, and insert the USB disk. Again, interrupt at the prompt, and at the ok prompt type "<tt>copy-nand disk:\nand.img</tt>". This will copy from <tt>nand.img</tt> to the internal NAND. When back at the ok prompt, power off, remove the USB disk, and power on again to load from the new NAND image.
| display = block }}
| display = none }}


{{anchor|Example Customizations}}
{{anchor|Example Customizations}}
Line 64: Line 65:
Sometimes you may want to define the default language for the system, either for use or while localizing.
Sometimes you may want to define the default language for the system, either for use or while localizing.


The ''/etc/sysconfig/i18n'' file defines the '''LANG''' variable that Sugar will use.
The ''<tt>/etc/sysconfig/i18n</tt>'' file defines the '''<tt>LANG</tt>''' variable that Sugar will use.
| display = block }}
| display = none }}


{{anchor|Timezone}}
{{anchor|Timezone}}

=== Huso horario ===
=== Huso horario ===


La información relativa al huso o zona horaria es guardada en el archivo ''<tt>/etc/timezone</tt>''. Por ejemplo, la costa este de EE.UU. es "<tt>America/New_York</tt>". Este nombre hace referencia a los archivos que se encuentran en ''<tt>/usr/share/zoneinfo</tt>'', que controlan el huso o zona horaria y el comportamiento del horario de verano en el caso de aplicarse.
La información relativa al huso o zona horaria es guardada en el archivo ''<tt>/etc/timezone</tt>''. Por ejemplo, la costa este de EE.UU. es "<tt>America/New_York</tt>". Este nombre hace referencia a los archivos que se encuentran en ''<tt>/usr/share/zoneinfo</tt>'', que controlan el huso o zona horaria y el comportamiento del horario de verano en el caso de aplicarse.
{{ Translated text |
{{ Translated text |
Timezone information is stored in the file ''/etc/timezone''. For example, the east coast of the US is "America/New_York". This name references files found in ''/usr/share/zoneinfo'', that control the system's timezone and daylight savings time behavior.
Timezone information is stored in the file ''<tt>/etc/timezone</tt>''. For example, the east coast of the US is "<tt>America/New_York</tt>". This name references files found in ''<tt>/usr/share/zoneinfo</tt>'', that control the system's timezone and daylight savings time behavior.
| display = block }}
| display = none }}


{{anchor|Installing TrueType or OpenType Fonts}}
{{anchor|Installing TrueType or OpenType Fonts}}
Line 80: Line 82:
Se pueden instalar paquetes tipográficos pre-empaquetado, como usuario ''<tt>root</tt>'', a partir del repostitorio de Fedora como se muestra abajo, o se pueden instalar en un subdirectorio de ''<tt>/usr/share/fonts/ttf</tt>'' ejecutando el comando ''<tt>fc-cache -f</tt>'' a su fin.
Se pueden instalar paquetes tipográficos pre-empaquetado, como usuario ''<tt>root</tt>'', a partir del repostitorio de Fedora como se muestra abajo, o se pueden instalar en un subdirectorio de ''<tt>/usr/share/fonts/ttf</tt>'' ejecutando el comando ''<tt>fc-cache -f</tt>'' a su fin.
{{ Translated text |
{{ Translated text |
Either install as root prepackaged font package(s) from the Fedora repository as outlined below, or install the fonts in a subdirectory of ''/usr/share/fonts/ttf'' and run the ''fc-cache -f'' command afterwards.
Either install as root prepackaged font package(s) from the Fedora repository as outlined below, or install the fonts in a subdirectory of ''<tt>/usr/share/fonts/ttf</tt>'' and run the ''<tt>fc-cache -f</tt>'' command afterwards.
| display = block }}
| display = none }}


{{anchor|Activities}}
{{anchor|Activities}}
Line 92: Line 94:
Para agregar una actividad, instálela en el mismo directorio.
Para agregar una actividad, instálela en el mismo directorio.
{{ Translated text |
{{ Translated text |
To remove an activity from the build, delete the desired directory from: ''/usr/share/activities'':<br>
To remove an activity from the build, delete the desired directory from: ''<tt>/usr/share/activities</tt>'':<br>
''rm -r TamTam.activity'' (for example)
''<tt>rm -r TamTam.activity</tt>'' (for example)


To add an activity, install it in this same directory.
To add an activity, install it in this same directory.
| display = block }}
| display = none }}


{{anchor|Keyboard}}
{{anchor|Keyboard}}
Line 122: Line 124:
# After the system has booted, press <tt>ctrl+alt+f1</tt> (f1 is the same as the "mesh-view" key);
# After the system has booted, press <tt>ctrl+alt+f1</tt> (f1 is the same as the "mesh-view" key);
# Login in as root (no password required);
# Login in as root (no password required);
# Open the file /etc/X11/xorg.conf for editing (use vi or any editor you are comfortable with);
# Open the file <tt>/etc/X11/xorg.conf</tt> for editing (use vi or any editor you are comfortable with);
# In the first InputDevice Section do the following modifications:
# In the first <tt>InputDevice Section</tt> do the following modifications:
#* To change the default language, e.g., from English to Spanish:
#* To change the default language, e.g., from English to Spanish:
#** Modify XkbLayout Setting from "us" to "es" (use "pt" for Portuguese, "ng" for Nigerian language support, etc.);
#** Modify <tt>XkbLayout Setting</tt> from "us" to "es" (use "pt" for Portuguese, "ng" for Nigerian language support, etc.);
#** Add an XkbOptions Option with the value "olpc";
#** Add an <tt>XkbOptions Option</tt> with the value "olpc";
#* To add a second language, e.g., English and Arabic:
#* To add a second language, e.g., English and Arabic:
#** Modify XkbLayout Setting from "us" to "us,ara" (use "ru" for Cyrillic, "ur" for Urdu, "th" for Thai, etc.);
#** Modify <tt>XkbLayout Setting</tt> from "<tt>us</tt>" to "<tt>us,ara</tt>" (use "<tt>ru</tt>" for Cyrillic, "<tt>ur</tt>" for Urdu, "<tt>th</tt>" for Thai, etc.);
#** Add an XkbOptions Option with the value "olpc2,olpc";
#** Add an <tt>XkbOptions Option</tt> with the value "<tt>olpc2,olpc</tt>";
# Save and close the file;
# Save and close the file;
# Either reboot the machine or restart X by issuing a "/sbin/telinit 3" command, followed by the "/sbin/telinit 5" command.
# Either reboot the machine or restart X by issuing a "<tt>/sbin/telinit 3</tt>" command, followed by the "<tt>/sbin/telinit 5</tt>" command.
| display = block }}
| display = none }}


Después de haber hecho las modificaciones, las dos líneas en <tt>xorg.conf</tt> deben ser similar a unas de las siguientes:
Después de haber hecho las modificaciones, las dos líneas en <tt>xorg.conf</tt> deben ser similar a unas de las siguientes:
{|
⚫
Option "XkbLayout" "es"
! width=50% | l10n para [[spanish|castellano]] !! l10n para [[english|inglés]] / [[arabic|árabe]]
⚫
Option "XkbOptions" "olpc"
|-

|
Después de que X haya reiniciado, el idioma de base será el Español (castellano).
Section "InputDevice"

Option "XkbLayout" "us,ara"
Option "XkbLayout" "es"
Option "XkbOptions" "olpc2,olpc"
Option "XkbOptions" "olpc"
|

Section "InputDevice"
⚫
Después de que X haya recomenzado, el idioma de base será Inglés; usted será capaz de cambiar a Árabe usando la tecla <i>AB/اب</i>.
⚫
Option "XkbLayout" "us,ara"
⚫
Option "XkbOptions" "olpc2,olpc"
|- valign=top
⚫
| Después de que X haya reiniciado, el idioma de base será el Español (castellano). || Después de que X haya reiniciado, el idioma de base será Inglés; usted será capaz de cambiar a Árabe usando la tecla [[Image:Key arabic.jpg|30px]].
|}
{{ Translated text |
{{ Translated text |
After you make the modifications, the two lines in xorg.conf should be similar to one of the following:
After you make the modifications, the two lines in <tt>xorg.conf</tt> should be similar to one of the following:
{|
⚫
Option "XkbLayout" "es"
! width=50% | l10n for [[spanish]] !! l10n for [[english]] / [[arabic]]
⚫
Option "XkbOptions" "olpc"
|-

|
After X is restarted, the default language will be Spanish.
Section "InputDevice"

Option "XkbLayout" "us,ara"
Option "XkbLayout" "es"
Option "XkbOptions" "olpc2,olpc"
Option "XkbOptions" "olpc"
|

Section "InputDevice"
⚫
After X is restarted, the default language will be English; you will be able to switch to Arabic using the <i>AB/اب</i> key.
⚫
Option "XkbLayout" "us,ara"
⚫
| display = block }}
⚫
Option "XkbOptions" "olpc2,olpc"
|- valign=top
⚫
| After X is restarted, the default language will be [[Spanish]] (es). || After X is restarted, the default language will be [[English]] (us); you will be able to switch to [[Arabic]] (ara) using the [[Image:Key arabic.jpg|30px]] key.
|}
⚫
| display = none }}


{{anchor|Installing packages from the Fedora repositories using yum}}
{{anchor|Installing packages from the Fedora repositories using yum}}
Line 176: Line 188:
Sugar is based off of Fedora and as such has a large amount of packages available to add to the base system. The tool used to do this is called yum. Because of memory constraints it is best to drop into run mode 3 which stops X. To do this log in as root either in the developer console or one of the virtual terminals and type this command:
Sugar is based off of Fedora and as such has a large amount of packages available to add to the base system. The tool used to do this is called yum. Because of memory constraints it is best to drop into run mode 3 which stops X. To do this log in as root either in the developer console or one of the virtual terminals and type this command:


'''init 3'''
'''<tt>init 3</tt>'''


X should exit and you should find yourself either at a login prompt or in the same virtual terminal. Log in as root if you are not already. To install or upgrade a package you simply use this command:
X should exit and you should find yourself either at a login prompt or in the same virtual terminal. Log in as root if you are not already. To install or upgrade a package you simply use this command:


'''yum upgrade <package name>'''
'''<tt>yum upgrade <package name></tt>'''


To search for available packages you can use this command:
To search for available packages you can use this command:


'''yum search <keyword>'''
'''<tt>yum search <keyword></tt>'''


More information about using yum with fedora [http://docs.fedoraproject.org/yum/ can be found here].
More information about using yum with fedora [http://docs.fedoraproject.org/yum/ can be found here].
| display = block }}
| display = none }}


{{anchor|Installing Flash, Java, MP3 codecs, MPEG4, patented codecs}}
{{anchor|Installing Flash, Java, MP3 codecs, MPEG4, patented codecs}}
Line 199: Line 211:


(Note that the Adobe Flash plugin 9.0.31.0 is known to work and 9.0.60.120 is known not to work.)
(Note that the Adobe Flash plugin 9.0.31.0 is known to work and 9.0.60.120 is known not to work.)
| display = block }}
| display = none }}


{{anchor|Helix (Real) Media Player}}
{{anchor|Helix (Real) Media Player}}

=== Helix (Real) Media Player ===
=== Helix (Real) Media Player ===


Line 207: Line 220:
{{ Translated text |
{{ Translated text |
The [[Helix media activity]] page covers installation of this activity and its associated codecs.
The [[Helix media activity]] page covers installation of this activity and its associated codecs.
| display = block }}
| display = none }}


{{anchor|Forcing Sugar to reprompt for name and colors}}
{{anchor|Forcing Sugar to reprompt for name and colors}}
Line 226: Line 239:
You can always edit:
You can always edit:
/home/olpc/.sugar/default/config
/home/olpc/.sugar/default/config
However, there may be times when you may want to force Sugar to prompt for a new name and colors as if with a new machine. You can do this by deleteing the configuration file and the SHH keys in the ./sugar/default directory.
However, there may be times when you may want to force Sugar to prompt for a new name and colors as if with a new machine. You can do this by deleteing the configuration file and the SHH keys in the <tt>./sugar/default</tt> directory.
rm /home/olpc/.sugar/default/config
rm /home/olpc/.sugar/default/config
rm /home/olpc/.sugar/default/owner.key
rm /home/olpc/.sugar/default/owner.key
Line 234: Line 247:
rm -r /home/olpc/.sugar/default/datastore
rm -r /home/olpc/.sugar/default/datastore
* This process '''does''' force the generation of new keys, which will ''potentially'' have (an adverse) impact on access to backup files on the [[school server]].
* This process '''does''' force the generation of new keys, which will ''potentially'' have (an adverse) impact on access to backup files on the [[school server]].
| display = block }}
| display = none }}


{{anchor|Creating CRC file}}
{{anchor|Creating CRC file}}
Line 260: Line 273:
After, you can from the command prompt create the crc from your custumized image
After, you can from the command prompt create the crc from your custumized image
./crcimg myfile.img
./crcimg myfile.img
Output is in myfile.crc
Output is in <tt>myfile.crc</tt>
| display = block }}
| display = none }}


[[Category:Developers]]
[[Category:Developers]]

Latest revision as of 15:20, 14 March 2009

  Esta página está supervisada por el equipo de OLPC.
  Traducción de Customizing NAND images original  
  english | español   +/- cambios  

Este documento describe como crear una imagen jffs2 a partir de la NAND interna de una laptop, generando una imagen que puede ser instalada en una XO diferente. La laptop que esta siendo copiada es la laptop "origen", y la laptop que recibe los contenidos del laptop origen es la laptop "destino".

This document describes how to create a jffs2 image from a laptop's internal NAND, producing an image that can be flashed onto a different XO. The laptop that is being backed up is the "host" laptop, and the laptop receiving the contents of the host laptop is the "target" laptop.

Procedimiento Básico

Pasos:

  • Haga las modificaciones necesarias en la laptop de origen que desea queden en la imagen a generar. Si usted se ha loggeado en Sugar y quiere el usuario vea el paso inicial de bienvenida/login nuevamente, vea la seccion Forzando a Sugar que repregunte nombre y color. Si usted planea usar la imagen en laptops con diferentes lenguajes y mapas de teclado, se debe borrar también el archivo /.olpc-configured. Esto forzará al sistema a correr el script olpc-configure en el próximo arranque.
  • IMPORTANTE: Asegúrese de borrar los siguientes archivos en /etc/ssh:
ssh_host_dsa_key
ssh_host_dsa_key.pub
ssh_host_key
ssh_host_key.pub
ssh_host_rsa_key
ssh_host_rsa_key.pub
  • Inserte un disco USB con el formato Windows (VFAT) en la laptop origen y rebootee.
  • En el "Type any key to interrupt automatic startup", presione una tecla. En el prompt "ok", tipee "save-nand disk:\nand.img" y presione enter. El contenido de la NAND será copiado al archivo nand.img en el disco USB. Se regresará al prompt "ok" una vez finalizada la copia, tras lo cual se puede apagar la laptop con el botón de encendido/apagado.
  • A partir del build 406, es necesario un archivo checksum para hacer una actualización del sistema. Para crear el archivo CRC vea la sección creando un archivo CRC.
  • Cambiando y sobre a la laptop "destino", inserte el disco USB. Nuevamente, interrumpa en el "ok" prompt y tipee "copy-nand disk:\nand.img". Esto copiará nand.img a la NAND interna. Cuando vuelva al "ok" prompt, apague, extraiga el disco USB y prenda de nuevo para cargar a partir de la nueva imagen NAND.

Steps:

  • Make the modifications on the host laptop that you want to be present in the generated image. If you've logged into Sugar and want the user to see the welcome/login prompt again, see the Section #Forcing Sugar to reprompt for name and colors. If you plan to use the image in laptops with different languages and keyboard layouts, you should delete also the file /.olpc-configured. This will force the system to run the olpc-configure script in the next boot.
  • IMPORTANT: Make sure you delete these files in /etc/ssh:
ssh_host_dsa_key
ssh_host_dsa_key.pub
ssh_host_key
ssh_host_key.pub
ssh_host_rsa_key
ssh_host_rsa_key.pub
  • Insert a Windows-formatted (VFAT) USB disk into the host laptop, and reboot.
  • At the "Type any key to interrupt automatic startup" key, press a key. At the "ok" prompt, type "save-nand disk:\nand.img" and press return. The contents of the NAND will be backed up to the nand.img file on the USB disk. The "ok" prompt will return when the copy has finished, and you can then power the laptop off with the power button.
  • Since build 406, you need a checksum file to successfully upgrade the system. To create the CRC file see the Section #Creating CRC file.
  • Move to the "target" laptop, and insert the USB disk. Again, interrupt at the prompt, and at the ok prompt type "copy-nand disk:\nand.img". This will copy from nand.img to the internal NAND. When back at the ok prompt, power off, remove the USB disk, and power on again to load from the new NAND image.

Ejemplos de personalizaciones

Idioma

Algunas veces se puede querer determinar el idioma base del sistema, ya sea para su uso o mientras se realiza la localización.

El archivo /etc/sysconfig/i18n define la variable LANG que será usada por Sugar.

Sometimes you may want to define the default language for the system, either for use or while localizing.

The /etc/sysconfig/i18n file defines the LANG variable that Sugar will use.

Huso horario

La información relativa al huso o zona horaria es guardada en el archivo /etc/timezone. Por ejemplo, la costa este de EE.UU. es "America/New_York". Este nombre hace referencia a los archivos que se encuentran en /usr/share/zoneinfo, que controlan el huso o zona horaria y el comportamiento del horario de verano en el caso de aplicarse.

Timezone information is stored in the file /etc/timezone. For example, the east coast of the US is "America/New_York". This name references files found in /usr/share/zoneinfo, that control the system's timezone and daylight savings time behavior.

Instalación de tipografías TrueType u OpenType

Se pueden instalar paquetes tipográficos pre-empaquetado, como usuario root, a partir del repostitorio de Fedora como se muestra abajo, o se pueden instalar en un subdirectorio de /usr/share/fonts/ttf ejecutando el comando fc-cache -f a su fin.

Either install as root prepackaged font package(s) from the Fedora repository as outlined below, or install the fonts in a subdirectory of /usr/share/fonts/ttf and run the fc-cache -f command afterwards.

Actividades

Para eliminar una actividad del build, elimine su directorio de: /usr/share/activities

rm -r TamTam.activity (por ejemplo)

Para agregar una actividad, instálela en el mismo directorio.

To remove an activity from the build, delete the desired directory from: /usr/share/activities:
rm -r TamTam.activity (for example)

To add an activity, install it in this same directory.

Teclado

Si los datos de manufactura no coinciden con el teclado deseado, es necesario configurar el tipo de teclado.

Para cambiar el mapeo de símbolos del teclado, siga los siguientes pasos:

  1. Después de que el sistema haya booteado, presione ctrl+alt+f1 (f1 es la misma tecla de "mesh-view");
  2. Identifíquese como root (no se requiere password);
  3. Abra el archivo /etc/X11/xorg.conf para editar (use vi o cualquier otro editor de su preferencia);
  4. En la primera sección de "InputDevice" haga las siguientes modificaciones :
    • Para cambiar el idioma de base por ejemplo de Inglés a Español:
      • Modifique XkbLayout Setting de "us" a "es" (use "pt" para Portugués, "ng" para soporte Nigeriano, etc.);
      • Añada una XkbOptions Option con el valor "olpc";
    • Para añadir un segundo idioma, por ejemplo Inglés y Árabe:
      • Modifique XkbLayout Setting de "us" a "us,ara" (use "ru" para Cirílico, "ur" para Urdu, "th" para Tailandés, etc.);
      • Añada una XkbOptions Option con el valor "olpc2,olpc";
  5. Guarde y cierre el archivo;
  6. Puede rebootear la máquina o reiniciar X por medio del comando "/sbin/telinit 3", seguido de "/sbin/telinit 5".

If the manufacturing data does not match the keyboard you need, you can set the keyboard type.

To change the symbol mapping of the keyboard, follow the following steps:

  1. After the system has booted, press ctrl+alt+f1 (f1 is the same as the "mesh-view" key);
  2. Login in as root (no password required);
  3. Open the file /etc/X11/xorg.conf for editing (use vi or any editor you are comfortable with);
  4. In the first InputDevice Section do the following modifications:
    • To change the default language, e.g., from English to Spanish:
      • Modify XkbLayout Setting from "us" to "es" (use "pt" for Portuguese, "ng" for Nigerian language support, etc.);
      • Add an XkbOptions Option with the value "olpc";
    • To add a second language, e.g., English and Arabic:
      • Modify XkbLayout Setting from "us" to "us,ara" (use "ru" for Cyrillic, "ur" for Urdu, "th" for Thai, etc.);
      • Add an XkbOptions Option with the value "olpc2,olpc";
  5. Save and close the file;
  6. Either reboot the machine or restart X by issuing a "/sbin/telinit 3" command, followed by the "/sbin/telinit 5" command.

Después de haber hecho las modificaciones, las dos líneas en xorg.conf deben ser similar a unas de las siguientes:

l10n para castellano l10n para inglés / árabe 
Section "InputDevice"
 Option    "XkbLayout"   "es"
 Option    "XkbOptions"  "olpc"

Section "InputDevice"
 Option    "XkbLayout"   "us,ara"
 Option    "XkbOptions"  "olpc2,olpc"
Después de que X haya reiniciado, el idioma de base será el Español (castellano). Después de que X haya reiniciado, el idioma de base será Inglés; usted será capaz de cambiar a Árabe usando la tecla Key arabic.jpg.

After you make the modifications, the two lines in xorg.conf should be similar to one of the following:

{

Instalando paquetes de los repositorios de Fedora usando yum

Sugar esta basado en Fedora y por lo tanto dispone de una gran cantidad de paquetes que se pueden agregar al sistema base. La herramienta para hacer esto se llama yum. Debido a los límites de memoria disponible es mejor entrar en 'run mode 3' que no utiliza X. Para ello es necesario ser root y escribir en la consola de desarrollador o una de las terminales virtuales el siguiente comando:

init 3

X debería terminar y se debería encontrar nuevamente en el prompt de login o en la misma terminal virtual. Identifíquese (login) como root si aún no lo ha hecho. Para instalar o actualizar un paquete basta con usar el siguiente comando:

yum upgrade <nombre del paquete>

Para buscar paquetes disponibles existe el siguietne comando:

yum search <palabra>

Para más información acerca de como usar yum en Fedora vea yum en el sitio de fedoraporoject.

Sugar is based off of Fedora and as such has a large amount of packages available to add to the base system. The tool used to do this is called yum. Because of memory constraints it is best to drop into run mode 3 which stops X. To do this log in as root either in the developer console or one of the virtual terminals and type this command:

init 3

X should exit and you should find yourself either at a login prompt or in the same virtual terminal. Log in as root if you are not already. To install or upgrade a package you simply use this command:

yum upgrade <package name>

To search for available packages you can use this command:

yum search <keyword>

More information about using yum with fedora can be found here.

Instalando Flash, Java, MP3 codecs, MPEG4, codecs patentados

Estos formatos restringidos tienen problemas que hacen difícil o imposible que la OLPC los preinstale, pero usted puede estar capacitado e interesado en distribuir sistemas con ellos preinstalados.

(Nótese que el plugin Adobe Flash 9.0.31.0 se sabe que funciona mientras que el 9.0.60.120 no).

These Restricted Formats have problems that makes it difficult or impossible for OLPC to preinstall, but you may be able and interested in deploying systems with these preinstalled.

(Note that the Adobe Flash plugin 9.0.31.0 is known to work and 9.0.60.120 is known not to work.)

Helix (Real) Media Player

La página Helix media activity cubre la instalación de dicha actividad y sus codecs asociados.

The Helix media activity page covers installation of this activity and its associated codecs.

Forzando a Sugar a volver a visualizar el prompt para nombres y colores

Usted puede siempre puede editar: 

/home/olpc/.sugar/defaults/config

Sin embargo, puede haber ocasiones en las cuales usted pueda querer forzar para que Sugar solicite nuevamente un nuevo nombre y colores como con una máquina nueva. Esto se puede lograr borrando el archivo de configuración y las claves SHH en el directorio ./sugar/default. 

rm /home/olpc/.sugar/defaults/config
rm /home/olpc/.sugar/defaults/owner.key
rm /home/olpc/.sugar/defaults/owner.key.pub

Note que:

  • El proceso anterior no limpia el almacén de datos del Diario—se requiere de un paso adicional para borrar el directorio /home/olpc/.sugar/defaults/datastore que vaciará el Diario;
rm -r /home/olpc/.sugar/defaults/datastore
  • Este proceso si fuerza la creación de nuevas claves, que potencialmente tendrán un impacto (adverso) al momento de acceder a las copias de respaldo en el servidor escolar.

You can always edit: 

/home/olpc/.sugar/default/config

However, there may be times when you may want to force Sugar to prompt for a new name and colors as if with a new machine. You can do this by deleteing the configuration file and the SHH keys in the ./sugar/default directory. 

rm /home/olpc/.sugar/default/config
rm /home/olpc/.sugar/default/owner.key
rm /home/olpc/.sugar/default/owner.key.pub

Note that:

  • The above process does not clean out the Journal data repository—the additional step of deleteing the directory /home/olpc/.sugar/default/datastore will empty the Journal;
rm -r /home/olpc/.sugar/default/datastore
  • This process does force the generation of new keys, which will potentially have (an adverse) impact on access to backup files on the school server.

Creando el archivo CRC

Primero es necesario bajar y compilar pilgrim 

git clone git://git.fedoraproject.org/git/pilgrim
cd pilgrim/crcimg
make

File:Crcimg.sh - ejecutable crcimg de Linux

Después, usted puede desde la prompt de comandos crear el crc para su imagen personalizada: 

./crcimg myfile.img

El resultado se encuentra en myfile.crc

First, you need to download and compile pilgrim 

git clone git://git.fedoraproject.org/git/pilgrim
cd pilgrim/crcimg
make

File:Crcimg.sh - Linux crcimg executable

After, you can from the command prompt create the crc from your custumized image 

./crcimg myfile.img

Output is in myfile.crc

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Customizing_NAND_images/lang-es&oldid=198588"