Translations:Flat html/4/de

From PC-BSD Wiki
Jump to: navigation, search


Flat html/content/de


Translations:Introduction/Page display title/de


Translations:Goals and Features/Page display title/de

Goals and Features/de

Translations:What's New in 9.2/Page display title/de

What's New in 9.2/de

Translations:PC-BSD® Releases/Page display title/de

PC-BSD® Releases/de

Translations:PC-BSD® for Linux Users/Page display title/de

PC-BSD® for Linux Users/de

Translations:Pre-Installation Tasks/Page display title/de

Pre-Installation Tasks/de

Translations:Hardware Requirements/Page display title/de

Hardware Requirements/de

Translations:Laptops/Page display title/de


Translations:Partitioning the Hard Drive/Page display title/de

Partitioning the Hard Drive/de

Translations:Obtaining PC-BSD®/Page display title/de

Obtaining PC-BSD®/de

Translations:Burning the Installation Media/Page display title/de

Burning the Installation Media/de

Translations:PC-BSD® Live Mode/Page display title/de

PC-BSD® Live Mode/de

Translations:Using VirtualBox/Page display title/de

Using VirtualBox/de

Translations:Installing PC-BSD®/Page display title/de

Installing PC-BSD®/de

Translations:Starting the PC-BSD® Installation/Page display title/de

Starting the PC-BSD® Installation/de

Translations:Language Selection Screen/Page display title/de

Language Selection Screen/de

Translations:System Selection Screen/Page display title/de

System Selection Screen/de

Translations:Disk Selection Screen/Page display title/de

Disk Selection Screen/de

Translations:Installation Progress Screen/Page display title/de

Installation Progress Screen/de

Translations:Installation Finished Screen/Page display title/de

Installation Finished Screen/de

Translations:Post Installation Configuration and Installation Troubleshooting/Page display title/de

Post Installation Configuration and Installation Troubleshooting/de

Translations:Booting Into PC-BSD®/Page display title/de

Booting Into PC-BSD®/de

Translations:Language Screen/Page display title/de

Language Screen/de

Translations:Time Zone Selection Screen/Page display title/de

Time Zone Selection Screen/de

Translations:Set Root Password Screen/Page display title/de

Set Root Password Screen/de

Translations:Create a User Screen/Page display title/de

Create a User Screen/de

Translations:Connect to a Wireless Network/Page display title/de

Connect to a Wireless Network/de

Translations:Post Install Finished Screen/Page display title/de

Post Install Finished Screen/de

Translations:Logging In/Page display title/de

Logging In/de

Translations:Installation Troubleshooting/Page display title/de

Installation Troubleshooting/de

Translations:Advanced Installation Topics/Page display title/de

Advanced Installation Topics/de

Translations:Install a Server/Page display title/de

Install a Server/de

Translations:Dual Booting/Page display title/de

Dual Booting/de


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:

  • if you are making software changes to a boot environment, you can take a snapshot of that environment at any stage during modifications by using the beadm create command. A snapshot is a read-only image of a boot environment at a given point in time. A snapshot is not bootable but you can create a boot environment, based on that snapshot, by using the beadm create -e command followed by the beadm activate command to specify that this boot environment will become the default boot environment on the next reboot.
  • you can create custom names for each snapshot to identify when or why that snapshot was created. You can use the beadm list -s command to view the available snapshots for a boot environment.
  • you can save multiple boot environments on your system and perform various updates on each of them as needed. For example, you can clone a boot environment by using the beadm create command. A clone is a bootable copy of a boot environment. You can install, test, and update different software packages on the original boot environment and on its clone.
  • although only one boot environment can be active at a time, you can mount an inactive boot environment using the beadm mount command. You could then chroot into the mount point in order to update specific packages on the mounted environment.
  • you can move a boot environment to another machine, physical or virtual, in order to check hardware support.
