Goals and Features
What's New in 9.2
PC-BSD® for Linux Users
Partitioning the Hard Drive
Burning the Installation Media
PC-BSD® Live Mode
Starting the PC-BSD® Installation
Language Selection Screen
System Selection Screen
Disk Selection Screen
Installation Progress Screen
Installation Finished Screen
Post Installation Configuration and Installation Troubleshooting
Booting Into PC-BSD®
Time Zone Selection Screen
Set Root Password Screen
Create a User Screen
Connect to a Wireless Network
Post Install Finished Screen
Advanced Installation Topics
Install a Server
Multiple Boot Environments
PC-BSD® supports a feature of ZFS known as multiple boot environments (BEs). With multiple boot environments, the process of updating software becomes a low-risk operation as you can backup your current boot environment before upgrading or making software updates to your system. If needed, you also have the option of booting into a backup boot environment. For example:
Managing Boot Environments
Boot environments are managed with the beadm command which must be run as the superuser. The following example creates a BE named beforeupgrade. The new BE is a clone of the current BE, the ZFS environment that you booted into.
beadm create beforeupgrade Created successfully
To view all BEs, use the list command
BE Active Mountpoint Space Policy Created default NR / 6.05G static 2012-07-09 05:06beforeupgrade - - 1K static 2012-07-10 12:25
The possible flags in the "Active" field are as follows:
In this example, the current BE is called default, it is active now, and at next reboot; and it is mounted. The newly created beforeupgrade BE exists, but is inactive and unmounted. To activate the new BE:
beadm activate beforeupgrade
Activated successfully beadm list BE Active Mountpoint Space Policy Created default N / 64.5K static 2012-07-09 05:06beforeupgrade R - 6.05G static 2012-07-10 12:25
The flags now indicate that the system is currently booted into default, but at next boot the system will boot into beforeupgrade. Only one boot environment can be active at a time.
Creating an Automated Installation with pc-sysinstall
Enlightenmentis a lean, fast, modular, and extensible window manager. It provides a desktop for launching applications, managing windows, and doing other system tasks like suspending, reboots, and managing files.
The first time you run Enlightenment, you will be prompted to select your Language, then either a touchscreen or a standard computer profile. You will then be prompted to select the size of title bars, the type of window focus, and whether or not to use compositing. If in doubt, you can select the defaults by pressing "Next" at each initial configuration screen.
Figure 6.6a shows a screenshot of Enlightenment running a standard computer profile on PC-BSD® 9.2. The icon on the far left of the iBar has been clicked in order to access the applications menu.
Enlightenment is very customizable. Thedescribes how to configure windows, shelves, menus, wallpaper, and much more.
is an extremely light window manager. It does not support window decorations or icons and uses keyboard shortcuts to access xterms in order to run applications from the command line. Figure 6.7a shows a screenshot of evilwm running on PC-BSD® 9.2.
Notice that there are no icons, nor is there a system tray, an application panel, or window buttons. An xterm has been opened using Ctrl+Alt+Enter and shows the output of the ps command.
The keyboard shortcuts for manipulating windows are listed on.
To exit evilwm and return to the login screen, type killall evilwm within an xterm.
Installing Applications and Keeping PC-BSD® Updated
Meta Package Manager
Create Your Own PBI Repository
Active Directory & LDAP
Adobe Flash Player preferences
Java, Flash, and Fonts
Files and File Sharing
is open source software that allows you to create your own cloud storage. This allows you to share data, contacts, and calendars with other devices and users.
In PC-BSD®, you can create your own private cloud service by installing ownCloud either into a traditional jail that you created using Warden® or into a TrueOS® installation. For security reasons, installing ownCloud directly onto a desktop installation is not recommended, as the web and database services it requires may expose the desktop to security vulnerabilities. If you are installing ownCloud on a PC-BSD® system, create a traditional jail as it isolates the software installed into the jail from your desktop operating system.
Install and Start the Required Services
If you are installing ownCloud into a traditional jail, make sure that the jail has been started, then go to the “Tools” tab of the jail and click the “Package Manager” button as seen in the example in Figure 9.9a.
Check the boxes for databases ➜ mysql56-server, lang ➜ php55, and www ➜ apache24, then click the “Apply” button to install these packages.
Once installed, go to Tools ➜ Service Manager which will open the screen shown in Figure 9.9b. Highlight the apache22 service and click the "Enable Service" button and then the "Start" button. Repeat for the mysql service.
Verify that you can reach the web server by typing the IP address of the jail into a web browser. You should receive an "It works!" message. You will need to first allow incoming TCP port 80 on the jail interface using Firewall Manager if you use a web browser on a different computer.
If you are installing ownCloud onto a TrueOS® system, you will need to create the jail and install the dependencies from the command line. When creating the jail, specify the jail IP address and hostname as seen in this example:
warden create 10.0.0.1 owncloudjail --startauto
pc-metapkgmanager --pkgset warden --chroot /usr/jails/10.0.0.1 add MySQL,Apache,
Once the software is installed, access the jail by its IP address in order to edit the /etc/rc.conf file within the jail so that the required services start when the jail is available:
warden chroot 10.0.0.1 vi /etc/rc.conf
Add these two lines to that file:
Save your edits then start the services:
Verify that you can reach the web server by typing the IP address of the jail into a web browser. You should receive a "It works!" message. You will need to first edit /etc/pf.conf in order to allow incoming TCP port 80 using if you use a web browser on a different computer. An example would be to add a line to the "Nic specific rules" section:
pass in quick on re0 proto tcp from any to (re0) port 80 keep state
You may wish to replace any with just the IP addresses of the systems on your network. re0 should be replaced with the interface used by the jail.
You are now ready to download and configure ownCloud. If you are using a traditional jail on your desktop, go to Tools -> Launch Terminal to access the jail's command line. If you are using TrueOS®, use the warden chroot command to access the command line of the jail.
Once at the command line of the jail, download ownCloud into the Apache data directory.
cd /usr/local/www/apache24/data fetch http://download.owncloud.com/download/2012.4.5.12/owncloud-2012.4.5.12-enterprise.tar.bz2 tar xzvf owncloud-2012.4.5.12-enterprise.tar.bz2 chown -R www:www owncloud
Next, configure the MySQL database, substituting ocuser and mypass with the username and password that you wish to use:
mysql -u root mysql> create database owncloud; mysql> grant all on owncloud.* to ocuser@localhost identified by "mypass"; mysql> quit
Next, add the required PHP options to Apache. Open /usr/local/etc/apache24/httpd.conf in an editor and look for this line:
#AddType application/x-gzip .tgz
Add the following lines directly below that line:
AddType application/x-httpd-php .php AddType application/x-httpd-php-source .phps
Then, look for the following section:
<IfModule dir_module> DirectoryIndex index.html </IfModule>
and change it to:
<IfModule dir_module> DirectoryIndex index.html index.php </IfModule>
Save your changes and restart the Apache and MySQL services.
Test your changes from a web browser by adding "owncloud" to the end of the IP address of the jail. For example, type http://10.0.0.1/owncloud/. You should see the setup screen shown in Figure 9.9c.
Input the name of the user and password that will be used to administer ownCloud, then click the " "Advanced" button. In the advanced settings, click the "MySQL" tab and input the MySQL username, password, and database name that you configured previously. Click the “Finish setup” button to save your changes and enter your new cloud interface -- shown in Figure 9.9d.
Click the left panel of the interface to access a type of media. For example, if you click "Files" and then the "New" button, you can upload a file, folder, or from a URL. If you click "Contacts", you can add a contact or import/export the address book.
Click the "Settings" icon at the bottom of the left panel to add users, configure applications, change the administrative configuration, and to access "Help".
Instructions for synchronizing the calendar and address book, integrating with a file manager, and integrating with a media player can be found in the. Synchronization clients are available from .
FreeBSD Handbook and FAQ
Search and Portals
Become a Beta TesterFlat html/de/10.1
Become a TranslatorFlat html/de/10.1
Become a Developer
Most of the PC-BSD® specific GUI tools are developed in C++ using the QT Libraries, and other non-GUI development is done using standard Bourne shell scripts. There may be cases where other languages or libraries are needed, but those will be evaluated on a case-by-case basis, so feel free to let us know your proposals on the developers mailing list.
Developers will also find the following resources helpful:
Have you found a bug in PC-BSD®? If so, please take the time to read through this section to ensure that your bug gets reported to the correct group and is resolved in a timely fashion.
First, determine the type of bug that you are encountering. Is it a bug that is preventing you from properly installing and running PC-BSD® (a system bug), or is it an issue with an installed software package such as FireFox (an application bug)?
An application bug can fall into a few different categories.
Application Packaging Bug
The first is a packaging bug, which is when you can not install the application or it simply crashes on startup. Please report these types of bugs by logging into theand clicking "New Ticket". In the "Type" drop-down menu select "PBI Packaging Bug" and select the operating system version you are using in the "Version" drop-down menu. Use descriptive words in the "Summary". In the "Description", provide as much detail as possible about the bug, such as:
If you would like to include a screenshot of the error or a log that includes error messages, check the box "I have files to attach to this ticket" to browse to the location of the attachment. Use the "Preview" button to read through your ticket to make sure that the information is clear to the person who will resolve the issue. When finished, click the "Create ticket" button to submit your bug report.
Application Runtime Bug
An application runtime bug occurs when an application installs and is able to start successfully, but during use, it crashes or exhibits some other type of undesired behavior. An example would be OpenOffice failing to import a type of document properly or a chat client unable to keep a connection to a network.
If you installed the application using AppCafe® and you think that the problem is related to how the PBI was packaged, report the bug on the . If you suspect that the problem is with the underlying FreeBSD port, you can use FreshPorts.org to determine the email address of the port maintainer. If you do email the port maintainer, indicate the name of the port, any error messages that you receive and how to reproduce the bug, and indicate if you are able to assist the maintainer in testing any patches to the port. Once the port is fixed, let the PBI Discussion Forum know so that the PBI can be rebuilt using the fixed port.
System Driver Bugs
A system bug is any bug which prevents the initial installation of PC-BSD®, or causes issues with hardware. Some examples would be a non-bootable system, failed installation, missing drivers for your hardware, or a non-functional desktop after installation. To report this type of issue please follow the instructions below for your type of system bug.
An example of a system driver bug would be a missing network driver, no sound output, or no disk drives detected. Most of these types of issues are directly related to the FreeBSD base upon which PC-BSD® is built, and are best fixed by discussing them with the FreeBSD team directly. Reporting a bug to FreeBSD can be done using thepage. You should also search the FreeBSD mailing lists as other users may have already discovered the bug or have a work-around for your particular hardware. Below are some of the related mailing lists:
System Installation Bugs
Any bugs encountered during the installation of PC-BSD® should be reported to the, with as much detail as possible, including:
Submit PBI Requests
Purchase PC-BSD® Swag
Host a Mirror
We are always interested in more download mirrors. If you have a system with a high-speed connection, 350-500GB of space, and the ability to rsync with a host, you can greatly help the PC-BSD® project and PC-BSD® users by becoming a mirror. More mirrors means faster download speeds and more geographic locations for users to download from.
This rsync command will mirror the entire collection of installation files and PBIs:
rsync -vaz --delete-delay --delay-updates isc.pcbsd.org::ftp .
That command should be run as a cron job with a recommended frequency of at least once daily with a preferred interval of every 12 hours.
Once you have begun the rsync process, send an email to kris at pcbsd dot org letting him know the URL of the mirror so that the new mirror can get listed and become available to users.
Seed a Torrent
PC-BSD® is also distributed as aand you can increase download speeds for other users by seeding, especially during the first two weeks after a new release. If you are new to seeding, read through the first.
The Network-P2P category of AppCafe® provides several torrent utilities including:
Become an Advocate
List of Tables
<ref>tags exist, but no
<references/>tag was found