The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: answer/para
Context English State
This means that a function that may sleep was called while a mutex (or other unsleepable) lock was held.
The reason this is an error is because mutexes are not intended to be held for long periods of time; they are supposed to only be held to maintain short periods of synchronization. This programming contract allows device drivers to use mutexes to synchronize with the rest of the kernel during interrupts. Interrupts (under FreeBSD) may not sleep. Hence it is imperative that no subsystem in the kernel block for an extended period while holding a mutex.
To catch such errors, assertions may be added to the kernel that interact with the <citerefentry><refentrytitle>witness</refentrytitle><manvolnum>4</manvolnum></citerefentry> subsystem to emit a warning or fatal error (depending on the system configuration) when a potentially blocking call is made while holding a mutex.
In summary, such warnings are non-fatal, however with unfortunate timing they could cause undesirable effects ranging from a minor blip in the system's responsiveness to a complete system lockup.
For additional information about locking in FreeBSD see <citerefentry><refentrytitle>locking</refentrytitle><manvolnum>9</manvolnum></citerefentry>.
buildworld
installworld
Why does <_:buildtarget-1/>/<_:buildtarget-2/> die with the message <errorname>touch: not found</errorname>?
This error does not mean that the <citerefentry><refentrytitle>touch</refentrytitle><manvolnum>1</manvolnum></citerefentry> utility is missing. The error is instead probably due to the dates of the files being set sometime in the future. If the CMOS clock is set to local time, run <command>adjkerntz -i</command> to adjust the kernel clock when booting into single-user mode.
User Applications
Where are all the user applications?
Refer to <link xlink:href="@@URL_RELPREFIX@@/ports/index.html">the ports page</link> for info on software packages ported to FreeBSD.
Most ports should work on all supported versions of FreeBSD. Those that do not are specifically marked as such. Each time a FreeBSD release is made, a snapshot of the ports tree at the time of release is also included in the <filename>ports/</filename> directory.
FreeBSD supports compressed binary packages to easily install and uninstall ports. Use <citerefentry><refentrytitle>pkg</refentrytitle><manvolnum>7</manvolnum></citerefentry> to control the installation of packages.
How do I download the Ports tree? Should I be using Subversion?
Any of the methods listed here work:
Use portsnap for most use cases. Refer to <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/ports-using.html">Using the Ports Collection</link> for instructions on how to use this tool.
Use Subversion if custom patches to the ports tree are needed or if running FreeBSD-CURRENT. Refer to <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/svn.html">Using Subversion</link> for details.
Why can I not build this port on my 11.<replaceable>X</replaceable> -, or 12.<replaceable>X</replaceable> -STABLE machine?
If the installed FreeBSD version lags significantly behind <emphasis>-CURRENT</emphasis> or <emphasis>-STABLE</emphasis>, update the Ports Collection using the instructions in <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/ports-using.html">Using the Ports Collection</link>. If the system is up-to-date, someone might have committed a change to the port which works for <emphasis>-CURRENT</emphasis> but which broke the port for <emphasis>-STABLE</emphasis>. <link xlink:href="https://bugs.FreeBSD.org/submit/">Submit</link> a bug report, since the Ports Collection is supposed to work for both the <emphasis>-CURRENT</emphasis> and <emphasis>-STABLE</emphasis> branches.
I just tried to build <filename>INDEX</filename> using <command>make index</command>, and it failed. Why?
First, make sure that the Ports Collection is up-to-date. Errors that affect building <filename>INDEX</filename> from an up-to-date copy of the Ports Collection are high-visibility and are thus almost always fixed immediately.
There are rare cases where <filename>INDEX</filename> will not build due to odd cases involving <varname>OPTIONS_SET</varname> being set in <filename>make.conf</filename>. If you suspect that this is the case, try to make <filename>INDEX</filename> with those variables turned off before reporting it to <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports">FreeBSD ports mailing list</link>.
I updated the sources, now how do I update my installed ports?
FreeBSD does not include a port upgrading tool, but it does have some tools to make the upgrade process somewhat easier. Additional tools are available to simplify port handling and are described the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/ports-using.html">Upgrading Ports</link> section in the FreeBSD Handbook.
Do I need to recompile every port each time I perform a major version update?
Yes! While a recent system will run with software compiled under an older release, things will randomly crash and fail to work once other ports are installed or updated.
When the system is upgraded, various shared libraries, loadable modules, and other parts of the system will be replaced with newer versions. Applications linked against the older versions may fail to start or, in other cases, fail to function properly.
For more information, see <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html#freebsdupdate-upgrade">the section on upgrades</link> in the FreeBSD Handbook.
Do I need to recompile every port each time I perform a minor version update?
In general, no. FreeBSD developers do their utmost to guarantee binary compatibility across all releases with the same major version number. Any exceptions will be documented in the Release Notes, and advice given there should be followed.

Loading…

No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: answer/para
Flags
read-only
Source string location
book.translate.xml:2264
String age
a year ago
Source string age
a year ago
Translation file
books/faq.pot, string 366