Translation Information

Project website docs.freebsd.org/en
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
Translation license BSD 2-Clause "Simplified" License
Filemask documentation/content/*/articles/freebsd-releng/_index.po
Translation file Download documentation/content/es/articles/freebsd-releng/_index.po
User avatar None

Automatic translation

Documentation / articles/freebsd-releng/_indexSpanish

Once the builds have completed, additional helper scripts are available to generate development snapshot emails which are sent to the `freebsd-snapshots@freebsd.org` mailing list:
Una vez que se han completado las compilaciones, se dispone de guiones auxiliares adicionales para generar correos electrónicos de instantáneas de desarrollo que se envían a la lista de correo <literal>freebsd-snapshots@freebsd.org</literal>:
yesterday
New contributor yesterday
User avatar None

Automatic translation

Documentation / articles/freebsd-releng/_indexSpanish

Assuming these filesystem paths, [.filename]#thermite.sh# would be invoked as:
Asumiendo estas rutas de sistemas de archivos, <filename>thermite.sh</filename> sería invocado como:
yesterday
New contributor yesterday
User avatar None

Automatic translation

Documentation / articles/freebsd-releng/_indexSpanish

Each branch also has its own [.filename]#builds-X.conf# configuration, which is used by [.filename]#thermite.sh#. The [.filename]#thermite.sh# script iterates through each ${revision}, ${TARGET_ARCH}, ${KERNCONF}, and ${type} value, creating a master list of what to build. However, a given combination from the list will only be built if the respective configuration file exists, which is where the naming scheme above is relevant.
Cada rama también tiene su propia configuración <filename>builds-X.conf</filename>, que es usada por <filename>thermite.sh</filename>. El script <filename>thermite.sh</filename> itera a través de cada valor ${revision}, ${TARGET_ARCH}, ${KERNCONF}, y ${type}, creando una lista maestra de lo que hay que construir. Sin embargo, una determinada combinación de la lista sólo se construirá si existe el respectivo archivo de configuración, que es donde el esquema de denominación anterior es relevante.
yesterday
New contributor yesterday
User avatar None

Automatic translation

Documentation / articles/freebsd-releng/_indexSpanish

Each architecture and individual kernel have their own configuration file used by [.filename]#release.sh#. Each branch has its own [.filename]#defaults-X.conf# configuration which contains entries common throughout each architecture, where overrides or special variables are set and/or overridden in the per-build files.
Cada arquitectura y kernel individual tiene su propio archivo de configuración usado por <filename>release.sh</filename>. Cada rama tiene su propia configuración <filename>defaults-X.conf</filename>, que contiene entradas comunes en cada arquitectura, donde se establecen y/o anulan las anulaciones o variables especiales en los archivos por construcción.
yesterday
New contributor yesterday
User avatar None

Automatic translation

Documentation / articles/freebsd-releng/_indexSpanish

# release.sh configuration for powerpc/powerpc64
CHROOTDIR="/scratch-powerpc64"
TARGET="powerpc"
TARGET_ARCH="powerpc64"
KERNEL="GENERIC64"
# release.sh configuration for powerpc/powerpc64
CHROOTDIR="/scratch-powerpc64"
TARGET="powerpc"
TARGET_ARCH="powerpc64"
KERNEL="GENERIC64"
yesterday
New contributor yesterday
Browse all translation changes

Statistics

Percent Strings Words Chars
Total 194 4,181 32,346
Translated 19% 38 291 2,029
Needs editing 6% 13 524 3,508
Failing checks 0% 1 9 140

Last activity

Last change April 10, 2021, 10:54 a.m.
Last author Anonymous

Daily activity

Daily activity

Weekly activity

Weekly activity