The following features have been added to or improved for PC-BSD® 9.1:
The next screen, seen in Figure 3.3a, allows you to change your keyboard model, keyboard layout, and preferred variant. If English is your native language and you are using a basic English keyboard, you can just press Next to accept the defaults.
Otherwise, use the menus to change the default selection(s) to match your keyboard type and language. You can test your changes by typing into the white area at the bottom of the screen, just below the message that indicates you can test your selected settings.
Figure 3.3a: Keyboard Setup Screen Allows you to Select your Keyboard Model, Layout, and Variant
Figure 3.8a: Sources Selection Screen
Highlight the FreeBSD component that you would like to install in the "Available" box and click the blue > button to add it to the "Selected" box. If you change your mind, highlight the item in the "Selected" box and click the blue < button. Whatever shows up in the "Selected" box when you click the Next button, will be installed for you.
VLC - Possibly would work after installing on both machines?
use mplayer to access webcam:
mplayer -cache 128 -tv driver=v4l:width=640:height=480:outfmt=i420:device=/dev/video0 -vc rawi420 -vo xv tv://
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:
A PBI file includes all the runtime and library dependencies required by the application. This means that a PBI is a large file, but this does not necessarily mean that the installed PBI will be that large. During installation, the PBI system compares the currently installed libraries and files with the ones contained within the PBI file and only installs the ones that are not already installed on the system. A hash database is used to eliminate dependency problems while allowing the computer to share libraries between different programs.
In order to create a PBI, the software must already be ported to FreeBSD. The easiest way to confirm whether or not a FreeBSD port exists is to search for the software at. If a port does not exist, you can issue a port request at the PC-BSD® Port Requests forum using . Alternately, if you have ported software before, the contains detailed instructions for porting software to FreeBSD.
Creating a PBI from an existing FreeBSD port is a mostly automated process that does not require development skills. Some ports are effortless to convert while more complex ports may require some thought and simple scripting. Two utilities are available for converting a FreeBSD port into a PBI:
Testing the PBI
Once your PBI has built, test the PBI to ensure that it installs and that the application works.
As the superuser, use the pbi_add command with the --no-checksig option:
pbi_add --no-checksig /path_to_pbi
Once installed, start the application from the command line to determine if there are any error messages at application launch. When testing the executable, use the one located in /usr/pbi/(pbi-name)/bin/ so all the linking will be properly set up. Otherwise you can get some interesting errors about missing files.
If the executable does not start the application, the executable may actually be a wrapper script rather than a binary file. If so, check the first line of the script to make sure that it is using the right path for the scripting language. For example, #!/bin/python is an incorrect path which should be changed to #!/usr/pbi/(pbi-name)/bin/python.
The suggested path works because each program is packaged with the proper version of the language it uses and you want to make sure it uses that one. This is usually accomplished by putting a quick sed line in the post-install.sh script to fix the first line as seen in the post install script for.
If the application starts and it is a GUI application, go through the various menus to see if they produce any errors.
If you encounter any error messages in either starting or using the application, record them. If the fix for resolving the error messages is not clear to you, send the error report to the.
If your PBI works and you would like to submit its module to be included on the build server, compress it after changing to your module directory (%%PBI_APPDIR%%):
>tar czvf ~/your_pbi_name.tar.gz .
This will create a compressed tarball named your_pbi_name.tar.gz in your home directory. Send this file to the.
Submit the PBI
Include the following in your mailing list submission, this consistent format will be helpful to all:
More than one PBI may be submitted by the same person in the same email, but please limit to five per message per day and be sure to include the above information for each.
Here is an example submission:
Email Subject: PBI submission Epiar
Epiar (ep-ee-are) is an open source computer game, in which the player navigates space from planet to planet, saving money to buy ship upgrades and new ships. The player can also join mercenary missions, attack other ships to steal their money and technology, and explore the universe. The game combines the action/arcade elements of aircraft dogfighting and the openness of role playing games to create this experience.
Epiar is a space exploration/combat/trading game. The Escape Velocity (EV) series for the Mac was the major point of inspiration for this game. Other notable games of this genre include:
- Elite (the original game EV was based on) - Star control 1/2 (and it's now open source successor Ur-Quan masters) - Star Flight - Solar Winds
Email Attachment:epiar.tar.gz 200K
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.
The Network-P2P category of AppCafe® provides several torrent utilities including:
<ref>tags exist, but no
<references/>tag was found