Translation status

396 Strings 98%
Browse Translate
12,240 Words 96%

Strings status

396
All strings — 12,240 words Browse Translate Zen
390
Translated strings — 11,759 words Browse Translate Zen
6
Unfinished strings — 481 words Browse Translate Zen
6
Strings marked for edit — 481 words Browse Translate Zen
6
Unfinished strings without suggestions — 481 words Browse Translate Zen
1
Strings with any failing checks — 1 word Browse Translate Zen
1
Translated strings with any failing checks — 1 word Browse Translate Zen
58
Translated strings with dismissed checks — 390 words Browse Translate Zen
1
Failing check: Inconsistent — 1 word Browse Translate Zen
396
Strings without a label — 12,240 words Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
books/arch-handbook/partii This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 2 6 37 2 0 0 0
books/developers-handbook/policies/_index This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. This translation is locked. BSD-2-Clause 0% 93 2,145 13,148 91 2 0 0
books/handbook/colophon This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 3 25 166 3 0 0 0
books/arch-handbook/partiii This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 2 4 30 2 1 0 0
books/handbook/wayland/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 135 4,028 26,832 135 0 0 0
books/fdp-primer/see-also/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 18 77 865 18 0 0 0
books/developers-handbook/kerneldebug/_index This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 210 5,085 33,598 210 0 0 0
books/fdp-primer/rosetta/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 62 417 4,051 62 0 0 0
books/developers-handbook/partiv This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. BSD-2-Clause 0% 2 4 35 2 0 0 0
articles/license-guide/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 89 2,782 18,589 89 1 0 0
Browse all components

Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/articles/linux-emulation/_index.po
Translation file Download documentation/content/es/articles/linux-emulation/_index.po
Last change May 21, 2023, 6:01 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 396 12,240 77,383
Translated 98% 390 96% 11,759 96% 74,333
Needs editing 1% 6 3% 481 3% 3,050
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 1 1% 1 1% 3
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

4 changes 0 changes 2 changes 0 changes 0 changes 419 changes 2 changes 0 changes 0 changes 0 changes 7 changes 0 changes 0 changes 0 changes 3 changes 2 changes 1 change 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 14 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

12,240
Hosted words
396
Hosted strings
98%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+96%
Hosted words
+100%
+100%
Hosted strings
—
+98%
Translated
—
—
Contributors
+100%
User avatar None

New strings to translate

Documentation / articles/linux-emulation/_index — Spanish

6 new strings to translate appeared to the translation. 10 days ago
User avatar None

Resource update

Documentation / articles/linux-emulation/_index — Spanish

The "documentation/content/es/articles/linux-emulation/_index.po" file was changed. 10 days ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Spanish

Many UNIX(R) derivates implement the man:ptrace[2] syscall to allow various tracking and debugging features. This facility enables the tracing process to obtain various information about the traced process, like register dumps, any memory from the process address space, etc. and also to trace the process like in stepping an instruction or between system entries (syscalls and traps). man:ptrace[2] also lets you set various information in the traced process (registers etc.). man:ptrace[2] is a UNIX(R)-wide standard implemented in most UNIX(R)es around the world.
Muchos derivados de UNIX(R) implementan la llamada al sistema man:ptrace[2] para proporcionar diversas características de depuración y traza. Estas características permiten la traza de un proceso para obtener información valiosa acerca del proceso que es trazado, como volcado de registros, cualquier posición de memoria del espacio de direcciones del proceso, etc. y también para trazar procesos para saltar una instrucción o entre entradas al sistema (llamadas al sistema y traps). man:ptrace[2] también te permite establecer información en los procesos trazados (registros, etc). man:ptrace[2] es un estándar ampliamente disponible e implementado en la mayoría de UNIX(R) en todo el mundo.
10 days ago
User avatar None

Source string changed

Documentation / articles/linux-emulation/_index — Spanish

Many UNIX(R) derivates implement the man:ptrace[2] syscall in order to allow various tracking and debugging features. This facility enables the tracing process to obtain various information about the traced process, like register dumps, any memory from the process address space, etc. and also to trace the process like in stepping an instruction or between system entries (syscalls and traps). man:ptrace[2] also lets you set various information in the traced process (registers etc.). man:ptrace[2] is a UNIX(R)-wide standard implemented in most UNIX(R)es around the world.
10 days ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Spanish

The Linux(R) emulation layer is not complete, as some syscalls are not implemented properly and some are not implemented at all. The emulation layer employs a facility to mark unimplemented syscalls with the `DUMMY` macro. These dummy definitions reside in [.filename]#linux_dummy.c# in a form of `DUMMY(syscall);`, which is then translated to various syscall auxiliary files and the implementation consists of printing a message saying that this syscall is not implemented. The `UNIMPL` prototype is not used because we want to be able to identify the name of the syscall that was called to know what syscalls are more important to implement.
La capa de emulación de Linux(R) no es completa ya que algunas llamadas al sistema no están implementadas de forma adecuada y otras no están implementadas en absoluto. La capa de emulación utiliza un método para marcar las llamadas al sistema no implementadas con la macro `DUMMY`. Estas definiciones dummy se encuentran en [.filename]#linux_dummy.c# en la forma `DUMMY(syscall)`, que luego se traduce a varios ficheros auxiliares de llamadas al sistema y cuya implementación consiste en imprimir un mensaje diciendo que la llamada no está implementada. El prototipo `UNIMPL` no se utiliza porque queremos ser capaces de identificar el nombre de la llamada al sistema que fue invocada con el fin de saber qué llamadas al sistema son importantes de implementar.
10 days ago
User avatar None

