Source string Read only

(itstool) path: note/para
Context English State
If the URL to the package repository is: <literal></literal>, then the repository configuration file in <filename>/usr/local/etc/pkg/repos/custom.conf</filename> would look like:
custom: {
url: "<replaceable></replaceable>",
enabled: yes,
Post-Installation Considerations
Regardless of whether the software was installed from a binary package or port, most third-party applications require some level of configuration after installation. The following commands and locations can be used to help determine what was installed with the application.
Most applications install at least one default configuration file in <filename>/usr/local/etc</filename>. In cases where an application has a large number of configuration files, a subdirectory will be created to hold them. Often, sample configuration files are installed which end with a suffix such as <filename>.sample</filename>. The configuration files should be reviewed and possibly edited to meet the system's needs. To edit a sample file, first copy it without the <filename>.sample</filename> extension.
Applications which provide documentation will install it into <filename>/usr/local/share/doc</filename> and many applications also install manual pages. This documentation should be consulted before continuing.
Some applications run services which must be added to <filename>/etc/rc.conf</filename> before starting the application. These applications usually install a startup script in <filename>/usr/local/etc/rc.d</filename>. See <link linkend="configtuning-starting-services">Starting Services</link> for more information.
By design, applications do not run their startup script upon installation, nor do they run their stop script upon deinstallation or upgrade. This decision is left to the individual system administrator.
Users of <citerefentry><refentrytitle>csh</refentrytitle><manvolnum>1</manvolnum></citerefentry> should run <command>rehash</command> to rebuild the known binary list in the shells <envar>PATH</envar>.
Use <command>pkg info</command> to determine which files, man pages, and binaries were installed with the application.
Dealing with Broken Ports
When a port does not build or install, try the following:
Search to see if there is a fix pending for the port in the <link xlink:href="@@URL_RELPREFIX@@/support.html">Problem Report database</link>. If so, implementing the proposed fix may fix the issue.
Ask the maintainer of the port for help. Type <command>make maintainer</command> in the ports skeleton or read the port's <filename>Makefile</filename> to find the maintainer's email address. Remember to include the <literal>$FreeBSD:</literal> line from the port's <filename>Makefile</filename> and the output leading up to the error in the email to the maintainer.
Some ports are not maintained by an individual but instead by a group maintainer represented by a <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/mailing-list-faq/article.html">mailing list</link>. Many, but not all, of these addresses look like <email role="nolink">freebsd-<replaceable>listname</replaceable></email>. Please take this into account when sending an email.
In particular, ports maintained by <email role="nolink"></email> are not maintained by a specific individual. Instead, any fixes and support come from the general community who subscribe to that mailing list. More volunteers are always needed!
If there is no response to the email, use Bugzilla to submit a bug report using the instructions in <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/problem-reports/article.html">Writing FreeBSD Problem Reports</link>.
Fix it! The <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/porters-handbook/index.html">Porter's Handbook</link> includes detailed information on the ports infrastructure so that you can fix the occasional broken port or even submit your own!
Install the package instead of the port using the instructions in <xref linkend="pkgng-intro"/>.
The X Window System
An installation of FreeBSD using <application>bsdinstall</application> does not automatically install a graphical user interface. This chapter describes how to install and configure <application>Xorg</application>, which provides the open source X Window System used to provide a graphical environment. It then describes how to find and install a desktop environment or window manager.
Users who prefer an installation method that automatically configures the <application>Xorg</application> should refer to <link xlink:href="">GhostBSD</link>, <link xlink:href="">MidnightBSD</link> or <link xlink:href="">NomadBSD</link>.
For more information on the video hardware that <application>Xorg</application> supports, refer to the <link xlink:href=""></link> website.
The various components of the X Window System, and how they interoperate.
How to install and configure <application>Xorg</application>.
How to install and configure several window managers and desktop environments.
How to use <trademark class="registered">TrueType</trademark> fonts in <application>Xorg</application>.
How to set up your system for graphical logins (<application>XDM</application>).
Know how to install additional third-party software as described in <xref linkend="ports"/>.
While it is not necessary to understand all of the details of the various components in the X Window System and how they interact, some basic knowledge of these components can be useful.


No matching activity found.

Browse all component changes

Things to check

Multiple failing checks

The translations in several languages have failing checks



English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: note/para
Source string location
String age
a year ago
Source string age
a year ago
Translation file
books/handbook.pot, string 1837