Project locked to follow the migration to Hugo/AsciiDoctor, sorry for the inconvenience and please wait a few days to continue with the translations.

The translation is temporarily closed for contributions due to maintenance, please come back later.
Language Translated Untranslated Untranslated words Checks Suggestions Comments
English This translation is used for source strings. This component is linked to the FreeBSD Doc (Archived)/articles_bsdl-gpl repository. This translation is locked. BSD-2-Clause-FreeBSD 20
Portuguese (Brazil) This component is linked to the FreeBSD Doc (Archived)/articles_bsdl-gpl repository. This translation is locked. BSD-2-Clause-FreeBSD 94% 5 263 25
Spanish This component is linked to the FreeBSD Doc (Archived)/articles_bsdl-gpl repository. This translation is locked. BSD-2-Clause-FreeBSD 94% 5 263 22
Start new translation
Please sign in to see the alerts.
Project website wiki.freebsd.org/DocTranslationOnWeblate
Instructions for translators

https://wiki.freebsd.org/DocTranslationOnWeblate Mailing list for translators: <<freebsd-translators@freebsd.org>

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-FreeBSD
Filemask articles/*/solid-state.po
Languages 3
Source strings 87
Source words 2,641
Source characters 19,259
Hosted strings 261
Hosted words 7,923
Hosted characters 57,777
Component locked a month ago
New strings to translate a month ago
New strings to translate a month ago
Resource update a month ago
To make it possible to enter a ports directory and successfully run <command>make</command> <_:buildtarget-1/>, we must create a packages directory on a non-memory filesystem that will keep track of our packages across reboots. BecauseAs it is necessary to mount your filesystems as read-write for the installation of a package anyway, it is sensible to assume that an area on the flash media can also be used for package information to be written to.
a month ago
However, even a small installation of FreeBSD using normal installation procedures can produce a system in size of greater than 200 megabytes. Because mMost people will be using smaller flash memory devices (128 megabytes is considered fairly large - 32 or even 16 megabytes is common), so an installation using normal mechanisms is not possible—there is simply not enough disk space for even the smallest of conventional installations.
a month ago
BecausSince ATA compatible compact-flash cards are seen by FreeBSD as normal IDE hard drives, you could theoretically install FreeBSD from the network using the kern and mfsroot floppies or from a CD.
a month ago
All embedded FreeBSD systems that use flash memory as system disk will be interested in memory disks and memory filesystems. BecauseAs a result of the limited number of writes that can be done to flash memory, the disk and the filesystems on the disk will most likely be mounted read-only. In this environment, filesystems such as <filename>/tmp</filename> and <filename>/var</filename> are mounted as memory filesystems to allow the system to create logs and update counters and temporary files. Memory filesystems are a critical component to a successful solid state FreeBSD implementation.
a month ago
Resource update a month ago
User avatar None

Source string changed

FreeBSD Doc (Archived) / articles_solid-stateSpanish

To make it possible to enter a ports directory and successfully run <command>make</command> <_:buildtarget-1/>, we must create a packages directory on a non-memory filesystem that will keep track of our packages across reboots. BecauseAs it is necessary to mount your filesystems as read-write for the installation of a package anyway, it is sensible to assume that an area on the flash media can also be used for package information to be written to.
a month ago
Browse all component changes

Daily activity

Daily activity

Weekly activity

Weekly activity