Source string changed

Documentation / articles/linux-emulation/_index — Spanish

The Linux(R) emulation layer is not complete, as some syscalls are not implemented properly and some are not implemented at all. The emulation layer employs a facility to mark unimplemented syscalls with the `DUMMY` macro. These dummy definitions reside in [.filename]#linux_dummy.c# in a form of `DUMMY(syscall);`, which is then translated to various syscall auxiliary files and the implementation consists of printing a message saying that this syscall is not implemented. The `UNIMPL` prototype is not used because we want to be able to identify the name of the syscall that was called in order to know what syscalls are more important to implement.
10 days ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Spanish

`sched_bind` is an API used to bind a thread to a particular CPU for all the time it executes the code, until a `sched_unbind` function call does not unbind it. This feature has a key role in situations where you cannot trust the current state of CPUs (for example, at very early stages of boot), as you want to avoid your thread to migrate on inactive CPUs. Since `sched_bind` and `sched_unbind` manipulate internal scheduler structures, they need to be enclosed in `sched_lock` acquisition/releasing when used.
`sched_bind` es una API que se utiliza para vincular un hilo a una CPU en particular durante todo el tiempo que ejecuta el código, hasta que no lo desvincula la llamada a la función `sched_unbind`. Esta función tiene un papel clave en situaciones en las que no puedes confiar en el estado actual de las CPU (por ejemplo, en las primeras etapas del arranque), ya que deseas evitar que tu hilo migre a CPUs inactivas. Como `sched_bin` y `sched_unbind` manipulan las estructuras internas del planificador, es necesario que estén dentro de la adquisición/liberación `sched_lock` cuando se usan.
10 days ago
User avatar None

Source string changed

Documentation / articles/linux-emulation/_index — Spanish

`sched_bind` is an API used in order to bind a thread to a particular CPU for all the time it executes the code, until a `sched_unbind` function call does not unbind it. This feature has a key role in situations where you cannot trust the current state of CPUs (for example, at very early stages of boot), as you want to avoid your thread to migrate on inactive CPUs. Since `sched_bind` and `sched_unbind` manipulate internal scheduler structures, they need to be enclosed in `sched_lock` acquisition/releasing when used.
10 days ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Spanish

The FreeBSD kernel has been made preemptive basically to deal with interrupt threads. In fact, to avoid high interrupt latency, time-sharing priority threads can be preempted by interrupt threads (in this way, they do not need to wait to be scheduled as the normal path previews). Preemption, however, introduces new racing points that need to be handled, as well. Often, to deal with preemption, the simplest thing to do is to completely disable it. A critical section defines a piece of code (borderlined by the pair of functions man:critical_enter[9] and man:critical_exit[9], where preemption is guaranteed to not happen (until the protected code is fully executed). This can often replace a lock effectively but should be used carefully to not lose the whole advantage that preemption brings.
El kernel de FreeBSD se ha hecho preemptivo básicamente para tratar con hilos de interrupción. De hecho, para evitar una latencia de interrupción alta, los hilos de tiempo compartido con prioridad pueden ser reemplazados por hilos de interrupción (de esta manera, no necesitan esperar para ser programados como vistas previas de la ruta normal). Un kernel preemptivo, sin embargo, introduce nuevos puntos de carrera que también deben manejarse. A menudo, para hacer frente a la preemptividad, lo más sencillo es desactivarla por completo. Una sección crítica define un fragmento de código (delimitado por el par de funciones man:critical_enter[9] y man:critical_exit[9], donde se garantiza que la preemptividad no ocurrirá hasta que el código protegido se ejecute por completo). Esto a menudo puede reemplazar un lock de manera efectiva, pero debe usarse con cuidado para no perder toda la ventaja que brinda la preemptividad.
10 days ago
User avatar None

Source string changed

Documentation / articles/linux-emulation/_index — Spanish

The FreeBSD kernel has been made preemptive basically to deal with interrupt threads. In fact, in order to avoid high interrupt latency, time-sharing priority threads can be preempted by interrupt threads (in this way, they do not need to wait to be scheduled as the normal path previews). Preemption, however, introduces new racing points that need to be handled, as well. Often, in order to deal with preemption, the simplest thing to do is to completely disable it. A critical section defines a piece of code (borderlined by the pair of functions man:critical_enter[9] and man:critical_exit[9], where preemption is guaranteed to not happen (until the protected code is fully executed). This can often replace a lock effectively but should be used carefully in order to not lose the whole advantage that preemption brings.
10 days ago
Browse all translation changes