WARNUNG For boot environments to work properly, do not change the default ZFS layout during installation. The default ZFS layout ensures that when you create multiple boot environments, the /usr/pbi/, /usr/local/, /usr/home/, /usr/ports/, /usr/src/ and /var/ directories remain untouched. This way, if you rollback to a previous boot environment, you will not lose data in your home directories, any installed applications, or downloaded src or ports.

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

beadm list

BE Active Mountpoint Space Policy Created default NR / 6.05G static 2012-07-09 05:06

beforeupgrade - - 1K static 2012-07-10 12:25
The possible flags in the "Active" field are as follows:
  • R: active on reboot
  • N: active now
  • -: inactive

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:06

beforeupgrade 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.

Translations:Upgrading PC-BSD®/Page display title/de

Upgrading PC-BSD®/de

Translations:Creating an Automated Installation with pc-sysinstall/Page display title/de

Creating an Automated Installation with pc-sysinstall/de

Translations:Desktops/Page display title/de


Translations:GNOME2/Page display title/de


Translations:KDE4/Page display title/de


Translations:LXDE/Page display title/de


Translations:XFCE4/Page display title/de


Translations:Awesome/Page display title/de



Enlightenment[1] is 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.
Figure 6.6a: Enlightenment Running on PC-BSD®

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. The User Guide[2] describes how to configure windows, shelves, menus, wallpaper, and much more.


evilwm[3] 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.

Figure 6.7a: evilwm Running on PC-BSD®

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 the evilwm site[4].

To exit evilwm and return to the login screen, type killall evilwm within an xterm.

Translations:Fluxbox/Page display title/de


Translations:FVWM/Page display title/de


Translations:I3/Page display title/de


Translations:IceWM/Page display title/de


Translations:Openbox/Page display title/de


Translations:Ratpoison/Page display title/de


Translations:Spectrwm/Page display title/de


Translations:WindowLab/Page display title/de


Translations:Window Maker/Page display title/de

Window Maker/de

Translations:Installing Applications and Keeping PC-BSD® Updated/Page display title/de

Installing Applications and Keeping PC-BSD® Updated/de

Translations:Using AppCafe®/Page display title/de

Using AppCafe®/de

Translations:PBI Manager/Page display title/de

PBI Manager/de

Translations:Update Manager/Page display title/de

Update Manager/de

Translations:Meta Package Manager/Page display title/de

Meta Package Manager/de

Translations:Create Your Own PBI Repository/Page display title/de

Create Your Own PBI Repository/de

Translations:Control Panel/Page display title/de

Control Panel/de

Translations:EasyPBI/Page display title/de


Translations:About/Page display title/de


Translations:Active Directory & LDAP/Page display title/de

Active Directory & LDAP/de

Translations:Hardware Compatibility/Page display title/de

Hardware Compatibility/de

Translations:GDM Configuration/Page display title/de

GDM Configuration/de

Translations:Service Manager/Page display title/de

Service Manager/de

Translations:System Manager/Page display title/de

System Manager/de

Translations:User Manager/Page display title/de

User Manager/de

Translations:Bluetooth Manager/Page display title/de

Bluetooth Manager/de

Translations:Mount Tray/Page display title/de

Mount Tray/de

Translations:Sound Configuration/Page display title/de

Sound Configuration/de

Translations:Display/Page display title/de


Translations:Printing/Page display title/de


Translations:Scanner/Page display title/de


Translations:Network Configuration/Page display title/de

Network Configuration/de

Translations:Firewall Manager/Page display title/de

Firewall Manager/de

Translations:Life Preserver/Page display title/de

Life Preserver/de

Translations:Adobe Flash Player preferences/Page display title/de

Adobe Flash Player preferences/de

Translations:Warden®/Page display title/de


Translations:Using PC-BSD®/Page display title/de

Using PC-BSD®/de

Translations:Java, Flash, and Fonts/Page display title/de

Java, Flash, and Fonts/de

Translations:Multimedia/Page display title/de


Translations:Files and File Sharing/Page display title/de

Files and File Sharing/de

Translations:MythTV/Page display title/de


Translations:XBMC/Page display title/de


