NetBSD/usr.sbin/sysinst/msg.pm.es

167 lines
6.9 KiB
Erlang
Raw Normal View History

/* $NetBSD: msg.pm.es,v 1.4 2020/11/05 11:10:11 martin Exp $ */
Rework internal data structures and "interfaces to user interface" functions to get rid of all disklabel assumptions. Previously (even for GPT partitioning) struct disklabel was used, which obviously breaks large disk setups. Also many MD parts and parts of the user interface assumed (a) a struct disklabel is used internally to store partitioning information and (b) partitions are named 'a' ... $MAXPART. Get rid of this and replace it with a quite abstract interface that should be able to deal with all variants in partition storage: - partitions are stored in a (partly abstract) struct disk_partitions and most parts of it are only accessed via accessor functions provided by a "partitioning scheme". - implement partitioning schemes for MBR, disklabel and GPT (with likely RDB [amiga] and Apple Partition Map [mac*] to follow soon) - partitioning schemes may be cascaded, e.g. on x86 when using MBR as "outer partitions", we have disklabel as "inner partitions". - all user interface goes via accessor functions in the partitioning scheme, some of which return pointers to special user interface descriptors (e.g. to allow editing partition flags, which are scheme specific) Overall the user interface changes (in this initial step) are minimal but noticable. A new Anita is needed for automatic test setups - many thanks to Andreas Gustafsson for lots of early testing and a new Anita version, and to Manuel Bouyer for cooperation and tests of the Anita release. This work was sponsored by The NetBSD Foundation, Inc.
2019-06-12 09:20:17 +03:00
/*
* Copyright 1997 Piermont Information Systems Inc.
* All rights reserved.
*
* Written by Philip A. Nelson for Piermont Information Systems Inc.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. The name of Piermont Information Systems Inc. may not be used to endorse
* or promote products derived from this software without specific prior
* written permission.
*
* THIS SOFTWARE IS PROVIDED BY PIERMONT INFORMATION SYSTEMS INC. ``AS IS''
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL PIERMONT INFORMATION SYSTEMS INC. BE
* LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
* THE POSSIBILITY OF SUCH DAMAGE.
*
*/
/* extended partition manager message catalog -- Spanish, machine independent */
message fillzeros {Llenar con ceros}
message fillrandom {Llene los datos al azar}
message raid0 {0 - Sin paridad, creaci<EFBFBD>n de bandas s<EFBFBD>lo es simple.}
message raid1 {1 - Creaci<EFBFBD>n de reflejos. La paridad es el espejo.}
message raid4 {4 - Striping con paridad almacenada en el <EFBFBD>ltimo componente. component.}
message raid5 {5 - Striping con paridad en los componentes de todos. components.}
message wannaunblock {El dispositivo est<EFBFBD> bloqueado. <EFBFBD>Quiere forzar a desbloquear y continuar? unblock it and continue?}
message wannatry {<EFBFBD>Quieres probar?}
message create_cgd {Crear cifrado de volumen (CGD)}
message create_vnd {Crear imagen de disco virtual (VND)}
Rework internal data structures and "interfaces to user interface" functions to get rid of all disklabel assumptions. Previously (even for GPT partitioning) struct disklabel was used, which obviously breaks large disk setups. Also many MD parts and parts of the user interface assumed (a) a struct disklabel is used internally to store partitioning information and (b) partitions are named 'a' ... $MAXPART. Get rid of this and replace it with a quite abstract interface that should be able to deal with all variants in partition storage: - partitions are stored in a (partly abstract) struct disk_partitions and most parts of it are only accessed via accessor functions provided by a "partitioning scheme". - implement partitioning schemes for MBR, disklabel and GPT (with likely RDB [amiga] and Apple Partition Map [mac*] to follow soon) - partitioning schemes may be cascaded, e.g. on x86 when using MBR as "outer partitions", we have disklabel as "inner partitions". - all user interface goes via accessor functions in the partitioning scheme, some of which return pointers to special user interface descriptors (e.g. to allow editing partition flags, which are scheme specific) Overall the user interface changes (in this initial step) are minimal but noticable. A new Anita is needed for automatic test setups - many thanks to Andreas Gustafsson for lots of early testing and a new Anita version, and to Manuel Bouyer for cooperation and tests of the Anita release. This work was sponsored by The NetBSD Foundation, Inc.
2019-06-12 09:20:17 +03:00
message create_vg {Crear grupo de vol<EFBFBD>menes (LVM VG)}
message create_lv {Crear vol<EFBFBD>menes l<EFBFBD>gicos}
message create_raid {Crear RAID por software}
message updpmlist {Actualizar lista de dispositivos}
message savepm {Guardar los cambios}
message pmblocked {BLOQUEADO}
message pmunchanged {SIN USO}
message pmused {UTILIZA}
message pmmounted {(montado)}
message pmunused {(sin usar)}
message pmgptdisk {Disco con GPT}
message finishpm {Finalizar el particionado}
message limitcount {L<EFBFBD>mite para el n<EFBFBD>mero de dispositivos se lleg<EFBFBD>!}
message invaliddev {No v<EFBFBD>lido dispositivo!}
message avdisks {Discos disponibles:}
message nofreedev {No se puede asignar nodo de dispositivo!}
message partman_header
{Partition Manager. Todos los discos, particiones y etc muestra all<EFBFBD>.
Si desea utilizar RAID, LVM o CGD, siga estos pasos:
1) Crear particiones con el tipo necesario;
2) Crear RAID / LVM VG / CGD el uso de estas particiones; 3) Gu<EFBFBD>rdalo;
4) Crear particiones de vol<EFBFBD>menes RAID / CGD o l<EFBFBD>gico de LVM.}
/* used to form strings like: "vnd0 on /var/tmp/disk1.img" */
message pm_menu_on {on}
/* Called with: Example
* $0 = device name raid0
* $1 = raid level 1
*/
message raid_menufmt {$0 (nivel $1)}
message raid_err_menufmt {RAID VACIO!}
message raid_disks_fmt {Discos}
message raid_spares_fmt {Piezas de recambio}
message raid_level_fmt {RAID de nivel}
message raid_numrow_fmt {numRow}
message raid_numcol_fmt {numCol}
message raid_numspare_fmt {numSpare}
message raid_sectpersu_fmt {sectPerSU}
message raid_superpar_fmt {SUsPerParityUnit}
message raid_superrec_fmt {SUsPerReconUnit}
message raid_nomultidim {Matrices multidimensionales no son compatibles!}
message raid_numrow_ask {numRow?}
message raid_numcol_ask {numCol?}
message raid_numspare_ask {numSpare?}
message raid_sectpersu_ask {sectPerSU?}
message raid_superpar_ask {SUsPerParityUnit?}
message raid_superrec_ask {SUsPerReconUnit?}
message raid_disks {Los discos en RAID}
message vnd_err_menufmt {CAMINO NO DEFINIDO!}
message vnd_assign {ASSIGN}
message vnd_path_fmt {Ruta del archivo}
message vnd_assign_fmt {Create new image}
message vnd_size_fmt {Tama<EFBFBD>o}
message vnd_ro_fmt {S<EFBFBD>lo lectura}
message vnd_geom_fmt {Establecer la geometr<EFBFBD>a de la mano}
message vnd_bps_fmt {Bytes por sector}
message vnd_spt_fmt {Sectores por pista}
message vnd_tpc_fmt {Pistas por cilindro}
message vnd_cyl_fmt {Cilindros}
message vnd_path_ask {Ruta de acceso?}
message vnd_size_ask {Tama<EFBFBD>o (MB)?}
message vnd_bps_ask {Bytes por sector?}
message vnd_spt_ask {Sectores por pista?}
message vnd_tpc_ask {Pistas por cilindro?}
message vnd_cyl_ask {Cilindros}
message cgd_err_menufmt {DISCO NO SE DEFINE!}
message cgd_dev_fmt {Dispositivo de base}
message cgd_enc_fmt {Encriptaci<EFBFBD>n}
message cgd_key_fmt {Tama<EFBFBD>o de la clave}
message cgd_iv_fmt {Algoritmo IV}
message cgd_keygen_fmt {La generaci<EFBFBD>n de claves}
message cgd_verif_fmt {M<EFBFBD>todo de verificaci<EFBFBD>n}
message lvm_disks {Discos en VG}
message lvm_err_menufmt {VACIAR VG!}
message lvm_disks_fmt {PV's}
message lvm_name_fmt {Nombre}
message lvm_maxlv_fmt {MaxLogicalVolumes}
message lvm_maxpv_fmt {MaxPhysicalVolumes}
message lvm_extsiz_fmt {PhysicalExtentSize}
message lvm_name_ask {Nombre?}
message lvm_maxlv_ask {MaxLogicalVolumes?}
message lvm_maxpv_ask {MaxPhysicalVolumes?}
message lvm_extsiz_ask {PhysicalExtentSize (MB)?}
message lvmlv_menufmt {El volumen l<EFBFBD>gico}
message lvmlv_name_fmt {Nombre}
message lvmlv_size_fmt {Tama<EFBFBD>o}
message lvmlv_ro_fmt {S<EFBFBD>lo lectura}
message lvmlv_cont_fmt {Contigua}
message lvmlv_extnum_fmt {LogicalExtentsNumber}
message lvmlv_minor_fmt {Menor n<EFBFBD>mero}
message lvmlv_mirrors_fmt {Espejos}
message lvmlv_regsiz_fmt {MirrorLogRegionSize}
message lvmlv_pers_fmt {N<EFBFBD>mero de persistente menor}
message lvmlv_readahsect_fmt {ReadAheadSectors}
message lvmlv_stripes_fmt {Rayas}
message lvmlv_stripesiz_fmt {Stripesize}
message lvmlv_zero_fmt {Puesta a cero de la primera KB}
message lvmlv_name_ask {Nombre?}
message lvmlv_size_ask {Tama<EFBFBD>o (MB)?}
message lvmlv_extnum_ask {LogicalExtentsNumber?}
message lvmlv_minor_ask {N<EFBFBD>mero menor de edad?}
message lvmlv_mirrors_ask {Espejos?}
message lvmlv_regsiz_ask {MirrorLogRegionSize?}
message lvmlv_readahsect_ask {ReadAheadSectors?}
message lvmlv_stripes_ask {Rayas?}
message notsupported {Operaci<EFBFBD>n no admitida!}
message edit_parts {Editar particiones}
message switch_parts {Switch partitioning scheme}
message fmtasraid {Formato como RAID}
message fmtaslvm {Formato como LVM PV}
message encrypt {Cifrar (CGD)}
message erase {Borrado seguro}
message undo {Deshacer los cambios}
message unconfig {Desconfigurar}
message edit {Editar}
message doumount {Fuerza umount}