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 Nov. 8, 2025, 4:33 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 396 12,239 77,384
Translated 99% 394 99% 12,152 99% 76,771
Needs editing 1% 2 1% 87 1% 613
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
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

0 changes 0 changes 0 changes 0 changes 10 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

12,239
Hosted words
396
Hosted strings
99%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
−1%
Translated
+100%
+100%
Contributors
—
User avatar None

New strings to translate

Documentation / articles/linux-emulation/_index — Spanish

2 new strings to translate appeared to the translation. 4 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. 4 days ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Spanish

Marshall Kirk McKusick - George V. Neville-Neil. Design and Implementation of the FreeBSD operating system. Addison-Wesley, 2005.
Marshall Kirk McKusick - George V. Nevile-Neil. Diseño e implementación del sistema operativo FreeBSD. Addison-Wesley, 2005.
4 days ago
User avatar None

Source string changed

Documentation / articles/linux-emulation/_index — Spanish

Marshall Kirk McKusick - George V. Neville-Neil. Design and Implementation of the FreeBSD operating system. Addison-Wesley, 2005.
4 days ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Spanish

The locking is implemented to be per-subsystem because we do not expect a lot of contention on these. There are two locks: `emul_lock` used to protect manipulating of `linux_emuldata` and `emul_shared_lock` used to manipulate `linux_emuldata_shared`. The `emul_lock` is a nonsleepable blocking mutex while `emul_shared_lock` is a sleepable blocking `sx_lock`. Due to of the per-subsystem locking we can coalesce some locks and that is why the em_find offers the non-locking access.
El mecanismo de bloqueo se implementa por cada subsistema porque no esperamos en ellos mucha contención. Hay dos locks: `emul_lock` se usa para manipular de forma segura `linux_emuldata` y `emul_shared_lock` se usa para manipular `linux_emuldata_shared`. `emul_lcok` es un mutex con el que no se puede dormir mientras que `emul_shared_lock` es un `sx_lock` con el que se puede dormir. Debido al mecanismo de bloqueo por subsistema podemos juntar algunos locks y por eso em_find proporciona acceso sin necesidad de bloqueos.
4 days ago
User avatar None

Source string changed

Documentation / articles/linux-emulation/_index — Spanish

The locking is implemented to be per-subsystem because we do not expect a lot of contention on these. There are two locks: `emul_lock` used to protect manipulating of `linux_emuldata` and `emul_shared_lock` used to manipulate `linux_emuldata_shared`. The `emul_lock` is a nonsleepable blocking mutex while `emul_shared_lock` is a sleepable blocking `sx_lock`. Due to of the per-subsystem locking we can coalesce some locks and that is why the em _find offers the non-locking access.
4 days ago
User avatar None

String updated in the repository

Documentation / articles/linux-emulation/_index — Spanish

Common UNIX(R) API defines a syscall as a way to issue commands from a user space process to the kernel. The most common implementation is either by using an interrupt or specialized instruction (think of `SYSENTER`/`SYSCALL` instructions for ia32). Syscalls are defined by a number. For example in FreeBSD, the syscall number 85 is the man:swapon[2] syscall and the syscall number 132 is man:mkfifo[2]. Some syscalls need parameters, which are passed from the user-space to the kernel-space in various ways (implementation dependent). Syscalls are synchronous.
La API común de UNIX(R) define una syscall como una forma de emitir órdenes desde un proceso del espacio de usuario al kernel. La implementación más común es mediante el uso de una interrupción o una instrucción especializada (piense en las instrucciones `SYSENTER`/`SYSCALL` para ia32). Las syscalls se definen mediante un número. Por ejemplo en FreeBSD, la llamada al sistema número 85 es la llamada al sistema man:swapon[2] y la llamada al sistema número 132 es man:mkfifo[2]. Algunas syscalls necesitan parámetros, que se pasan del espacio de usuario al espacio del núcleo de varias maneras (dependiendo de la implementación). Las syscalls son síncronas.
4 days ago
User avatar None

Committed changes

Documentation / articles/linux-emulation/_index — Spanish

Committed changes a year ago
User avatar juanda097

Translation changed

Documentation / articles/linux-emulation/_index — Spanish

Common UNIX(R) API defines a syscall as a way to issue commands from a user space process to the kernel. The most common implementation is either by using an interrupt or specialized instruction (think of `SYSENTER`/`SYSCALL` instructions for ia32). Syscalls are defined by a number. For example in FreeBSD, the syscall number 85 is the man:swapon[2] syscall and the syscall number 132 is man:mkfifo[2]. Some syscalls need parameters, which are passed from the user-space to the kernel-space in various ways (implementation dependent). Syscalls are synchronous.
ElLa API común de UNIX(R) define llamadas al sistemauna syscall como una forma de ejecutar comandos en el kernel desmitir órdenes desde un proceso del espacio de usuario. al kernel. La implementación más habitual es utilizarcomún es mediante el uso de una interrupción o una instrucción especializada (comopiense en las instrucciones `SYSENTER`/`SYSCALL` enpara ia32). Las llamadas al sistemasyscalls se definen mediante un número. Por ejemplo en FreeBSD, la llamada al sistema número 85 es la llamada al sistema de man:swapon[2] y la llamada al sistema número 132 es man:mkfifo[2]. Algunas llamadas al sistemasyscalls necesitan parámetros, que sone pasados desden del espacio de usuario al espacio de kernell núcleo de varias formmaneras (dependiendo de la implementación). Las llamadas al sistemasyscalls son síncronas.
a year ago
User avatar None

New string to translate

Documentation / articles/linux-emulation/_index — Spanish

1 new string to translate appeared in the translation. a year ago
Browse all translation changes