Translations:Windows Emulation/Page display title/de

Windows Emulation/de

Translations:Remote Desktop/Page display title/de

Remote Desktop/de

Translations:Thin Client/Page display title/de

Thin Client/de


ownCloud[5] 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.

Figure 9.9a: Install the Required Packages

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.

Figure 9.9b: Start the Required Services

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 owncloudjail --startauto
pc-metapkgmanager --pkgset warden --chroot /usr/jails/ add MySQL,Apache,
Figure 9.9c: ownCloud Initial Setup Screen

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                                                           vi /etc/rc.conf

Add these two lines to that file:


Save your edits then start the services:

usr/local/etc/rc.d/apache22 start
/usr/local/etc/rc.d/mysql-server start                                          

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.

Configuring ownCloud

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
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

and change it to:

<IfModule dir_module>
  DirectoryIndex index.html index.php
/usr/local/etc/rc.d/apache24 restart                                            
/usr/local/etc/rc.d/mysql-server restart
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 You should see the setup screen shown in Figure 9.9c.

Figure 9.9d: ownCloud Interface

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 documentation section of the ownCloud website[6]. Synchronization clients are available from the owncloud site[7].

Translations:Security/Page display title/de


Translations:Accessibility/Page display title/de


Translations:Finding Help/Page display title/de

Finding Help/de

Translations:PC-BSD® Forums/Page display title/de

PC-BSD® Forums/de

Translations:IRC Channel/Page display title/de

IRC Channel/de

Translations:Mailing Lists/Page display title/de

Mailing Lists/de

Translations:FreeBSD Handbook and FAQ/Page display title/de

FreeBSD Handbook and FAQ/de

Translations:Social Media/Page display title/de

Social Media/de

Translations:Search and Portals/Page display title/de

Search and Portals/de

Translations:Other Resources/Page display title/de

Other Resources/de

Translations:Supporting PC-BSD®/Page display title/de

Supporting PC-BSD®/de

Werden Sie eine Beta-Testerin oder ein Beta-Tester

Flat html/4/de/de/10.1.2

Werden Sie eine Übersetzerin oder ein Übersetzer

Flat html/4/de/de/10.1.2

Werden Sie eine Entwicklerin oder ein Entwickler

Become a Developer/content/de

Melden Sie Fehler

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 the Trac Database[8] and 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:

  • the name of the program
  • a detailed description of the bug, including any error messages and which commands or menus you used to generate the error

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 PBI Discussion Forum[9]. If you suspect that the problem is with the underlying FreeBSD port, you can use 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 the Send PR[10] page. 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:

  • ACPI[11]: power management and ACPI development
  • Emulation[12]: place to discuss Linux, VirtualBox, Wine and Linux Flash plugin support
  • USB[14]: USB support and development
  • Xorg[15]: Xorg and video drivers and development

System Installation Bugs

Any bugs encountered during the installation of PC-BSD® should be reported to the Trac Database[16], with as much detail as possible, including:

  • PC-BSD® version
  • hardware information, disk and partition sizes, amount of RAM and CPU
  • description of any defaults that you changed using the installer's "Customize" button
  • attach a copy of your saved /tmp/pc-sysinstall.log; if you did not save it during the installation, a copy was saved for you to /root/pc-sysinstall.log

Translations:Submit PBI Requests/Page display title/de

Submit PBI Requests/de

Translations:Test PBIs/Page display title/de

Test PBIs/de

Create PBIs

PBI Module Builder Guide/de

Translations:Purchase PC-BSD® Swag/Page display title/de

Purchase PC-BSD® Swag/de

Spiegelserver hosten

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 .

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.

Translations:Seed a Torrent/Page display title/de

PC-BSD® is also distributed as a torrent[17] and 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 GotBSD FAQ[18] first.

The Network-P2P category of AppCafe® provides several torrent utilities including:

Translations:Become an Advocate/Page display title/de

Become an Advocate/de



Cite error: <ref> tags exist, but no <references/> tag was found
Personal tools