PC-BSD Wiki - User contributions [en]

Talk:Pages about PC-BSD

2013-05-11T05:29:06Z

Vater:

== article about [[PC-BSD]] for the [https://simple.wikipedia.org/wiki/Simple_English_Wikipedia Simple English Wikipedia] ==

does anyone can create a "simple" article for wikipedia? https://simple.wikipedia.org/wiki/PC-BSD

--[[User:Vater|Rg]] ([[User talk:Vater|talk]]) 22:23, 10 May 2013 (PDT)

Talk:Pages about PC-BSD

2013-05-11T05:23:30Z

Vater: /* article about for the Simple English Wikipedia */ new section

== article about for the [https://simple.wikipedia.org/wiki/Simple_English_Wikipedia Simple English Wikipedia] ==

does anyone can create a "simple" article for wikipedia? https://simple.wikipedia.org/wiki/PC-BSD

--[[User:Vater|Rg]] ([[User talk:Vater|talk]]) 22:23, 10 May 2013 (PDT)

PC-BSD® Releases

2013-04-15T04:35:41Z

Vater:

<translate>
<noinclude>{{NavHeader|back=What's New Since 9.1|forward=PC-BSD® for Linux Users|custompagename=PC-BSD{{r}} Releases|custompagecategory={{PAGENAME}}}}</noinclude>


As of September 2008, PC-BSD® release version numbers are the same as those for FreeBSD. When the first number of a release is followed by a zero (e.g. version 9.0), this means that this version of PC-BSD® introduces many new features. When the second number of a release is not a zero (e.g. version 9.1), this means that the new version may have some new features, but it mostly fixes known software problems and security vulnerabilities. If a release includes the letters RC, this means that it is a "Release Candidate", or that the developers are still adding and fixing features and need testers to help them find any existing problems in preparation for the upcoming release. If the release includes the word BETA, it means that that version is still buggy and needs the help of testers to find as many problems as possible so that they can be fixed.


{{note|width=60%|align=right|icon64=if you want to use PC-BSD® (not test it), you should install the most recent release (i.e. the one with the highest number), not a BETA or RC version.}}


PC-BSD® releases follow the same {{citelink|url=http://www.freebsd.org/security/#sup|txt=EoL (end of life) schedule}} as the underlying FreeBSD release. Any security patches for a supported release will appear in [[Update Manager]], making it easy to keep your PC-BSD® system fully patched against known security vulnerabilities.


<noinclude>
{{Refheading}}
[[category:handbook]]
[[category:Introduction]]
[[category:PC-BSD® Releases]]
</noinclude>
</translate>

Create Your Own PBI Repository/de

2013-04-15T04:31:24Z

Vater: Created page with "Als Voreinstellung zeigt AppCafe® die PBIs, welche von der offiziellen PC-BSD® Paketquelle verfügbar sind. Es unterstützt aber auch fremde Paketquellen, die es Organisatio..."

<noinclude>{{NavHeader|back=Meta Package Manager|forward=Control Panel}}</noinclude>

Als Voreinstellung zeigt AppCafe® die PBIs, welche von der offiziellen PC-BSD® Paketquelle verfügbar sind. Es unterstützt aber auch fremde Paketquellen, die es Organisationen erlauben PBIs für ihre eigenen Anwendungen zu erstellen und sie für ihre Benutzer über AppCafe® verfügbar zu machen.

In order to create a custom repository, you need to:

* create the OpenSSL signing key which will be used to sign custom PBIs

* generate a repository file and populate it with custom PBIs

* generate the meta-data for the PBIs which are available within the repository

This section describes these steps in more detail.

=== Generate the Signing Key ===

Running a repository requires that all the PBIs in the custom repository be digitally signed for security and identification purposes. In order to sign the PBIs, generate an OpenSSL key pair using the following commands:

{{txtbox|box='''openssl genrsa -out privkey.pem 4096'''
Generating RSA private key, 4096 bit long modulus
..................++
.............................................................................++
e is 65537 (0x10001)
'''openssl rsa -in privkey.pem -pubout > pub.key'''
writing RSA key}}

These commands will create the files ''privkey.pem'' and ''pub.key''. The ''privkey.pem'' file will be used to digitally sign your created PBI files and the ''pub.key'' file will be included with the repository configuration (''.rpo'') file.

=== Create the Repository ===

In order to create the repository you will need a FTP, HTTP, or HTTPS server to host your repository’s meta-data files and to store the repository's PBIs. The server can be a public URL on the Internet or a private LAN server, as long as it is accessible to your target audience.

Once you have the URL to the server, create the repository's ''.rpo'' file using the [[PBI_Manager#pbi_makerepo.281.29 | '''pbi_makerepo''']] command. Replace the values in the following example with your own description, path to your generated ''pub.key'' file, the URL to the location where the PBIs will be hosted, the URL to the location to contain the repository's meta-data files, and the directory to place the created ''.rpo'' file.

{{txtbox|wrap|box='''pbi_makerepo --desc “My Example Repository” --key pub.key --mirror {{ftp}}//ftp.example.org/pbi-files” --url {{http}}www.example.org/pbi-meta” /root'''}}

This command will generate the ''pbi-repo.rpo'' file in the specified directory on the server. This file is needed for clients to register with and begin using the new repository. Instruct your clients to download this file to their PC-BSD® desktop, then to configure their system to use the repository using this command as the superuser:

{{txtbox|box='''pbi_addrepo pbi-repo.rpo'''}}

Once the repository is registered on the clients system, their pbi daemon will automatically keep track of downloading and updating both meta-files and PBIs from the URLs you specified in the repository configuration file.

=== Generate the Repository's Meta-Data ===

On a PC-BSD® system, you can now create the meta-data and PBI files so that clients have something to download. The meta-data file is used to give the client information about the PBIs available from the repository, such as categories, application names, and descriptions. When creating categories, you can use the same category names that appear in AppCafe®, or you can create your own categories. Each category and each PBI will need its own icon. These icons need to exist on the server before generating the meta-data file.

When you are ready, create an empty meta-data file in the format ''pbi-meta-<Major Version Number>.'' This command should be used for 9.x series PBIs:

{{txtbox|box='''touch pbi-meta-9'''}}

Then use the [[PBI Manager#pbi_metatool(1) | '''pbi_metatool''']] command to add the category for a PBI. The following command adds the "Archivers" category, its description, and the URL pointing to the mandatory 64x64 ''.png'' icon file to the specified meta-data file.

{{txtbox|box='''pbi_metatool add --cat -n “Archivers” -d “File Archivers and Utilities” -i {{http}}www.example.org/pbiicons/archivers.png” pbi-meta-9'''}}

Next, add the following information about the PBI: the name of the application, the category, the application author, a description of the application, the URL pointing to the mandatory 64x64 ''.png'' icon file for the application, a comma delimited list (with no spaces) of search keywords, the type of license, the type of application ("Graphical", "Text", or "Service"), the URL to the application's website, and the name of the meta-data file to add the information to.

{{txtbox|wrap|box='''pbi_metatool add --app -n “cabextract” -c “Archivers” -a “Stuart Caie” -d “Utility for reading and extracting .cab files.” -i ''{{http}}www.example.org/pbi-icons/cabextract.png'' -k “cab,archive,extract” -l “LGPL” -t “Text” -u “{{http}}www.cabextract.org.uk” pbi-meta-9'''}}

Repeat this command for each PBI that will be available in the repository, creating new categories as you need to do so.

When you are finished adding the information for the repository's PBIs, compress the file with '''bzip2''' and upload it to the server. The location in our example would be ''{{http}}www.example.org/pbi-meta/pbi-meta-9.bz2''. Once the file is uploaded, clients can use the [[PBI Manager#pbi_browser(1) | '''pbi_browser''']] command or AppCafe® to browse the repository's PBIs.

You should now create your custom PBIs then upload them to their specified category in the download directory on the server. In our example, the download directory is ''{{ftp}}ftp.example.org/pbi-files''. Refer to the section on [[PBI Module Builder Guide | creating PBIs]] for instructions on creating PBIs using either the EasyPBI graphical utility or the [[PBI Manager#pbi_makeport(1) | '''pbi_makeport''']] command line utility.

When creating your PBIs, remember to sign them with the private key. If you are using [[EasyPBI#Build the Module | EasyPBI]], specify the location to the ''privkey.pem'' file by clicking the "Change File" button shown in Figure 8.1d. If you are using the '''pbi_makeport''' command, include '''--sign privkey.pem''' in the command.

Lastly, create the ''pbi-index-9'' file and add the names of the uploaded PBIs to the file. Use the [[PBI Manager#pbi_indextool(1) | '''pbi_indextool''']] to add each entry, specifying that PBI's filename (will end in ''.pbi''), the download location (in the format category/pbi_name), and the name of the index file.

{{txtbox|box='''touch pbi-index-9'''
'''pbi_indextool -f cabextract-1.2-amd64.pbi -u “archivers/cabextract-1.2-amd64.pbi” pbi-index-9'''}}

When you are finished adding entries to this file, use '''bzip2''' to compress it and upload the ''pbi-index-9.bz2'' to the same location on the server where the ''pbi-meta-9.bz2'' file is stored. Clients can now download and install PBIs from your custom repository, using the [[PBI Manager#pbi_add(1) | '''pbi_add''']] command or AppCafe®.

=== Configure the Automatic Build of Updated Ports ===

Over time, the PBIs in your repository will become out-of-date as the versions of the underlying ports change. You can automate the process of automatically rebuilding the newer version of a PBI, as well as generating the binary diff changes to the PBI (which users use to upgrade their installed version of the PBI), whenever an underlying port changes.

To configure this scenario, ensure that all of your PBI modules exist under the same directory and follow the directory structure of the ports tree. For example, if you have created PBIs for cabextract and firefox, the subdirectory structure for ''/usr/local/my_pbis/'' would be ''archivers/cabextract/'' and ''www/firefox/''.

To start the build process, use the [[PBI Manager#pbi_autobuild(8)|'''pbi_autobuild''']] command as seen in this example:

{{txtbox|box='''pbi_autobuild --keep 2 -c /usr/local/my_pbis -o /usr/local/my_pbis --prune --tmpfs --sign /root/privkey.pem –genpatch'''}}

This command keeps the last 2 versions of the PBI, reads the modules located in the subdirectories of ''/usr/local/my_pbis'', places the built PBIs in the ''/usr/local/my_pbis'' directory, removes any PBIs which no longer have an associated module, uses tmpfs to optimize build speed, signs the PBIs with the specified key, and generates the ''.pbp'' patch files needed by users to upgrade an installed version of the previous PBI. The new PBIs and ''.pbp'' files will be placed in the specified outgoing directory. If an earlier version of the PBI exists in that directory, it will be placed into the ''archived'' subdirectory.

If the ccache FreeBSD port is installed on the build system and the CCACHE_DIR variable is set, '''pbi_autobuild''' will detect and use it which can greatly speed up the process of building the PBIs.

Depending upon the load on the build server and how many PBIs are affected by the build, you may wish to modify some [[PBI Module Builder Guide#pbi.conf|''pbi.conf'']] values in particular PBI modules. The variables that can affect a build are:

* '''PBI_BUILDKEY:''' set to a numerical value to instruct '''pbi_autobuild''' to rebuild that particular PBI. This is useful when a port has failed to build or you wish to rebuild a PBI with new compile options even though the upstream target port has not changed.

* '''PBI_AB_PRIORITY:''' when automatically building a large number of PBIs, the build process occurs alphabetically. By setting an incremental integer value, it is possible to artificially force the building of PBIs in the specified order of importance.

* '''PBI_AB_NOTMPFS:''' typically, using the --tmpfs flag greatly speeds up the build process by extracting a port's files into memory, and compiling directly into RAM. However some ports, such as OpenOffice, require more memory than is available, causing the build to fail. By setting this variable to YES in that PBI's ''pbi.conf'', it is possible to flag that port as needing to build in the traditional manner from disk.

* '''PBI_MAKEOPTS:''' if you use ccache, you may occasionally run into a port that will not compile properly with CCACHE enabled. For that PBI, edit this variable to include ''NO_CCACHE=yes'' which will disable CCACHE for that specific port build.

<noinclude>

[[category:handbook]]
[[category:Create Your Own PBI Repository]]
</noinclude>

Translations:Create Your Own PBI Repository/2/de

2013-04-15T04:31:23Z

Als Voreinstellung zeigt AppCafe® die PBIs, welche von der offiziellen PC-BSD® Paketquelle verfügbar sind. Es unterstützt aber auch fremde Paketquellen, die es Organisationen erlauben PBIs für ihre eigenen Anwendungen zu erstellen und sie für ihre Benutzer über AppCafe® verfügbar zu machen.

Create Your Own PBI Repository/de

2013-04-15T04:13:23Z

Vater: Created page with "Erstelle deine eigene PBI Paketquelle"

<noinclude>{{NavHeader|back=Meta Package Manager|forward=Control Panel}}</noinclude>

By default, AppCafe® displays the PBIs which are available from the official PC-BSD® repository. It also supports custom repositories, allowing organizations to create PBIs for their own applications and to make them available to their users within AppCafe®.

In order to create a custom repository, you need to:

* create the OpenSSL signing key which will be used to sign custom PBIs

* generate a repository file and populate it with custom PBIs

* generate the meta-data for the PBIs which are available within the repository

This section describes these steps in more detail.

=== Generate the Signing Key ===

Running a repository requires that all the PBIs in the custom repository be digitally signed for security and identification purposes. In order to sign the PBIs, generate an OpenSSL key pair using the following commands:

{{txtbox|box='''openssl genrsa -out privkey.pem 4096'''
Generating RSA private key, 4096 bit long modulus
..................++
.............................................................................++
e is 65537 (0x10001)
'''openssl rsa -in privkey.pem -pubout > pub.key'''
writing RSA key}}

These commands will create the files ''privkey.pem'' and ''pub.key''. The ''privkey.pem'' file will be used to digitally sign your created PBI files and the ''pub.key'' file will be included with the repository configuration (''.rpo'') file.

=== Create the Repository ===

In order to create the repository you will need a FTP, HTTP, or HTTPS server to host your repository’s meta-data files and to store the repository's PBIs. The server can be a public URL on the Internet or a private LAN server, as long as it is accessible to your target audience.

Once you have the URL to the server, create the repository's ''.rpo'' file using the [[PBI_Manager#pbi_makerepo.281.29 | '''pbi_makerepo''']] command. Replace the values in the following example with your own description, path to your generated ''pub.key'' file, the URL to the location where the PBIs will be hosted, the URL to the location to contain the repository's meta-data files, and the directory to place the created ''.rpo'' file.

{{txtbox|wrap|box='''pbi_makerepo --desc “My Example Repository” --key pub.key --mirror {{ftp}}//ftp.example.org/pbi-files” --url {{http}}www.example.org/pbi-meta” /root'''}}

This command will generate the ''pbi-repo.rpo'' file in the specified directory on the server. This file is needed for clients to register with and begin using the new repository. Instruct your clients to download this file to their PC-BSD® desktop, then to configure their system to use the repository using this command as the superuser:

{{txtbox|box='''pbi_addrepo pbi-repo.rpo'''}}

Once the repository is registered on the clients system, their pbi daemon will automatically keep track of downloading and updating both meta-files and PBIs from the URLs you specified in the repository configuration file.

=== Generate the Repository's Meta-Data ===

On a PC-BSD® system, you can now create the meta-data and PBI files so that clients have something to download. The meta-data file is used to give the client information about the PBIs available from the repository, such as categories, application names, and descriptions. When creating categories, you can use the same category names that appear in AppCafe®, or you can create your own categories. Each category and each PBI will need its own icon. These icons need to exist on the server before generating the meta-data file.

When you are ready, create an empty meta-data file in the format ''pbi-meta-<Major Version Number>.'' This command should be used for 9.x series PBIs:

{{txtbox|box='''touch pbi-meta-9'''}}

Then use the [[PBI Manager#pbi_metatool(1) | '''pbi_metatool''']] command to add the category for a PBI. The following command adds the "Archivers" category, its description, and the URL pointing to the mandatory 64x64 ''.png'' icon file to the specified meta-data file.

{{txtbox|box='''pbi_metatool add --cat -n “Archivers” -d “File Archivers and Utilities” -i {{http}}www.example.org/pbiicons/archivers.png” pbi-meta-9'''}}

Next, add the following information about the PBI: the name of the application, the category, the application author, a description of the application, the URL pointing to the mandatory 64x64 ''.png'' icon file for the application, a comma delimited list (with no spaces) of search keywords, the type of license, the type of application ("Graphical", "Text", or "Service"), the URL to the application's website, and the name of the meta-data file to add the information to.

{{txtbox|wrap|box='''pbi_metatool add --app -n “cabextract” -c “Archivers” -a “Stuart Caie” -d “Utility for reading and extracting .cab files.” -i ''{{http}}www.example.org/pbi-icons/cabextract.png'' -k “cab,archive,extract” -l “LGPL” -t “Text” -u “{{http}}www.cabextract.org.uk” pbi-meta-9'''}}

Repeat this command for each PBI that will be available in the repository, creating new categories as you need to do so.

When you are finished adding the information for the repository's PBIs, compress the file with '''bzip2''' and upload it to the server. The location in our example would be ''{{http}}www.example.org/pbi-meta/pbi-meta-9.bz2''. Once the file is uploaded, clients can use the [[PBI Manager#pbi_browser(1) | '''pbi_browser''']] command or AppCafe® to browse the repository's PBIs.

You should now create your custom PBIs then upload them to their specified category in the download directory on the server. In our example, the download directory is ''{{ftp}}ftp.example.org/pbi-files''. Refer to the section on [[PBI Module Builder Guide | creating PBIs]] for instructions on creating PBIs using either the EasyPBI graphical utility or the [[PBI Manager#pbi_makeport(1) | '''pbi_makeport''']] command line utility.

When creating your PBIs, remember to sign them with the private key. If you are using [[EasyPBI#Build the Module | EasyPBI]], specify the location to the ''privkey.pem'' file by clicking the "Change File" button shown in Figure 8.1d. If you are using the '''pbi_makeport''' command, include '''--sign privkey.pem''' in the command.

Lastly, create the ''pbi-index-9'' file and add the names of the uploaded PBIs to the file. Use the [[PBI Manager#pbi_indextool(1) | '''pbi_indextool''']] to add each entry, specifying that PBI's filename (will end in ''.pbi''), the download location (in the format category/pbi_name), and the name of the index file.

{{txtbox|box='''touch pbi-index-9'''
'''pbi_indextool -f cabextract-1.2-amd64.pbi -u “archivers/cabextract-1.2-amd64.pbi” pbi-index-9'''}}

When you are finished adding entries to this file, use '''bzip2''' to compress it and upload the ''pbi-index-9.bz2'' to the same location on the server where the ''pbi-meta-9.bz2'' file is stored. Clients can now download and install PBIs from your custom repository, using the [[PBI Manager#pbi_add(1) | '''pbi_add''']] command or AppCafe®.

=== Configure the Automatic Build of Updated Ports ===

Over time, the PBIs in your repository will become out-of-date as the versions of the underlying ports change. You can automate the process of automatically rebuilding the newer version of a PBI, as well as generating the binary diff changes to the PBI (which users use to upgrade their installed version of the PBI), whenever an underlying port changes.

To configure this scenario, ensure that all of your PBI modules exist under the same directory and follow the directory structure of the ports tree. For example, if you have created PBIs for cabextract and firefox, the subdirectory structure for ''/usr/local/my_pbis/'' would be ''archivers/cabextract/'' and ''www/firefox/''.

To start the build process, use the [[PBI Manager#pbi_autobuild(8)|'''pbi_autobuild''']] command as seen in this example:

{{txtbox|box='''pbi_autobuild --keep 2 -c /usr/local/my_pbis -o /usr/local/my_pbis --prune --tmpfs --sign /root/privkey.pem –genpatch'''}}

This command keeps the last 2 versions of the PBI, reads the modules located in the subdirectories of ''/usr/local/my_pbis'', places the built PBIs in the ''/usr/local/my_pbis'' directory, removes any PBIs which no longer have an associated module, uses tmpfs to optimize build speed, signs the PBIs with the specified key, and generates the ''.pbp'' patch files needed by users to upgrade an installed version of the previous PBI. The new PBIs and ''.pbp'' files will be placed in the specified outgoing directory. If an earlier version of the PBI exists in that directory, it will be placed into the ''archived'' subdirectory.

If the ccache FreeBSD port is installed on the build system and the CCACHE_DIR variable is set, '''pbi_autobuild''' will detect and use it which can greatly speed up the process of building the PBIs.

Depending upon the load on the build server and how many PBIs are affected by the build, you may wish to modify some [[PBI Module Builder Guide#pbi.conf|''pbi.conf'']] values in particular PBI modules. The variables that can affect a build are:

* '''PBI_BUILDKEY:''' set to a numerical value to instruct '''pbi_autobuild''' to rebuild that particular PBI. This is useful when a port has failed to build or you wish to rebuild a PBI with new compile options even though the upstream target port has not changed.

* '''PBI_AB_PRIORITY:''' when automatically building a large number of PBIs, the build process occurs alphabetically. By setting an incremental integer value, it is possible to artificially force the building of PBIs in the specified order of importance.

* '''PBI_AB_NOTMPFS:''' typically, using the --tmpfs flag greatly speeds up the build process by extracting a port's files into memory, and compiling directly into RAM. However some ports, such as OpenOffice, require more memory than is available, causing the build to fail. By setting this variable to YES in that PBI's ''pbi.conf'', it is possible to flag that port as needing to build in the traditional manner from disk.

* '''PBI_MAKEOPTS:''' if you use ccache, you may occasionally run into a port that will not compile properly with CCACHE enabled. For that PBI, edit this variable to include ''NO_CCACHE=yes'' which will disable CCACHE for that specific port build.

<noinclude>

[[category:handbook]]
[[category:Create Your Own PBI Repository]]
</noinclude>

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

2013-04-15T04:13:22Z

Vater: Created page with "Erstelle deine eigene PBI Paketquelle"

Erstelle deine eigene PBI Paketquelle

PC-BSD FAQ

2013-03-08T13:05:59Z

Vater:

{{NavHome}}
Welcome to the PC-BSD FAQ!

The FAQ (Frequently Asked Questions) is meant to answer the questions that users new to PC-BSD ask most. This document is under constant development, meaning that you may come across mistakes and out-of-date information. If you find a mistake or have a question you cannot find an answer to, let us know on the {{Citelink|url=http://forums.pcbsd.org/forumdisplay.php?f=25|txt=Documentation Forum}}, the {{Citelink|url=http://lists.pcbsd.org/mailman/listinfo/docs|txt=Documentation Mailinglist}}, or by leaving a comment at the {{Citelink|url=http://blog.pcbsd.org/|txt=PC-BSD Blog}}. We hope this FAQ is both simple and useful and makes using PC-BSD an enjoyable experience. We value your opinion and thank you for your support.

''Please note that the original FAQ site at <nowiki>http://faqs.pcbsd.org/</nowiki> had been broken and woefully out-of-date for quite some time, and now is out of service. The original intent was that content from that FAQ site would be transferred here and updated in the process. '''There now is a [[Talk:PC-BSD FAQ|guideline]] for this page to assist those with desire to shape it - volunteers welcomed!'''''

=== Introduction ===

The FAQ is divided into categories. Each category contains related questions which you can click on to find their answers. You can use your browser's search utility to search for key words to help find the answer you are looking for. Or, you can read through parts of the FAQ that sound interesting and learn something new along the way.

If you cannot find your answer here, it may be in the [[PC-BSD Users Handbook]].

=== PC-BSD Installation ===

==== Is it possible to install PC-BSD on an extended partition? ====

No. PC-BSD can only be installed on primary partitions. Unless you are planning on using the entire hard disk, your partitions need to be created prior to starting the installation. This means that if you want to create multiple partitions or install other operating systems, you will need a third-party partition manager. If Windows or Mac OS X is already installed, you can use their disk management utility. You can also use an open source utility such as {{Citelink|url=http://partedmagic.com/|txt=Parted Magic}}.

==== How do I edit GRUB in Linux to boot PC-BSD? ====

The [[Dual Booting#GRUB|GRUB]] section of the PC-BSD Users Handbook shows how to do this for both GRUB versions 1 and 2.

=== Post-Installation Issues ===

=== Software Installation ===

==== How do I install software on my PC-BSD system? ====

The easiest way is to install PBI software using Software Manager. This is the recommended method as it does everything for you and provides an easy way to find, install, upgrade, and uninstall applications that have been tested to run on your PC-BSD system. It also ensures that you do not inadvertantly overwrite or delete files or libraries needed by the operating system or other applications. Instructions on how to use Software Manager are in this [[PC-BSD Users Handbook#Installing software via PBI | section]] of the PC-BSD Users Handbook.

Advanced users familiar with the FreeBSD ports and packages collection can use Ports Jail to safely manage their FreeBSD applications. Instructions on how to use Ports Jail can be found in this [[PC-BSD Users Handbook#Using Ports Jail | section]] of the PC-BSD Users Handbook. '''NOTE:''' using ports or packages outside of Ports Jail can over time render your system unusable, especially if a major library changes. Be forewarned and use Ports Jail.

It is not recommended that you download .tgz files directly from sites such as Sourceforge as most software needs to be ported to work on a FreeBSD/PC-BSD system. If the application you are looking for is not in Software Manager or {{Citelink|url=http://www.freshports.org|txt=Freshports}} (which allows you to search for all available FreeBSD ports/packages), it is better to [[PC-BSD Users Handbook#Submit PBI Requests | submit a request for a PBI]].

When adding a new program without using the pbi system, you may want to use it immediately but all that is returned is a "no such command" error. In this situation, at the command prompt type ''rehash''. What this does is recalculates the hash table for the path variable, which basically means that the newly added program or command becomes recognized as having been installed and will now be accessible to you.

==== Can I use Linux software on my PC-BSD system? ====

First, you should know that most "Linux" software is really "open source" software. That is, it is freely available for many operating systems, not just Linux. Most software that runs on Linux should also run on PC-BSD.

Like FreeBSD, PC-BSD uses something called Linux Binary Compatability. In a nutshell, that means you can run many Linux applications as-is. This {{Citelink|fbsdh|url=linuxemu.html|txt=section}} of the FreeBSD Handbook explains this compatability in more detail and describes when it does not work.

However, you do not have to setup Linux Binary Compatability on your PC-BSD system as it is already configured for you and should "just work". To install applications, see the PC-BSD FAQ [[#How do I install software on my PC-BSD system? | ''How do I install software on my PC-BSD system?'']].

=== Applications ===

==== How do I enhance fonts in OpenOffice? ====

Fonts in OpenOffice.org are rather difficult to look nice because OpenOffice.org has its own rendering engine. Basically you can only enable/disable antialiasing at certain fonts sizes instead of taking your system font configuration into account.

You can use Software Manager to install Microsoft fonts, then launch OpenOffice and click: Tools -> Options -> OpenOffice.org -> View. Make sure the boxes "Use system font for user interface" and "Screen font antialiasing" are checked and increase the Pixels to 16. Click the OK button and OpenOffice should look like Microsoft Windows with clear and clean fonts.

This [[PC-BSD Users Handbook#Installing True Type Fonts | section]] of the PC-BSD Users Handbook has more information on using True Type fonts.

=== Application Problems ===

=== Using PC-BSD ===

==== Help, I Forgot My Password! ====

==== How do I reset my root password? ====

Do not panic! Simply restart the system, and select "2. Boot PC-BSD in single user mode" when you see the boot menu. You will see some boot messages which end in this line:

Enter full pathname of shell or RETURN for /bin/sh:

Press enter and you will see a # prompt. Type the following command:

# '''mount -a -o rw'''

This will mount all of your filesystems in read/write mode. You can now change the root password with this command:

# '''passwd'''
Changing local password for root
New Password:

When you are finished, type '''exit''' to continue booting the system.

==== How do I login as root? ====

The PC-BSD login manager disallows root logins for security reasons and there really isn't a reason to login as root on your PC-BSD system. If a command requires administrative access, PC-BSD will prompt you for the administrative password.

If you are using the command line within KDE and need to pass the administrative password to that command, put the word '''kdesu''' in front of your command. Advanced users can also use the '''su''' command to temporarily switch to the superuser account.

==== How do I login to a window manager other than KDE? ====

In order to switch to another desktop environment, you must first log out of KDE using the KDE menu -> Leave -> Logout. When you see the login screen, click the button in the lower left corner (round circle with lines). It will open a menu showing all of the currently installed window managers. By default, {{Citelink|wp|url=Fluxbox|txt=Fluxbox}} and {{Citelink|wp|url=twm|txt=twm}} are installed for you. Fluxbox is a light-weight window manager that is easy to use and makes a good choice for older hardware where KDE runs too slowly. twm is designed for the user who prefers to use the command line and wants an extremely basic windowing system.

Since these window managers are installed with PC-BSD, they provide access to the PC-BSD system tools. This means that you can still use PC-BSD specific utilities such as Software Manager and Update Manager. However, you will quickly discover which utilities came with KDE as these will be missing in the launch menus of other window managers.

If you would like to use GNOME, see the FAQ [[#How do I use GNOME on PC-BSD? | ''How do I use GNOME on PC-BSD?'']]. If you would like to install another window manager, see the FAQ [[#How do I install another window manager on PC-BSD? | ''How do I install another window manager on PC-BSD?'']].

==== How do I use GNOME on PC-BSD? ====

GNOME is not installed with PC-BSD, but you can install it using Software Manager. Simply search for "gnome" in the Software Browser tab of Software Manager, then click on its Download link to install GNOME. GNOME is quite large (about 500 MB) so it will take a bit of time for it to download and install. When the installation is finished, a message will indicate that you need to log out of KDE and select GNOME from the drop down menu of listed window managers (it will be added to this list for you).

The GNOME PBI will install many GNOME utilities for you which you will find listed in GNOME's application launcher menu. However, it is not integrated with the PC-BSD system utilities such as Software Manager and Update Manager. You will also soon discover which utilities were KDE applications and which are GNOME applications as each of these desktop environments provide their own applications.

ADD SECTION ON IF/HOW YOU CAN LAUNCH AND SUCCESSFULLY USE THESE MANUALLY

==== How do I install another window manager on PC-BSD? ====

==== Will future versions of PC-BSD pre-install GNOME and integrate PC-BSD tools into its menus? ====

For 9.0, the developers are working on de-coupling PC-BSD's tools from KDE. This means that having a desktop which can use any window manager
may become a reality in the future.

=== Networking ===

=== Hardware ===

==== Compatible Hardware ====

==== Incompatible Hardware ====

=== Miscellaneous ===

=== Error Messages ===

=== Preliminary Questions ===

=== PBI Tutorials ===

=== FreeBSD General Support ===

=== Developer Documentation ===

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[Category:PC-BSD FAQ]]
</noinclude>

EasyPBI

2013-02-11T20:59:21Z

Vater: /* Test and Fine-Tune the Module */

<noinclude>{{NavHeader|back=Control Panel|forward=About}}</noinclude>

EasyPBI is a graphical application that makes it easy to build a PBI module from a FreeBSD port. Beginning with PC-BSD® 9.1, EasyPBI ships with PC-BSD® and can be found in the [[Control Panel]].

This section demonstrates how to use this utility to convert an existing FreeBSD port into a PC-BSD® PBI. You may wish to skim the section on how to [[PBI Module Builder Guide | Create PBIs]] first, as well as refer to that Guide should you have trouble creating a PBI or wish to create a more complex PBI.

To start EasyPBI, double-click its icon in Control Panel or type '''EasyPBI''' from within an X terminal as your regular user account.

If the ports collection is not installed, you will receive the message shown in Figure 8.1a the first time you start EasyPBI.

'''Figure 8.1a: Ports Must be Installed to Use EasyPBI'''

[[File:Easypbi1d.png]]

If multiple users will be using the EasyPBI utility, go to ''[[Control Panel]]'' ➜ [[System Manager#Install FreeBSD Source and Ports| ''System Manager'' ➜ ''Tasks'']] and click the ''Fetch Ports Tree'' button. Alternately, use the following command as the superuser '''portsnap fetch extract'''. Either of these methods will install the ports collection into ''/usr/ports''.

If you are the only user who will be using the EasyPBI utility, click ''OK'' to launch the main EasyPBI screen, shown in Figure 8.1b. Click ''File'' ➜ ''Get Ports'' which will download the ports collection to the ''[[EasyPBI]]'' subdirectory located in your home directory.

'''Figure 8.1b: EasyPBI Graphical Interface'''

[[File:Easypbi1b.png]]

If the ports collection was already installed or was installed using System Manager or '''portsnap''', the message in the bottom area of the screen will instead indicate To get started, please push the ''New Module'' button.

== Creating a PBI Module ==

Before building a PBI, refer to the {{citelink|url=http://forums.pcbsd.org/forumdisplay.php?f=61|txt=PBI Requests forum}} to determine which PBIs have been requested by users. You should also check that a module does not already exist for the PBI in the {{citelink|url=http://trac.pcbsd.org/browser#pbi/modules|txt=PBI Modules}} section of trac. Existing modules are listed alphabetically, according to their category in the ports collection.

To create a new module, click the ''New Module'' button and use the browser to select the desired port from the FreeBSD ports tree. Once a port is selected, EasyPBI will attempt to automatically supply the port information for the PBI and display the results in the GUI. In the example shown in Figure 8.1c, the ''net/trickle'' port has been selected and the fields have been auto-filled in.

'''Figure 8.1c: Review the New Module'''

[[File:Easypbi1c.png]]

You should review these fields for accuracy. If you click "Get Port Info" {{citelink|url=http://freshports.org|txt=FreshPorts.org}} will open in the default web browser so that you can view additional information about the port.

A generic icon will be supplied for the module; you can change the default icon by clicking the ''Choose Icon'' button. When using a custom icon, use a 64x64 ''.png'' file with a transparent background.

Check the ''Create Desktop/Menu Entries' if you wish the program's icon to be available on the desktop and in the desktop's application menu.

Once the port information is complete, click the ''Create Module'' button and EasyPBI will produce the PBI module. The module will be named after the port and will be stored in a subdirectory of the ''EasyPBI/Modules'' directory in your home directory. In this example, the module is located in ''EasyPBI/Modules/trickle''.

=== Build the Module ===

Creating the module itself is very quick and takes less than a minute. However, you still need to build and test the module to make sure that the application works as expected. Depending upon the complexity of the application, you may have to edit the initial module then rebuild and retest it until you are satisfied with the PBI for the application.

Once the module is created, you are ready to build a PBI from the module. Click on the ''Build PBI'' tab and click the ''Select Module'' button to browse to the module you created. Figure 8.1d shows this tab with our example PBI selected.

'''Figure 8.1d: The Build PBI Tab'''

[[File:Easypbi3b.png]]

The top half of this screen contains modifiable settings which are used when building PBIs:

'''Save Settings as Defaults:''' the settings in this section revert back to the default settings when you exit EasyPBI. This allows you to override the default settings for a particular build. If you wish your changes to be permanent, click this button.

'''Output Directory:''' specifies the directory to store the built module. By default, it is the ''EasyPBI/PBI'' subdirectory of the user's home directory. Click the ''Change Directory'' button to select another location.

'''Digital Signature File:''' the PBIs available from the PC-BSD® repositories are digitally signed by the PC-BSD® project's signature file. If you are creating your own repository, click the ''Change File'' button to select your own digital signature file. [[Create Your Own PBI Repository]] provides instructions for creating a signature file.

'''Use TMPFS:''' if your build system has a lot of RAM, selecting this option can speed up the build.

'''Use Package Caching:''' this setting is recommended as it reuses previously built packages to speed up subsequent builds.

The rest of this screen is used to build the specified module:

'''Select Module:''' select the previously created module to build.

'''Build PBI:''' starts the build of the PBI module. It will prompt you for the superuser password and requires a working Internet connection in order to build the PBI. This process may take quite a while, depending upon the port selected and the speed of your computer. The build messages will be displayed in the window at the bottom of the tab. EasyPBI will inform you when the PBI build is finished, and whether it was successful or not.

'''Stop Build:''' stops the build process. Click the ''Build PBI'' button to resume the build.

'''Save Build Log:''' useful if the build fails. Will prompt you to select the location to store ''build.log'' which can be read with any ASCII text editor.

You can produce additional modules from the ''Create Module'' tab while a PBI build is running.

If the PBI build fails for some reason, you may need to modify the module as described in the next section. Use the build log to determine the error and modify the module as needed. If you are unsure how to fix the module, send the ''build.log'' for the failure to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}.

=== Test and Fine-Tune the Module ===

Once your build is finished, test the PBI to ensure that it installs and that the application works.

To install the PBI, become the superuser, '''cd''' to the "Output Directory", and use the '''pbi_add''' command. Unless you have specified your own digital signature, include the '''--no-checksig''' option.

'''su'''
Password:
'''cd ~dru/EasyPBI/PBI'''
'''ls'''
trickle-1.07_2_amd64.pbi trickle-1.07_2_amd64.pbi.sha256
'''pbi_add --no-checksig trickle-1.07_2_amd64.pbi'''
Verifying Checksum...OK
Extracting to: /usr/pbi/trickle-amd64
Installed: trickle-1.07_2

If the module installs successfully, perform the following tests:

* if you checked the box ''Create Desktop/Menu Entries'', verify that a desktop icon was created (from a desktop that supports icons), that an entry was added to that desktop's application menu, and that the application successfully launches from the application menu. If you used a custom icon, verify that the icon was used.

* start the application from the command line to determine if there are any error messages at application launch. When starting the application, specify the full path to the application's binary to make sure that you are testing the PBI's binary.

* for GUI applications, 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 the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}.

The ''Module Editor'' tab, seen in Figure 8.1e, can be used to modify the module's settings. Use the ''Select Module'' button to browse to the location of the module and to un-grey-out the settings in this screen.

'''Figure 8.1e: EasyPBI Module Editor'''

[[File:easypbi4a.png]]

Several tabs are provided, allowing you to customize the PBI module. It should be noted that most PBI modules do not require you to make any configuration changes in the ''Module Editor'' tab. This tab allows the creation of more complex PBI modules that require additional FreeBSD ports or scripts which are not provided by the default FreeBSD port.

The rest of this section describes the actions available within each tab. If you modify any settings in the PBI module, rebuild it then test again to see if the changes fixed the PBI.

==== pbi.conf ====

Typically the ''Program Name'', ''Program Website'', and ''Program Author'' are left at their default values. If this information is incorrect, you should email the FreeBSD port maintainer shown in the ''Program Author'' field so that the information can be corrected in the FreeBSD port.

If you choose to replace the ''Program Icon'', use a 64x64 ''.png'' file with a transparent background.

If your PBI requires a dependency that is not provided by the FreeBSD port, use the ''+'' button next to ''Make Port Before'' to select the needed port.

If you wish an additional port to be included with your PBI, use the ''+'' button next to ''Make Port After'' to select the desired port.

The ''Make Options'' field lets you specify a space separated list of options. The available options and their default settings will be listed in the ''OPTIONS='' section of the port's ''Makefile''.

If the resulting PBI needs to be run as the root user, check the ''Require Root Permissions'' box.

==== Resources ====

This tab, shown in Figure 8.1f, is used to add additional files to the PBI module.

'''Figure 8.1f: PBI Module Resource Configuration'''

[[Image:Easypbi5a.png]]

An example of an additional file would be an application that requires the user to accept a License. Use the ''+ Add Resource'' button to browse to the location of the ''LICENSE'' file.

Another example would be when you wish to use a custom script to start the application rather than starting the application binary directly. A custom script could also be used to verify that the service is enabled or to generate a custom configuration file.

If the application uses custom installer graphics, add them using this screen.

==== Desktop/Menu Entries ====

This tab, shown in Figure 8.1g, is used to fine-tune the desktop icon and the application menu entry for the application.

'''Figure 8.1g: Customizing the PBI's Desktop and Menu Entries'''

[[Image:Easypbi6a.png]]

If the ''Create Desktop/Menu Entries'' box was checked when creating the module and EasyPBI detects that the application is graphical, the default entries for the application will be listed. In our PBI example, '''trickle''' is a command line application so no entries were created by default. If your application is graphical but EasyPBI did not detect it, you can manually add the desired entries using the ''Remove Desktop Entry'' and ''Remove Menu Entry'' buttons.

Under ''Executable'', the drop-down menu will display all of the binaries that came with the application. Select the binary that should launch when the user clicks the desktop icon or selects the application from the application menu. Alternately, you can select ''Custom Binary'' and input the path to the desired executable.

The ''Entry Label'' field allows you to customize the name that will appear with the icon and application menu entry.

The ''Icon'' drop-down menu allows you to select the ''.png'' file to use for the icon. This file must exist in ''~/EasyPBI/Modules/PBI_name/resources'' in order to appear in the drop-down menu. Use the ''Select Module'' button to re-select the module if you add the icon after loading the module.

The ''Menu Category'' drop-down menu is used to select the category the application menu entry will be added to.

To add a desktop entry, select an ''Executable'', input an ''Entry Label'', and click the ''+ Add Desktop Entry'' button. This will generate the ''.desktop'' file to be used by XDG-compliant desktops. The entry will appear under ''Current Desktop Entries''.

To add an application menu entry, select an ''Executable'', input an ''Entry Label'', and click the ''+ Add Menu Entry'' button. The generated ''.desktop'' file will appear under ''Current Menu Entries''.

==== External-Links ====

This tab, shown in Figure 8.1h, is used to customize how the specified binary starts.

'''Figure 8.1h: Configuring Custom Links for the PBI'''

[[Image:Easypbi7a.png]]

To customize how a binary starts, highlight it and click the ''Action'' drop-down menu. The possible actions are:

* '''binary:''' indicates that this is an executable. EasyPBI will automatically create the necessary wrapper and PATH links for you.

* '''linux:''' indicates that this is a Linux executable. EasyPBI will automatically create the necessary Linux wrapper and PATH links for you.

* '''keep:''' instructs the PBI to ''' ''not'' ''' overwrite an existing binary when linking a file into the LOCALBASE. By default, LOCALBASE is set to ''/usr/local''.

* '''replace:''' instructs the PBI to overwrite an existing binary when linking a file into the LOCALBASE.

* '''nocrash:''' disables the crashhandler GUI from running on this PBI. Note that the glue for the crash handler is not built into the base system yet.

If you select an ''Action'', use the up arrow to add it. If you change your mind, click the ''Clear Changes'' button.

=== Submit the Module ===

Once you are satisfied with the PBI, go to the "Module Editor" tab and use the "Select Module" button to select the PBI's module. Then click the "Package Module" button. A pop-up window will indicate that the module has been compressed and that a ''.tar.gz'' file has been added to the PBI module directory. The file name for our example PBI is ''~dru/EasyPBI/Modules/trickle.tar.gz''.

If you send that file to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}, it will be added to the PC-BSD® build servers so that the 32- and 64-bit versions of the PBI can be built. Once the built PBIs are tested, they will be added to AppCafe® so that other PC-BSD® users can benefit from the PBI.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Control Panel]]
[[category:EasyPBI]]
[[category:webpage referred]]
</noinclude>

EasyPBI

2013-02-11T20:36:14Z

Vater: /* Build the Module */

<noinclude>{{NavHeader|back=Control Panel|forward=About}}</noinclude>

EasyPBI is a graphical application that makes it easy to build a PBI module from a FreeBSD port. Beginning with PC-BSD® 9.1, EasyPBI ships with PC-BSD® and can be found in the [[Control Panel]].

This section demonstrates how to use this utility to convert an existing FreeBSD port into a PC-BSD® PBI. You may wish to skim the section on how to [[PBI Module Builder Guide | Create PBIs]] first, as well as refer to that Guide should you have trouble creating a PBI or wish to create a more complex PBI.

To start EasyPBI, double-click its icon in Control Panel or type '''EasyPBI''' from within an X terminal as your regular user account.

If the ports collection is not installed, you will receive the message shown in Figure 8.1a the first time you start EasyPBI.

'''Figure 8.1a: Ports Must be Installed to Use EasyPBI'''

[[File:Easypbi1d.png]]

If multiple users will be using the EasyPBI utility, go to ''[[Control Panel]]'' ➜ [[System Manager#Install FreeBSD Source and Ports| ''System Manager'' ➜ ''Tasks'']] and click the ''Fetch Ports Tree'' button. Alternately, use the following command as the superuser '''portsnap fetch extract'''. Either of these methods will install the ports collection into ''/usr/ports''.

If you are the only user who will be using the EasyPBI utility, click ''OK'' to launch the main EasyPBI screen, shown in Figure 8.1b. Click ''File'' ➜ ''Get Ports'' which will download the ports collection to the ''[[EasyPBI]]'' subdirectory located in your home directory.

'''Figure 8.1b: EasyPBI Graphical Interface'''

[[File:Easypbi1b.png]]

If the ports collection was already installed or was installed using System Manager or '''portsnap''', the message in the bottom area of the screen will instead indicate To get started, please push the ''New Module'' button.

== Creating a PBI Module ==

Before building a PBI, refer to the {{citelink|url=http://forums.pcbsd.org/forumdisplay.php?f=61|txt=PBI Requests forum}} to determine which PBIs have been requested by users. You should also check that a module does not already exist for the PBI in the {{citelink|url=http://trac.pcbsd.org/browser#pbi/modules|txt=PBI Modules}} section of trac. Existing modules are listed alphabetically, according to their category in the ports collection.

To create a new module, click the ''New Module'' button and use the browser to select the desired port from the FreeBSD ports tree. Once a port is selected, EasyPBI will attempt to automatically supply the port information for the PBI and display the results in the GUI. In the example shown in Figure 8.1c, the ''net/trickle'' port has been selected and the fields have been auto-filled in.

'''Figure 8.1c: Review the New Module'''

[[File:Easypbi1c.png]]

You should review these fields for accuracy. If you click "Get Port Info" {{citelink|url=http://freshports.org|txt=FreshPorts.org}} will open in the default web browser so that you can view additional information about the port.

A generic icon will be supplied for the module; you can change the default icon by clicking the ''Choose Icon'' button. When using a custom icon, use a 64x64 ''.png'' file with a transparent background.

Check the ''Create Desktop/Menu Entries' if you wish the program's icon to be available on the desktop and in the desktop's application menu.

Once the port information is complete, click the ''Create Module'' button and EasyPBI will produce the PBI module. The module will be named after the port and will be stored in a subdirectory of the ''EasyPBI/Modules'' directory in your home directory. In this example, the module is located in ''EasyPBI/Modules/trickle''.

=== Build the Module ===

Creating the module itself is very quick and takes less than a minute. However, you still need to build and test the module to make sure that the application works as expected. Depending upon the complexity of the application, you may have to edit the initial module then rebuild and retest it until you are satisfied with the PBI for the application.

Once the module is created, you are ready to build a PBI from the module. Click on the ''Build PBI'' tab and click the ''Select Module'' button to browse to the module you created. Figure 8.1d shows this tab with our example PBI selected.

'''Figure 8.1d: The Build PBI Tab'''

[[File:Easypbi3b.png]]

The top half of this screen contains modifiable settings which are used when building PBIs:

'''Save Settings as Defaults:''' the settings in this section revert back to the default settings when you exit EasyPBI. This allows you to override the default settings for a particular build. If you wish your changes to be permanent, click this button.

'''Output Directory:''' specifies the directory to store the built module. By default, it is the ''EasyPBI/PBI'' subdirectory of the user's home directory. Click the ''Change Directory'' button to select another location.

'''Digital Signature File:''' the PBIs available from the PC-BSD® repositories are digitally signed by the PC-BSD® project's signature file. If you are creating your own repository, click the ''Change File'' button to select your own digital signature file. [[Create Your Own PBI Repository]] provides instructions for creating a signature file.

'''Use TMPFS:''' if your build system has a lot of RAM, selecting this option can speed up the build.

'''Use Package Caching:''' this setting is recommended as it reuses previously built packages to speed up subsequent builds.

The rest of this screen is used to build the specified module:

'''Select Module:''' select the previously created module to build.

'''Build PBI:''' starts the build of the PBI module. It will prompt you for the superuser password and requires a working Internet connection in order to build the PBI. This process may take quite a while, depending upon the port selected and the speed of your computer. The build messages will be displayed in the window at the bottom of the tab. EasyPBI will inform you when the PBI build is finished, and whether it was successful or not.

'''Stop Build:''' stops the build process. Click the ''Build PBI'' button to resume the build.

'''Save Build Log:''' useful if the build fails. Will prompt you to select the location to store ''build.log'' which can be read with any ASCII text editor.

You can produce additional modules from the ''Create Module'' tab while a PBI build is running.

If the PBI build fails for some reason, you may need to modify the module as described in the next section. Use the build log to determine the error and modify the module as needed. If you are unsure how to fix the module, send the ''build.log'' for the failure to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}.

=== Test and Fine-Tune the Module ===

Once your build is finished, test the PBI to ensure that it installs and that the application works.

To install the PBI, become the superuser, '''cd''' to the "Output Directory", and use the '''pbi_add''' command. Unless you have specified your own digital signature, include the '''--no-checksig''' option.

'''su'''
Password:
'''cd ~dru/EasyPBI/PBI'''
'''ls'''
trickle-1.07_2_amd64.pbi trickle-1.07_2_amd64.pbi.sha256
'''pbi_add --no-checksig trickle-1.07_2_amd64.pbi'''
Verifying Checksum...OK
Extracting to: /usr/pbi/trickle-amd64
Installed: trickle-1.07_2

If the module installs successfully, perform the following tests:

* if you checked the box "Create Desktop/Menu Entries", verify that a desktop icon was created (from a desktop that supports icons), that an entry was added to that desktop's application menu, and that the application successfully launches from the application menu. If you used a custom icon, verify that the icon was used.

* start the application from the command line to determine if there are any error messages at application launch. When starting the application, specify the full path to the application's binary to make sure that you are testing the PBI's binary.

* for GUI applications, 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 the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}.

The "Module Editor" tab, seen in Figure 8.1e, can be used to modify the module's settings. Use the "Select Module" button to browse to the location of the module and to un-grey-out the settings in this screen.

'''Figure 8.1e: EasyPBI Module Editor'''

[[File:easypbi4a.png]]

Several tabs are provided, allowing you to customize the PBI module. It should be noted that most PBI modules do not require you to make any configuration changes in the "Module Editor" tab. This tab allows the creation of more complex PBI modules that require additional FreeBSD ports or scripts which are not provided by the default FreeBSD port.

The rest of this section describes the actions available within each tab. If you modify any settings in the PBI module, rebuild it then test again to see if the changes fixed the PBI.

==== pbi.conf ====

Typically the "Program Name", "Program Website", and "Program Author" are left at their default values. If this information is incorrect, you should email the FreeBSD port maintainer shown in the "Program Author" field so that the information can be corrected in the FreeBSD port.

If you choose to replace the "Program Icon", use a 64x64 ''.png'' file with a transparent background.

If your PBI requires a dependency that is not provided by the FreeBSD port, use the + button next to "Make Port Before" to select the needed port.

If you wish an additional port to be included with your PBI, use the + button next to "Make Port After" to select the desired port.

The "Make Options" field lets you specify a space separated list of options. The available options and their default settings will be listed in the ''OPTIONS='' section of the port's ''Makefile''.

If the resulting PBI needs to be run as the root user, check the "Require Root Permissions" box.

==== Resources ====

This tab, shown in Figure 8.1f, is used to add additional files to the PBI module.

'''Figure 8.1f: PBI Module Resource Configuration'''

[[Image:Easypbi5a.png]]

An example of an additional file would be an application that requires the user to accept a License. Use the "+Add Resource" button to browse to the location of the ''LICENSE'' file.

Another example would be when you wish to use a custom script to start the application rather than starting the application binary directly. A custom script could also be used to verify that the service is enabled or to generate a custom configuration file.

If the application uses custom installer graphics, add them using this screen.

==== Desktop/Menu Entries ====

This tab, shown in Figure 8.1g, is used to fine-tune the desktop icon and the application menu entry for the application.

'''Figure 8.1g: Customizing the PBI's Desktop and Menu Entries'''

[[Image:Easypbi6a.png]]

If the "Create Desktop/Menu Entries" box was checked when creating the module and EasyPBI detects that the application is graphical, the default entries for the application will be listed. In our PBI example, '''trickle''' is a command line application so no entries were created by default. If your application is graphical but EasyPBI did not detect it, you can manually add the desired entries using the "Remove Desktop Entry" and "Remove Menu Entry" buttons.

Under "Executable", the drop-down menu will display all of the binaries that came with the application. Select the binary that should launch when the user clicks the desktop icon or selects the application from the application menu. Alternately, you can select "Custom Binary" and input the path to the desired executable.

The "Entry Label" field allows you to customize the name that will appear with the icon and application menu entry.

The "Icon" drop-down menu allows you to select the ''.png'' file to use for the icon. This file must exist in ''~/EasyPBI/Modules/PBI_name/resources'' in order to appear in the drop-down menu. Use the "Select Module" button to re-select the module if you add the icon after loading the module.

The "Menu Category" drop-down menu is used to select the category the application menu entry will be added to.

To add a desktop entry, select an "Executable", input an "Entry Label", and click the "+Add Desktop Entry" button. This will generate the ''.desktop'' file to be used by XDG-compliant desktops. The entry will appear under "Current Desktop Entries".

To add an application menu entry, select an "Executable", input an "Entry Label", and click the "+Add Menu Entry" button. The generated ''.desktop'' file will appear under "Current Menu Entries".

==== External-Links ====

This tab, shown in Figure 8.1h, is used to customize how the specified binary starts.

'''Figure 8.1h: Configuring Custom Links for the PBI'''

[[Image:Easypbi7a.png]]

To customize how a binary starts, highlight it and click the "Action" drop-down menu. The possible actions are:

* '''binary:''' indicates that this is an executable. EasyPBI will automatically create the necessary wrapper and PATH links for you.

* '''linux:''' indicates that this is a Linux executable. EasyPBI will automatically create the necessary Linux wrapper and PATH links for you.

* '''keep:''' instructs the PBI to ''' ''not'' ''' overwrite an existing binary when linking a file into the LOCALBASE. By default, LOCALBASE is set to ''/usr/local''.

* '''replace:''' instructs the PBI to overwrite an existing binary when linking a file into the LOCALBASE.

* '''nocrash:''' disables the crashhandler GUI from running on this PBI. Note that the glue for the crash handler is not built into the base system yet.

If you select an "Action", use the up arrow to add it. If you change your mind, click the "Clear Changes" button.

=== Submit the Module ===

Once you are satisfied with the PBI, go to the "Module Editor" tab and use the "Select Module" button to select the PBI's module. Then click the "Package Module" button. A pop-up window will indicate that the module has been compressed and that a ''.tar.gz'' file has been added to the PBI module directory. The file name for our example PBI is ''~dru/EasyPBI/Modules/trickle.tar.gz''.

If you send that file to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}, it will be added to the PC-BSD® build servers so that the 32- and 64-bit versions of the PBI can be built. Once the built PBIs are tested, they will be added to AppCafe® so that other PC-BSD® users can benefit from the PBI.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Control Panel]]
[[category:EasyPBI]]
[[category:webpage referred]]
</noinclude>

EasyPBI

2013-02-11T20:22:14Z

Vater:

<noinclude>{{NavHeader|back=Control Panel|forward=About}}</noinclude>

EasyPBI is a graphical application that makes it easy to build a PBI module from a FreeBSD port. Beginning with PC-BSD® 9.1, EasyPBI ships with PC-BSD® and can be found in the [[Control Panel]].

This section demonstrates how to use this utility to convert an existing FreeBSD port into a PC-BSD® PBI. You may wish to skim the section on how to [[PBI Module Builder Guide | Create PBIs]] first, as well as refer to that Guide should you have trouble creating a PBI or wish to create a more complex PBI.

To start EasyPBI, double-click its icon in Control Panel or type '''EasyPBI''' from within an X terminal as your regular user account.

If the ports collection is not installed, you will receive the message shown in Figure 8.1a the first time you start EasyPBI.

'''Figure 8.1a: Ports Must be Installed to Use EasyPBI'''

[[File:Easypbi1d.png]]

If multiple users will be using the EasyPBI utility, go to ''[[Control Panel]]'' ➜ [[System Manager#Install FreeBSD Source and Ports| ''System Manager'' ➜ ''Tasks'']] and click the ''Fetch Ports Tree'' button. Alternately, use the following command as the superuser '''portsnap fetch extract'''. Either of these methods will install the ports collection into ''/usr/ports''.

If you are the only user who will be using the EasyPBI utility, click ''OK'' to launch the main EasyPBI screen, shown in Figure 8.1b. Click ''File'' ➜ ''Get Ports'' which will download the ports collection to the ''[[EasyPBI]]'' subdirectory located in your home directory.

'''Figure 8.1b: EasyPBI Graphical Interface'''

[[File:Easypbi1b.png]]

If the ports collection was already installed or was installed using System Manager or '''portsnap''', the message in the bottom area of the screen will instead indicate To get started, please push the ''New Module'' button.

== Creating a PBI Module ==

Before building a PBI, refer to the {{citelink|url=http://forums.pcbsd.org/forumdisplay.php?f=61|txt=PBI Requests forum}} to determine which PBIs have been requested by users. You should also check that a module does not already exist for the PBI in the {{citelink|url=http://trac.pcbsd.org/browser#pbi/modules|txt=PBI Modules}} section of trac. Existing modules are listed alphabetically, according to their category in the ports collection.

To create a new module, click the ''New Module'' button and use the browser to select the desired port from the FreeBSD ports tree. Once a port is selected, EasyPBI will attempt to automatically supply the port information for the PBI and display the results in the GUI. In the example shown in Figure 8.1c, the ''net/trickle'' port has been selected and the fields have been auto-filled in.

'''Figure 8.1c: Review the New Module'''

[[File:Easypbi1c.png]]

You should review these fields for accuracy. If you click "Get Port Info" {{citelink|url=http://freshports.org|txt=FreshPorts.org}} will open in the default web browser so that you can view additional information about the port.

A generic icon will be supplied for the module; you can change the default icon by clicking the ''Choose Icon'' button. When using a custom icon, use a 64x64 ''.png'' file with a transparent background.

Check the ''Create Desktop/Menu Entries' if you wish the program's icon to be available on the desktop and in the desktop's application menu.

Once the port information is complete, click the ''Create Module'' button and EasyPBI will produce the PBI module. The module will be named after the port and will be stored in a subdirectory of the ''EasyPBI/Modules'' directory in your home directory. In this example, the module is located in ''EasyPBI/Modules/trickle''.

=== Build the Module ===

Creating the module itself is very quick and takes less than a minute. However, you still need to build and test the module to make sure that the application works as expected. Depending upon the complexity of the application, you may have to edit the initial module then rebuild and retest it until you are satisfied with the PBI for the application.

Once the module is created, you are ready to build a PBI from the module. Click on the "Build PBI" tab and click the "Select Module" button to browse to the module you created. Figure 8.1d shows this tab with our example PBI selected.

'''Figure 8.1d: The Build PBI Tab'''

[[File:Easypbi3b.png]]

The top half of this screen contains modifiable settings which are used when building PBIs:

'''Save Settings as Defaults:''' the settings in this section revert back to the default settings when you exit EasyPBI. This allows you to override the default settings for a particular build. If you wish your changes to be permanent, click this button.

'''Output Directory:''' specifies the directory to store the built module. By default, it is the ''EasyPBI/PBI'' subdirectory of the user's home directory. Click the "Change Directory" button to select another location.

'''Digital Signature File:''' the PBIs available from the PC-BSD® repositories are digitally signed by the PC-BSD® project's signature file. If you are creating your own repository, click the "Change File" button to select your own digital signature file. [[#Create Your Own PBI Repository|Create Your Own PBI Repository]] provides instructions for creating a signature file.

'''Use TMPFS:''' if your build system has a lot of RAM, selecting this option can speed up the build.

'''Use Package Caching:''' this setting is recommended as it reuses previously built packages to speed up subsequent builds.

The rest of this screen is used to build the specified module:

'''Select Module:''' select the previously created module to build.

'''Build PBI:''' starts the build of the PBI module. It will prompt you for the superuser password and requires a working Internet connection in order to build the PBI. This process may take quite a while, depending upon the port selected and the speed of your computer. The build messages will be displayed in the window at the bottom of the tab. EasyPBI will inform you when the PBI build is finished, and whether it was successful or not.

'''Stop Build:''' stops the build process. Click the "Build PBI" button to resume the build.

'''Save Build Log:''' useful if the build fails. Will prompt you to select the location to store ''build.log'' which can be read with any ASCII text editor.

You can produce additional modules from the "Create Module" tab while a PBI build is running.

If the PBI build fails for some reason, you may need to modify the module as described in the next section. Use the build log to determine the error and modify the module as needed. If you are unsure how to fix the module, send the ''build.log'' for the failure to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}.

=== Test and Fine-Tune the Module ===

Once your build is finished, test the PBI to ensure that it installs and that the application works.

To install the PBI, become the superuser, '''cd''' to the "Output Directory", and use the '''pbi_add''' command. Unless you have specified your own digital signature, include the '''--no-checksig''' option.

'''su'''
Password:
'''cd ~dru/EasyPBI/PBI'''
'''ls'''
trickle-1.07_2_amd64.pbi trickle-1.07_2_amd64.pbi.sha256
'''pbi_add --no-checksig trickle-1.07_2_amd64.pbi'''
Verifying Checksum...OK
Extracting to: /usr/pbi/trickle-amd64
Installed: trickle-1.07_2

If the module installs successfully, perform the following tests:

* if you checked the box "Create Desktop/Menu Entries", verify that a desktop icon was created (from a desktop that supports icons), that an entry was added to that desktop's application menu, and that the application successfully launches from the application menu. If you used a custom icon, verify that the icon was used.

* start the application from the command line to determine if there are any error messages at application launch. When starting the application, specify the full path to the application's binary to make sure that you are testing the PBI's binary.

* for GUI applications, 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 the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}.

The "Module Editor" tab, seen in Figure 8.1e, can be used to modify the module's settings. Use the "Select Module" button to browse to the location of the module and to un-grey-out the settings in this screen.

'''Figure 8.1e: EasyPBI Module Editor'''

[[File:easypbi4a.png]]

Several tabs are provided, allowing you to customize the PBI module. It should be noted that most PBI modules do not require you to make any configuration changes in the "Module Editor" tab. This tab allows the creation of more complex PBI modules that require additional FreeBSD ports or scripts which are not provided by the default FreeBSD port.

The rest of this section describes the actions available within each tab. If you modify any settings in the PBI module, rebuild it then test again to see if the changes fixed the PBI.

==== pbi.conf ====

Typically the "Program Name", "Program Website", and "Program Author" are left at their default values. If this information is incorrect, you should email the FreeBSD port maintainer shown in the "Program Author" field so that the information can be corrected in the FreeBSD port.

If you choose to replace the "Program Icon", use a 64x64 ''.png'' file with a transparent background.

If your PBI requires a dependency that is not provided by the FreeBSD port, use the + button next to "Make Port Before" to select the needed port.

If you wish an additional port to be included with your PBI, use the + button next to "Make Port After" to select the desired port.

The "Make Options" field lets you specify a space separated list of options. The available options and their default settings will be listed in the ''OPTIONS='' section of the port's ''Makefile''.

If the resulting PBI needs to be run as the root user, check the "Require Root Permissions" box.

==== Resources ====

This tab, shown in Figure 8.1f, is used to add additional files to the PBI module.

'''Figure 8.1f: PBI Module Resource Configuration'''

[[Image:Easypbi5a.png]]

An example of an additional file would be an application that requires the user to accept a License. Use the "+Add Resource" button to browse to the location of the ''LICENSE'' file.

Another example would be when you wish to use a custom script to start the application rather than starting the application binary directly. A custom script could also be used to verify that the service is enabled or to generate a custom configuration file.

If the application uses custom installer graphics, add them using this screen.

==== Desktop/Menu Entries ====

This tab, shown in Figure 8.1g, is used to fine-tune the desktop icon and the application menu entry for the application.

'''Figure 8.1g: Customizing the PBI's Desktop and Menu Entries'''

[[Image:Easypbi6a.png]]

If the "Create Desktop/Menu Entries" box was checked when creating the module and EasyPBI detects that the application is graphical, the default entries for the application will be listed. In our PBI example, '''trickle''' is a command line application so no entries were created by default. If your application is graphical but EasyPBI did not detect it, you can manually add the desired entries using the "Remove Desktop Entry" and "Remove Menu Entry" buttons.

Under "Executable", the drop-down menu will display all of the binaries that came with the application. Select the binary that should launch when the user clicks the desktop icon or selects the application from the application menu. Alternately, you can select "Custom Binary" and input the path to the desired executable.

The "Entry Label" field allows you to customize the name that will appear with the icon and application menu entry.

The "Icon" drop-down menu allows you to select the ''.png'' file to use for the icon. This file must exist in ''~/EasyPBI/Modules/PBI_name/resources'' in order to appear in the drop-down menu. Use the "Select Module" button to re-select the module if you add the icon after loading the module.

The "Menu Category" drop-down menu is used to select the category the application menu entry will be added to.

To add a desktop entry, select an "Executable", input an "Entry Label", and click the "+Add Desktop Entry" button. This will generate the ''.desktop'' file to be used by XDG-compliant desktops. The entry will appear under "Current Desktop Entries".

To add an application menu entry, select an "Executable", input an "Entry Label", and click the "+Add Menu Entry" button. The generated ''.desktop'' file will appear under "Current Menu Entries".

==== External-Links ====

This tab, shown in Figure 8.1h, is used to customize how the specified binary starts.

'''Figure 8.1h: Configuring Custom Links for the PBI'''

[[Image:Easypbi7a.png]]

To customize how a binary starts, highlight it and click the "Action" drop-down menu. The possible actions are:

* '''binary:''' indicates that this is an executable. EasyPBI will automatically create the necessary wrapper and PATH links for you.

* '''linux:''' indicates that this is a Linux executable. EasyPBI will automatically create the necessary Linux wrapper and PATH links for you.

* '''keep:''' instructs the PBI to ''' ''not'' ''' overwrite an existing binary when linking a file into the LOCALBASE. By default, LOCALBASE is set to ''/usr/local''.

* '''replace:''' instructs the PBI to overwrite an existing binary when linking a file into the LOCALBASE.

* '''nocrash:''' disables the crashhandler GUI from running on this PBI. Note that the glue for the crash handler is not built into the base system yet.

If you select an "Action", use the up arrow to add it. If you change your mind, click the "Clear Changes" button.

=== Submit the Module ===

Once you are satisfied with the PBI, go to the "Module Editor" tab and use the "Select Module" button to select the PBI's module. Then click the "Package Module" button. A pop-up window will indicate that the module has been compressed and that a ''.tar.gz'' file has been added to the PBI module directory. The file name for our example PBI is ''~dru/EasyPBI/Modules/trickle.tar.gz''.

If you send that file to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}, it will be added to the PC-BSD® build servers so that the 32- and 64-bit versions of the PBI can be built. Once the built PBIs are tested, they will be added to AppCafe® so that other PC-BSD® users can benefit from the PBI.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Control Panel]]
[[category:EasyPBI]]
[[category:webpage referred]]
</noinclude>

Meta Package Manager

2013-02-05T21:24:42Z

Vater:

<noinclude>{{NavHeader|back=Update Manager|forward=Create Your Own PBI Repository}}</noinclude>

'''pc-metapkgmanager''' is the back-end command line utility used by the PC-BSD® installer, System Manager, Update Manager, and Warden® to manage meta-packages. Meta-packages are like system components, and include supported and unsupported desktops, development utilities, hardware drivers, and miscellaneous applications such as MythTV or XBMC.

Beginning with version 9.1, PC-BSD® uses metapkgsets to determine which system components are available and which applications are installed with each system component. Currently, two metapkgsets are available: ''pcbsd'' which defines the available desktop components, and ''warden'' which defines the components available when creating a jail with Warden® or installing a PC-BSD® server. You can view the contents of these metapkgsets on {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/current#build-files/metapkgsets|txt=trac}}.

The '''pc-metapkgmanager''' command can be used at the command line to install or delete meta-packages, update to the latest package set, or to change the default metapkgset. If you type the command without any options, it will display its usage:

'''pc-metapkgmanager'''
usage: pc-metapkgmanager [options]
Options:
add pkg1,pkg2 <loc> -- Add the specified list of meta-packages
<loc> should be a FTP / HTTP url where pkg_add
can fetch packages, or an absolute path to
location of pkg files on disk.
checkup -- Check for updates to pkgs
del pkg1,pkg2 -- Delete the specified list of meta-packages
list -- List the available meta-packages
status <pkg> -- List the status of the specified meta-packages
update pkg,pkg2 <loc> -- Update system packages. Can use 'all' or <pkg,pkg2>.
<loc> should be a FTP / HTTP url where pkg_add
can fetch packages, or an absolute path to
location of pkg files on disk.
--pkgset <pkgset> -- Change default pkgset we are using
--chroot <dir> -- Operate on the directory specified using chroot

=== Finding, Installing, and Uninstalling Meta-Packages ===

To determine which meta-packages are available:

'''pc-metapkgmanager list |more'''
Meta Package: Awesome
-------------------------------------
Description: A highly configurable, next generation framework window manager
Icon: /var/db/pc-metapkgmanager/pkgsets/pcbsd/Awesome/pkg-icon.png
Parent: Unsupported-Desktops
Desktop: YES
Required Packages:
awesome-3.4.13
Meta Package: Compiz
-------------------------------------
Description: Compiz - OpenGL compositing manager
Icon: /var/db/pc-metapkgmanager/pkgsets/pcbsd/Compiz/pkg-icon.png
Parent: Misc
Desktop: NO
Required Packages:
compiz-fusion-0.8.4_2
Meta Package: Desktops
-------------------------------------
Description: Supported Desktop Environments for your PC-BSD system.
Icon: /var/db/pc-metapkgmanager/pkgsets/pcbsd/Desktops/pkg-icon.png
Desktop: NO
Category Entry
Meta Package: Development
-------------------------------------
Description: Development tools and utilities for your Desktop
Icon: /var/db/pc-metapkgmanager/pkgsets/pcbsd/Development/pkg-icon.png
Desktop: NO
--More--(byte 989)

To view which meta-packages are available in an alternate metapkgset, specify the metapkgset name. For example, to view the available ''warden'' meta-packages from your desktop, use this command:

'''pc-metapkgmanager --pkgset warden list | more'''
Meta Package: Apache
-------------------------------------
Description: The Apache Web Server
Icon: /var/db/pc-metapkgmanager/pkgsets/warden/Apache/pkg-icon.png
Parent: Web-Servers
Desktop: NO
Required Packages:
apache-2.2.22_6
Meta Package: BigBlueButton
-------------------------------------
Description: BigBlueButton enables universities and colleges to deliver
a high-quality learning experience to remote students.
Icon: /var/db/pc-metapkgmanager/pkgsets/warden/BigBlueButton/pkg-icon.png
Parent: Web-Apps
Desktop: NO
Required Packages:
mysql-server-5.5.27
bigbluebutton-0.71_3
Meta Package: Database-Servers
-------------------------------------
Description: Database Server Software
Icon: /var/db/pc-metapkgmanager/pkgsets/warden/Database-Servers/pkg-icon.png
Desktop: NO
Category Entry
Meta Package: Development
-------------------------------------
Description: Development tools and utilities
Icon: /var/db/pc-metapkgmanager/pkgsets/warden/Development/pkg-icon.png
--More--(byte 989)

To permanently change the default metapkgset between ''pcbsd'' and ''warden'', modify the ''PCBSD_METAPKGSET'' variable in ''/usr/local/etc/pcbsd.conf''.

To determine if a meta-package is installed, specify its "Meta Package" name as shown in the output of the '''pc-metapkgmanager list''' command. For example, to see if the Awesome desktop is installed:

'''pc-metapkgmanager status Awesome'''
The meta-pkg Awesome is not installed

To install the meta-package, use the '''add''' option and specify the meta-package name. Only the superuser can install meta-packages. If you do not specify the URL, the default mirror will be used. If you receive an error when downloading the package, you can change the default mirror in ''Control Panel'' ➜ ''[[System Manager]]'' ➜ ''Mirrors''.

The following example installs the Awesome meta-package. '''pc-metapkgmanager''' will provide messages regarding the status of the installation:

'''pc-metapkgmanager add Awesome'''
Pending Meta-Package changes: 1
Package source: NET
Preparing to add: Awesome...
Checking for updates to old packages...
Installing Meta-Package: Awesome
Getting package list...
Pending package changes: 6
Downloading package: awesome-3.4.13
//usr/local/tmp/awesome-3.4.13.txz 100% of 704 kB 637 kBps
Downloading package: libev-4.11,1
//usr/local/tmp/libev-4.11,1.txz 100% of 117 kB 361 kBps
Downloading package: libxdg-basedir-1.1.1
//usr/local/tmp/libxdg-basedir-1.1.1.txz 100% of 11 kB 130 kBps
Downloading package: xcb-util-image-0.3.8
//usr/local/tmp/xcb-util-image-0.3.8.txz 100% of 18 kB 141 kBps
Downloading package: xcb-util-keysyms-0.3.8
//usr/local/tmp/xcb-util-keysyms-0.3.8.txz 100% of 8040 B 72 kBps
Downloading package: xcb-util-wm-0.3.8
//usr/local/tmp/xcb-util-wm-0.3.8.txz 100% of 35 kB 148 kBps
Installing package: awesome-3.4.13
Skipping installed package: libev-4.11,1
Skipping installed package: libxdg-basedir-1.1.1
Skipping installed package: xcb-util-image-0.3.8
Skipping installed package: xcb-util-keysyms-0.3.8
Skipping installed package: xcb-util-wm-0.3.8
The meta-pkg Awesome is installed
Finished Meta-Package: Awesome
Meta-Package changes finished!

To delete an installed meta-package, specify its name. Only the superuser can uninstall meta-packages. As seen in the following example, '''pc-metapkgmanager''' automatically determines which dependent packages are still needed by other applications and which can be safely removed.

'''pc-metapkgmanager del Awesome'''
Pending Meta-Package changes: 1
Removing Meta-Package: Awesome
Getting package list...
Pending package changes: 66
Removing: awesome-3.4.13
Skipping Meta-Required: giflib-4.2.0_2
Removing: libev-4.11,1
Removing: libxdg-basedir-1.1.1
Removing: xcb-util-image-0.3.8
Removing: xcb-util-keysyms-0.3.8
Removing: xcb-util-wm-0.3.8
Skipping Required: bitstream-vera-1.10_5
Skipping Required: cairo-1.10.2_4,2
<snip output of other required packages>
The meta-pkg Awesome is not installed
Meta-Package changes finished!

=== Upgrading Meta-Packages ===

'''pc-metapkgmanager''' can also be used to determine if any meta-packages are out of date and to update meta-packages. To determine if any meta-packages have newer versions:

'''pc-metapkgmanager checkup'''
All packages are up to date!

In this example, all meta-packages are at their latest versions. If any were out of date, you would instead receive the message "The following package updates are available:" followed by the names of the out-of-date meta-packages.

To update a meta-package, use the '''pc-metapkgmanager update''' command followed by the name of the specific meta-package or the word '''all''' to update all out-of-date meta-packages.

'''pc-metapkgmanager''' records any error messages to ''/tmp/.pc-metamanager.log''. This log file automatically rotates whenever it reaches 5MB in size.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Maintaining and Extending PC-BSD®]]
[[category:Meta Package Manager]]
</noinclude>

PBI Manager

2013-02-05T21:19:48Z

Vater:

<noinclude>{{NavHeader|back=Using AppCafe®|forward=Update Manager}}</noinclude>

PBI Manager is a suite of command line utilities which can be used to install, remove, create and manage PBIs. It is also available for [[#Installing PBI Manager|FreeBSD systems]]. The PBI Manager is released under the {{citelink|url=http://www.freebsd.org/copyright/freebsd-license.html|txt=BSD license}}.

== Features ==

The 9.x PBI format introduced the following features:

* '''Upgrade deltas:''' since PBIs are self-contained, installation files tend to be large. In the previous implementation, updating a PBI required the re-downloading of the entire installation archive. For larger applications this could be a time-consuming process, especially over low bandwidth connections. The new PBI specification performs updates using binary diff patches known as PBP (Push Button Patch) files. PBPs are a fraction of the PBI's size; in some cases less than 5% of the original PBI archive. An upgrade automatically checks for for the presence of a PBP file and attempts to use it, only falling back to the original archive should the process fail.

* '''Library and file sharing:''' in the previous implementation of the PBI format it was common that identical files existed between various applications. These duplicates, while necessary to provide the self-contained functionality, wasted both disk space and runtime memory. This waste of space has been greatly reduced through the use of a hash-dir directory where libraries and common files are shared through a system of hard links. When an identical file is found in a PBI, the original will be removed and a hard-link stored in the hash-dir. After a PBI has been removed, any unneeded files left in the hash-dir are cleaned up by the pbid(8) daemon which monitors and maintains the integrity of the shared files.

* '''Repository management:''' allows administrators and PBI builders to create and manage their own repositories of PBIs. This repository system provides a number of tools for PBI distribution, release management, and repository browsing.

* '''Digitally signed PBIs:''' each repository includes an openssl public key file which is installed on the end user's system. Each PBI includes several signatures for the content archive and installation and removal scripts. During the PBI installation process, these signatures are checked to confirm that the archive has not been tampered with during transit. This key file is also used to associate a particular PBI with a parent repository for upgrade purposes, since it is possible that multiple repositories will have the same applications.

* '''Root password not required:''' most applications can be installed and upgraded by regular user (non-root) accounts. This allows enhanced security in office or home situations, where users can now add/remove desktop applications without needing access to the root password. PBIs that impact on the security of the system (e.g. installing a web server) will require root access.

* '''Implementation:''' the previous PBI design was developed in QT/KDE C++, making it inappropriate for use at the command line. The new format is implemented 100% in shell and is comprised of command-line utilities, each with an associated man page. These utilities are discussed in more detail in the rest of this section.

== Additional Resources ==

* {{citelink|url=http://www.pcbsd.org/~kris/pbi9-slides.pdf|txt=The PBI Format Re-implemented for Free/PC-BSD® (conference slides)}}

* {{citelink|url=http://www.pcbsd.org/~kris/asiabsdcon2011-pbi9.pdf|txt=The PBI Format Re-implemented for Free/PC-BSD® (formal paper)}}

* [[PBI9 Format|The PBI Format for 9.0 and Beyond]]

== Release History ==

; 1.0: ({{#dateformat:24 Sept 2012}}) - Kris Moore

:* Fix build with CLANG

:* Add support for shared XDG / Mime directories among users

:* Enhance icons handling when adding to LOCALBASE

:* Fixed a bug pruning the old version from an INDEX

:* Get rid of left-over .sha256 files in auto-build directories

; 0.9.9: ({{#dateformat:27 Aug 2012}}) - Kris Moore

:* Added new C .pbiwrapper file, which can set LD* variables, and use setuid among others

:* Fixed issues doing pkg_add on pkgs which need license agreements

:* Added support for saving / re-creating users & groups that a port may need

:* Fixed some issues getting the correct Package Name

:* Fixed and issue using exclude lists

:* Added option to view archive contents with pbi_add -i -v

:* Added internal priority system to pbi autobuilding

:* Speed up build system with better package caching

:* Added additional tmpfs support for auto-building, to further speed up process

:* Auto-source /etc/profile, to catch any HTTP_PROXY / FTP_PROXY values the user may set

; 0.9.8: ({{#dateformat:11 May 2011}}) - Kris Moore

:* Add support for copying linux binaries from ports, with their respective libs

:* Add GUI speed calculations when downloading

:* Allow some overrides to built-in defaults, for FreeNAS / pfSense and others

:* Added fail-safes to make sure the user didn't manually mount things into a PBI directory

; 0.9.7: ({{#dateformat:07 Dec 2011}}) - Kris Moore

:* Use -a flag for fetch to retry after soft failures

:* Do not create binary patch files, if they are larger than the source

:* Add ability to use /etc/pbi-make.conf on system, letting us set universal make options

:* Simplify the startup with less parsing commands

:* Add new -R flag for pbi_add, which only downloads a PBI from a mirror, without installing it

:* Add support for using "ccache" automatically if configured on the host system

:* Fixed a bug using "pbi_create" on a directory manually, make sure file end up in proper PBI application directory

:* Make sure we use the systems share/icons directory to use shared cursors / icons across all PBIs

; 0.9.6: ({{#dateformat:07 Nov 2011}})

:* Fix some bugs doing cleanup of stagedir / build directories

:* Properly kill fetch process when canceling a download

:* Improve buildworld on FreeBSD to use /usr/src if it already has source

:* Fix some random warnings when building via sudo

; 0.9.5: ({{#dateformat:03 Nov 2011}})

:* Add sizes of PBIs to the meta index files

:* Fix bug adding default icon to PBIs when none is specified

:* Fix handling of PBI_PROGREVISION

:* Make sure we unmount nullfs mounts completely

; 0.9.4: ({{#dateformat:19 Oct 2011}})

:* Fix issue using system-fonts in PBIs

:* Fix issue removing files which have been set r--

:* Slow down fetch process to fix issues with fetch protocol errors

:* Fix bug coping linux libraries into final PBI file

:* Allow user settings in external-links to overwrite auto-detected values

:* Fix bug running "stat" on files with spaces in name

:* Validate the build checksum before doing patching

:* Speed up builds with optional --tmpfs flags

:* Add priority system to building modules

:* Fix issues setting proxy support from pbi.conf / pcbsd.conf files

:* Validate repo URL's when creating .rpo file

; 0.9.3: ({{#dateformat:18 Jul 2011}})

:* Unset variables between auto-builds

:* Fixed some warnings with 'cut' when parsing i18n strings

:* When doing auto-builds, run through alphabetically

:* Increase check frequency when first trying to download index's

:* Speed up the hashdir merging

:* Show repo MD5 with listings

:* If no index files, do not fail on listing, just show empty repo

; 0.9.2: ({{#dateformat:23 May 2011}})

:* Fixed usage errors with "tr"

:* Syntax fixes when trying to install app with no meta-data

:* Fixed some bugs with binary patching

:* Fixed auto-builder using the PBI_BUILDKEY in modules pbi.conf file

:* When building ports, do not export PREFIX since it confuses some linux ports

:* Perform check if user is root, if PBI is flagged root-only

:* Auto-builder now checks if port is compatible with arch type of system

; 0.9.1: ({{#dateformat:3 May 2011}})

:* Initial public release

== What is the PBI format? ==

One of the things holding back mainstream adoption of open source desktops is the package management format. With almost all open source desktops, software is simply treated as part of the operating system. Thus, when performing an update of some seemingly trivial application, you run the risk of potentially needing to upgrade other packages which could break other critical parts of your desktop.

While package management systems have gotten better at resolving dependency issues, trying to fix conflicts to prevent breakage before it occurs, they still do not address the underlying problem: every software package is a part of the system, and pulling on any one thread has the potential of causing a break somewhere farther down the line.

The PBI format tries to correct this underlying flaw. Rather than making every application a part of the base system, PBIs are self-contained, including their own dependent library tree and related data. As a result, when you install a PBI there are no dependency issues to resolve, and applications can be added or removed freely, without fear of causing breakage to the desktop or any other installed software.

== Installing PBI Manager ==

If you are running PC-BSD® 9 or higher, then the PBI Manager is already installed, and you can use it via the command-line, or a front-end such as the AppCafe®.

FreeBSD users can install it from the {{citelink|url=http://www.freshports.org/ports-mgmt/pbi-manager|txt=ports tree}}.

Users interested in installing the development version from our {{citelink|url=http://trac.pcbsd.org/brower/pcbsd/current/src-sh/pbi-manager/|txt=SVN repository}} can do so with the following commands: 

{{txtbox|width=65%|box='''svn co {{svn}}svn.pcbsd.org/pcbsd/current/src-sh/pbi-manager''' 
'''cd pbi-manager''' 
'''make install'''}}

'''NOTE: The development version may be unstable / buggy, use at your own risk'''

== Getting PBI Files ==

A list of approved and available PBIs can be viewed with '''pbi_info -i''' or '''pbi_browser''', and then installed with '''pbi_add -r <pbiname>'''.

'''NOTE:''' PBI files previously created for PC-BSD® 7.x/8.x will NOT work with PBI Manager as it was designed for version 9.x.

== Underlying File / Directory Structure ==

The underlying files and directories used by PBI Manager are as follows:

* '''/usr/local/etc/pbi.conf''': location of the PBI Manager configuration file

* '''/usr/pbi/''': where PBIs are installed on the system

* '''/var/db/pbi/''': contains data files related to installed PBIs and repositories

* '''/usr/local/sbin/pbi_*''': location of the PBI Manager commands

* '''/usr/local/share/pbi-manager/module-examples/convertoldmod.sh''': script which can be used to convert an existing 7.x or 8.x PBI module to the new 9.x format

== Feedback / Reporting Problems ==

Feedback, problem reports, and general discussion are welcome on the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=PBI Developers Mailing list}}.

== Command Reference ==

The following commands are installed by PBI Manager. For more details, refer to that command's man page. Note that single character commands can not be stacked. As an example, you must type '''pbi_add -i -v''' as '''pbi_add -iv''' will fail.

=== pbi_add(1) ===

Similar to FreeBSD's '''pkg_add''', the '''pbi_add''' command is used for adding/installing PBIs on a system, either from a local file or remotely from a repository. This utility supports the options listed in Table 7.2a. All of the options, except for '''-r''', assume that the ''.pbi'' file has already been downloaded and is in the current or specified directory.

'''Table 7.2a: pbi_add Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-e'''}}
{{Tbl-cell|row=1|extract only, do not install; will extract the archive to ''~/<pbidirname>'' unless the '''-o''' option is used}}
|-
{{Tbl-cell|row=2|'''-f'''}}
{{Tbl-cell|row=2|force installation, overwriting an already installed copy of the application}}
|-
{{Tbl-cell|row=3|'''-g'''}}
{{Tbl-cell|row=3|show path to icons and images for GUI installations}}
|-
{{Tbl-cell|row=4|'''-i'''}}
{{Tbl-cell|row=4|display information about specified PBI; if combined with '''-v''', will display all of the files that will be installed with the PBI}}
|-
{{Tbl-cell|row=5|'''-l'''}}
{{Tbl-cell|row=5|display license for specified PBI}}
|-
{{Tbl-cell|row=6|'''-o outdir'''}}
{{Tbl-cell|row=6|specify the directory to use when extracting the PBI with '''-e'''}}
|-
{{Tbl-cell|row=7|'''-r'''}}
{{Tbl-cell|row=7|remote fetch installation file from update server; the system architecture and version will be automatically determined in order to fetch the correct file and resume support is built-in}}
|-
{{Tbl-cell|row=8|'''-R'''}}
{{Tbl-cell|row=8|remote fetch the install file from the update server but do not install}}
|-
{{Tbl-cell|row=9|'''-v'''}}
{{Tbl-cell|row=9|enable verbose output}}
|-
{{Tbl-cell|row=10|'''--checkscript'''}}
{{Tbl-cell|row=10|display any custom scripts used in the installation/removal of the PBI}}
|-
{{Tbl-cell|row=11|'''--licagree'''}}
{{Tbl-cell|row=11|agree to license terms and conditions; to view the license, use '''-l'''}}
|-
{{Tbl-cell|row=12|'''--no-checksig'''}}
{{Tbl-cell|row=12|skip the openssl signature verification of the PBI data}}
|-
{{Tbl-cell|row=13|'''--no-checksum'''}}
{{Tbl-cell|row=13|skip the checksum verification of the archive data}}
|-
{{Tbl-cell|row=14|'''--no-hash'''}}
{{Tbl-cell|row=14|disable using the shared hash dir}}
|-
{{Tbl-cell|row=15|'''--repo repoid'''}}
{{Tbl-cell|row=15|specify which repository to use}}
|-
{{Tbl-cell|row=16|'''--rArch arch'''}}
{{Tbl-cell|row=16|manually specify the PBI architecture type of i386 or amd64}}
|-
{{Tbl-cell|row=17|'''--rVer version'''}}
{{Tbl-cell|row=17|specify which version of the PBI to install}}
|-
|}

For security reasons, it is recommend that users first use the '''-i -v''' and '''--checkscript''' options to view archive contents and installation scripts prior to installing a PBI file.

To install a PBI from a remote repository, use: '''pbi_add -r name_of.pbi'''. The following example will install the alpine PBI on a 32-bit system:

{{txtbox|width=65%|box='''pbi_add -r alpine''' 
Downloading {{ftp}}ftp.pcbsd.org/pub/mirror/PBI/mail/alpine/9/x32/alpine-2.00_3-i386.pbi 
/usr/pbi/.alpine-2.00_3-i386.pbi 100% of 11 MB 295 kBps 00m00s 
Verifying Checksum...OK 
Extracting to: /usr/pbi/alpine-i386 
Installed: Alpine-2.00_3}}

PBI Manager will automatically detect the architecture and install the appropriate PBI. If only a 32-bit version is available and you are on a 64-bit system, the 32-bit PBI will be installed and will work correctly on the PC-BSD® system.

If you previously downloaded the PBI, do not include the '''-r''' switch and give the fullname of the PBI:

{{txtbox|width=65%|box='''pbi_add alpine-2.00_3-i386.pbi'''}}

=== pbi_addrepo(8) ===

The '''pbi_addrepo''' command is used to register a new PBI repository on a system. If the '''pbid''' daemon is running, the repository's index and meta files will be automatically fetched and made ready for browsing. The command has one argument: the name of the repository file. Repository files have a ''.rpo'' extension and are created with the '''pbi_makerepo''' command.

=== pbi_autobuild(8) ===

The '''pbi_autobuild''' command is used on the PBI build system to build any out-of-date or new packages. It can traverse the FreeBSD ports and metadata trees, building missing PBI files or PBIs in which the target port version has been updated. Instructions for using this command to keep a custom repository up-to-date can be found in the section [[Create Your Own PBI Repository#Configure the Automatic Build of Updated Ports|Configure the Automatic Build of Updated Ports]].

Table 7.2b summarizes this command's options:

'''Table 7.2b: pbi_autobuild Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-c confdir'''}}
{{Tbl-cell|row=1|mandatory; specify the directory containing the PBI configuration modules; any found ''pbi.conf'' files will be parsed, and if PBI_MAKEPORT is set, the target port will be used for the build; if PBI_MAKEPORT is unset, the auto-build will attempt to match the module to a FreeBSD port based upon the dirname of ''pbi.conf''}}
|-
{{Tbl-cell|row=2|'''-d portsdir'''}}
{{Tbl-cell|row=2|specify an alternative ports directory; defaults to ''/usr/ports/''}}
|-
{{Tbl-cell|row=3|'''-h script'''}}
{{Tbl-cell|row=3|specify a helper script to call after building a PBI}}
|-
{{Tbl-cell|row=4|'''-o outdir'''}}
{{Tbl-cell|row=4|mandatory; the directory to place the finished PBI files}}
|-
{{Tbl-cell|row=5|'''-p num'''}}
{{Tbl-cell|row=5|if your build hardware has the CPU and disk I/O to support concurrent build processes, specify the number of concurrent builds}}
|-
{{Tbl-cell|row=6|'''-32'''}}
{{Tbl-cell|row=6|include when building a 32-bit PBI on a 64-bit system}}
|-
{{Tbl-cell|row=7|'''--genpatch'''}}
{{Tbl-cell|row=7|when building a new PBI, check for archived copies and generate smaller patch updates to the new version (*.pbp files)}}
|-
{{Tbl-cell|row=8|'''--keep num'''}}
{{Tbl-cell|row=8|when building new PBIs, keep <num> copies of past versions of working PBI in ''<outdir>/archived/'' folder; these archived copies can be used with the '''--genpatch''' command to generate update patch files}}
|-
{{Tbl-cell|row=9|'''--pkgcache'''}}
{{Tbl-cell|row=9|enable caching of ''.txz'' pkg files which greatly speeds up subsequent builds of a PBI}}
|-
{{Tbl-cell|row=10|'''--prune'''}}
{{Tbl-cell|row=10|remove any PBIs which no longer have an associated module}}
|-
{{Tbl-cell|row=11|'''--tmpfs'''}}
{{Tbl-cell|row=11|automatically create and mount a tmp filesystem which can speed up port compiles on systems with available RAM}}
|-
{{Tbl-cell|row=12|'''--sign keyfile'''}}
{{Tbl-cell|row=12|digitally sign the PBI file with the specified openssl private key file}}
|-
|}

=== pbi_browser(1) ===

The '''pbi_browser''' command provides a CLI front-end to browsing a repository's available PBIs. Options for viewing categories and searching by keyword are available, and once the desired PBI is located, it will show the '''pbi_add''' command which can be used to install the application. Table 7.2c summarizes the available options.

'''Table 7.2c: pbi_browser Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-c category'''}}
{{Tbl-cell|row=1|displays a list of PBIs in the specified category}}
|-
{{Tbl-cell|row=2|'''-s search'''}}
{{Tbl-cell|row=2|search for PBIs containing the specified string in the name, description, or keywords}}
|-
{{Tbl-cell|row=3|'''--listcats'''}}
{{Tbl-cell|row=3|list the available categories}}
|-
{{Tbl-cell|row=4|'''--viewall'''}}
{{Tbl-cell|row=4|list all available PBIs}}
|-
|}

=== pbi.conf(5) ===

''pbi.conf'' is an ASCII text configuration file containing values that are used by the various '''pbi_*''' commands. The proxy variables are only needed if the system uses a proxy server to access the Internet. Table 7.2d lists the supported variables.

'''Table 7.2d: pbi_conf Variables'''

{{Tbl-init}}
{{Tbl-title|width=20%|'''Variable'''}}
{{Tbl-title|width=80%|'''Description'''}}
|-
{{Tbl-cell|row=1|PBID_REFRESH}}
{{Tbl-cell|row=1|wakeup time in seconds for '''pbid''' to run its checks}}
|-
{{Tbl-cell|row=2|PBI_INDEXREFRESH}}
{{Tbl-cell|row=2|number of hours representing how often '''pbid''' refreshes the index and meta files from repos; default is every 24 hours}}
|-
{{Tbl-cell|row=3|PBI_PROXYURL}}
{{Tbl-cell|row=3|proxy server IP address}}
|-
{{Tbl-cell|row=4|PBI_PROXYPORT}}
{{Tbl-cell|row=4|proxy server port number}}
|-
{{Tbl-cell|row=5|PBI_PROXYTYPE}}
{{Tbl-cell|row=5|can be HTTP or SOCKS5}}
|-
{{Tbl-cell|row=6|PBI_PROXYUSER}}
{{Tbl-cell|row=6|username used to authenticate with proxy server}}
|-
{{Tbl-cell|row=7|PBI_PROXYPASS}}
{{Tbl-cell|row=7|password used to authenticate with proxy server}}
|-
|}

=== pbi_create(1) ===

The '''pbi_create''' command provides a way for packagers to manually specify a target directory to be compressed into a PBI file. The option '''-b''' can also be used to re-package an already installed PBI back to an archive. PBI creators are encouraged to send a tarball of the resulting PBI module to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=PBI-dev mailing list}} so they can be added to the PC-BSD® PBI repository and made available to other PC-BSD® users.

Table 7.2e summarizes the available options:

'''Table 7.2e: pbi_create Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-a author'''}}
{{Tbl-cell|row=1|specify the author for this PBI}}
|-
{{Tbl-cell|row=2|'''-b'''}}
{{Tbl-cell|row=2|make a backup of an installed PBI; specify the target PBI name instead of the PBI directory}}
|-
{{Tbl-cell|row=3|'''-c confdir'''}}
{{Tbl-cell|row=3|specify the metadata configuration directory; while not required it is highly recommended as metadata is required to create icons and binary entry-points}}
|-
{{Tbl-cell|row=4|'''-d portsdir'''}}
{{Tbl-cell|row=4|specify an alternative ports directory; defaults to ''/usr/ports/''}}
|-
{{Tbl-cell|row=5|'''-i icon'''}}
{{Tbl-cell|row=5|specify a default icon, relative to ''pbidir/''}}
|-
{{Tbl-cell|row=6|'''-n name'''}}
{{Tbl-cell|row=6|specify a name for this PBI}}
|-
{{Tbl-cell|row=7|'''-o outdir'''}}
{{Tbl-cell|row=7|place the finished ''.pbi'' file into the specified directory; defaults to $HOME}}
|-
{{Tbl-cell|row=8|'''-p port'''}}
{{Tbl-cell|row=8|use the given port to get PBI name and version}}
|-
{{Tbl-cell|row=9|'''-r version'''}}
{{Tbl-cell|row=9|specify a version for this PBI}}
|-
{{Tbl-cell|row=10|'''-u weburl'''}}
{{Tbl-cell|row=10|specify a website URL for the PBI}}
|-
{{Tbl-cell|row=11|'''--no-hash'''}}
{{Tbl-cell|row=11|disable using the shared hash directory which uses hard links to share files between applications}}
|-
{{Tbl-cell|row=12|'''--sign keyfile'''}}
{{Tbl-cell|row=12|digitally sign the PBI file with the specified openssl private key file}}
|-
|}

As the superuser, you can create a PBI with the '''pbi_create''' command using the following syntax:

{{txtbox|width=65%|box='''pbi_create -a <author> -n <name> -r <version> -w <weburl> <target directory>'''}}

Inside the target directory place the application's binaries or scripts along with any required dependencies. To indicate which file(s) represent the runtime command(s), include a file named ''external-links'' in the target directory. That file contains an entry for each command, as seen in the following example:

{{txtbox|width=65%|box={{pound}} Files to be symlinked into the default LOCALBASE 
{{pound}} One per-line, relative to %%PBI_APPDIR%% and LOCALBASE 
{{pound}} Defaults to keeping any existing files in LOCALBASE 
{{pound}} Use bin-files/ for binaries that need wrapper functionality

{{pound}} TARGET{{tabstop}}LINK IN LOCALBASE{{tabstop}}ACTION 
bin/myapp{{tabstop}}bin/myapp{{tabstop}}{{tabstop}}{{tabstop}}binary,nocrash}}

This entry instructs '''pbi_create''' to make the wrapper scripts for the ''myapp'' binary, along with placing it in the user's PATH at install time.

It is also possible to include desktop icons and mime entries using the ''xdg-mime/'', ''xdg-desktop/'' and ''xdg-menu/'' directories. The section on how to [[Create PBIs]] contains more details about creating these files. These directories should be created as subdirectories of the target directory of your application.

=== pbi_delete(1) ===

Similar to FreeBSD's '''pkg_delete''', the '''pbi_delete''' command removes an installed PBI from the system. It also schedules cleaning for the shared library directory, which is performed by '''pbid'''. Table 7.2f summarizes its options:

'''Table 7.2f: pbi_delete Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-v'''}}
{{Tbl-cell|row=1|enable verbose output}}
|-
{{Tbl-cell|row=2|'''--clean-hdir'''}}
{{Tbl-cell|row=2|perform a full cleaning of the shared hash directory, removing any unused files; should only be required after a system crash or failure in removing a PBI}}
|-
|}

When removing a PBI, you must give its full name. The full name can be found in the output of '''pbi_info'''. The following example searches for the ntop PBI and removes it:

{{txtbox|width=65%|box='''pbi_info {{pipe}} grep ntop''' 
ntop-4.0.1_1-i386 
'''pbi_delete -v ntop-4.0.1_1-i386''' 
Running pre-removal script: /var/db/pbi/installed/ntop-4.0.1_1-i386/pre-remove.sh 
Removing: /usr/pbi/ntop-i386 
Removing: /var/db/pbi/installed/ntop-4.0.1_1-i386}}

=== pbi_deleterepo(8) ===

The '''pbi_deleterepo''' command can be used to remove a registered repository from the system. It takes the repository's ID as the only command argument.

=== pbi_icon(1) ===

The '''pbi_icon''' command provides a number of options for adding desktop icons, menu entries, and mime data for an installed PBI. Not all PBIs will contain desktop/menu/mime data. Additionally, the window manager must be {{citelink|url=http://en.wikipedia.org/wiki/Xdg|XDG}}-compliant to understand a PBI's icon and mime settings. Table 7.2g summarizes this command's options:

'''Table 7.2g: pbi_icon Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''add-desktop'''}}
{{Tbl-cell|row=1|installs desktop icon; should be run as regular user}}
|-
{{Tbl-cell|row=2|'''add-mime'''}}
{{Tbl-cell|row=2|installs mime information; should be run as root}}
|-
{{Tbl-cell|row=3|'''add-menu'''}}
{{Tbl-cell|row=3|installs menu icons; should be run as root}}
|-
{{Tbl-cell|row=4|'''add-pathlnk'''}}
{{Tbl-cell|row=4|installs any $PATH links to ''~/bin'' when run as user or to $LOCALBASE when run as root}}
|-
{{Tbl-cell|row=5|'''del-desktop'''}}
{{Tbl-cell|row=5|removes desktop icon; should be run as regular user}}
|-
{{Tbl-cell|row=6|'''del-menu'''}}
{{Tbl-cell|row=6|removes menu icons; should be run as root}}
|-
{{Tbl-cell|row=7|'''del-mime'''}}
{{Tbl-cell|row=7|removes mime information; should be run as root}}
|-
{{Tbl-cell|row=8|'''del-pathlnk'''}}
{{Tbl-cell|row=8|removes any $PATH links to ''~/bin'' when run as user or to $LOCALBASE when run as root}}
|-
|}

=== pbi_indextool(1) ===

The '''pbi_indextool''' command is useful for repository maintainers. It allows PBI files to be added and removed from the repository's ''INDEX'' file. An example of using this command can be found in [[Create Your Own PBI Repository]]. Table 7.2h summarizes the available options:

'''Table 7.2h: pbi_indextool Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Command'''}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=70%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''add'''}}
{{Tbl-cell|row=1|'''-b vers'''}}
{{Tbl-cell|row=1|mark previous versions as having a binary diff patch (''.pbp'' file used for upgrading) available}}
|-
{{Tbl-cell|row=2|'''add'''}}
{{Tbl-cell|row=2|'''-f pbifile'''}}
{{Tbl-cell|row=2|mandatory, name of PBI being added to the target ''INDEX'' file}}
|-
{{Tbl-cell|row=3|'''add'''}}
{{Tbl-cell|row=3|'''-k num'''}}
{{Tbl-cell|row=3|number of previous versions of this PBI to keep in the ''INDEX'' file}}
|-
{{Tbl-cell|row=4|'''add'''}}
{{Tbl-cell|row=4|'''-u fileurl'''}}
{{Tbl-cell|row=4|mandatory URL to PBI location on server in the format category/pbi_name}}
|-
{{Tbl-cell|row=5|'''rem'''}}
{{Tbl-cell|row=5|'''-m arch'''}}
{{Tbl-cell|row=5|mandatory architecture type for PBI being removed (e.g. i386, amd64)}}
|-
{{Tbl-cell|row=6|'''rem'''}}
{{Tbl-cell|row=6|'''-n pbiname'''}}
{{Tbl-cell|row=6|mandatory name of PBI being removed from the ''INDEX'' file}}
|-
{{Tbl-cell|row=7|'''rem'''}}
{{Tbl-cell|row=7|'''-v version'''}}
{{Tbl-cell|row=7|mandatory, version of the PBI being removed from the ''INDEX'' file}}
|-
|}

=== pbi_info(1) ===

Similar to FreeBSD's '''pkg_info''' command, the '''pbi_info''' command is used to determine which PBIs are currently installed. Table 7.2i summarizes the available options:

'''Table 7.2i: pbi_info Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-a'''}}
{{Tbl-cell|row=1|list all PBIs installed on the system; same as running '''pbi_info''' without an argument}}
|-
{{Tbl-cell|row=2|'''-i'''}}
{{Tbl-cell|row=2|list all available PBIs from any repo}}
|-
{{Tbl-cell|row=3|'''-v'''}}
{{Tbl-cell|row=3|enable verbose output}}
|-
|}

=== pbi_listrepo(1) ===

The '''pbi_listrepo''' command manages installed repositories on a system. Table 7.2j summarizes this command's options:

'''Table 7.2j: pbi_listrepo Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''--down'''}}
{{Tbl-cell|row=1|move the targeted repoID down a single number in priority}}
|-
{{Tbl-cell|row=2|'''-mirror URL'''}}
{{Tbl-cell|row=2|change the specified repoID's mirror URL}}
|-
{{Tbl-cell|row=3|'''--up'''}}
{{Tbl-cell|row=3|move the targeted repoID up a single number in priority}}
|-
|}

Run the command without any options to list the IDs of the available repositories.

=== pbi_makepatch(1) ===

The '''pbi_makepatch''' command is automatically used by '''pbi_autobuild''' to create small ''*.pbp'' (Push Button Patch) files. These files can be downloaded to a user's system in order to update a PBI's version without re-downloading the entire archive. This allows users to download only the incremental changes when a PBI is upgraded. The command can also be run manually by providing two PBI archives to compare and generate a patch file for.

Table 7.2k summarizes the available options:

'''Table 7.2k: pbi_makepatch Options

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-o outdir'''}}
{{Tbl-cell|row=1|save the resulting ''*pbp'' file to the specified directory}}
|-
{{Tbl-cell|row=2|'''--sign keyfile'''}}
{{Tbl-cell|row=2|use the specified openssl key to digitally sign the patch file}}
|-
{{Tbl-cell|row=3|'''--tmpfs'''}}
{{Tbl-cell|row=3|can reduce building time for large PBIs}}
|-
|}

=== pbi_makeport(1) ===

The '''pbi_makeport''' command can be used by packagers to build a target FreeBSD port and convert it into a PBI file. Many options are provided to fine-tune the build process, and meta-data modules can also be specified to further improve the resulting PBI file. The first time this command is run, it will build a fresh chroot sandbox environment which can be used for clean-room building of the target port without affecting the host system. More details about how to create a PBI using this command, can be found in the [[PBI Module Builder Guide#Creating a New PBI with pbi makeport | ''PBI Module Builder Guide'']].

'''NOTE:''' the '''pbi_makeport''' command has support for using {{citelink|url=http://ccache.samba.org/|txt=ccache}} to speed up the compile process. If '''ccache''' is installed on the host system and the CCACHE_DIR variable is set, the '''pbi_makeport''' command will automatically utilize it for the port compile phase. This can be disabled by setting NO_CCACHE=yes in ''/etc/pbi-make.conf'' on the host system, or as an optional make flag in a module's ''pbi.conf'' file.

'''pbi_makeport''', will attempt to create any users or groups that the underlying ports require during the PBI installation. If the PBI is being installed as non-root, it will instead provide a warning message regarding any users or groups that need to be manually created. For this functionality to work, the port must set ''USERS='' or ''GROUPS='' in its ''Makefile'' and provide the corresponding UID and/or GID entries.

Table 7.2l summarizes the available options:

'''Table 7.2l: pbi_makeport Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-B'''}}
{{Tbl-cell|row=1|build-only; generally used with '''-k''' to build a port before running '''pbi_create''' manually}}
|-
{{Tbl-cell|row=2|'''-c confdir'''}}
{{Tbl-cell|row=2|specify the metadata configuration directory; while not required it is highly recommended as metadata is required to create icons and binary entry-points }}
|-
{{Tbl-cell|row=3|'''-d portsdir'''}}
{{Tbl-cell|row=3|specify an alternative ports directory; defaults to ''/usr/ports''}}
|-
{{Tbl-cell|row=4|'''-k'''}}
{{Tbl-cell|row=4|keep the build files after building the PBI}}
|-
{{Tbl-cell|row=5|'''-o outdir'''}}
{{Tbl-cell|row=5|the directory to place the finished PBI file; defaults to user's $HOME directory}}
|-
{{Tbl-cell|row=6|'''-p prefix'''}}
{{Tbl-cell|row=6|manually provide a PREFIX which determines the location where the PBI will be installed on the end-user's system}}
|-
{{Tbl-cell|row=7|'''--32'''}}
{{Tbl-cell|row=7|include when building a 32-bit PBI on a 64-bit system}}
|-
{{Tbl-cell|row=8|'''--delbuild'''}}
{{Tbl-cell|row=8|remove any existing build directories before starting the build}}
|-
{{Tbl-cell|row=9|'''--mkdebug'''}}
{{Tbl-cell|row=9|will drop to a debugging shell should the port make fail}}
|-
{{Tbl-cell|row=10|'''--no-prune'''}}
{{Tbl-cell|row=10|disable auto-pruning of non-REQUIREDBY ports after the compile phase; by default any ports which are used solely for building and which are not required for program execution will be pruned}}
|-
{{Tbl-cell|row=11|'''--pkgdir dir'''}}
{{Tbl-cell|row=11|uses the specified directory to cache the .txz package so subsequent builds will not rebuild the port from source
}}
|-
{{Tbl-cell|row=12|'''--tmpfs'''}}
{{Tbl-cell|row=12|automatically create and mount a tmp filesystem and use it for WRKDIRPREFIX; can speed up port compiles on systems with available RAM}}
|-
{{Tbl-cell|row=13|'''--sign keyfile'''}}
{{Tbl-cell|row=13|digitally sign the PBI file with the specified openssl private key file}}
|-
|}

=== pbi_makerepo(1) ===

The '''pbi_makerepo''' command allows repository maintainers to create a single ''*.rpo'' file containing various information about the new repository. This ''.rpo'' file can then be installed on the target system with '''pbi_addrepo'''. Table 7.2m summarizes the available options.

'''Table 7.2m: pbi_makerepo Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''--desc description'''}}
{{Tbl-cell|row=1|required; description of the repo to be shown in the repo list}}
|-
{{Tbl-cell|row=2|'''--key keyfile'''}}
{{Tbl-cell|row=2|required; OpenSSL public key used to verify the digital signature of PBIs installed from this repo}}
|-
{{Tbl-cell|row=3|'''--mirror URL'''}}
{{Tbl-cell|row=3|required; URL in <nowiki>http://</nowiki>, <nowiki>https://</nowiki>, or <nowiki>ftp://</nowiki> format to download PBIs and updates from}}
|-
{{Tbl-cell|row=4|'''--url URL'''}}
{{Tbl-cell|row=4|required; URL in <nowiki>http://</nowiki>, <nowiki>https://</nowiki>, or <nowiki>ftp://</nowiki> format to use when downloading the master ''INDEX'' file of available PBIs}}
|-
|}

=== pbi_metatool(1) ===

The '''pbi_metatool''' command provides a way for repository maintainers to modify the PBI metadata in their repository in order to add or remove application categories or specified PBIs. An example of using this command can be found in [[Create Your Own PBI Repository]]. Table 7.2n summarizes the available options:

'''Table 7.2n: pbi_metatool Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Command'''}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=70%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''add''' or '''rem'''}}
{{Tbl-cell|row=1|'''--cat'''}}
{{Tbl-cell|row=1|indicates that a new category is being added to or removed from the target metafile}}
|-
{{Tbl-cell|row=2|'''add''' or '''rem'''}}
{{Tbl-cell|row=2|'''--app'''}}
{{Tbl-cell|row=2|adds or removes a new PBI to/from the target metafile}}
|-
{{Tbl-cell|row=3|'''add'''}}
{{Tbl-cell|row=3|'''-a author'''}}
{{Tbl-cell|row=3|adds the name of the application's author to the target metafile}}
|-
{{Tbl-cell|row=4|'''add'''}}
{{Tbl-cell|row=4|'''-c category'''}}
{{Tbl-cell|row=4|name of new category to add to the target metafile}}
|-
{{Tbl-cell|row=5|'''add'''}}
{{Tbl-cell|row=5|'''-d desc'''}}
{{Tbl-cell|row=5|mandatory description of PBI or category being added}}
|-
{{Tbl-cell|row=6|'''add'''}}
{{Tbl-cell|row=6|'''-i icon'''}}
{{Tbl-cell|row=6|mandatory URL to 64x64 ''.png'' icon of PBI or category being added}}
|-
{{Tbl-cell|row=7|'''add'''}}
{{Tbl-cell|row=7|'''-k keywords'''}}
{{Tbl-cell|row=7|comma delimited list (with no spaces) of search keywords}}
|-
{{Tbl-cell|row=8|'''add'''}}
{{Tbl-cell|row=8|'''-l license'''}}
{{Tbl-cell|row=8|type of license (e.g. BSD, GPL, Commercial)}}
|-
{{Tbl-cell|row=9|'''add''' or '''rem'''}}
{{Tbl-cell|row=9|'''-n name'''}}
{{Tbl-cell|row=9|mandatory name of category or PBI being added to or removed from the target metafile}}
|-
{{Tbl-cell|row=10|'''add'''}}
{{Tbl-cell|row=10|'''-t type'''}}
{{Tbl-cell|row=10|type of application (e.g. Graphical, Text, Service)}}
|-
{{Tbl-cell|row=11|'''add'''}}
{{Tbl-cell|row=11|'''-u URL'''}}
{{Tbl-cell|row=11|website of application being added}}
|-
{{Tbl-cell|row=12|'''add'''}}
{{Tbl-cell|row=12|'''-r'''}}
{{Tbl-cell|row=12|include if application needs to be installed as the superuser}}
|-
|}

=== pbi_patch(1) ===

The '''pbi_patch''' command is used to update an installed PBI to a different version using a small diff Push Button Patch ''*.pbp'' file. This allows the user to perform an incremental upgrade of an installed PBI. The available options are summarized in Table 7.2o.

'''Table 7.2o: pbi_patch Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-e'''}}
{{Tbl-cell|row=1|extract only, do not install; will extract the archive to ''~/<pbidirname>'' unless '''-o''' is used.}}
|-
{{Tbl-cell|row=2|'''-g'''}}
{{Tbl-cell|row=2|extract image data from header; commonly used for GUI installations}}
|-
{{Tbl-cell|row=3|'''-i'''}}
{{Tbl-cell|row=3|display information about this PBI file}}
|-
{{Tbl-cell|row=4|'''-o outdir'''}}
{{Tbl-cell|row=4|specify the directory to use when only extracting the PBI with '''-e'''}}
|-
{{Tbl-cell|row=5|'''--checkscript'''}}
{{Tbl-cell|row=5|display any custom scripts used in the installation/removal of this PBI file; recommended if the PBI file is suspect in any way}}
|-
{{Tbl-cell|row=6|'''--no-checksig'''}}
{{Tbl-cell|row=6|skip the openssl signature verification of the PBI data}}
|-
{{Tbl-cell|row=7|'''--no-hash'''}}
{{Tbl-cell|row=7|disable using the shared hash directory which uses hard links to share files between applications}}
|-
|}

=== pbi_update(1) ===

The '''pbi_update''' command is used to display information about which PBIs have available updates and to perform the updates. Table 7.2p summarizes the available options.

'''Table 7.2p: pbi_update Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-c'''}}
{{Tbl-cell|row=1|check only the specified PBI for available updates}}
|-
{{Tbl-cell|row=2|'''--check-all'''}}
{{Tbl-cell|row=2|run a full check of all installed PBIs and display list of available updates}}
|-
{{Tbl-cell|row=3|'''-disable-auto'''}}
{{Tbl-cell|row=3|disable auto-updating of the target PBI}}
|-
{{Tbl-cell|row=4|'''--enable-auto'''}}
{{Tbl-cell|row=4|enable auto-updating of the target PBI}}
|-
{{Tbl-cell|row=5|'''--update-all'''}}
{{Tbl-cell|row=5|update all installed PBIs to the latest versions}}
|-
|}

=== pbi_update_hashdir(1) ===

The '''pbi_update_hashdir''' command is used by the '''pbid''' daemon to merge the contents of a PBI into the hash directory.

=== pbid(8) ===

The '''pbid''' command runs a small daemon which performs maintenance of installed PBIs, merges files into the shared hashdir, fetches the repository ''INDEX'' and meta files, and makes the adding and removing of PBIs much faster. It will automatically be started from the''/usr/local/etc/rc.d/pbid'' startup script if ''pbid_enable="YES"'' is in the ''/etc/rc.conf'' file.

This utility supports the option summarized in table 7.2q:

'''Table 7.2q: pbid Options'''

{{Tbl-init}}
{{Tbl-title|width=15%|'''Switch'''}}
{{Tbl-title|width=85%|'''Description'''}}
|-
{{Tbl-cell|row=1|'''-v'''}}
{{Tbl-cell|row=1|enable verbose output when the daemon starts}}
|-
{{Tbl-cell|row=2|'''--refresh'''}}
{{Tbl-cell|row=2|schedule a refresh of index and meta files }}
|-
|}

This command logs its output to ''/var/log/pbid.log''. Check this log for errors should you experience any problems with PBI maintenance.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Maintaining and Extending PC-BSD®]]
[[category:PBI Manager]]
[[category:protect]]
[[category:Referred by manpage]]
</noinclude>

Laptops

2013-01-27T02:42:03Z

Vater:

<noinclude>{{NavHeader|back=Hardware Requirements|forward=Partitioning the Hard Drive}}</noinclude>

Many PC-BSD® users successfully run PC-BSD® on their laptops. To determine if the hardware on your laptop is supported, search the {{citelink|url=http://laptop.bsdgroup.de/freebsd/|txt=FreeBSD Laptop Compatibility List}}. Consider adding to this list if your model is not listed or the information for your model is out-of-date.

Depending upon the model of laptop, you may run across some issues. These typically deal with:

* '''Sleep/suspend:''' unfortunately, {{citelink|wp|url=Advanced_Configuration_and_Power_Interface|txt=ACPI}} is not an exact science, meaning that you may have to experiment with various '''sysctl''' variables in order to achieve successful sleep and suspend states on your particular laptop model. A BIOS setting of {{citelink|wp|url=Advanced_Configuration_and_Power_Interface#Global_states|txt=suspend state}} ''S1'' can lead to a system freeze. If your laptop is a ThinkPad, {{citelink|url=http://thinkwiki.org|txt=Thinkwiki}} is an excellent source. For other types of laptops, try reading the SYSCTL VARIABLES section of '''man 4 acpi''' and check to see if there is an ACPI man page specific to your vendor by typing '''apropos acpi.''' The {{citelink|fbsdh|url=configtuning-sysctl.html|txt=Tuning with sysctl(8)}} section of the FreeBSD Handbook demonstrates how to determine your current '''sysctl''' values, modify a value, and make a modified value persist after a reboot. If the battery reading is incorrect, try the workaround in this {{citelink|url=http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/160838|txt=PR}}.

* '''Internal wireless:''' some chipsets do not have a FreeBSD driver yet. If you would like to try converting a Windows driver into a FreeBSD module, use the instructions in this {{citelink|url=http://blog.pcbsd.org/2010/11/looking-for-ndis-testers-freebsd-and-pc-bsd/|txt=Official PC-BSD{{RM}} blog post}}.

* '''Internal ATI or Radeon graphics:''' at this time, these chipsets will only support 2D graphics. This may be fixed by PC-BSD® 9.2.

* '''Synaptics:''' depending upon the hardware, you may or may not be able to disable the system's touchpad. This {{citelink|url=http://forums.freebsd.org/showpost.php?s=63c71cacb981215c14b64b74481d17cd&p=100670&postcount=17|txt=forum post}} describes how to enable Synaptics and some of the '''sysctl''' options that this feature provides.

* '''Nvidia ''Optimus'' graphics:''' the current workaround is to disable optimus in BIOS and/or set the onboard intel video to be dominant. On Lenovo ({{citelink|url=http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-76476|txt=Thinkpad T410, W510}}) there may be three options, Integrated (intel), Discrete (nVidia), Switchable (problematic/unsupported).

If you wish to test your laptop's hardware, consider using [[PC-BSD® Live Mode]] before committing to an installation.

If you would like to install PC-BSD® onto an Asus Eee, read the {{citelink|fbsd|url=AsusEee|txt=FreeBSD Eee page}} first.

The {{citelink|url=http://wiki.freebsd.org/TuningPowerConsumption|txt=FreeBSD Tuning Power Consumption page}} has some tips for reducing power consumption.

=== ThinkPads with Known Bugs ===

The ThinkPad T420 may panic during install. If it does, go into the BIOS and set the video mode to "discrete" which should allow you to complete an installation.

Some Thinkpads have a BIOS bug that prevents them from booting from GPT labelled disks. If you are unable to boot into a new installation, restart the installer and go into Advanced Mode in the [[Disk Selection Screen]]. Make sure that the "Partition disk with GPT" box is unchecked. If it was checked previously, redo the installation with the box unchecked.

If you wish to install PC-BSD® on an older IBM/Lenovo ThinkPad laptop, it is important to first check your ThinkPad model number to see if its BIOS has a known bug. ''' ''This bug is rather nasty and will render the computer completely unbootable--even the BIOS will be inaccessible.'' ''' This situation occurs as the BIOS thinks that the PC-BSD® (FreeBSD) partition number represents the IBM repair partition. The only way to get the affected laptop to boot again is to physically remove the hard drive, insert it into another laptop, wipe the drive, and insert the drive back into the system. While the hard drive is in the other system, you will note that PC-BSD® boots just fine as the problem is with the BIOS, not the hard drive. Once the BIOS is accessible again, you should upgrade (or possibly downgrade) the BIOS to a version number that fixes this bug. See Table 2.2a for the models which are affected, the BIOS version number that fixes the bug, and links to the BIOS software should you need to upgrade your BIOS. The BIOS needs to incorporate the fix "The system cannot boot from a hard disk drive with partition ID of n5h where n is 1 or greater".

'''Table 2.2a: ThinkPad BIOS Versions with Known Bug'''

{{Tbl-init|width=60%}}
{{Tbl-title|Model Number|width=60%}}
{{Tbl-title|BIOS Version That Fixes The Bug}}
|-

{{Tbl-cellw|A20m}}
{{Tbl-cellw|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-4TJLS3|txt=1.08 (IWET54WW)}} }}
|-

{{Tbl-cellg|A20p}}
{{Tbl-cellg|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-4TFT8K|txt=1.05 (IVET62WW)}} }}
|-

{{Tbl-cellw|A21e(2628)}}
{{Tbl-cellw|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-43531|txt=1.07 (KUET30WW)}} }}
|-

{{Tbl-cellg|A21m (except Sxx models)}}
{{Tbl-cellg|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-39917|txt=1.02 (KXET24WW)}} }}
|-

{{Tbl-cellw|A21p}}
{{Tbl-cellw|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-4TFT8F|txt=1.04 (KYET27WW)}} }}
|-

{{Tbl-cellg|A22m (except Sxx models)}}
{{Tbl-cellg|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-39917|txt=1.02 (KXET24WW)}} }}
|-

{{Tbl-cellw|A22p}}
{{Tbl-cellw|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-4TFT8F|txt=1.04 (KYET27WW)}} }}
|-

{{Tbl-cellg|T20}}
{{Tbl-cellg|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-4R3UYP|txt=1.10 (IYET49WW)}} }}
|-

{{Tbl-cellw|T21}}
{{Tbl-cellw|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=DSHY-3YVKSE|txt=1.04 (KZET22WW)}} }}
|-

{{Tbl-cellg|X20}}
{{Tbl-cellg|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-4R3M3F|txt=2.16 (IZET96WW)}} }}
|-

{{Tbl-cellw|X21}}
{{Tbl-cellw|content={{citelink|url=http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-4R3M3F|txt=2.16 (IZET96WW)}} }}
|-
|}

=== Acer Laptops with Known Bug ===
In models 2920z and 4920G, there is an issue with the BIOS settings for the HPET timer. The solution is to set a {{citelink|fbsdh|url=device-hints.html|txt=hardware hint}}.

Boot the installation media and select "7. Escape to the loader prompt" when you see the menu shown in Figure 2.2a.

'''Figure 2.2a: PC-BSD® Boot Menu'''

[[File:Install1b.jpeg]]

At the resulting prompt, type:

'''set hint.hpet.0.allowed_irqs="0x400000"'''
'''boot'''

You should now be able to install PC-BSD®. Once the installer boots for the first time, you will need to repeat that command in order to boot into PC-BSD®. Once you are in PC-BSD®, you can make the hint permanent by carefully adding this line to ''/boot/loader.conf'' as the superuser:

hint.hpet.0.allowed_irqs="0x400000"

=== MacBooks ===

Before starting, you should review the {{citelink|fbsd|url=AppleMacbook|txt=MacBook on FreeBSD Wiki}}.

Starting in PC-BSD® 9.0-RC1, support has been added for installing directly to Mac OS X BootCamp partitions.

First, you can install an OS X boot manager, such as {{citelink|url=http://refit.sourceforge.net/|txt=rEFIt}}. This step is optional as it requires either a dedicated partition or it installs into your OS X partition and takes over the boot process.

Next you will need to make some free space to install into. You can use the MacBook's {{citelink|wp|url=Boot_Camp_(software)|txt=Boot Camp}} utility to make a primary partition of at least 25 GB in size.

After creating the BootCamp partition, boot from the PC-BSD® install media and proceed with a normal installation. When you get to the "Disk Selection" screen, be sure to select the ''' ''ada0p3: linux-data'' ''' partition for installation. After installation, reboot and select BSD from the rEFIt (or an alternate) boot menu to boot into the new PC-BSD® installation.

=== Touch Screens ===

Starting in PC-BSD® 9.0, automatic detection of USB-based touch screen devices has been added. During the display wizard phase, if your touch-screen is auto-detected, the necessary flags will be added to ''/etc/X11/xorg.conf'' automatically. If your display is USB and is NOT auto-detected, please send the output of '''usbconfig''' and your ''/etc/X11/xorg.conf'' file to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/testing|txt=PC-BSD® testing mailing list}}.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Pre-Installation Tasks]]
[[category:laptops]]
</noinclude>

Template:Txtbox

2013-01-17T12:57:08Z

Vater:

<includeonly>{|align="center" cellspacing="0" cellpadding="2" style="border:none; width:98%; border-collapse: collapse;"
|style=" border: #aaaaaa dashed 1px; background: #f6f6f6; text-align:left; padding-left: .7em; padding-right: .4em; padding-top: .4em; padding-bottom: 0; width:{{{width|50%}}}"|{{{box|error}}}
|style="border:none; text-align:left;"|{{{1|}}}
|}</includeonly><noinclude>
== Explanation ==

(This needs to be adjusted to match the effect of the template.) This template encloses the provided text within a dashed line box. The text to the right of the box may be some type of comment such as ''"a prompt asking for the root password will open."''. By assigning width it can be adjusted if necessary, otherwise the content to the right of the box defaults to a width of 60% out of the 98% used. Note that formatting is needed (such as <nowiki> </nowiki>) to prevent the content from becoming one long line or paragraph (the <nowiki><nowiki></nowiki> or 'leading space' formatting tricks do not work). Other style markup like for ''italic'' or '''bold''' should be placed directly around the content and not around the entire template.

== Usage ==

'''<nowiki>{{</nowiki>txtbox|box=''' 
''content''<nowiki> </nowiki> 
<nowiki>'''</nowiki>''second line'' - <nowiki>{{</nowiki>highlight|note that bold and italic and highlight/redlight<nowiki>}}'''</nowiki> 
'''|''' 
''Text to right of box''<nowiki> </nowiki> 
<nowiki>''</nowiki>''second line'' - <nowiki>{{</nowiki>redlight|are possible too.<nowiki>''}}</nowiki> 
'''|''' 
'''''width='''value'' 
'''}}'''

== Example ==

{{txtbox|box=
content 
'''second line''' - {{highlight|note that bold and italic and highlight/redlight}}
|
Text to right of box 
''second line'' - {{redlight|are possible too.}}
}}</noinclude>

PBI Build Testing

2013-01-17T12:01:44Z

Vater: /* Getting a port turned into a PBI */

{{NavHome}}
This area of the wiki is for those who have worked on turning a FreeBSD port into a PBI. Those who wish to add their results may do so in the table below.

=== Getting a port turned into a PBI ===

If you wish to keep your favorite port across system updates, there is more than one way to accomplish this, but soon to become common is the creation of a PBI. The process of turning a port into a PBI can be a very simple matter of either using [[PBI Module Builder Guide#Creating a New PBI with pbi_makeport|'''pbi_makeport''']] from the commandline, or the GUIfied '''[[EasyPBI]]''' program. However, not every port submits so easily to this conversion process, and sometimes extra interaction is needed in order to succeed. The purpose of this area is to help document how those challenging ports get turned into PBIs and also perhaps, by way of this information, assist with improvement to the tools that would automate the process.

'''Note:''' This page pertains to PBI version 9.

=== What has been Attempted ===

'''Table: Ports that have been attempted. Is this version of the port a ''One-Click'' PBI creation candidate?'''

{{Tbl-init|width=100%}}
{{Tbl-title|width=8%|'''Category'''}}
{{Tbl-title|width=23%|'''Port name'''}}
{{Tbl-title|width=7%|'''Version'''}}
{{Tbl-title|width=10%|'''Options'''}}
{{Tbl-title|width=6%|'''1-Click'''}}
{{Tbl-title|width=49%|'''Special changes (and/or errors)'''}}
|- 

{{Tbl-cell|row=1|sysutils}}
{{Tbl-cell|row=1|'''easypbi'''}}
{{Tbl-cell|row=1|1.0}}
{{Tbl-cell|row=1|defaults}}
{{Tbl-cell|row=1|yes}}
{{Tbl-cell|row=1|}}
|-

{{Tbl-cell|row=2|www}}
{{Tbl-cell|row=2|'''firefox'''}}
{{Tbl-cell|row=2|8.0,1}}
{{Tbl-cell|row=2|defaults}}
{{Tbl-cell|row=2|yes}}
{{Tbl-cell|row=2|needs adjustment to define desktop icon}}
|-

{{Tbl-cell|row=3|mail}}
{{Tbl-cell|row=3|'''gmail-notify'''}}
{{Tbl-cell|row=3|1.6.1.1_4}}
{{Tbl-cell|row=3|defaults}}
{{Tbl-cell|row=3|yes}}
{{Tbl-cell|row=3|needs adjustment to define desktop icon}}
|-

{{Tbl-cell|row=4|irc}}
{{Tbl-cell|row=4|'''quassel'''}}
{{Tbl-cell|row=4|0.73}}
{{Tbl-cell|row=4|}}
{{Tbl-cell|row=4|no}}
{{Tbl-cell|row=4|needs work; cannot create monolithic version, other versions have problems.}}
|-

{{Tbl-cell|row=5|emulators}}
{{Tbl-cell|row=5|'''virtualbox-ose'''}}
{{Tbl-cell|row=5|4.0.14}}
{{Tbl-cell|row=5|defaults}}
{{Tbl-cell|row=5|no}}
{{Tbl-cell|row=5|seems like it cannot pull-in kernel source}}
|-

{{Tbl-cell|row=6|emulators}}
{{Tbl-cell|row=6|'''virtualbox-ose-additions'''}}
{{Tbl-cell|row=6|4.0.14}}
{{Tbl-cell|row=6|defaults}}
{{Tbl-cell|row=6|no}}
{{Tbl-cell|row=6|seems like it cannot pull-in kernel source}}
|-

{{Tbl-cell|row=7|emulators}}
{{Tbl-cell|row=7|'''virtualbox-ose-kmod'''}}
{{Tbl-cell|row=7|4.0.14}}
{{Tbl-cell|row=7|defaults}}
{{Tbl-cell|row=7|no}}
{{Tbl-cell|row=7|seems like it cannot pull-in kernel source}}
|-

{{Tbl-cell|row=8|deskutils}}
{{Tbl-cell|row=8|'''znotes'''}}
{{Tbl-cell|row=8|0.45}}
{{Tbl-cell|row=8|defaults}}
{{Tbl-cell|row=8|yes}}
{{Tbl-cell|row=8|needs adjustment to define included desktop icon}}
|-
|}

'''''One-click candidates''''' are fully functional but can have minor flaws, such as a generic desktop/menu icon, or appearing in ''lost & found''. Some ports have various non-default options which may prevent creation or cause a substantially different PBI to be made that either performs differently or lacks certain features (such as NLS).

PBI Build Testing

2013-01-17T11:59:57Z

Vater:

{{NavHome}}
This area of the wiki is for those who have worked on turning a FreeBSD port into a PBI. Those who wish to add their results may do so in the table below.

=== Getting a port turned into a PBI ===

If you wish to keep your favorite port across system updates, there is more than one way to accomplish this, but soon to become common is the creation of a PBI. The process of turning a port into a PBI can be a very simple matter of either using [[PBI Module Builder Guide#Creating a New PBI with pbi_makeport|'''pbi_makeport''']] from the commandline, or the GUIfied [[PBI Module Builder Guide#Using EasyPBI|'''EasyPBI''']] program. However, not every port submits so easily to this conversion process, and sometimes extra interaction is needed in order to succeed. The purpose of this area is to help document how those challenging ports get turned into PBIs and also perhaps, by way of this information, assist with improvement to the tools that would automate the process.

'''Note:''' This page pertains to PBI version 9.

=== What has been Attempted ===

'''Table: Ports that have been attempted. Is this version of the port a ''One-Click'' PBI creation candidate?'''

{{Tbl-init|width=100%}}
{{Tbl-title|width=8%|'''Category'''}}
{{Tbl-title|width=23%|'''Port name'''}}
{{Tbl-title|width=7%|'''Version'''}}
{{Tbl-title|width=10%|'''Options'''}}
{{Tbl-title|width=6%|'''1-Click'''}}
{{Tbl-title|width=49%|'''Special changes (and/or errors)'''}}
|- 

{{Tbl-cell|row=1|sysutils}}
{{Tbl-cell|row=1|'''easypbi'''}}
{{Tbl-cell|row=1|1.0}}
{{Tbl-cell|row=1|defaults}}
{{Tbl-cell|row=1|yes}}
{{Tbl-cell|row=1|}}
|-

{{Tbl-cell|row=2|www}}
{{Tbl-cell|row=2|'''firefox'''}}
{{Tbl-cell|row=2|8.0,1}}
{{Tbl-cell|row=2|defaults}}
{{Tbl-cell|row=2|yes}}
{{Tbl-cell|row=2|needs adjustment to define desktop icon}}
|-

{{Tbl-cell|row=3|mail}}
{{Tbl-cell|row=3|'''gmail-notify'''}}
{{Tbl-cell|row=3|1.6.1.1_4}}
{{Tbl-cell|row=3|defaults}}
{{Tbl-cell|row=3|yes}}
{{Tbl-cell|row=3|needs adjustment to define desktop icon}}
|-

{{Tbl-cell|row=4|irc}}
{{Tbl-cell|row=4|'''quassel'''}}
{{Tbl-cell|row=4|0.73}}
{{Tbl-cell|row=4|}}
{{Tbl-cell|row=4|no}}
{{Tbl-cell|row=4|needs work; cannot create monolithic version, other versions have problems.}}
|-

{{Tbl-cell|row=5|emulators}}
{{Tbl-cell|row=5|'''virtualbox-ose'''}}
{{Tbl-cell|row=5|4.0.14}}
{{Tbl-cell|row=5|defaults}}
{{Tbl-cell|row=5|no}}
{{Tbl-cell|row=5|seems like it cannot pull-in kernel source}}
|-

{{Tbl-cell|row=6|emulators}}
{{Tbl-cell|row=6|'''virtualbox-ose-additions'''}}
{{Tbl-cell|row=6|4.0.14}}
{{Tbl-cell|row=6|defaults}}
{{Tbl-cell|row=6|no}}
{{Tbl-cell|row=6|seems like it cannot pull-in kernel source}}
|-

{{Tbl-cell|row=7|emulators}}
{{Tbl-cell|row=7|'''virtualbox-ose-kmod'''}}
{{Tbl-cell|row=7|4.0.14}}
{{Tbl-cell|row=7|defaults}}
{{Tbl-cell|row=7|no}}
{{Tbl-cell|row=7|seems like it cannot pull-in kernel source}}
|-

{{Tbl-cell|row=8|deskutils}}
{{Tbl-cell|row=8|'''znotes'''}}
{{Tbl-cell|row=8|0.45}}
{{Tbl-cell|row=8|defaults}}
{{Tbl-cell|row=8|yes}}
{{Tbl-cell|row=8|needs adjustment to define included desktop icon}}
|-
|}

'''''One-click candidates''''' are fully functional but can have minor flaws, such as a generic desktop/menu icon, or appearing in ''lost & found''. Some ports have various non-default options which may prevent creation or cause a substantially different PBI to be made that either performs differently or lacks certain features (such as NLS).

Game Testing

2013-01-17T11:40:41Z

Vater: /* Windows */

{{NavHome}}

This area of the wiki is for those who have tried getting a Windows or Linux game running on PC-BSD. Those who wish to add their results may do so in the table below. __NOTOC__ 

== The promise of non-native games on PC-BSD ==

It is well known that a constant stream of games arrive on store shelves for Windows and that a few titles sometimes are available for Linux, but that does not mean BSD is left without options. There are two main methods that can be used to access games, and both are through some kind of emulation or compatibility layer. FreeBSD (and therefore PC-BSD) has a Linux compatibility layer. There are a number of emulators, and a program (Wine) containing a subset of Windows capability that has been ported to BSD. It is hoped that through this list more games may be discovered that work but do not (or cannot) exist as PBIs, and also perhaps, by way of this information, assistance might be given to increase the amount accessible to PC-BSD.

'''Note:''' This page pertains to PC-BSD version 9.x.

== Linux ==

=== Resources ===

==== Libraries and other files ====

* {{Citelink|url=http://www.freshports.org/devel/linux-f10-sdl12/|txt=sdl12}}

==== Documentation and Examples ====

* Previously ported {{Citelink|url=http://www.freshports.org/games/linux-doom3|txt=linux-doom3}} that might be used as an example.

== Windows ==

Steam.msi (Microsoft) can be installed on pcbsd with the last Wine version (1.5.19)

The only problem is no displaying text.

In order to resolve it :

* Run wine regedit.

* Navigate to HKEY_CURRENT_USER\Software\Valve\Steam in the tree.

* Look for a DWriteEnable value in the panel on the right. If it doesn't exist, add it as a DWORD value.

* Set DWriteEnable to 0 and exit out of the registry editor.


== Attempted ==


== What currently works ==

'''Table: Games that have been attempted. How well does this version of the game run?'''

{{Tbl-init|width=100%}}
{{Tbl-title|width=10%|'''Type'''}}
{{Tbl-title|width=23%|'''Name'''}}
{{Tbl-title|width=7%|'''Version'''}}
{{Tbl-title|width=7%|'''Platform'''}}
{{Tbl-title|width=53%|'''Special changes (and/or errors)'''}}
|-
{{Tbl-cell|row=1|RPG}}
{{Tbl-cell|row=1|'''Diablo II'''}}
{{Tbl-cell|row=1|1.13}}
{{Tbl-cell|row=1|Windows}}
{{Tbl-cell|row=1|align=justified|Using the mechanism of installing on Windows (both Diablo2 and LoD expansion), then copying the installation files to a USB key, you can run the game with Wine.
Example: wine Diablo\ II.exe -w

(Note: the -w is required for Windowed mode).

Tested on PC-BSD 9.0x64 and Wine64 1.4.1
}}
|-
{{Tbl-cell|row=2|}}
{{Tbl-cell|row=2|'''Left for Dead 2'''}}
{{Tbl-cell|row=2|}}
{{Tbl-cell|row=2|Windows}}
{{Tbl-cell|row=2|Steam.msi (Microsoft) via Wine version (1.5.20)}}
|-
{{Tbl-cell|row=3|}}
{{Tbl-cell|row=3|'''Rome Total WAR'''}}
{{Tbl-cell|row=3|}}
{{Tbl-cell|row=3|Windows}}
{{Tbl-cell|row=3|Steam.msi (Microsoft) via Wine version (1.5.20)}}
|-
{{Tbl-cell|row=3|}}
{{Tbl-cell|row=3|'''Rome: Total War - Barbarian Invasion'''}}
{{Tbl-cell|row=3|}}
{{Tbl-cell|row=3|Windows}}
{{Tbl-cell|row=3|Steam.msi (Microsoft) via Wine version (1.5.20)}}
|-
{{Tbl-cell|row=3|}}
{{Tbl-cell|row=3|'''Rome: Total War - Alexander'''}}
{{Tbl-cell|row=3|}}
{{Tbl-cell|row=3|Windows}}
{{Tbl-cell|row=3|Steam.msi (Microsoft) via Wine version (1.5.20)}}
|-
{{Tbl-cell|row=3|}}
{{Tbl-cell|row=3|'''crusader kings 2'''}}
{{Tbl-cell|row=3|}}
{{Tbl-cell|row=3|Windows}}
{{Tbl-cell|row=3|Steam.msi (Microsoft) via Wine version (1.5.20)}}
|-
{{Tbl-cell|row=4|}}
{{Tbl-cell|row=4|'''Medieval total WAR 2'''}}
{{Tbl-cell|row=4|}}
{{Tbl-cell|row=4|Windows}}
{{Tbl-cell|row=4|Steam.msi (Microsoft) via Wine version (1.5.20)}}
|}

<noinclude>{{refheading}}</noinclude>

Wireless Testing

2013-01-10T05:13:04Z

Vater:

{{NavHome}}
This area of the wiki is for those who wish to assist by reporting non-working wireless drivers or by testing new drivers. Both reporting and testing provides valuable information to the developers of wireless drivers. It also helps to ensure that PC-BSD® and FreeBSD provide support for the wireless devices used by their users.

This page contains four tables:

* [[#Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? | Table 1]]: devices in this table do not have a FreeBSD driver yet. If your device requires you to run the '''ndisgen''' script to convert a Windows driver to a FreeBSD driver module, it belongs in this table. Such devices use ndis(4) as their driver name. The goal of this table is to determine which devices need a native FreeBSD driver.

* [[#Table 2: Existing Wireless Drivers That Do not Work Well | Table 2]]: devices in this table already have a FreeBSD driver, but there are problems with the driver e.g. certain features are unavailable or the driver crashes. The goal of this table is to provide information to developers so the driver can be fixed. This means that you should reference any existing PRs or other URLs containing a description of the problem. If a PR does not exist, consider submitting one; information on how to submit a useful PR can be found at {{Citelink|url=http://www.freebsd.org/doc/en/articles/problem-reports/article.html|txt=Writing FreeBSD Problem Reports}}.

* [[#Table 3: Wireless Devices Known to Work | Table 3]]: devices in this table have a working FreeBSD driver, making it a quick reference to determine if a device is supported. If your device works and is not in the table, take a minute to create a wiki login account and add an entry for your device.

* [[#Table 4: Devices Needing Drivers | Table 4]]: devices in this table have users who desire support but lack a FreeBSD driver.

If your wireless device is not supported and is not listed in [[#Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? | Table 1]], please create a wiki account and add it. However, please do a little bit of research first:

* Perform a web search for the name of the device and the word FreeBSD (for example, "freebsd broadcom 5709"). This should give you a good idea if the driver already exists--and if so, the name of the driver--or if other FreeBSD users have had problems getting their device to work.

* If you are not sure of the name and model of your internal device, try this command: '''pciconf -lv | grep -i wireless'''. If the device is USB, try '''usbconfig dump_all_config_desc'''.

* If a FreeBSD driver does not exist, download a Windows driver for the device, run the interactive script '''ndisgen''' as the superuser, and see if you can successfully use the generated driver module. Add the results for your architecture (i386 or amd64) to [[#Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? | Table 1]].

'''Note:''' ndisgen currently does not support the NDIS 6.X API. In practical terms, this means that you should only try it on XP and 2003 drivers. Make sure you download and try to convert the correct driver for your architecture (32 or 64 bit). If you would like to help test the most recent version of ndisgen, follow {{Citelink|url=http://blog.pcbsd.org/2010/11/looking-for-ndis-testers-freebsd-and-pc-bsd/|txt=these instructions}}.

'''Note:''' report of ndisgen process causing a faulty situation. '''Description:''' Wireless is active, but when trying to connect to the network, the screen goes dark and the system stops responding. The black screen can be removed by restarting, but after reboot PC-BSD® does not enter the boot loader section. The system shows a prompt ''FreeBSD (Amnesia mode)''. '''Likely solution:''' {{Citelink|url=http://www.freebsd.org/cgi/query-pr.cgi?pr=165622&sourceid=opensearch|txt=FreeBSD problem report and patch}} for "Unregistered use of FPU in kernel" panic caused by miniport driver adapted via ndisgen.

'''Note to iwi(4) users:''' work is ongoing to improve this driver. Please see {{Citelink|url=http://people.freebsd.org/~bschmidt/iwi/|txt=Bernhard Schmidt's iwi wiki}} if you are interested in testing these changes.

== Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? ==

{| border=1
|'''Device Name'''
|'''i386'''
|'''amd64'''
|'''Comments'''
|-
|BCM4310
|
|NO
|
|-
|BCM4313
|YES
|YES
|Download this {{Citelink|url=http://dl.dropbox.com/u/1101857/%5Bwikidrivers.com%5D%20Broadcom_BCM43xx_5.100.235.19_win5x.exe|txt=WinXP}} driver, add bcmwl5.inf and bcmwl5.sys (bcmwl564.sys if using the amd64 version of freebsd) as driver files and both bcm43xx.cat (bcm43xx64.cat for amd64) and bcmwlcoi.dll (bcmwlcoi64.dll for amd64) as firmware files (this is important, if you do not add them through the ndisgen interface you will get a kernel panic as soon as you kldload the bcmwl5_sys.ko or bcmwl564_sys.ko file), move all the generated *.ko files to /boot/modules, add {{Citelink|url=http://pastebin.com/bRPaBS7N|txt=this}} to your /etc/rc.conf ({{Citelink|url=http://pastebin.com/qYR1wXs4|txt=this}} for amd64 users), and {{Citelink|url=http://pastebin.com/s2gBzVVQL|txt=this}} to your /boot/loader.conf, add your wpa_supplicant.conf file to /etc and finally reboot the PC to get the drivers loaded and interfaces created.
Note: The WinXP drivers mentioned above work only on FreeBSD 9.0RC3 and later, if you need to use FreeBSD 8.2 or 7.4 use the curtiebo's Win98 driver, also the drivers listed are extremelly sensitive to correct timing during installation and can brick your *BSD install, and are also very unstable and cause lots of kernel panics.
|-
|RTL8185
|YES
|YES
|Try Me driver instead of XP. Use XP driver version 1.10. Should be about 280 KiB in size. Must manually load driver. Placing it in /boot/loader.conf did not initialize device. As far as I have tested it fully works. You may have to manually configure it as well. The graphical network manager did not work for me. (More info in discussion). Just finished setting up amd64 system. XP64 driver version 1.10 does work (using it now). Follow same procedures as i386 driver.
|-
|RT3062
|YES
|Not tested
|Appears to be working, but not fully functional. Have had an issue where sometimes it will not connect on boot and I've had to reboot. Also it has serious issues with uploading. Using {{Citelink|url=http://zonetusa.net/media/import/ZEW16X2_DRxp.zipL|txt=this driver}}
|-
|RTL8191SE
|YES
|NO
|driver Vistax64: ndisgen generates rtl8192se_sys.ko . kernel load it , but module isn't used. pciconf -lv output : 
none7@pci0:10:0:0:class=0x028000 card=0x818110ec chip=0x817210ec rev=0x10 hdr=0x00 
vendor = 'Realtek Semiconductor' 
device = 'Realtek RTL8191SE wireless LAN 802.11N PCI-E NIC (RTL8191SE ?)' 
class = network 

Vista drivers are not XP drivers and will not work.
|-
|RTL8187SE
|YES
|NO
|Not kldload if_ndis, says the archive already exists. PC-BSD® (x86) is restarted after kldload rtl8187Se_sys.ko from Windows XP driver. The wireless continue to not function.
|-
|RTL8192SE
|YES
|YES, in 8.2
|use the the Windows XP driver
|-
|}

If a driver exists for your wireless device but the driver does not work well, add a description of the problem to [[#Table 2: Existing Wireless Drivers That Do not Work Well | Table 2]]. Take a minute to {{Citelink|url=http://www.freebsd.org/cgi/query-pr-summary.cgi?query|txt=query the PR database}} and add the PR number if one exists.

== Table 2: Existing Wireless Drivers That Do not Work Well ==

{| border=1
|'''Driver Name'''
|'''i386'''
|'''amd64'''
|'''PR Number'''
|'''Comments'''
|-
|rum
|X
|X
|
|Some chip revisions have problems with poor signal strength if distance from AP is medium to high.
|-
|wpi
|
|
|
|Known issue in 8.2 (http://www.freebsd.org/cgi/query-pr.cgi?pr=143874). Updating src and rebuilding kernel as per that link or upgrading to 9.0 fixes issue.
|}

[[#Table 3: Wireless Devices Known to Work | Table 3]] provides a handy resource for checking to see if your wireless driver is known to work on FreeBSD and PC-BSD®. Devices should be added alphabetically (then numerically). Only add devices that you have successfully used (e.g. do not add devices that "should" work according to the driver man page).

== Table 3: Wireless Devices Known to Work ==

{| border=1
|'''Device Name'''
|'''Driver'''
|'''i386'''
|'''amd64'''
|'''Comments'''
|-
|AR5001
|ath
|YES
|
|
|-
|AR9285
|ath
|
|YES
|works in 9.1
|-
| Belkin 54G (F5D7050)
| rum
| YES
|
| external USB
|-
|Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (BCM4311)
|bwn
|YES
|YES
|Works in 8.1 or later, only station, adhoc-demo and monitor mode is currently supported. Must install net/bwn-firmware-kmod port. Not the bwi-firmware-kmod. 8.1 users may need to modify /usr/src/sys/kern/subr_firmware.c to read FIRMWARE_MAX 50 and recompile their kernel; this is not necessary in 8.2 or higher.
|-
|Broadcom 802.11b/g (BCM4318)
|bwn
|YES
|YES
|Same as above
|-
| Intel 5100AGN
| iwn
|
|
|Should work in 8.1 or later
|-
|Intel 6205a
|iwn
|
|
|Works in 9.0. Instructions for 8.2 at http://blog.cochard.me/2011/08/backporting-intel-prowireless-6205a.html
|-
|RLT8187B
|urtw
|
|
|Should work in 8.0 or later
|-
|}

== Table 4: Devices Needing Drivers ==

The following interfaces need a FreeBSD driver:

{| border=1
|'''Device Name'''
|'''Driver Sources/Notes'''
|-
|AR9287
|committed to HEAD May 26/11
|-
|BCM4321
|bwn(4) needs support for N PHYs
|-
|BCM4322
|
|-
|BCM43224
|http://wireless.kernel.org/en/users/Drivers/brcm80211
|-
|BCM43225
|http://wireless.kernel.org/en/users/Drivers/brcm80211
|-
|BCM4313
|http://wireless.kernel.org/en/users/Drivers/brcm80211
|-
|DW1501
|Its actually a BCM4313, PCI Id. 0x4727, thus same driver at http://wireless.kernel.org/en/users/Drivers/brcm80211
|-
|RT2760T
|does not seem to have a blob for Linux yet
|-
|RT2800
|
|-
|RT2860
|http://forums.pcbsd.org/showthread.php?t=13722&page=2
|-
|RT5390
|http://www.phoronix.com/scan.php?page=news_item&px=OTA5MA open sourced in 2/11
|-
|RTL8188CE
|OpenBSD uses urtwn
|-
|}

== Additional Information ==

=== Mobile broadband ===
{{Citelink|url=http://packages.ubuntu.com/precise/mobile-broadband-provider-info|txt=Mobile Broadband provider info}}

<noinclude>{{refheading}}</noinclude>

Game Testing

2013-01-10T05:02:31Z

Vater:

{{NavHome}}

This area of the wiki is for those who have tried getting a Windows or Linux game running on PC-BSD. Those who wish to add their results may do so in the table below. __NOTOC__ 

== The promise of non-native games on PC-BSD ==

It is well known that a constant stream of games arrive on store shelves for Windows and that a few titles sometimes are available for Linux, but that does not mean BSD is left without options. There are two main methods that can be used to access games, and both are through some kind of emulation or compatibility layer. FreeBSD (and therefore PC-BSD) has a Linux compatibility layer. There are a number of emulators, and a program (Wine) containing a subset of Windows capability that has been ported to BSD. It is hoped that through this list more games may be discovered that work but do not (or cannot) exist as PBIs, and also perhaps, by way of this information, assistance might be given to increase the amount accessible to PC-BSD.

'''Note:''' This page pertains to PC-BSD version 9.x.

== Linux ==

=== Resources ===

==== Libraries and other files ====

* {{Citelink|url=http://www.freshports.org/devel/linux-f10-sdl12/|txt=sdl12}}

==== Documentation and Examples ====

* Previously ported {{Citelink|url=http://www.freshports.org/games/linux-doom3|txt=linux-doom3}} that might be used as an example.

== Windows ==

Steam.msi (Microsoft ) can be installed on pcbsd with the last Wine version (1.5.19)

The only problem is no displaying text.

In order to resolve it :

* Run wine regedit.

* Navigate to HKEY_CURRENT_USER\Software\Valve\Steam in the tree.

* Look for a DWriteEnable value in the panel on the right. If it doesn't exist, add it as a DWORD value.

* Set DWriteEnable to 0 and exit out of the registry editor.



== What currently works ==

'''Table: Games that have been attempted. How well does this version of the game run?'''

{{Tbl-init|width=100%}}
{{Tbl-title|width=10%|'''Type'''}}
{{Tbl-title|width=23%|'''Name'''}}
{{Tbl-title|width=7%|'''Version'''}}
{{Tbl-title|width=7%|'''Platform'''}}
{{Tbl-title|width=53%|'''Special changes (and/or errors)'''}}
|-
{{Tbl-line|bg=ff|align=left|RPG}}
{{Tbl-line|bg=ff|align=left|'''Diablo II'''}}
{{Tbl-line|bg=ff|align=left|1.13}}
{{Tbl-line|bg=ff|align=left|Windows}}
{{Tbl-line|bg=ff|align=justified|Using the mechanism of installing on Windows (both Diablo2 and LoD expansion), then copying the installation files to a USB key, you can run the game with Wine.
Example: wine Diablo\ II.exe -w

(Note: the -w is required for Windowed mode).

Tested on PC-BSD 9.0x64 and Wine64 1.4.1
}}
|-
{{Tbl-line|}}
{{Tbl-line|'''Left for Dead 2'''}}
{{Tbl-line|}}
{{Tbl-line|Windows}}
{{Tbl-line|Steam.msi (Microsoft) via Wine version (1.5.19)}}
|-
{{Tbl-line|bg=ff}}
{{Tbl-line|bg=ff|'''Rome Total WAR'''}}
{{Tbl-line|bg=ff}}
{{Tbl-line|bg=ff|Windows}}
{{Tbl-line|bg=ff|Steam.msi (Microsoft) via Wine version (1.5.19)}}
|}

<noinclude>{{refheading}}</noinclude>

Game Testing

2013-01-10T05:01:09Z

Vater:

{{NavHome}}

This area of the wiki is for those who have tried getting a Windows or Linux game running on PC-BSD. Those who wish to add their results may do so in the table below. __NOTOC__ 

== The promise of non-native games on PC-BSD ==

It is well known that a constant stream of games arrive on store shelves for Windows and that a few titles sometimes are available for Linux, but that does not mean BSD is left without options. There are two main methods that can be used to access games, and both are through some kind of emulation or compatibility layer. FreeBSD (and therefore PC-BSD) has a Linux compatibility layer. There are a number of emulators, and a program (Wine) containing a subset of Windows capability that has been ported to BSD. It is hoped that through this list more games may be discovered that work but do not (or cannot) exist as PBIs, and also perhaps, by way of this information, assistance might be given to increase the amount accessible to PC-BSD. '''Note:''' This page pertains to PC-BSD version 9.x.

== Linux ==

=== Resources ===

==== Libraries and other files ====

* {{Citelink|url=http://www.freshports.org/devel/linux-f10-sdl12/|txt=sdl12}}

==== Documentation and Examples ====

* Previously ported {{Citelink|url=http://www.freshports.org/games/linux-doom3|txt=linux-doom3}} that might be used as an example.

== Windows ==

Steam.msi (Microsoft ) can be installed on pcbsd with the last Wine version (1.5.19)

The only problem is no displaying text.

In order to resolve it :

* Run wine regedit.

* Navigate to HKEY_CURRENT_USER\Software\Valve\Steam in the tree.

* Look for a DWriteEnable value in the panel on the right. If it doesn't exist, add it as a DWORD value.

* Set DWriteEnable to 0 and exit out of the registry editor.



== What currently works ==

'''Table: Games that have been attempted. How well does this version of the game run?'''

{{Tbl-init|width=100%}}
{{Tbl-title|width=10%|'''Type'''}}
{{Tbl-title|width=23%|'''Name'''}}
{{Tbl-title|width=7%|'''Version'''}}
{{Tbl-title|width=7%|'''Platform'''}}
{{Tbl-title|width=53%|'''Special changes (and/or errors)'''}}
|-
{{Tbl-line|bg=ff|align=left|RPG}}
{{Tbl-line|bg=ff|align=left|'''Diablo II'''}}
{{Tbl-line|bg=ff|align=left|1.13}}
{{Tbl-line|bg=ff|align=left|Windows}}
{{Tbl-line|bg=ff|align=justified|Using the mechanism of installing on Windows (both Diablo2 and LoD expansion), then copying the installation files to a USB key, you can run the game with Wine.
Example: wine Diablo\ II.exe -w

(Note: the -w is required for Windowed mode).

Tested on PC-BSD 9.0x64 and Wine64 1.4.1
}}
|-
{{Tbl-line|}}
{{Tbl-line|'''Left for Dead 2'''}}
{{Tbl-line|}}
{{Tbl-line|Windows}}
{{Tbl-line|Steam.msi (Microsoft) via Wine version (1.5.19)}}
|-
{{Tbl-line|bg=ff}}
{{Tbl-line|bg=ff|'''Rome Total WAR'''}}
{{Tbl-line|bg=ff}}
{{Tbl-line|bg=ff|Windows}}
{{Tbl-line|bg=ff|Steam.msi (Microsoft) via Wine version (1.5.19)}}
|}

<noinclude>{{refheading}}</noinclude>

Game Testing

2013-01-10T04:55:46Z

Vater:

{{NavHome}}

This area of the wiki is for those who have tried getting a Windows or Linux game running on PC-BSD. Those who wish to add their results may do so in the table below. __NOTOC__ 

== The promise of non-native games on PC-BSD ==

It is well known that a constant stream of games arrive on store shelves for Windows and that a few titles sometimes are available for Linux, but that does not mean BSD is left without options. There are two main methods that can be used to access games, and both are through some kind of emulation or compatibility layer. FreeBSD (and therefore PC-BSD) has a Linux compatibility layer. There are a number of emulators, and a program (Wine) containing a subset of Windows capability that has been ported to BSD. It is hoped that through this list more games may be discovered that work but do not (or cannot) exist as PBIs, and also perhaps, by way of this information, assistance might be given to increase the amount accessible to PC-BSD. '''Note:''' This page pertains to PC-BSD version 9.x.

== Linux ==

=== Resources ===

==== Libraries and other files ====

* [http://www.freshports.org/devel/linux-f10-sdl12/ sdl12]

==== Documentation and Examples ====

* Previously ported [http://www.freshports.org/games/linux-doom3 linux-doom3] that might be used as an example.

== Windows ==

Steam.msi (Microsoft ) can be installed on pcbsd with the last Wine version (1.5.19)

The only problem is no displaying text.

In order to resolve it :

* Run wine regedit.

* Navigate to HKEY_CURRENT_USER\Software\Valve\Steam in the tree.

* Look for a DWriteEnable value in the panel on the right. If it doesn't exist, add it as a DWORD value.

* Set DWriteEnable to 0 and exit out of the registry editor.

(solution from http://askubuntu.com/questions/21436...n-ubuntu-12-04)


== What currently works ==

'''Table: Games that have been attempted. How well does this version of the game run?'''

{{Tbl-init|width=100%}}
{{Tbl-title|width=10%|'''Type'''}}
{{Tbl-title|width=23%|'''Name'''}}
{{Tbl-title|width=7%|'''Version'''}}
{{Tbl-title|width=7%|'''Platform'''}}
{{Tbl-title|width=53%|'''Special changes (and/or errors)'''}}
|-
{{Tbl-line|bg=ff|align=left|RPG}}
{{Tbl-line|bg=ff|align=left|'''Diablo II'''}}
{{Tbl-line|bg=ff|align=left|1.13}}
{{Tbl-line|bg=ff|align=left|Windows}}
{{Tbl-line|bg=ff|align=justified|Using the mechanism of installing on Windows (both Diablo2 and LoD expansion), then copying the installation files to a USB key, you can run the game with Wine.
Example: wine Diablo\ II.exe -w

(Note: the -w is required for Windowed mode).

Tested on PC-BSD 9.0x64 and Wine64 1.4.1
}}
|-
{{Tbl-line|}}
{{Tbl-line|'''Left for Dead 2'''}}
{{Tbl-line|}}
{{Tbl-line|Windows}}
{{Tbl-line|Steam.msi (Microsoft) via Wine version (1.5.19)}}
|-
{{Tbl-line|bg=ff}}
{{Tbl-line|bg=ff|'''Rome Total WAR'''}}
{{Tbl-line|bg=ff}}
{{Tbl-line|bg=ff|Windows}}
{{Tbl-line|bg=ff|Steam.msi (Microsoft) via Wine version (1.5.19)}}
|}

Talk:Enlightenment

2013-01-06T18:39:23Z

Vater: add information (about PC-BSD) in the wiki of the Enlightenment-project

== add information (about PC-BSD) in the wiki of the [[Enlightenment]]-project ==


* http://trac.enlightenment.org/e/wiki/Operating_Systems
* http://trac.enlightenment.org/e/wiki/Installation_BSD

--[[User:Vater|Rg]] 10:39, 6 January 2013 (PST)

Enlightenment

2013-01-03T20:26:09Z

Vater: i hope, that nobody will miss "e17"

<noinclude>{{NavHeader|back=Awesome|forward=evilwm}}</noinclude>

{{citelink|url=http://www.enlightenment.org|txt=Enlightenment}} 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.

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.1. The icon on the far left of the iBar has been clicked in order to access the applications menu.

'''Figure 6.6a: Enlightenment Running on PC-BSD®'''

[[File:Enlightenment1.png]]

Enlightenment is very customizable. The {{citelink|url=http://trac.enlightenment.org/e/wiki/User_Guide|txt=User Guide}} describes how to configure windows, shelves, menus, wallpaper, and much more.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:desktops]]
[[category:enlightenment]]
</noinclude>

Burning the Installation Media

2013-01-03T20:17:29Z

Vater: /* Writing the IMG File on a Windows System */

<noinclude>{{NavHeader|back=Obtaining PC-BSD®|forward=PC-BSD® Live Mode}}</noinclude>

Once you have downloaded PC-BSD® and verified its checksum, burn the file to the correct media type. This section demonstrates how to do so using several different applications and operating systems. Each application assumes that the correct media (CD, DVD, or USB flash drive) for the type of file is inserted.

=== Burning the CD/DVD ISO File on a BSD or Linux System ===

This section demonstrates how to burn the installation ISO on a Linux or BSD system using the following tools: K3B, Brasero, and '''growisofs'''.

==== K3B ====

{{citelink|url=http://www.kde.org/applications/multimedia/k3b/|txt=K3B}} is an easy-to-use graphical burning application for Linux and BSD systems. On a PC-BSD® system, it is installed with the KDE desktop. You can also install the K3B PBI using [[Using AppCafe®]].

To burn your ISO, launch K3B, browse to the location of the ''.iso'' file in the screen shown in Figure 2.5f and click ''Tools'' ➜ ''Burn Image...'' to see the screen in Figure 2.5g.

'''Figure 2.5f: Selecting the Burn Image Tool Within K3B'''

[[File:K3b1c.png]]

'''Figure 2.5g: K3B's Burn Image Screen'''

[[File:K3b2c.png]]

Click the "Start" button to burn the file. K3B will automatically eject the media once the burn is complete.

==== Brasero ====

{{citelink|url=http://projects.gnome.org/brasero/|txt=Brasero}} is an easy to use burning application included with the [[GNOME2|GNOME desktop]]. A PBI is also available within [[Using AppCafe® | AppCafe®]]. To launch Brasero within GNOME, click ''Applications'' ➜ ''Multimedia'' ➜ ''Brasero Disk Burner'' and the dialog window shown in Figure 2.5h will be displayed. Alternately, type '''brasero''' from within any window manager.

'''Figure 2.5h: Brasero's Initial Screen'''

[[File:Brasero1a.png]]

Click ''Burn image'' to open the screen seen in Figure 2.5i. Use the ''Click here to select a disk image'' button to select your ''.iso'' file.

'''Figure 2.5i: Brasero Image Burning Setup'''

[[File:Brasero2b.png]]

The name and size of your ''.iso'' file should appear and Brasero will indicate the size of the media. The lower portion of Figure 2.5i shows the menu that appears if you click on the "Properties" button. You can change these options if you wish, but the default settings are fine in most cases. When you are ready, click the "Burn" button and Brasero will burn your ISO.

==== Xfburn ====

{{citelink|url=http://goodies.xfce.org/projects/applications/xfburn|txt=Xfburn}} is available to [[Using AppCafe®#Installing and Uninstalling PBI Software | install as PBI Software]] and is installed with [[XFCE4]].

==== growisofs ====

If you are familiar with using the command line on a FreeBSD or PC-BSD® system, you can use the '''growisofs''' command line utility to burn the DVD. This utility is included with the dvd+rw-tools FreeBSD port which is installed by default on a PC-BSD® system. If that software is not yet installed on a FreeBSD system, issue this command as the superuser:

'''pkg_add -r dvd+rw-tools'''

Depending upon the type of DVD burner hardware, you may have to configure the system to use it. If the device is ATAPI (i.e. not USB or SCSI), the ATAPI driver must be loaded. The superuser can issue this command:

'''kldload atapicam'''

If you just get your prompt back, the driver successfully loaded. If you get the message "kldload: cannot load atapicam: File exists", this means that the driver was already loaded. If the device is USB or SCSI, no additional drivers need to be loaded if you are running the generic FreeBSD kernel. After inserting the DVD media into the device, you can start the burn using this command:

'''growisofs -Z /dev/cd0=PCBSD9.1-x64-DVD.iso'''

If your device is not the first CD device, change the number 0 accordingly. If your ISO has a different name, substitute the correct name in the command shown above.

=== Burning the CD/DVD ISO File on a Mac OS X System ===

To burn the ISO on a Mac OS X system, go to "Finder ➜ Applications ➜ Utilities ➜ Disk Utility". With a blank media inserted into the burner, highlight the device representing the CD/DVD writer and click the "Burn" button. This will open up a browser where you can select the ISO to burn. In the example shown in Figure 2.5j, the DVD ISO has been selected and the device is a Sony DVD writer.

'''Figure 2.5j: Using Disk Utility on Mac OS X'''

[[File:Mac1a.png]]

Once the ISO is highlighted, click the "Burn" button. A pop-up message will indicate that the device is ready to burn. Click "Burn" once more and "Disk Utility" will write the ISO to the CD/DVD media.

=== Burning the CD/DVD ISO File on a Windows System ===

Several burning applications are available for Windows. This section will demonstrate how to use Windows 7's Disc Image Burner, ImgBurn, and InfraRecorder.

==== Windows 7 Disc Image Burner ====

Windows 7 has built-in support for writing ISO images to disc. Right-click on the ''.iso'' file in Windows Explorer and select "Open with ➜ Windows Disc Image Burner" to open the screen shown in Figure 2.5a. Click "Burn" to write the disc. See the Microsoft article {{citelink|url=http://windows.microsoft.com/en-US/windows7/Burn-a-CD-or-DVD-from-an-ISO-file|txt=Burn a CD or DVD from an ISO file}} for more detailed instructions.

'''Figure 2.5a: Windows Disc Image Burner'''

[[File:Diskburner1.png]]

==== ImgBurn ====

{{citelink|url=http://www.imgburn.com/|txt=ImgBurn}} is an easy to use ISO burner for Windows that is available for free download. After installing and launching ImgBurn, select "Write image file to disk" from the main menu, seen in Figure 2.5b:

'''Figure 2.5b: Initial ImgBurn Screen'''

[[File:Imgburn1a.png]]

You can then use File ➜ Browse for a source file... to select the ''.iso'' file to burn; once selected, your screen should look similar to Figure 2.5c. Click the Write icon in the lower left corner to begin the burn.

'''Figure 2.5c: Selecting the Source and Destination in ImgBurn

[[File:Imgburn2b.png]]

ImgBurn will provide a status bar to indicate the progress of the burn. When it is finished, ImgBurn will eject the burner tray then reclose it in order to verify the burn. If the tray does not return itself, which may occur on a laptop, push the tray back in if you wish to verify the burn.

==== InfraRecorder ====

{{citelink|url=http://infrarecorder.org/|txt=InfraRecorder}} is an open source burning application for both CDs and DVDs. Once installed, open InfraRecorder and click on the "Write Image" button shown in Figure 2.5d:

'''Figure 2.5d: Initial InfraRecorder Screen'''

[[File:Pic1.png]]

InfraRecorder will display a screen where you can browse to the location of the ''.iso'' file. Once selected, you will be presented with an options screen shown in Figure 2.5e:

'''Figure 2.5e: Burn Options in InfraRecorder'''

[[File:Infrarecorder1b.png]]

You can accept the defaults and click "OK" to start the burn. When finished, the burner tray will open and a dialog box will appear indicating that the burning process has finished.

=== Writing an ISO File to USB Using SUSE Studio ImageWriter ===

'''THIS DOES NOT RESULT IN A BOOTABLE STICK, NEEDS MORE TESTING, DITTO FOR UNETBOOTIN'''

{{citelink|wp|url=SUSE_Studio_ImageWriter|txt=SUSE Studio ImageWriter}} is a utility for burning ISO files to a USB flash drive. It works on Linux and Windows.

To use this utility, download {{citelink|url=https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe|txt=ImageWriter.exe}}. If you open this executable on a Windows system, you will see the screen shown in Figure 2.5k.

'''Figure 2.5k: Using ImageWriter in Windows'''

[[File:Image_writer.png]]

Due to a bug in the Windows implementation, you will need to type ''*.*'' and press enter in order for the ISO file to show in the selection screen. Once you have selected the ISO and the USB device, click the "Copy" button to burn the image to the device. The application will warn that all existing data on the device will be deleted.

=== Writing an IMG File to USB ===

To write an ''.img.bz2'' file you will need the following:

* a utility that can extract ''.bz2'' zipped files

* a utility that can write the image to a USB media; the utility that you use will depend upon your operating system

* a USB thumb drive or hard drive large enough to hold the image

Once the image is written, boot from the removable device and proceed with the [[Installing PC-BSD®|PC-BSD® installation]].

==== Writing the IMG File on a BSD or Linux System ====

If you selected to download an ''.img.bz2'' file instead of an ISO, you can write the image file to a flash card or removable USB drive using the '''bunzip2''' and '''dd''' command line utilities on a BSD or Linux system. On a FreeBSD system, the superuser can use these commands to extract the specified image and write it to the first plugged in USB device:

'''bunzip2 PCBSD9.1-x64-USBFULL.img.bz2'''
'''dd if=PCBSD9.1-x64-USBFULL.img of=/dev/da0 bs=64k conv=sync'''
63200+0 records in
63200+0 records out
4141875200 bytes transferred in 1395.261087 secs (2968531 bytes/sec)

When using the '''dd''' command:

* '''if=''' refers to the input file to be written; it should end with an ''.img'' extension

* '''of=''' refers to the output file (the device name of the flash card or removable USB drive); increment the number in the name if it is not the first USB device

* '''bs=''' refers to the block size

* '''conv=sync''' pads the final block so it is the specified block size

'''NOTE for Linux users:''' if you type '''mount''' with the USB stick inserted, you will see two or more device nodes corresponding to the USB stick. For example, ''/dev/sdc'' and ''/dev/sdc1'', where ''/dev/sdc1'' corresponds to the primary partition of the USB stick. Before using the '''dd''' command, ensure that the usb stick is first unmounted. When using the '''dd''' command, remember to use ''/dev/sdc'' (device node without the number) as the option for the output file '''of='''. Once the '''dd''' completes, you might not be able to mount the USB stick on Linux, as Linux has very limited support for UFS (the BSD filesystem that gets created on the USB stick).

==== Writing the IMG File on a Mac OS X System ====

To extract the ''.img.bz2'' file on a Mac system, use Finder to browse to the location of the file, as seen in Figure 2.5m.

'''Figure 2.5m: Extracting the Image on Mac'''

[[File:Mac2b.png|border]]

Simply double-click the file to extract it to the ''.img'' format. Finder will create a second file with the ''.img'' extension.

To burn that ''.img'' file, insert a USB stick and open "Terminal". Run the '''diskutil list''' command to find out the device name of the USB disk, unmount the USB disk, then use '''dd''' to write the image to the raw disk (''rdisk''). In the following example, an 8GB USB stick has a device name of ''/dev/disk1'' and a raw device name of ''/dev/rdisk1''.

'''diskutil list'''
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 499.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *8.0 GB disk1
1: DOS_FAT_32 UNTITLED 8.0 GB disk1s1

'''diskutil unmountDisk /dev/disk1'''
Unmount of all volumes on disk1 was successful

'''sudo dd if=/Users/dru/Downloads/PCBSD9.1-x64-USBFULL.img of=/dev/rdisk1 bs=4m'''
Password:
375+0 records in
375+0 records out
1572864000 bytes transferred in 86.742798 secs (18132502 bytes/sec)

==== Writing the IMG File on a Windows System ====

To burn the image file on a Windows system, you can use {{citelink|url=https://launchpad.net/win32-image-writer|txt=win32-image-writer}}. You will also need a utility that can extract ''.bz2'' files such as {{citelink|url=http://www.7-zip.org/|txt=7-Zip}}.

When downloading win32-image-writer, download the latest version that ends in ''-binary.zip'' and use a utility such as Windows Explorer or 7zip to unzip the executable.

To extract the PC-BSD® image file using 7-Zip, browse to the location containing your downloaded ''.img.bz2'' file, as seen in the example in Figure 2.5k.

'''Figure 2.5k: Using 7-Zip to Extract Image File'''

[[File:7zip1.png]]

Click the "Extract" button and browse to the location where you would like to save the extracted image. Once extracted, your image will end in ''.img'', and will be ready to be written to a USB device using the win32-image-writer application.

If you launch '''win32-image-writer.exe''', it will start the "Win32 Disk Imager" utility, shown in Figure 2.5l. Use the "Browse" button to browse to the location of the .img file. Insert a USB thumb drive and select its drive letter (in this example, drive D). Click the "Write" button and the image will be written to the USB thumb drive.

'''Figure 2.5l: Using Win32 Disk Imager to Write the Image'''

[[File:Image.png]]

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Pre-Installation Tasks]]
[[category:Burning the Installation Media]]
</noinclude>

Burning the Installation Media

2013-01-03T20:10:20Z

Vater: s/OSX/OS X && s/Mac OS/Mac OS

<noinclude>{{NavHeader|back=Obtaining PC-BSD®|forward=PC-BSD® Live Mode}}</noinclude>

Once you have downloaded PC-BSD® and verified its checksum, burn the file to the correct media type. This section demonstrates how to do so using several different applications and operating systems. Each application assumes that the correct media (CD, DVD, or USB flash drive) for the type of file is inserted.

=== Burning the CD/DVD ISO File on a BSD or Linux System ===

This section demonstrates how to burn the installation ISO on a Linux or BSD system using the following tools: K3B, Brasero, and '''growisofs'''.

==== K3B ====

{{citelink|url=http://www.kde.org/applications/multimedia/k3b/|txt=K3B}} is an easy-to-use graphical burning application for Linux and BSD systems. On a PC-BSD® system, it is installed with the KDE desktop. You can also install the K3B PBI using [[Using AppCafe®]].

To burn your ISO, launch K3B, browse to the location of the ''.iso'' file in the screen shown in Figure 2.5f and click ''Tools'' ➜ ''Burn Image...'' to see the screen in Figure 2.5g.

'''Figure 2.5f: Selecting the Burn Image Tool Within K3B'''

[[File:K3b1c.png]]

'''Figure 2.5g: K3B's Burn Image Screen'''

[[File:K3b2c.png]]

Click the "Start" button to burn the file. K3B will automatically eject the media once the burn is complete.

==== Brasero ====

{{citelink|url=http://projects.gnome.org/brasero/|txt=Brasero}} is an easy to use burning application included with the [[GNOME2|GNOME desktop]]. A PBI is also available within [[Using AppCafe® | AppCafe®]]. To launch Brasero within GNOME, click ''Applications'' ➜ ''Multimedia'' ➜ ''Brasero Disk Burner'' and the dialog window shown in Figure 2.5h will be displayed. Alternately, type '''brasero''' from within any window manager.

'''Figure 2.5h: Brasero's Initial Screen'''

[[File:Brasero1a.png]]

Click ''Burn image'' to open the screen seen in Figure 2.5i. Use the ''Click here to select a disk image'' button to select your ''.iso'' file.

'''Figure 2.5i: Brasero Image Burning Setup'''

[[File:Brasero2b.png]]

The name and size of your ''.iso'' file should appear and Brasero will indicate the size of the media. The lower portion of Figure 2.5i shows the menu that appears if you click on the "Properties" button. You can change these options if you wish, but the default settings are fine in most cases. When you are ready, click the "Burn" button and Brasero will burn your ISO.

==== Xfburn ====

{{citelink|url=http://goodies.xfce.org/projects/applications/xfburn|txt=Xfburn}} is available to [[Using AppCafe®#Installing and Uninstalling PBI Software | install as PBI Software]] and is installed with [[XFCE4]].

==== growisofs ====

If you are familiar with using the command line on a FreeBSD or PC-BSD® system, you can use the '''growisofs''' command line utility to burn the DVD. This utility is included with the dvd+rw-tools FreeBSD port which is installed by default on a PC-BSD® system. If that software is not yet installed on a FreeBSD system, issue this command as the superuser:

'''pkg_add -r dvd+rw-tools'''

Depending upon the type of DVD burner hardware, you may have to configure the system to use it. If the device is ATAPI (i.e. not USB or SCSI), the ATAPI driver must be loaded. The superuser can issue this command:

'''kldload atapicam'''

If you just get your prompt back, the driver successfully loaded. If you get the message "kldload: cannot load atapicam: File exists", this means that the driver was already loaded. If the device is USB or SCSI, no additional drivers need to be loaded if you are running the generic FreeBSD kernel. After inserting the DVD media into the device, you can start the burn using this command:

'''growisofs -Z /dev/cd0=PCBSD9.1-x64-DVD.iso'''

If your device is not the first CD device, change the number 0 accordingly. If your ISO has a different name, substitute the correct name in the command shown above.

=== Burning the CD/DVD ISO File on a Mac OS X System ===

To burn the ISO on a Mac OS X system, go to "Finder ➜ Applications ➜ Utilities ➜ Disk Utility". With a blank media inserted into the burner, highlight the device representing the CD/DVD writer and click the "Burn" button. This will open up a browser where you can select the ISO to burn. In the example shown in Figure 2.5j, the DVD ISO has been selected and the device is a Sony DVD writer.

'''Figure 2.5j: Using Disk Utility on Mac OS X'''

[[File:Mac1a.png]]

Once the ISO is highlighted, click the "Burn" button. A pop-up message will indicate that the device is ready to burn. Click "Burn" once more and "Disk Utility" will write the ISO to the CD/DVD media.

=== Burning the CD/DVD ISO File on a Windows System ===

Several burning applications are available for Windows. This section will demonstrate how to use Windows 7's Disc Image Burner, ImgBurn, and InfraRecorder.

==== Windows 7 Disc Image Burner ====

Windows 7 has built-in support for writing ISO images to disc. Right-click on the ''.iso'' file in Windows Explorer and select "Open with ➜ Windows Disc Image Burner" to open the screen shown in Figure 2.5a. Click "Burn" to write the disc. See the Microsoft article {{citelink|url=http://windows.microsoft.com/en-US/windows7/Burn-a-CD-or-DVD-from-an-ISO-file|txt=Burn a CD or DVD from an ISO file}} for more detailed instructions.

'''Figure 2.5a: Windows Disc Image Burner'''

[[File:Diskburner1.png]]

==== ImgBurn ====

{{citelink|url=http://www.imgburn.com/|txt=ImgBurn}} is an easy to use ISO burner for Windows that is available for free download. After installing and launching ImgBurn, select "Write image file to disk" from the main menu, seen in Figure 2.5b:

'''Figure 2.5b: Initial ImgBurn Screen'''

[[File:Imgburn1a.png]]

You can then use File ➜ Browse for a source file... to select the ''.iso'' file to burn; once selected, your screen should look similar to Figure 2.5c. Click the Write icon in the lower left corner to begin the burn.

'''Figure 2.5c: Selecting the Source and Destination in ImgBurn

[[File:Imgburn2b.png]]

ImgBurn will provide a status bar to indicate the progress of the burn. When it is finished, ImgBurn will eject the burner tray then reclose it in order to verify the burn. If the tray does not return itself, which may occur on a laptop, push the tray back in if you wish to verify the burn.

==== InfraRecorder ====

{{citelink|url=http://infrarecorder.org/|txt=InfraRecorder}} is an open source burning application for both CDs and DVDs. Once installed, open InfraRecorder and click on the "Write Image" button shown in Figure 2.5d:

'''Figure 2.5d: Initial InfraRecorder Screen'''

[[File:Pic1.png]]

InfraRecorder will display a screen where you can browse to the location of the ''.iso'' file. Once selected, you will be presented with an options screen shown in Figure 2.5e:

'''Figure 2.5e: Burn Options in InfraRecorder'''

[[File:Infrarecorder1b.png]]

You can accept the defaults and click "OK" to start the burn. When finished, the burner tray will open and a dialog box will appear indicating that the burning process has finished.

=== Writing an ISO File to USB Using SUSE Studio ImageWriter ===

'''THIS DOES NOT RESULT IN A BOOTABLE STICK, NEEDS MORE TESTING, DITTO FOR UNETBOOTIN'''

{{citelink|wp|url=SUSE_Studio_ImageWriter|txt=SUSE Studio ImageWriter}} is a utility for burning ISO files to a USB flash drive. It works on Linux and Windows.

To use this utility, download {{citelink|url=https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe|txt=ImageWriter.exe}}. If you open this executable on a Windows system, you will see the screen shown in Figure 2.5k.

'''Figure 2.5k: Using ImageWriter in Windows'''

[[File:Image_writer.png]]

Due to a bug in the Windows implementation, you will need to type ''*.*'' and press enter in order for the ISO file to show in the selection screen. Once you have selected the ISO and the USB device, click the "Copy" button to burn the image to the device. The application will warn that all existing data on the device will be deleted.

=== Writing an IMG File to USB ===

To write an ''.img.bz2'' file you will need the following:

* a utility that can extract ''.bz2'' zipped files

* a utility that can write the image to a USB media; the utility that you use will depend upon your operating system

* a USB thumb drive or hard drive large enough to hold the image

Once the image is written, boot from the removable device and proceed with the [[Installing PC-BSD®|PC-BSD® installation]].

==== Writing the IMG File on a BSD or Linux System ====

If you selected to download an ''.img.bz2'' file instead of an ISO, you can write the image file to a flash card or removable USB drive using the '''bunzip2''' and '''dd''' command line utilities on a BSD or Linux system. On a FreeBSD system, the superuser can use these commands to extract the specified image and write it to the first plugged in USB device:

'''bunzip2 PCBSD9.1-x64-USBFULL.img.bz2'''
'''dd if=PCBSD9.1-x64-USBFULL.img of=/dev/da0 bs=64k conv=sync'''
63200+0 records in
63200+0 records out
4141875200 bytes transferred in 1395.261087 secs (2968531 bytes/sec)

When using the '''dd''' command:

* '''if=''' refers to the input file to be written; it should end with an ''.img'' extension

* '''of=''' refers to the output file (the device name of the flash card or removable USB drive); increment the number in the name if it is not the first USB device

* '''bs=''' refers to the block size

* '''conv=sync''' pads the final block so it is the specified block size

'''NOTE for Linux users:''' if you type '''mount''' with the USB stick inserted, you will see two or more device nodes corresponding to the USB stick. For example, ''/dev/sdc'' and ''/dev/sdc1'', where ''/dev/sdc1'' corresponds to the primary partition of the USB stick. Before using the '''dd''' command, ensure that the usb stick is first unmounted. When using the '''dd''' command, remember to use ''/dev/sdc'' (device node without the number) as the option for the output file '''of='''. Once the '''dd''' completes, you might not be able to mount the USB stick on Linux, as Linux has very limited support for UFS (the BSD filesystem that gets created on the USB stick).

==== Writing the IMG File on a Mac OS X System ====

To extract the ''.img.bz2'' file on a Mac system, use Finder to browse to the location of the file, as seen in Figure 2.5m.

'''Figure 2.5m: Extracting the Image on Mac'''

[[File:Mac2b.png|border]]

Simply double-click the file to extract it to the ''.img'' format. Finder will create a second file with the ''.img'' extension.

To burn that ''.img'' file, insert a USB stick and open "Terminal". Run the '''diskutil list''' command to find out the device name of the USB disk, unmount the USB disk, then use '''dd''' to write the image to the raw disk (''rdisk''). In the following example, an 8GB USB stick has a device name of ''/dev/disk1'' and a raw device name of ''/dev/rdisk1''.

'''diskutil list'''
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 499.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *8.0 GB disk1
1: DOS_FAT_32 UNTITLED 8.0 GB disk1s1

'''diskutil unmountDisk /dev/disk1'''
Unmount of all volumes on disk1 was successful

'''sudo dd if=/Users/dru/Downloads/PCBSD9.1-x64-USBFULL.img of=/dev/rdisk1 bs=4m'''
Password:
375+0 records in
375+0 records out
1572864000 bytes transferred in 86.742798 secs (18132502 bytes/sec)

==== Writing the IMG File on a Windows System ====

To burn the image file on a Windows system, you can use {{citelink|url=https://launchpad.net/win32-image-writer win32-image-writer}}. You will also need a utility that can extract ''.bz2'' files such as {{citelink|url=http://www.7-zip.org/|txt=7-Zip}}.

When downloading win32-image-writer, download the latest version that ends in ''-binary.zip'' and use a utility such as Windows Explorer or 7zip to unzip the executable.

To extract the PC-BSD® image file using 7-Zip, browse to the location containing your downloaded ''.img.bz2'' file, as seen in the example in Figure 2.5k.

'''Figure 2.5k: Using 7-Zip to Extract Image File'''

[[File:7zip1.png]]

Click the "Extract" button and browse to the location where you would like to save the extracted image. Once extracted, your image will end in ''.img'', and will be ready to be written to a USB device using the win32-image-writer application.

If you launch '''win32-image-writer.exe''', it will start the "Win32 Disk Imager" utility, shown in Figure 2.5l. Use the "Browse" button to browse to the location of the .img file. Insert a USB thumb drive and select its drive letter (in this example, drive D). Click the "Write" button and the image will be written to the USB thumb drive.

'''Figure 2.5l: Using Win32 Disk Imager to Write the Image'''

[[File:Image.png]]

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Pre-Installation Tasks]]
[[category:Burning the Installation Media]]
</noinclude>

Burning the Installation Media

2013-01-03T19:53:49Z

Vater: /* Xfburn */ CHECK MY ENGLISH, PLEASE!!! + linked to the page of the project of the application + Hidden the text of To-do

<noinclude>{{NavHeader|back=Obtaining PC-BSD®|forward=PC-BSD® Live Mode}}</noinclude>

Once you have downloaded PC-BSD® and verified its checksum, burn the file to the correct media type. This section demonstrates how to do so using several different applications and operating systems. Each application assumes that the correct media (CD, DVD, or USB flash drive) for the type of file is inserted.

=== Burning the CD/DVD ISO File on a BSD or Linux System ===

This section demonstrates how to burn the installation ISO on a Linux or BSD system using the following tools: K3B, Brasero, and '''growisofs'''.

==== K3B ====

{{citelink|url=http://www.kde.org/applications/multimedia/k3b/|txt=K3B}} is an easy-to-use graphical burning application for Linux and BSD systems. On a PC-BSD® system, it is installed with the KDE desktop. You can also install the K3B PBI using [[Using AppCafe®]].

To burn your ISO, launch K3B, browse to the location of the ''.iso'' file in the screen shown in Figure 2.5f and click ''Tools'' ➜ ''Burn Image...'' to see the screen in Figure 2.5g.

'''Figure 2.5f: Selecting the Burn Image Tool Within K3B'''

[[File:K3b1c.png]]

'''Figure 2.5g: K3B's Burn Image Screen'''

[[File:K3b2c.png]]

Click the "Start" button to burn the file. K3B will automatically eject the media once the burn is complete.

==== Brasero ====

{{citelink|url=http://projects.gnome.org/brasero/|txt=Brasero}} is an easy to use burning application included with the [[GNOME2|GNOME desktop]]. A PBI is also available within [[Using AppCafe® | AppCafe®]]. To launch Brasero within GNOME, click ''Applications'' ➜ ''Multimedia'' ➜ ''Brasero Disk Burner'' and the dialog window shown in Figure 2.5h will be displayed. Alternately, type '''brasero''' from within any window manager.

'''Figure 2.5h: Brasero's Initial Screen'''

[[File:Brasero1a.png]]

Click ''Burn image'' to open the screen seen in Figure 2.5i. Use the ''Click here to select a disk image'' button to select your ''.iso'' file.

'''Figure 2.5i: Brasero Image Burning Setup'''

[[File:Brasero2b.png]]

The name and size of your ''.iso'' file should appear and Brasero will indicate the size of the media. The lower portion of Figure 2.5i shows the menu that appears if you click on the "Properties" button. You can change these options if you wish, but the default settings are fine in most cases. When you are ready, click the "Burn" button and Brasero will burn your ISO.

==== Xfburn ====

{{citelink|url=http://goodies.xfce.org/projects/applications/xfburn|txt=Xfburn}} is available to [[Using AppCafe®#Installing and Uninstalling PBI Software | install as PBI Software]] and is installed with [[XFCE4]].

==== growisofs ====

If you are familiar with using the command line on a FreeBSD or PC-BSD® system, you can use the '''growisofs''' command line utility to burn the DVD. This utility is included with the dvd+rw-tools FreeBSD port which is installed by default on a PC-BSD® system. If that software is not yet installed on a FreeBSD system, issue this command as the superuser:

'''pkg_add -r dvd+rw-tools'''

Depending upon the type of DVD burner hardware, you may have to configure the system to use it. If the device is ATAPI (i.e. not USB or SCSI), the ATAPI driver must be loaded. The superuser can issue this command:

'''kldload atapicam'''

If you just get your prompt back, the driver successfully loaded. If you get the message "kldload: cannot load atapicam: File exists", this means that the driver was already loaded. If the device is USB or SCSI, no additional drivers need to be loaded if you are running the generic FreeBSD kernel. After inserting the DVD media into the device, you can start the burn using this command:

'''growisofs -Z /dev/cd0=PCBSD9.1-x64-DVD.iso'''

If your device is not the first CD device, change the number 0 accordingly. If your ISO has a different name, substitute the correct name in the command shown above.

=== Burning the CD/DVD ISO File on a Mac OSX System ===

To burn the ISO on a Mac OSX system, go to "Finder ➜ Applications ➜ Utilities ➜ Disk Utility". With a blank media inserted into the burner, highlight the device representing the CD/DVD writer and click the "Burn" button. This will open up a browser where you can select the ISO to burn. In the example shown in Figure 2.5j, the DVD ISO has been selected and the device is a Sony DVD writer.

'''Figure 2.5j: Using Disk Utility on Mac OSX'''

[[File:Mac1a.png]]

Once the ISO is highlighted, click the "Burn" button. A pop-up message will indicate that the device is ready to burn. Click "Burn" once more and "Disk Utility" will write the ISO to the CD/DVD media.

=== Burning the CD/DVD ISO File on a Windows System ===

Several burning applications are available for Windows. This section will demonstrate how to use Windows 7's Disc Image Burner, ImgBurn, and InfraRecorder.

==== Windows 7 Disc Image Burner ====

Windows 7 has built-in support for writing ISO images to disc. Right-click on the ''.iso'' file in Windows Explorer and select "Open with ➜ Windows Disc Image Burner" to open the screen shown in Figure 2.5a. Click "Burn" to write the disc. See the Microsoft article {{citelink|url=http://windows.microsoft.com/en-US/windows7/Burn-a-CD-or-DVD-from-an-ISO-file|txt=Burn a CD or DVD from an ISO file}} for more detailed instructions.

'''Figure 2.5a: Windows Disc Image Burner'''

[[File:Diskburner1.png]]

==== ImgBurn ====

{{citelink|url=http://www.imgburn.com/|txt=ImgBurn}} is an easy to use ISO burner for Windows that is available for free download. After installing and launching ImgBurn, select "Write image file to disk" from the main menu, seen in Figure 2.5b:

'''Figure 2.5b: Initial ImgBurn Screen'''

[[File:Imgburn1a.png]]

You can then use File ➜ Browse for a source file... to select the ''.iso'' file to burn; once selected, your screen should look similar to Figure 2.5c. Click the Write icon in the lower left corner to begin the burn.

'''Figure 2.5c: Selecting the Source and Destination in ImgBurn

[[File:Imgburn2b.png]]

ImgBurn will provide a status bar to indicate the progress of the burn. When it is finished, ImgBurn will eject the burner tray then reclose it in order to verify the burn. If the tray does not return itself, which may occur on a laptop, push the tray back in if you wish to verify the burn.

==== InfraRecorder ====

{{citelink|url=http://infrarecorder.org/|txt=InfraRecorder}} is an open source burning application for both CDs and DVDs. Once installed, open InfraRecorder and click on the "Write Image" button shown in Figure 2.5d:

'''Figure 2.5d: Initial InfraRecorder Screen'''

[[File:Pic1.png]]

InfraRecorder will display a screen where you can browse to the location of the ''.iso'' file. Once selected, you will be presented with an options screen shown in Figure 2.5e:

'''Figure 2.5e: Burn Options in InfraRecorder'''

[[File:Infrarecorder1b.png]]

You can accept the defaults and click "OK" to start the burn. When finished, the burner tray will open and a dialog box will appear indicating that the burning process has finished.

=== Writing an ISO File to USB Using SUSE Studio ImageWriter ===

'''THIS DOES NOT RESULT IN A BOOTABLE STICK, NEEDS MORE TESTING, DITTO FOR UNETBOOTIN'''

{{citelink|wp|url=SUSE_Studio_ImageWriter|txt=SUSE Studio ImageWriter}} is a utility for burning ISO files to a USB flash drive. It works on Linux and Windows.

To use this utility, download {{citelink|url=https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe|txt=ImageWriter.exe}}. If you open this executable on a Windows system, you will see the screen shown in Figure 2.5k.

'''Figure 2.5k: Using ImageWriter in Windows'''

[[File:Image_writer.png]]

Due to a bug in the Windows implementation, you will need to type ''*.*'' and press enter in order for the ISO file to show in the selection screen. Once you have selected the ISO and the USB device, click the "Copy" button to burn the image to the device. The application will warn that all existing data on the device will be deleted.

=== Writing an IMG File to USB ===

To write an ''.img.bz2'' file you will need the following:

* a utility that can extract ''.bz2'' zipped files

* a utility that can write the image to a USB media; the utility that you use will depend upon your operating system

* a USB thumb drive or hard drive large enough to hold the image

Once the image is written, boot from the removable device and proceed with the [[Installing PC-BSD®|PC-BSD® installation]].

==== Writing the IMG File on a BSD or Linux System ====

If you selected to download an ''.img.bz2'' file instead of an ISO, you can write the image file to a flash card or removable USB drive using the '''bunzip2''' and '''dd''' command line utilities on a BSD or Linux system. On a FreeBSD system, the superuser can use these commands to extract the specified image and write it to the first plugged in USB device:

'''bunzip2 PCBSD9.1-x64-USBFULL.img.bz2'''
'''dd if=PCBSD9.1-x64-USBFULL.img of=/dev/da0 bs=64k conv=sync'''
63200+0 records in
63200+0 records out
4141875200 bytes transferred in 1395.261087 secs (2968531 bytes/sec)

When using the '''dd''' command:

* '''if=''' refers to the input file to be written; it should end with an ''.img'' extension

* '''of=''' refers to the output file (the device name of the flash card or removable USB drive); increment the number in the name if it is not the first USB device

* '''bs=''' refers to the block size

* '''conv=sync''' pads the final block so it is the specified block size

'''NOTE for Linux users:''' if you type '''mount''' with the USB stick inserted, you will see two or more device nodes corresponding to the USB stick. For example, ''/dev/sdc'' and ''/dev/sdc1'', where ''/dev/sdc1'' corresponds to the primary partition of the USB stick. Before using the '''dd''' command, ensure that the usb stick is first unmounted. When using the '''dd''' command, remember to use ''/dev/sdc'' (device node without the number) as the option for the output file '''of='''. Once the '''dd''' completes, you might not be able to mount the USB stick on Linux, as Linux has very limited support for UFS (the BSD filesystem that gets created on the USB stick).

==== Writing the IMG File on a Mac OSX System ====

To extract the ''.img.bz2'' file on a Mac system, use Finder to browse to the location of the file, as seen in Figure 2.5m.

'''Figure 2.5m: Extracting the Image on Mac'''

[[File:Mac2b.png|border]]

Simply double-click the file to extract it to the ''.img'' format. Finder will create a second file with the ''.img'' extension.

To burn that ''.img'' file, insert a USB stick and open "Terminal". Run the '''diskutil list''' command to find out the device name of the USB disk, unmount the USB disk, then use '''dd''' to write the image to the raw disk (''rdisk''). In the following example, an 8GB USB stick has a device name of ''/dev/disk1'' and a raw device name of ''/dev/rdisk1''.

'''diskutil list'''
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 499.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *8.0 GB disk1
1: DOS_FAT_32 UNTITLED 8.0 GB disk1s1

'''diskutil unmountDisk /dev/disk1'''
Unmount of all volumes on disk1 was successful

'''sudo dd if=/Users/dru/Downloads/PCBSD9.1-x64-USBFULL.img of=/dev/rdisk1 bs=4m'''
Password:
375+0 records in
375+0 records out
1572864000 bytes transferred in 86.742798 secs (18132502 bytes/sec)

==== Writing the IMG File on a Windows System ====

To burn the image file on a Windows system, you can use {{citelink|url=https://launchpad.net/win32-image-writer win32-image-writer}}. You will also need a utility that can extract ''.bz2'' files such as {{citelink|url=http://www.7-zip.org/|txt=7-Zip}}.

When downloading win32-image-writer, download the latest version that ends in ''-binary.zip'' and use a utility such as Windows Explorer or 7zip to unzip the executable.

To extract the PC-BSD® image file using 7-Zip, browse to the location containing your downloaded ''.img.bz2'' file, as seen in the example in Figure 2.5k.

'''Figure 2.5k: Using 7-Zip to Extract Image File'''

[[File:7zip1.png]]

Click the "Extract" button and browse to the location where you would like to save the extracted image. Once extracted, your image will end in ''.img'', and will be ready to be written to a USB device using the win32-image-writer application.

If you launch '''win32-image-writer.exe''', it will start the "Win32 Disk Imager" utility, shown in Figure 2.5l. Use the "Browse" button to browse to the location of the .img file. Insert a USB thumb drive and select its drive letter (in this example, drive D). Click the "Write" button and the image will be written to the USB thumb drive.

'''Figure 2.5l: Using Win32 Disk Imager to Write the Image'''

[[File:Image.png]]

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Pre-Installation Tasks]]
[[category:Burning the Installation Media]]
</noinclude>

Burning the Installation Media

2013-01-03T19:34:14Z

Vater: renamed (consistently) and placed sections new

<noinclude>{{NavHeader|back=Obtaining PC-BSD®|forward=PC-BSD® Live Mode}}</noinclude>

Once you have downloaded PC-BSD® and verified its checksum, burn the file to the correct media type. This section demonstrates how to do so using several different applications and operating systems. Each application assumes that the correct media (CD, DVD, or USB flash drive) for the type of file is inserted.

=== Burning the CD/DVD ISO File on a BSD or Linux System ===

This section demonstrates how to burn the installation ISO on a Linux or BSD system using the following tools: K3B, Brasero, and '''growisofs'''.

==== K3B ====

{{citelink|url=http://www.kde.org/applications/multimedia/k3b/|txt=K3B}} is an easy-to-use graphical burning application for Linux and BSD systems. On a PC-BSD® system, it is installed with the KDE desktop. You can also install the K3B PBI using [[Using AppCafe®]].

To burn your ISO, launch K3B, browse to the location of the ''.iso'' file in the screen shown in Figure 2.5f and click ''Tools'' ➜ ''Burn Image...'' to see the screen in Figure 2.5g.

'''Figure 2.5f: Selecting the Burn Image Tool Within K3B'''

[[File:K3b1c.png]]

'''Figure 2.5g: K3B's Burn Image Screen'''

[[File:K3b2c.png]]

Click the "Start" button to burn the file. K3B will automatically eject the media once the burn is complete.

==== Brasero ====

{{citelink|url=http://projects.gnome.org/brasero/|txt=Brasero}} is an easy to use burning application included with the [[GNOME2|GNOME desktop]]. A PBI is also available within [[Using AppCafe® | AppCafe®]]. To launch Brasero within GNOME, click ''Applications'' ➜ ''Multimedia'' ➜ ''Brasero Disk Burner'' and the dialog window shown in Figure 2.5h will be displayed. Alternately, type '''brasero''' from within any window manager.

'''Figure 2.5h: Brasero's Initial Screen'''

[[File:Brasero1a.png]]

Click ''Burn image'' to open the screen seen in Figure 2.5i. Use the ''Click here to select a disk image'' button to select your ''.iso'' file.

'''Figure 2.5i: Brasero Image Burning Setup'''

[[File:Brasero2b.png]]

The name and size of your ''.iso'' file should appear and Brasero will indicate the size of the media. The lower portion of Figure 2.5i shows the menu that appears if you click on the "Properties" button. You can change these options if you wish, but the default settings are fine in most cases. When you are ready, click the "Burn" button and Brasero will burn your ISO.

==== Xfburn ====

Available as PBI and installed with XFCE. Add instructions for 9.2 Handbook.

==== growisofs ====

If you are familiar with using the command line on a FreeBSD or PC-BSD® system, you can use the '''growisofs''' command line utility to burn the DVD. This utility is included with the dvd+rw-tools FreeBSD port which is installed by default on a PC-BSD® system. If that software is not yet installed on a FreeBSD system, issue this command as the superuser:

'''pkg_add -r dvd+rw-tools'''

Depending upon the type of DVD burner hardware, you may have to configure the system to use it. If the device is ATAPI (i.e. not USB or SCSI), the ATAPI driver must be loaded. The superuser can issue this command:

'''kldload atapicam'''

If you just get your prompt back, the driver successfully loaded. If you get the message "kldload: cannot load atapicam: File exists", this means that the driver was already loaded. If the device is USB or SCSI, no additional drivers need to be loaded if you are running the generic FreeBSD kernel. After inserting the DVD media into the device, you can start the burn using this command:

'''growisofs -Z /dev/cd0=PCBSD9.1-x64-DVD.iso'''

If your device is not the first CD device, change the number 0 accordingly. If your ISO has a different name, substitute the correct name in the command shown above.

=== Burning the CD/DVD ISO File on a Mac OSX System ===

To burn the ISO on a Mac OSX system, go to "Finder ➜ Applications ➜ Utilities ➜ Disk Utility". With a blank media inserted into the burner, highlight the device representing the CD/DVD writer and click the "Burn" button. This will open up a browser where you can select the ISO to burn. In the example shown in Figure 2.5j, the DVD ISO has been selected and the device is a Sony DVD writer.

'''Figure 2.5j: Using Disk Utility on Mac OSX'''

[[File:Mac1a.png]]

Once the ISO is highlighted, click the "Burn" button. A pop-up message will indicate that the device is ready to burn. Click "Burn" once more and "Disk Utility" will write the ISO to the CD/DVD media.

=== Burning the CD/DVD ISO File on a Windows System ===

Several burning applications are available for Windows. This section will demonstrate how to use Windows 7's Disc Image Burner, ImgBurn, and InfraRecorder.

==== Windows 7 Disc Image Burner ====

Windows 7 has built-in support for writing ISO images to disc. Right-click on the ''.iso'' file in Windows Explorer and select "Open with ➜ Windows Disc Image Burner" to open the screen shown in Figure 2.5a. Click "Burn" to write the disc. See the Microsoft article {{citelink|url=http://windows.microsoft.com/en-US/windows7/Burn-a-CD-or-DVD-from-an-ISO-file|txt=Burn a CD or DVD from an ISO file}} for more detailed instructions.

'''Figure 2.5a: Windows Disc Image Burner'''

[[File:Diskburner1.png]]

==== ImgBurn ====

{{citelink|url=http://www.imgburn.com/|txt=ImgBurn}} is an easy to use ISO burner for Windows that is available for free download. After installing and launching ImgBurn, select "Write image file to disk" from the main menu, seen in Figure 2.5b:

'''Figure 2.5b: Initial ImgBurn Screen'''

[[File:Imgburn1a.png]]

You can then use File ➜ Browse for a source file... to select the ''.iso'' file to burn; once selected, your screen should look similar to Figure 2.5c. Click the Write icon in the lower left corner to begin the burn.

'''Figure 2.5c: Selecting the Source and Destination in ImgBurn

[[File:Imgburn2b.png]]

ImgBurn will provide a status bar to indicate the progress of the burn. When it is finished, ImgBurn will eject the burner tray then reclose it in order to verify the burn. If the tray does not return itself, which may occur on a laptop, push the tray back in if you wish to verify the burn.

==== InfraRecorder ====

{{citelink|url=http://infrarecorder.org/|txt=InfraRecorder}} is an open source burning application for both CDs and DVDs. Once installed, open InfraRecorder and click on the "Write Image" button shown in Figure 2.5d:

'''Figure 2.5d: Initial InfraRecorder Screen'''

[[File:Pic1.png]]

InfraRecorder will display a screen where you can browse to the location of the ''.iso'' file. Once selected, you will be presented with an options screen shown in Figure 2.5e:

'''Figure 2.5e: Burn Options in InfraRecorder'''

[[File:Infrarecorder1b.png]]

You can accept the defaults and click "OK" to start the burn. When finished, the burner tray will open and a dialog box will appear indicating that the burning process has finished.

=== Writing an ISO File to USB Using SUSE Studio ImageWriter ===

'''THIS DOES NOT RESULT IN A BOOTABLE STICK, NEEDS MORE TESTING, DITTO FOR UNETBOOTIN'''

{{citelink|wp|url=SUSE_Studio_ImageWriter|txt=SUSE Studio ImageWriter}} is a utility for burning ISO files to a USB flash drive. It works on Linux and Windows.

To use this utility, download {{citelink|url=https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe|txt=ImageWriter.exe}}. If you open this executable on a Windows system, you will see the screen shown in Figure 2.5k.

'''Figure 2.5k: Using ImageWriter in Windows'''

[[File:Image_writer.png]]

Due to a bug in the Windows implementation, you will need to type ''*.*'' and press enter in order for the ISO file to show in the selection screen. Once you have selected the ISO and the USB device, click the "Copy" button to burn the image to the device. The application will warn that all existing data on the device will be deleted.

=== Writing an IMG File to USB ===

To write an ''.img.bz2'' file you will need the following:

* a utility that can extract ''.bz2'' zipped files

* a utility that can write the image to a USB media; the utility that you use will depend upon your operating system

* a USB thumb drive or hard drive large enough to hold the image

Once the image is written, boot from the removable device and proceed with the [[Installing PC-BSD®|PC-BSD® installation]].

==== Writing the IMG File on a BSD or Linux System ====

If you selected to download an ''.img.bz2'' file instead of an ISO, you can write the image file to a flash card or removable USB drive using the '''bunzip2''' and '''dd''' command line utilities on a BSD or Linux system. On a FreeBSD system, the superuser can use these commands to extract the specified image and write it to the first plugged in USB device:

'''bunzip2 PCBSD9.1-x64-USBFULL.img.bz2'''
'''dd if=PCBSD9.1-x64-USBFULL.img of=/dev/da0 bs=64k conv=sync'''
63200+0 records in
63200+0 records out
4141875200 bytes transferred in 1395.261087 secs (2968531 bytes/sec)

When using the '''dd''' command:

* '''if=''' refers to the input file to be written; it should end with an ''.img'' extension

* '''of=''' refers to the output file (the device name of the flash card or removable USB drive); increment the number in the name if it is not the first USB device

* '''bs=''' refers to the block size

* '''conv=sync''' pads the final block so it is the specified block size

'''NOTE for Linux users:''' if you type '''mount''' with the USB stick inserted, you will see two or more device nodes corresponding to the USB stick. For example, ''/dev/sdc'' and ''/dev/sdc1'', where ''/dev/sdc1'' corresponds to the primary partition of the USB stick. Before using the '''dd''' command, ensure that the usb stick is first unmounted. When using the '''dd''' command, remember to use ''/dev/sdc'' (device node without the number) as the option for the output file '''of='''. Once the '''dd''' completes, you might not be able to mount the USB stick on Linux, as Linux has very limited support for UFS (the BSD filesystem that gets created on the USB stick).

==== Writing the IMG File on a Mac OSX System ====

To extract the ''.img.bz2'' file on a Mac system, use Finder to browse to the location of the file, as seen in Figure 2.5m.

'''Figure 2.5m: Extracting the Image on Mac'''

[[File:Mac2b.png|border]]

Simply double-click the file to extract it to the ''.img'' format. Finder will create a second file with the ''.img'' extension.

To burn that ''.img'' file, insert a USB stick and open "Terminal". Run the '''diskutil list''' command to find out the device name of the USB disk, unmount the USB disk, then use '''dd''' to write the image to the raw disk (''rdisk''). In the following example, an 8GB USB stick has a device name of ''/dev/disk1'' and a raw device name of ''/dev/rdisk1''.

'''diskutil list'''
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 499.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *8.0 GB disk1
1: DOS_FAT_32 UNTITLED 8.0 GB disk1s1

'''diskutil unmountDisk /dev/disk1'''
Unmount of all volumes on disk1 was successful

'''sudo dd if=/Users/dru/Downloads/PCBSD9.1-x64-USBFULL.img of=/dev/rdisk1 bs=4m'''
Password:
375+0 records in
375+0 records out
1572864000 bytes transferred in 86.742798 secs (18132502 bytes/sec)

==== Writing the IMG File on a Windows System ====

To burn the image file on a Windows system, you can use {{citelink|url=https://launchpad.net/win32-image-writer win32-image-writer}}. You will also need a utility that can extract ''.bz2'' files such as {{citelink|url=http://www.7-zip.org/|txt=7-Zip}}.

When downloading win32-image-writer, download the latest version that ends in ''-binary.zip'' and use a utility such as Windows Explorer or 7zip to unzip the executable.

To extract the PC-BSD® image file using 7-Zip, browse to the location containing your downloaded ''.img.bz2'' file, as seen in the example in Figure 2.5k.

'''Figure 2.5k: Using 7-Zip to Extract Image File'''

[[File:7zip1.png]]

Click the "Extract" button and browse to the location where you would like to save the extracted image. Once extracted, your image will end in ''.img'', and will be ready to be written to a USB device using the win32-image-writer application.

If you launch '''win32-image-writer.exe''', it will start the "Win32 Disk Imager" utility, shown in Figure 2.5l. Use the "Browse" button to browse to the location of the .img file. Insert a USB thumb drive and select its drive letter (in this example, drive D). Click the "Write" button and the image will be written to the USB thumb drive.

'''Figure 2.5l: Using Win32 Disk Imager to Write the Image'''

[[File:Image.png]]

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Pre-Installation Tasks]]
[[category:Burning the Installation Media]]
</noinclude>

Errata

2013-01-03T18:35:02Z

Vater:

{{NavHome}} __NOEDITSECTION__ 

== Explanation ==
Although every effort is made to create accurate instructions, sometimes the need for adjustment comes after a version of the handbook has been published. It is hoped that those changes are few and occur seldom. Here is where errors, omissions, and other changes or improvements will be recorded, organized by title and version.

=== PC-BSD Handbook ===
{{:PC-BSD® Users Handbook}}

'''Newest published version first:'''

==== Release 9.1 ====

{{Tbl-init|width=99%}}
{{Tbl-title|width=3%|'''Page'''}}
{{Tbl-title|width=18%|'''Main Heading'''}}
{{Tbl-title|width=22%|'''SubHeading'''}}
{{Tbl-title|width=28%|'''As Published'''}}
{{Tbl-title|width=28%|'''Adjustment'''}}
|-
|}

==== Release 9.0 ====

{{Tbl-init|width=99%}}
{{Tbl-title|width=3%|'''Page'''}}
{{Tbl-title|width=18%|'''Main Heading'''}}
{{Tbl-title|width=22%|'''SubHeading'''}}
{{Tbl-title|width=28%|'''As Published'''}}
{{Tbl-title|width=28%|'''Adjustment'''}}
|-
{{tbl-cell|row=1|align=right|21}}
{{tbl-cell|row=1|2.6 Obtaining PC-BSD}}
{{tbl-cell|row=1|2.6.1 Selecting Which File to Download}}
{{Tbl-cell|row=1|align=justified|There are two versions available for each type of file: one for 32-bit (i386) systems and one for 64-bit (amd64) systems. It is important that you download a file that matches your computer's processor type (32- or 64-bit).}}
{{Tbl-cell|row=1|align=justified|There are two versions available for each type of file: one for 32-bit (i386) systems and one for 64-bit (amd64) systems. It is important that you download a file that matches your computer's processor type (32- or 64-bit). {{highlight|Each media type includes a file, ''pcbsd-media'' which identifies the release version.}}}}
|-
{{tbl-cell|row=2|align=right|86}}
{{tbl-cell|row=2|4.5 Dual Booting}}
{{tbl-cell|row=2|4.5.3.1 Adding PC-BSD to Legacy GRUB}}
{{tbl-cell|row=2|'''Root:''' The root of the partition containing PC-BSD. In the above example, PC-BSD is installed on the first hard disk (hd0) and on the first partition (,1). Start counting your hard disk from zero (e.g. disk 0 for the first hard disk, disk 1 for the second hard disk) and your partition from one (e.g. 1 for the first partition on that disk, 2 for the second partition, etc.)}}
{{tbl-cell|row=2|'''Root:''' The root of the partition containing PC-BSD. In the above example, PC-BSD is installed on the first hard disk (hd0) and on the {{highlight|second}} partition (,1). Start counting your hard disk from zero (e.g. disk 0 for the first hard disk, disk 1 for the second hard disk) and your partition from {{highlight|zero}} (e.g. {{highlight|0}} for the first {{highlight|primary}} partition on that disk, {{highlight|1}} for the second {{highlight|primary}} partition, etc.)}}
|-
{{Tbl-cell|row=3|align=right|86}}
{{Tbl-cell|row=3|4.5 Dual Booting}}
{{Tbl-cell|row=3|4.5.3.2 Adding PC-BSD to GRUB Version 2}}
{{Tbl-cell|row=3|align=justified|If you installed PC-BSD on the first hard drive, in the 3rd primary partition, the entry would look something like this:}}
{{Tbl-cell|row=3|align=justified|If you installed PC-BSD on the first hard drive, in the 3rd primary partition, the entry {{highlight|in the file /etc/grub.d/40_custom}} would look something like this:}}
|-
{{Tbl-cell|row=4|align=right|87}}
{{Tbl-cell|row=4|4.5 Dual Booting}}
{{Tbl-cell|row=4|4.5.3.2 Adding PC-BSD to GRUB Version 2}}
{{Tbl-cell|row=4|align=justified|If you are trying to dual-boot with GRUB2 under Fedora 16, run '''grub2-mkconfig -o /boot/grub2/grub.cfg''' as the superuser.}}
{{Tbl-cell|row=4|align=justified|If you are trying to dual-boot with GRUB2 under Fedora 16 {{Highlight|or Gentoo}}, run '''grub2-mkconfig -o /boot/grub2/grub.cfg''' as the superuser {{Highlight|(Please note that if using Sabayon, you need to use '''grub-mkconfig''' instead of '''grub2-mkconfig''')}}.}}
|-
{{Tbl-cell|row=5|align=right|}}
{{Tbl-cell|row=5|}}
{{Tbl-cell|row=5|Unverified}}
{{Tbl-cell|row=5|}}
{{Tbl-cell|row=5|align=justified|content={{highlight|text=To enable Chinese input, it may be necessary to create and/or edit the .xinitrc file in your home directory to add two lines:}}
:{{highlight|text=1. export XMODIFIERS='@im=ibus'}}
:{{highlight|text=2. GTK_IM_MODULE=ibus }} }}
|-
|}

==== Release 8.2 ====
{{Tbl-init|width=99%}}
{{Tbl-title|width=3%|'''Page'''}}
{{Tbl-title|width=18%|'''Main Heading'''}}
{{Tbl-title|width=22%|'''SubHeading'''}}
{{Tbl-title|width=28%|'''As Published'''}}
{{Tbl-title|width=28%|'''Adjustment'''}}
|-
{{Tbl-cell|row=1|align=right|22}}
{{Tbl-cell|row=1|2 Pre-Installation Tasks}}
{{Tbl-cell|row=1|2.6.1.2 Nero}}
{{Tbl-cell|row=1|align=justified|The free version of Nero was suggested as a tool to burn the iso.}}
{{Tbl-cell|row=1|align=justified|This information is now inaccurate since '''the free version''' of Nero '''only burns Music CDs.'''}}
|-
{{Tbl-cell|row=2|align=right|22}}
{{Tbl-cell|row=2|2 Pre-Installation Tasks}}
{{Tbl-cell|row=2|2.6.2.2 Brasero}}
{{Tbl-cell|row=2|align=justified|The lower portion of Figure {{highlight|X-XX}} shows the menu that appears if you click on the Properties button.}}
{{Tbl-cell|row=2|align=justified|The lower portion of Figure {{highlight|2.6.2d}} shows the menu that appears if you click on the Properties button.}}
|-
{{Tbl-cell|row=3|align=right|24}}
{{Tbl-cell|row=3|2 Pre-Installation Tasks}}
{{Tbl-cell|row=3|2.6.3 Writing an IMG File to Flash Media}}
{{Tbl-cell|row=3|align=justified|<nowiki>dd if=PCBSD8.1-x86-USB-bootonly.img of=/dev/da0 bs=</nowiki>{{highlight|5k}}}}
{{Tbl-cell|row=3|align=justified|<nowiki>dd if=PCBSD8.1-x86-USB-bootonly.img of=/dev/da0 bs=</nowiki>{{highlight|64k}} (Also more sensible as base 2)}}
|-
{{Tbl-cell|row=4|align=right|183}}
{{Tbl-cell|row=4|9 Supporting PC-BSD}}
{{Tbl-cell|row=4|9.6 Test PBIs}}
{{Tbl-cell|row=4|align=justified|To give an example, the math/scilab PBI was flagged as FAILED in Figure {{highlight|X-XX}}.}}
{{Tbl-cell|row=4|align=justified|To give an example, the math/scilab PBI was flagged as FAILED in Figure {{highlight|9.6a}}.}}
|}

== FreeBSD Errata ==
: {{Citelink|url=http://www.freebsd.org/releases/9.1R/errata.html|txt=FreeBSD Errata for v9.1R}}
: {{Citelink|url=http://www.freebsd.org/releases/9.0R/errata.html|txt=FreeBSD Errata for v9.1R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.3R/errata.html|txt=FreeBSD Errata for v8.3R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.2R/errata.html|txt=FreeBSD Errata for v8.2R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.1R/errata.html|txt=FreeBSD Errata for v8.1R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.0R/errata.html|txt=FreeBSD Errata for v8.0R}}

<noinclude>{{refheading}}</noinclude>

Errata

2013-01-03T18:33:23Z

Vater: add section for newest version (9.1)

{{NavHome}} __NOEDITSECTION__ 

== Explanation ==
Although every effort is made to create accurate instructions, sometimes the need for adjustment comes after a version of the handbook has been published. It is hoped that those changes are few and occur seldom. Here is where errors, omissions, and other changes or improvements will be recorded, organized by title and version.

=== PC-BSD Handbook ===
{{:PC-BSD Users Handbook}}

'''Newest published version first:'''

==== Release 9.1 ====

{{Tbl-init|width=99%}}
{{Tbl-title|width=3%|'''Page'''}}
{{Tbl-title|width=18%|'''Main Heading'''}}
{{Tbl-title|width=22%|'''SubHeading'''}}
{{Tbl-title|width=28%|'''As Published'''}}
{{Tbl-title|width=28%|'''Adjustment'''}}
|-
|}

==== Release 9.0 ====

{{Tbl-init|width=99%}}
{{Tbl-title|width=3%|'''Page'''}}
{{Tbl-title|width=18%|'''Main Heading'''}}
{{Tbl-title|width=22%|'''SubHeading'''}}
{{Tbl-title|width=28%|'''As Published'''}}
{{Tbl-title|width=28%|'''Adjustment'''}}
|-
{{tbl-cell|row=1|align=right|21}}
{{tbl-cell|row=1|2.6 Obtaining PC-BSD}}
{{tbl-cell|row=1|2.6.1 Selecting Which File to Download}}
{{Tbl-cell|row=1|align=justified|There are two versions available for each type of file: one for 32-bit (i386) systems and one for 64-bit (amd64) systems. It is important that you download a file that matches your computer's processor type (32- or 64-bit).}}
{{Tbl-cell|row=1|align=justified|There are two versions available for each type of file: one for 32-bit (i386) systems and one for 64-bit (amd64) systems. It is important that you download a file that matches your computer's processor type (32- or 64-bit). {{highlight|Each media type includes a file, ''pcbsd-media'' which identifies the release version.}}}}
|-
{{tbl-cell|row=2|align=right|86}}
{{tbl-cell|row=2|4.5 Dual Booting}}
{{tbl-cell|row=2|4.5.3.1 Adding PC-BSD to Legacy GRUB}}
{{tbl-cell|row=2|'''Root:''' The root of the partition containing PC-BSD. In the above example, PC-BSD is installed on the first hard disk (hd0) and on the first partition (,1). Start counting your hard disk from zero (e.g. disk 0 for the first hard disk, disk 1 for the second hard disk) and your partition from one (e.g. 1 for the first partition on that disk, 2 for the second partition, etc.)}}
{{tbl-cell|row=2|'''Root:''' The root of the partition containing PC-BSD. In the above example, PC-BSD is installed on the first hard disk (hd0) and on the {{highlight|second}} partition (,1). Start counting your hard disk from zero (e.g. disk 0 for the first hard disk, disk 1 for the second hard disk) and your partition from {{highlight|zero}} (e.g. {{highlight|0}} for the first {{highlight|primary}} partition on that disk, {{highlight|1}} for the second {{highlight|primary}} partition, etc.)}}
|-
{{Tbl-cell|row=3|align=right|86}}
{{Tbl-cell|row=3|4.5 Dual Booting}}
{{Tbl-cell|row=3|4.5.3.2 Adding PC-BSD to GRUB Version 2}}
{{Tbl-cell|row=3|align=justified|If you installed PC-BSD on the first hard drive, in the 3rd primary partition, the entry would look something like this:}}
{{Tbl-cell|row=3|align=justified|If you installed PC-BSD on the first hard drive, in the 3rd primary partition, the entry {{highlight|in the file /etc/grub.d/40_custom}} would look something like this:}}
|-
{{Tbl-cell|row=4|align=right|87}}
{{Tbl-cell|row=4|4.5 Dual Booting}}
{{Tbl-cell|row=4|4.5.3.2 Adding PC-BSD to GRUB Version 2}}
{{Tbl-cell|row=4|align=justified|If you are trying to dual-boot with GRUB2 under Fedora 16, run '''grub2-mkconfig -o /boot/grub2/grub.cfg''' as the superuser.}}
{{Tbl-cell|row=4|align=justified|If you are trying to dual-boot with GRUB2 under Fedora 16 {{Highlight|or Gentoo}}, run '''grub2-mkconfig -o /boot/grub2/grub.cfg''' as the superuser {{Highlight|(Please note that if using Sabayon, you need to use '''grub-mkconfig''' instead of '''grub2-mkconfig''')}}.}}
|-
{{Tbl-cell|row=5|align=right|}}
{{Tbl-cell|row=5|}}
{{Tbl-cell|row=5|Unverified}}
{{Tbl-cell|row=5|}}
{{Tbl-cell|row=5|align=justified|content={{highlight|text=To enable Chinese input, it may be necessary to create and/or edit the .xinitrc file in your home directory to add two lines:}}
:{{highlight|text=1. export XMODIFIERS='@im=ibus'}}
:{{highlight|text=2. GTK_IM_MODULE=ibus }} }}
|-
|}

==== Release 8.2 ====
{{Tbl-init|width=99%}}
{{Tbl-title|width=3%|'''Page'''}}
{{Tbl-title|width=18%|'''Main Heading'''}}
{{Tbl-title|width=22%|'''SubHeading'''}}
{{Tbl-title|width=28%|'''As Published'''}}
{{Tbl-title|width=28%|'''Adjustment'''}}
|-
{{Tbl-cell|row=1|align=right|22}}
{{Tbl-cell|row=1|2 Pre-Installation Tasks}}
{{Tbl-cell|row=1|2.6.1.2 Nero}}
{{Tbl-cell|row=1|align=justified|The free version of Nero was suggested as a tool to burn the iso.}}
{{Tbl-cell|row=1|align=justified|This information is now inaccurate since '''the free version''' of Nero '''only burns Music CDs.'''}}
|-
{{Tbl-cell|row=2|align=right|22}}
{{Tbl-cell|row=2|2 Pre-Installation Tasks}}
{{Tbl-cell|row=2|2.6.2.2 Brasero}}
{{Tbl-cell|row=2|align=justified|The lower portion of Figure {{highlight|X-XX}} shows the menu that appears if you click on the Properties button.}}
{{Tbl-cell|row=2|align=justified|The lower portion of Figure {{highlight|2.6.2d}} shows the menu that appears if you click on the Properties button.}}
|-
{{Tbl-cell|row=3|align=right|24}}
{{Tbl-cell|row=3|2 Pre-Installation Tasks}}
{{Tbl-cell|row=3|2.6.3 Writing an IMG File to Flash Media}}
{{Tbl-cell|row=3|align=justified|<nowiki>dd if=PCBSD8.1-x86-USB-bootonly.img of=/dev/da0 bs=</nowiki>{{highlight|5k}}}}
{{Tbl-cell|row=3|align=justified|<nowiki>dd if=PCBSD8.1-x86-USB-bootonly.img of=/dev/da0 bs=</nowiki>{{highlight|64k}} (Also more sensible as base 2)}}
|-
{{Tbl-cell|row=4|align=right|183}}
{{Tbl-cell|row=4|9 Supporting PC-BSD}}
{{Tbl-cell|row=4|9.6 Test PBIs}}
{{Tbl-cell|row=4|align=justified|To give an example, the math/scilab PBI was flagged as FAILED in Figure {{highlight|X-XX}}.}}
{{Tbl-cell|row=4|align=justified|To give an example, the math/scilab PBI was flagged as FAILED in Figure {{highlight|9.6a}}.}}
|}

== FreeBSD Errata ==
: {{Citelink|url=http://www.freebsd.org/releases/9.1R/errata.html|txt=FreeBSD Errata for v9.1R}}
: {{Citelink|url=http://www.freebsd.org/releases/9.0R/errata.html|txt=FreeBSD Errata for v9.1R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.3R/errata.html|txt=FreeBSD Errata for v8.3R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.2R/errata.html|txt=FreeBSD Errata for v8.2R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.1R/errata.html|txt=FreeBSD Errata for v8.1R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.0R/errata.html|txt=FreeBSD Errata for v8.0R}}

<noinclude>{{refheading}}</noinclude>

Errata

2013-01-03T18:27:55Z

Vater: using citelink template

{{NavHome}} __NOEDITSECTION__ 

== Explanation ==
Although every effort is made to create accurate instructions, sometimes the need for adjustment comes after a version of the handbook has been published. It is hoped that those changes are few and occur seldom. Here is where errors, omissions, and other changes or improvements will be recorded, organized by title and version.

=== PC-BSD Handbook ===
{{:PC-BSD Users Handbook}}

'''Newest published version first:'''

==== Release 9.0 ====

{{Tbl-init|width=99%}}
{{Tbl-title|width=3%|'''Page'''}}
{{Tbl-title|width=18%|'''Main Heading'''}}
{{Tbl-title|width=22%|'''SubHeading'''}}
{{Tbl-title|width=28%|'''As Published'''}}
{{Tbl-title|width=28%|'''Adjustment'''}}
|-
{{tbl-cell|row=1|align=right|21}}
{{tbl-cell|row=1|2.6 Obtaining PC-BSD}}
{{tbl-cell|row=1|2.6.1 Selecting Which File to Download}}
{{Tbl-cell|row=1|align=justified|There are two versions available for each type of file: one for 32-bit (i386) systems and one for 64-bit (amd64) systems. It is important that you download a file that matches your computer's processor type (32- or 64-bit).}}
{{Tbl-cell|row=1|align=justified|There are two versions available for each type of file: one for 32-bit (i386) systems and one for 64-bit (amd64) systems. It is important that you download a file that matches your computer's processor type (32- or 64-bit). {{highlight|Each media type includes a file, ''pcbsd-media'' which identifies the release version.}}}}
|-
{{tbl-cell|row=2|align=right|86}}
{{tbl-cell|row=2|4.5 Dual Booting}}
{{tbl-cell|row=2|4.5.3.1 Adding PC-BSD to Legacy GRUB}}
{{tbl-cell|row=2|'''Root:''' The root of the partition containing PC-BSD. In the above example, PC-BSD is installed on the first hard disk (hd0) and on the first partition (,1). Start counting your hard disk from zero (e.g. disk 0 for the first hard disk, disk 1 for the second hard disk) and your partition from one (e.g. 1 for the first partition on that disk, 2 for the second partition, etc.)}}
{{tbl-cell|row=2|'''Root:''' The root of the partition containing PC-BSD. In the above example, PC-BSD is installed on the first hard disk (hd0) and on the {{highlight|second}} partition (,1). Start counting your hard disk from zero (e.g. disk 0 for the first hard disk, disk 1 for the second hard disk) and your partition from {{highlight|zero}} (e.g. {{highlight|0}} for the first {{highlight|primary}} partition on that disk, {{highlight|1}} for the second {{highlight|primary}} partition, etc.)}}
|-
{{Tbl-cell|row=3|align=right|86}}
{{Tbl-cell|row=3|4.5 Dual Booting}}
{{Tbl-cell|row=3|4.5.3.2 Adding PC-BSD to GRUB Version 2}}
{{Tbl-cell|row=3|align=justified|If you installed PC-BSD on the first hard drive, in the 3rd primary partition, the entry would look something like this:}}
{{Tbl-cell|row=3|align=justified|If you installed PC-BSD on the first hard drive, in the 3rd primary partition, the entry {{highlight|in the file /etc/grub.d/40_custom}} would look something like this:}}
|-
{{Tbl-cell|row=4|align=right|87}}
{{Tbl-cell|row=4|4.5 Dual Booting}}
{{Tbl-cell|row=4|4.5.3.2 Adding PC-BSD to GRUB Version 2}}
{{Tbl-cell|row=4|align=justified|If you are trying to dual-boot with GRUB2 under Fedora 16, run '''grub2-mkconfig -o /boot/grub2/grub.cfg''' as the superuser.}}
{{Tbl-cell|row=4|align=justified|If you are trying to dual-boot with GRUB2 under Fedora 16 {{Highlight|or Gentoo}}, run '''grub2-mkconfig -o /boot/grub2/grub.cfg''' as the superuser {{Highlight|(Please note that if using Sabayon, you need to use '''grub-mkconfig''' instead of '''grub2-mkconfig''')}}.}}
|-
{{Tbl-cell|row=5|align=right|}}
{{Tbl-cell|row=5|}}
{{Tbl-cell|row=5|Unverified}}
{{Tbl-cell|row=5|}}
{{Tbl-cell|row=5|align=justified|content={{highlight|text=To enable Chinese input, it may be necessary to create and/or edit the .xinitrc file in your home directory to add two lines:}}
:{{highlight|text=1. export XMODIFIERS='@im=ibus'}}
:{{highlight|text=2. GTK_IM_MODULE=ibus }} }}
|-
|}

==== Release 8.2 ====
{{Tbl-init|width=99%}}
{{Tbl-title|width=3%|'''Page'''}}
{{Tbl-title|width=18%|'''Main Heading'''}}
{{Tbl-title|width=22%|'''SubHeading'''}}
{{Tbl-title|width=28%|'''As Published'''}}
{{Tbl-title|width=28%|'''Adjustment'''}}
|-
{{Tbl-cell|row=1|align=right|22}}
{{Tbl-cell|row=1|2 Pre-Installation Tasks}}
{{Tbl-cell|row=1|2.6.1.2 Nero}}
{{Tbl-cell|row=1|align=justified|The free version of Nero was suggested as a tool to burn the iso.}}
{{Tbl-cell|row=1|align=justified|This information is now inaccurate since '''the free version''' of Nero '''only burns Music CDs.'''}}
|-
{{Tbl-cell|row=2|align=right|22}}
{{Tbl-cell|row=2|2 Pre-Installation Tasks}}
{{Tbl-cell|row=2|2.6.2.2 Brasero}}
{{Tbl-cell|row=2|align=justified|The lower portion of Figure {{highlight|X-XX}} shows the menu that appears if you click on the Properties button.}}
{{Tbl-cell|row=2|align=justified|The lower portion of Figure {{highlight|2.6.2d}} shows the menu that appears if you click on the Properties button.}}
|-
{{Tbl-cell|row=3|align=right|24}}
{{Tbl-cell|row=3|2 Pre-Installation Tasks}}
{{Tbl-cell|row=3|2.6.3 Writing an IMG File to Flash Media}}
{{Tbl-cell|row=3|align=justified|<nowiki>dd if=PCBSD8.1-x86-USB-bootonly.img of=/dev/da0 bs=</nowiki>{{highlight|5k}}}}
{{Tbl-cell|row=3|align=justified|<nowiki>dd if=PCBSD8.1-x86-USB-bootonly.img of=/dev/da0 bs=</nowiki>{{highlight|64k}} (Also more sensible as base 2)}}
|-
{{Tbl-cell|row=4|align=right|183}}
{{Tbl-cell|row=4|9 Supporting PC-BSD}}
{{Tbl-cell|row=4|9.6 Test PBIs}}
{{Tbl-cell|row=4|align=justified|To give an example, the math/scilab PBI was flagged as FAILED in Figure {{highlight|X-XX}}.}}
{{Tbl-cell|row=4|align=justified|To give an example, the math/scilab PBI was flagged as FAILED in Figure {{highlight|9.6a}}.}}
|}

== FreeBSD Errata ==
: {{Citelink|url=http://www.freebsd.org/releases/9.1R/errata.html|txt=FreeBSD Errata for v9.1R}}
: {{Citelink|url=http://www.freebsd.org/releases/9.0R/errata.html|txt=FreeBSD Errata for v9.1R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.3R/errata.html|txt=FreeBSD Errata for v8.3R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.2R/errata.html|txt=FreeBSD Errata for v8.2R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.1R/errata.html|txt=FreeBSD Errata for v8.1R}}
: {{Citelink|url=http://www.freebsd.org/releases/8.0R/errata.html|txt=FreeBSD Errata for v8.0R}}

<noinclude>{{refheading}}</noinclude>

Errata

2013-01-03T18:27:10Z

Vater:

{{NavHome}} __NOEDITSECTION__ 

== Explanation ==
Although every effort is made to create accurate instructions, sometimes the need for adjustment comes after a version of the handbook has been published. It is hoped that those changes are few and occur seldom. Here is where errors, omissions, and other changes or improvements will be recorded, organized by title and version.

=== PC-BSD Handbook ===
{{:PC-BSD Users Handbook}}

'''Newest published version first:'''

==== Release 9.0 ====

{{Tbl-init|width=99%}}
{{Tbl-title|width=3%|'''Page'''}}
{{Tbl-title|width=18%|'''Main Heading'''}}
{{Tbl-title|width=22%|'''SubHeading'''}}
{{Tbl-title|width=28%|'''As Published'''}}
{{Tbl-title|width=28%|'''Adjustment'''}}
|-
{{tbl-cell|row=1|align=right|21}}
{{tbl-cell|row=1|2.6 Obtaining PC-BSD}}
{{tbl-cell|row=1|2.6.1 Selecting Which File to Download}}
{{Tbl-cell|row=1|align=justified|There are two versions available for each type of file: one for 32-bit (i386) systems and one for 64-bit (amd64) systems. It is important that you download a file that matches your computer's processor type (32- or 64-bit).}}
{{Tbl-cell|row=1|align=justified|There are two versions available for each type of file: one for 32-bit (i386) systems and one for 64-bit (amd64) systems. It is important that you download a file that matches your computer's processor type (32- or 64-bit). {{highlight|Each media type includes a file, ''pcbsd-media'' which identifies the release version.}}}}
|-
{{tbl-cell|row=2|align=right|86}}
{{tbl-cell|row=2|4.5 Dual Booting}}
{{tbl-cell|row=2|4.5.3.1 Adding PC-BSD to Legacy GRUB}}
{{tbl-cell|row=2|'''Root:''' The root of the partition containing PC-BSD. In the above example, PC-BSD is installed on the first hard disk (hd0) and on the first partition (,1). Start counting your hard disk from zero (e.g. disk 0 for the first hard disk, disk 1 for the second hard disk) and your partition from one (e.g. 1 for the first partition on that disk, 2 for the second partition, etc.)}}
{{tbl-cell|row=2|'''Root:''' The root of the partition containing PC-BSD. In the above example, PC-BSD is installed on the first hard disk (hd0) and on the {{highlight|second}} partition (,1). Start counting your hard disk from zero (e.g. disk 0 for the first hard disk, disk 1 for the second hard disk) and your partition from {{highlight|zero}} (e.g. {{highlight|0}} for the first {{highlight|primary}} partition on that disk, {{highlight|1}} for the second {{highlight|primary}} partition, etc.)}}
|-
{{Tbl-cell|row=3|align=right|86}}
{{Tbl-cell|row=3|4.5 Dual Booting}}
{{Tbl-cell|row=3|4.5.3.2 Adding PC-BSD to GRUB Version 2}}
{{Tbl-cell|row=3|align=justified|If you installed PC-BSD on the first hard drive, in the 3rd primary partition, the entry would look something like this:}}
{{Tbl-cell|row=3|align=justified|If you installed PC-BSD on the first hard drive, in the 3rd primary partition, the entry {{highlight|in the file /etc/grub.d/40_custom}} would look something like this:}}
|-
{{Tbl-cell|row=4|align=right|87}}
{{Tbl-cell|row=4|4.5 Dual Booting}}
{{Tbl-cell|row=4|4.5.3.2 Adding PC-BSD to GRUB Version 2}}
{{Tbl-cell|row=4|align=justified|If you are trying to dual-boot with GRUB2 under Fedora 16, run '''grub2-mkconfig -o /boot/grub2/grub.cfg''' as the superuser.}}
{{Tbl-cell|row=4|align=justified|If you are trying to dual-boot with GRUB2 under Fedora 16 {{Highlight|or Gentoo}}, run '''grub2-mkconfig -o /boot/grub2/grub.cfg''' as the superuser {{Highlight|(Please note that if using Sabayon, you need to use '''grub-mkconfig''' instead of '''grub2-mkconfig''')}}.}}
|-
{{Tbl-cell|row=5|align=right|}}
{{Tbl-cell|row=5|}}
{{Tbl-cell|row=5|Unverified}}
{{Tbl-cell|row=5|}}
{{Tbl-cell|row=5|align=justified|content={{highlight|text=To enable Chinese input, it may be necessary to create and/or edit the .xinitrc file in your home directory to add two lines:}}
:{{highlight|text=1. export XMODIFIERS='@im=ibus'}}
:{{highlight|text=2. GTK_IM_MODULE=ibus }} }}
|-
|}

==== Release 8.2 ====
{{Tbl-init|width=99%}}
{{Tbl-title|width=3%|'''Page'''}}
{{Tbl-title|width=18%|'''Main Heading'''}}
{{Tbl-title|width=22%|'''SubHeading'''}}
{{Tbl-title|width=28%|'''As Published'''}}
{{Tbl-title|width=28%|'''Adjustment'''}}
|-
{{Tbl-cell|row=1|align=right|22}}
{{Tbl-cell|row=1|2 Pre-Installation Tasks}}
{{Tbl-cell|row=1|2.6.1.2 Nero}}
{{Tbl-cell|row=1|align=justified|The free version of Nero was suggested as a tool to burn the iso.}}
{{Tbl-cell|row=1|align=justified|This information is now inaccurate since '''the free version''' of Nero '''only burns Music CDs.'''}}
|-
{{Tbl-cell|row=2|align=right|22}}
{{Tbl-cell|row=2|2 Pre-Installation Tasks}}
{{Tbl-cell|row=2|2.6.2.2 Brasero}}
{{Tbl-cell|row=2|align=justified|The lower portion of Figure {{highlight|X-XX}} shows the menu that appears if you click on the Properties button.}}
{{Tbl-cell|row=2|align=justified|The lower portion of Figure {{highlight|2.6.2d}} shows the menu that appears if you click on the Properties button.}}
|-
{{Tbl-cell|row=3|align=right|24}}
{{Tbl-cell|row=3|2 Pre-Installation Tasks}}
{{Tbl-cell|row=3|2.6.3 Writing an IMG File to Flash Media}}
{{Tbl-cell|row=3|align=justified|<nowiki>dd if=PCBSD8.1-x86-USB-bootonly.img of=/dev/da0 bs=</nowiki>{{highlight|5k}}}}
{{Tbl-cell|row=3|align=justified|<nowiki>dd if=PCBSD8.1-x86-USB-bootonly.img of=/dev/da0 bs=</nowiki>{{highlight|64k}} (Also more sensible as base 2)}}
|-
{{Tbl-cell|row=4|align=right|183}}
{{Tbl-cell|row=4|9 Supporting PC-BSD}}
{{Tbl-cell|row=4|9.6 Test PBIs}}
{{Tbl-cell|row=4|align=justified|To give an example, the math/scilab PBI was flagged as FAILED in Figure {{highlight|X-XX}}.}}
{{Tbl-cell|row=4|align=justified|To give an example, the math/scilab PBI was flagged as FAILED in Figure {{highlight|9.6a}}.}}
|}

== FreeBSD Errata ==
: [http://www.freebsd.org/releases/9.1R/errata.html FreeBSD Errata for v9.1R]
: [http://www.freebsd.org/releases/9.0R/errata.html FreeBSD Errata for v9.0R]
: [http://www.freebsd.org/releases/8.3R/errata.html FreeBSD Errata for v8.3R]
: [http://www.freebsd.org/releases/8.2R/errata.html FreeBSD Errata for v8.2R]
: [http://www.freebsd.org/releases/8.1R/errata.html FreeBSD Errata for v8.1R]
: [http://www.freebsd.org/releases/8.0R/errata.html FreeBSD Errata for v8.0R]

Talk:Installation Troubleshooting

2013-01-03T18:15:53Z

Vater: /* the background */

Not sure exactly how/where to place this, but it ought to be added in some form.
==Error 19==
=== the background ===

; (from a [http://forums.freebsd.org/showthread.php?t=32601 FreeBSD forum post]):

In any event, booting to FreeBSD from Grub now leads to

Code:

Mounting from ufs:/dev/ad4s3a failed with error 19

and thereafter to a mountroot prompt. Typing '?' at the mountroot prompt provides no GEOM managed disk devices whatsoever.

At this stage, I created a re-install CD of FreeBSD 9.0-RELEASE and booted from it. However, the boot ended with

Code:

Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19

and then the mountroot prompt. Once again, typing a '?' at the prompt showed no GEOM managed disk devices.

=== the solution ===

; (from a [http://paulscomputernotes.blogspot.com.au/2012/06/installing-freebsd-90-drives.html blog post]):

Here's where I found it and all that is need is to open the loader prompt during the CD/DVD/USB boot (by pressing 2 or ESC) and adding the following line:

set debug.acpi.disabled ="hostres"

and then booting with

boot

Once the USB key has booted you can add the line

debug.acpi.disabled ="hostres"

to /boot/loader.conf, if you intend to use the key again.
In any event, once you have installed FreeBSD 9.0-RELEASE, you still need to add this line to /boot/loader.conf.

==== other refs ====

Also documented in Open issues of [http://www.freebsd.org/releases/9.0R/errata.html FreeBSD v9.0R errata].

Talk:Installation Troubleshooting

2013-01-03T18:14:21Z

Vater: /* the solution */

Not sure exactly how/where to place this, but it ought to be added in some form.
==Error 19==
=== the background ===
(from a [http://forums.freebsd.org/showthread.php?t=32601 FreeBSD forum post])

In any event, booting to FreeBSD from Grub now leads to
Code:

Mounting from ufs:/dev/ad4s3a failed with error 19

and thereafter to a mountroot prompt. Typing '?' at the mountroot prompt provides no GEOM managed disk devices whatsoever.

At this stage, I created a re-install CD of FreeBSD 9.0-RELEASE and booted from it. However, the boot ended with
Code:

Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19

and then the mountroot prompt. Once again, typing a '?' at the prompt showed no GEOM managed disk devices.

=== the solution ===

; (from a [http://paulscomputernotes.blogspot.com.au/2012/06/installing-freebsd-90-drives.html blog post]):

Here's where I found it and all that is need is to open the loader prompt during the CD/DVD/USB boot (by pressing 2 or ESC) and adding the following line:

set debug.acpi.disabled ="hostres"

and then booting with

boot

Once the USB key has booted you can add the line

debug.acpi.disabled ="hostres"

to /boot/loader.conf, if you intend to use the key again.
In any event, once you have installed FreeBSD 9.0-RELEASE, you still need to add this line to /boot/loader.conf.

==== other refs ====

Also documented in Open issues of [http://www.freebsd.org/releases/9.0R/errata.html FreeBSD v9.0R errata].

KDE4

2012-12-23T20:18:13Z

Vater:

<noinclude>{{NavHeader|back=GNOME2|forward=LXDE}}</noinclude>

The {{citelink|url=http://kde.org/|txt=KDE}} desktop environment provides many features and applications. However, it is hardware intensive and may run slowly on a computer with an older processor or a small amount of RAM. Figure 6.2a shows a screenshot of KDE4 running on PC-BSD® 9.1 with the "Applications" menu open:

'''Figure 6.2a: Applications Menu of KDE4'''

[[File:KDE4.png]]

Each category in the "Applications" menu contains many applications and the "Settings" and "System" categories contain many utilities for configuring your system. If you are new to KDE4, take some time to discover which applications best suit your needs. Some of the applications which are provided by KDE4 include:

* '''{{citelink|url=http://docs.kde.org/stable/en/kdegraphics/gwenview/index.html|txt=Gwenview}}:''' image viewer found in ''Graphics'' ➜ ''Image Viewer''.

* '''{{citelink|url=http://docs.kde.org/development/en/extragear-graphics/digikam/index.html|txt=Digikam}}:''' photo-management program found in ''Graphics'' ➜ ''Photo Management Program''.

* '''{{citelink|url=http://docs.kde.org/stable/en/kde-baseapps/konqueror/index.html/index.html|txt=Konqueror}}:''' file manager, web browser, and SSH client found in ''Internet'' ➜ ''Web Browser''.

* '''{{citelink|url=http://docs.kde.org/development/en/extragear-multimedia/kmplayer/index.html|txt=KMPlayer}}:''' media player found in ''Multimedia'' ➜ ''Media Player''. Plays most MPEG/VOB, AVI, Ogg/OGM, VIVO, ASF/WMA/WMV, QT/MOV/MP4, RealMedia, Matroska, NUT, NuppelVideo, FLI, YUV4MPEG, FILM, RoQ, PVA files, supported by many native, XAnim, and Win32 DLL codecs. You can watch VideoCD, SVCD, DVD, 3ivx, DivX 3/4/5, WMV and even H.264 movies.

* '''{{citelink|url=http://docs.kde.org/stable/en/kdegraphics/okular/index.html|txt=Okular}}:''' document viewer and annotator found in Office - Document Viewer. Supports PDF, OpenOffice, and Postscript files.

* '''{{citelink|url=http://docs.kde.org/development/en/kdepim/korganizer/index.html|txt=KOrganizer}}:''' organizer utility and reminder daemon found in ''Office'' ➜ ''Personal Organizer''.

* '''{{citelink|url=http://docs.kde.org/stable/en/kde-baseapps/dolphin/index.html|txt=Dolphin}}:''' file manager found in ''System'' ➜ ''File Manager''. Dolphin provides many features for manipulating files such as comments, tags, search, encryption, and archival (zip/unzip) functions.

By default, desktop effects are disabled, as not all video cards support them. If your video card supports 3D effects and you would like to enable them in KDE, go to ''System Settings'' ➜ ''Desktop Effects'' ➜ ''General'' and check the box "Enable desktop effects at startup".

Some of KDE's games require 3D support. If your video card does not support 3D, these games will fail to start.

You may or may not have installed all of KDE's components during installation. You can view the installed components and check (to add) or uncheck (to delete) various components using ''[[Control Panel]]'' ➜ [[System Manager#Install/Uninstall Desktops and System Components | ''System Manager'' ➜ ''System Packages'']] ➜ ''[[Desktops]]'' ➜ ''[[KDE4|KDE]]''.

If you have KDE installed and are currently logged into a different window manager, you can still run any KDE application by specifying its name. For example, type '''konqueror''' to run the Konqueror web browser or '''dolphin''' to access the Dolphin File Manager.

{{citelink|url=http://www.kde.org/applications/|txt=KDE Applications}} includes descriptions and screenshots of all of KDE's applications as well as links to their handbooks.

{{citelink|url=http://www.kde-look.org/|txt=kde-look.org}} contains additional themes and wallpapers.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:desktops]]
[[category:KDE4]]
</noinclude>

Evilwm

2012-12-19T06:52:37Z

Vater:

<noinclude>{{NavHeader|back=Enlightenment |forward=Fluxbox|custompagename=evilwm}}</noinclude>

{{citelink|url=http://evilwm.sourceforge.net/|txt=evilwm}} 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.6a shows a screenshot of evilwm running on PC-BSD® 9.1.

'''Figure 6.6a: evilwm Running on PC-BSD®'''

[[File:Evilwm.png]]

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 {{citelink|url=http://www.6809.org.uk/evilwm/usage.shtml|txt=the evilwm site}}.

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

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:desktops]]
[[category:evilwm]]
</noinclude>

Active Directory & LDAP

2012-12-19T06:52:16Z

Vater:

<noinclude>{{NavHeader|back=About|forward=Hardware Compatibility}}</noinclude>

Beginning with PC-BSD® 9.1, the Control Panel contains an "Active Directory & LDAP" icon for managing connections to an Active Directory or OpenLDAP domain. If your network contains an Active Directory or OpenLDAP server, use this icon to input the settings needed to connect to your account information stored on the network. At this time, these settings can not be set during installation of PC-BSD® 9.1; this will be added as a feature of version 9.2.

'''NOTE:''' this utility is to manage the settings of the client, not the Active Directory or OpenLDAP server itself.

To start the application, double-click its icon in Control Panel or type '''pc-su pc-adsldap'''. You will be prompted to input the administrative password. Figure 8.3a shows the configuration utility with the Active Directory tab open.

'''Figure 8.3a: Initial Active Directory & LDAP Screen'''

[[File:Ad2.png]]

=== Connecting to Active Directory ===

If you need to connect to a network running Active Directory, check the box "Enable Active Directory". This will change the greyed-out status of the rest of the screen, allowing you to configure the following:

* '''Domain Name (DNS/Realm-Name):''' input the name of the Active Directory domain (e.g. example.com) or child domain (e.g. sales.example.com). This setting is mandatory.

* '''NetBIOS Name:''' input the hostname of the PC-BSD® system as listed in the [[About]] icon.

* '''Workgroup Name:''' input the name of the Windows workgroup. Unless the administrator has changed it, the default workgroup name is ''WORKGROUP''.

* '''Allow Trusted Domains:''' only check this box if the network has {{citelink|url=http://technet.microsoft.com/en-us/library/cc757352%28WS.10%29.aspx|txt=active domain/forest trusts}}.

* '''Administrator Name:''' input the name of the Active Directory Administrator account.

* '''Administrator Password:''' input and confirm the password for the Active Directory Administrator account.

The values that you input using this GUI are saved to ''/usr/local/etc/pc-activedirectory.conf''.

=== Connecting to an OpenLDAP Server ===

Figure 8.3b shows the configuration utility with the LDAP tab open.

'''Figure 8.3b: Managing LDAP Client Settings'''

[[File:ldap.png]]

If you need to connect to a network which contains a configured LDAP server, check the box "Enable LDAP". This will change the greyed-out status of the rest of the screen, allowing you to configure the following:

* '''Hostname:''' input the hostname or IP address of the OpenLDAP server. This setting is mandatory.

* '''Base DN:''' input the top level of the LDAP directory tree to be used when searching for resources (e.g. dc=test,dc=org).

* '''Allow Anon Binding:''' only check this box if the LDAP server allows read and write access without requiring authentication.

* '''Root bind DN:''' input the name of the administrative account on the LDAP server (e.g. cn=Manager,dc=test,dc=org).

* '''Root bind password:''' input the password for the ''Root bind DN''.

* '''Password Encryption:''' select a type supported by the LDAP server, choices are: clear (unencrypted), crypt, md5, nds, racf, ad, or exop.

* '''User Suffix:''' this setting is optional and is usually a dept. or company name. The input value will be added to the name when a user account is added to the LDAP directory

* '''Group Suffix:''' this setting is optional and is usually a dept. or company name. The input value will be added to the name when a group is added to the LDAP directory.

* '''Password Suffix:''' this setting is optional. The input value will be added to the password when a password is added to the LDAP directory.

* '''Machine Suffix:''' this setting is optional and usually represents a description such as server or accounting. The input value will be added to the name when a system is added to the LDAP directory.

* '''Encryption Mode:''' choices are "Off", "SSL", or "TLS". The selected type must be supported by the LDAP server.

* '''Self Signed Certificate:''' used to verify the certificate of the LDAP server if SSL connections are used. Paste the output of the command '''openssl s_client -connect server:port -showcerts.'''

* '''Auxiliary Parameters:''' {{citelink|url=http://www.openldap.org/software/man.cgi?query=ldap.conf|txt=ldap.conf(5)}} options, one per line, not covered by other options in this screen.

The values that you input into this tab are saved to ''/usr/local/etc/pc-ldap.conf''.

If you are new to LDAP terminology, you may find it useful to skim through the {{Citelink|url=http://www.openldap.org/doc/admin24/|txt=OpenLDAP Software 2.4 Administrator's Guide}}.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Control Panel]]
[[category:Active Directory & LDAP]]
</noinclude>

I3

2012-12-19T06:51:16Z

Vater:

<noinclude>{{NavHeader|back=FVWM|forward=IceWM|custompagename=i3}}</noinclude>

{{citelink|url=http://i3wm.org/|txt=i3}} is a lightweight, tiling window manager. Keyboard shortcuts are provided to open xterms in order to start applications from the command line.

i3 provides a panel and on PC-BSD® that panel will contain icons for [[Bluetooth Manager]] (if the system has a Bluetooth interface), [[Update Manager]], [[Network Configuration]] (if your wireless card is detected), and [[Life Preserver]].

Figure 6.10a shows a screenshot of i3 running on PC-BSD® 9.1.

'''Figure 6.10a: i3 Window Manager on PC-BSD®'''

[[File:i3a.png]]

To open an xterm, use Alt+Enter. Windows do not provide minimize/mazimize or close buttons, so type '''exit''' when you are finished using an xterm. To leave the window manager and return to the login screen, type '''killall i3''' from within an xterm.

The {{citelink|url=http://i3wm.org/docs/userguide.html|txt=i3 Users Guide}} contains the default key bindings and instructions for customizing i3.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:desktops]]
[[category:i3]]
</noinclude>

EasyPBI

2012-12-19T06:50:46Z

Vater:

<noinclude>{{NavHeader|back=Control Panel|forward=About}}</noinclude>

EasyPBI is a graphical application that makes it easy to build a PBI module from a FreeBSD port. Beginning with PC-BSD® 9.1, EasyPBI ships with PC-BSD® and can be found in the Control Panel.

This section demonstrates how to use this utility to convert an existing FreeBSD port into a PC-BSD® PBI. You may wish to skim the section on how to [[Create PBIs]] first, as well as refer to that Guide should you have trouble creating a PBI or wish to create a more complex PBI.

To start EasyPBI, double-click its icon in Control Panel or type '''EasyPBI''' from within an X terminal as your regular user account.

If the ports collection is not installed, you will receive the message shown in Figure 8.1a the first time you start EasyPBI.

'''Figure 8.1a: Ports Must be Installed to Use EasyPBI'''

[[File:Easypbi1d.png]]

If multiple users will be using the EasyPBI utility, go to ''[[Control Panel]]'' ➜ [[System Manager#Install FreeBSD Source and Ports| ''System Manager'' ➜ ''Tasks'']] and click the ''Fetch Ports Tree'' button. Alternately, use the following command as the superuser: '''portsnap fetch extract.''' Either of these methods will install the ports collection into ''/usr/ports.''

If you are the only user who will be using the EasyPBI utility, click OK to launch the main EasyPBI screen, shown in Figure 8.1b. Click ''File'' ➜ ''Get Ports'' which will download the ports collection to the ''[[EasyPBI]]'' subdirectory located in your home directory.

'''Figure 8.1b: EasyPBI Graphical Interface'''

[[File:Easypbi1b.png]]

If the ports collection was already installed or was installed using System Manager or '''portsnap''', the message in the bottom area of the screen will instead indicate "To get started, please push the "New Module" button.

== Creating a PBI Module ==

Before building a PBI, refer to the {{citelink|url=http://forums.pcbsd.org/forumdisplay.php?f=61|txt=PBI Requests forum}} to determine which PBIs have been requested by users. You should also check that a module does not already exist for the PBI in the {{citelink|url=http://trac.pcbsd.org/browser#pbi/modules|txt=PBI Modules}} section of trac. Existing modules are listed alphabetically, according to their category in the ports collection.

To create a new module, click the "New Module" button and use the browser to select the desired port from the FreeBSD ports tree. Once a port is selected, EasyPBI will attempt to automatically supply the port information for the PBI and display the results in the GUI. In the example shown in Figure 8.1c, the ''net/trickle'' port has been selected and the fields have been auto-filled in.

'''Figure 8.1c: Review the New Module'''

[[File:Easypbi1c.png]]

You should review these fields for accuracy. If you click "Get Port Info" {{citelink|url=http://freshports.org|txt=FreshPorts.org}} will open in the default web browser so that you can view additional information about the port.

A generic icon will be supplied for the module; you can change the default icon by clicking the "Choose Icon" button. When using a custom icon, use a 64x64 ''.png'' file with a transparent background.

Check the "Create Desktop/Menu Entries" if you wish the program's icon to be available on the desktop and in the desktop's application menu.

Once the port information is complete, click the "Create Module" button and EasyPBI will produce the PBI module. The module will be named after the port and will be stored in a subdirectory of the ''EasyPBI/Modules'' directory in your home directory. In this example, the module is located in ''EasyPBI/Modules/trickle.''

=== Build the Module ===

Creating the module itself is very quick and takes less than a minute. However, you still need to build and test the module to make sure that the application works as expected. Depending upon the complexity of the application, you may have to edit the initial module then rebuild and retest it until you are satisfied with the PBI for the application.

Once the module is created, you are ready to build a PBI from the module. Click on the "Build PBI" tab and click the "Select Module" button to browse to the module you created. Figure 8.1d shows this tab with our example PBI selected.

'''Figure 8.1d: The Build PBI Tab'''

[[File:Easypbi3b.png]]

The top half of this screen contains modifiable settings which are used when building PBIs:

'''Save Settings as Defaults:''' the settings in this section revert back to the default settings when you exit EasyPBI. This allows you to override the default settings for a particular build. If you wish your changes to be permanent, click this button.

'''Output Directory:''' specifies the directory to store the built module. By default, it is the ''EasyPBI/PBI'' subdirectory of the user's home directory. Click the "Change Directory" button to select another location.

'''Digital Signature File:''' the PBIs available from the PC-BSD® repositories are digitally signed by the PC-BSD® project's signature file. If you are creating your own repository, click the "Change File" button to select your own digital signature file. [[#Create Your Own PBI Repository|Create Your Own PBI Repository]] provides instructions for creating a signature file.

'''Use TMPFS:''' if your build system has a lot of RAM, selecting this option can speed up the build.

'''Use Package Caching:''' this setting is recommended as it reuses previously built packages to speed up subsequent builds.

The rest of this screen is used to build the specified module:

'''Select Module:''' select the previously created module to build.

'''Build PBI:''' starts the build of the PBI module. It will prompt you for the superuser password and requires a working Internet connection in order to build the PBI. This process may take quite a while, depending upon the port selected and the speed of your computer. The build messages will be displayed in the window at the bottom of the tab. EasyPBI will inform you when the PBI build is finished, and whether it was successful or not.

'''Stop Build:''' stops the build process. Click the "Build PBI" button to resume the build.

'''Save Build Log:''' useful if the build fails. Will prompt you to select the location to store ''build.log'' which can be read with any ASCII text editor.

You can produce additional modules from the "Create Module" tab while a PBI build is running.

If the PBI build fails for some reason, you may need to modify the module as described in the next section. Use the build log to determine the error and modify the module as needed. If you are unsure how to fix the module, send the ''build.log'' for the failure to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}.

=== Test and Fine-Tune the Module ===

Once your build is finished, test the PBI to ensure that it installs and that the application works.

To install the PBI, become the superuser, '''cd''' to the "Output Directory", and use the '''pbi_add''' command. Unless you have specified your own digital signature, include the '''--no-checksig''' option.

'''su'''
Password:
'''cd ~dru/EasyPBI/PBI'''
'''ls'''
trickle-1.07_2_amd64.pbi trickle-1.07_2_amd64.pbi.sha256
'''pbi_add --no-checksig trickle-1.07_2_amd64.pbi'''
Verifying Checksum...OK
Extracting to: /usr/pbi/trickle-amd64
Installed: trickle-1.07_2

If the module installs successfully, perform the following tests:

* if you checked the box "Create Desktop/Menu Entries", verify that a desktop icon was created (from a desktop that supports icons), that an entry was added to that desktop's application menu, and that the application successfully launches from the application menu. If you used a custom icon, verify that the icon was used.

* start the application from the command line to determine if there are any error messages at application launch. When starting the application, specify the full path to the application's binary to make sure that you are testing the PBI's binary.

* for GUI applications, 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 the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}.

The "Module Editor" tab, seen in Figure 8.1e, can be used to modify the module's settings. Use the "Select Module" button to browse to the location of the module and to un-grey-out the settings in this screen.

'''Figure 8.1e: EasyPBI Module Editor'''

[[File:easypbi4a.png]]

Several tabs are provided, allowing you to customize the PBI module. It should be noted that most PBI modules do not require you to make any configuration changes in the "Module Editor" tab. This tab allows the creation of more complex PBI modules that require additional FreeBSD ports or scripts which are not provided by the default FreeBSD port.

The rest of this section describes the actions available within each tab. If you modify any settings in the PBI module, rebuild it then test again to see if the changes fixed the PBI.

==== pbi.conf ====

Typically the "Program Name", "Program Website", and "Program Author" are left at their default values. If this information is incorrect, you should email the FreeBSD port maintainer shown in the "Program Author" field so that the information can be corrected in the FreeBSD port.

If you choose to replace the "Program Icon", use a 64x64 ''.png'' file with a transparent background.

If your PBI requires a dependency that is not provided by the FreeBSD port, use the + button next to "Make Port Before" to select the needed port.

If you wish an additional port to be included with your PBI, use the + button next to "Make Port After" to select the desired port.

The "Make Options" field lets you specify a space separated list of options. The available options and their default settings will be listed in the ''OPTIONS='' section of the port's ''Makefile''.

If the resulting PBI needs to be run as the root user, check the "Require Root Permissions" box.

==== Resources ====

This tab, shown in Figure 8.1f, is used to add additional files to the PBI module.

'''Figure 8.1f: PBI Module Resource Configuration'''

[[Image:Easypbi5a.png]]

An example of an additional file would be an application that requires the user to accept a License. Use the "+Add Resource" button to browse to the location of the ''LICENSE'' file.

Another example would be when you wish to use a custom script to start the application rather than starting the application binary directly. A custom script could also be used to verify that the service is enabled or to generate a custom configuration file.

If the application uses custom installer graphics, add them using this screen.

==== Desktop/Menu Entries ====

This tab, shown in Figure 8.1g, is used to fine-tune the desktop icon and the application menu entry for the application.

'''Figure 8.1g: Customizing the PBI's Desktop and Menu Entries'''

[[Image:Easypbi6a.png]]

If the "Create Desktop/Menu Entries" box was checked when creating the module and EasyPBI detects that the application is graphical, the default entries for the application will be listed. In our PBI example, '''trickle''' is a command line application so no entries were created by default. If your application is graphical but EasyPBI did not detect it, you can manually add the desired entries using the "Remove Desktop Entry" and "Remove Menu Entry" buttons.

Under "Executable", the drop-down menu will display all of the binaries that came with the application. Select the binary that should launch when the user clicks the desktop icon or selects the application from the application menu. Alternately, you can select "Custom Binary" and input the path to the desired executable.

The "Entry Label" field allows you to customize the name that will appear with the icon and application menu entry.

The "Icon" drop-down menu allows you to select the ''.png'' file to use for the icon. This file must exist in ''~/EasyPBI/Modules/PBI_name/resources'' in order to appear in the drop-down menu. Use the "Select Module" button to re-select the module if you add the icon after loading the module.

The "Menu Category" drop-down menu is used to select the category the application menu entry will be added to.

To add a desktop entry, select an "Executable", input an "Entry Label", and click the "+Add Desktop Entry" button. This will generate the ''.desktop'' file to be used by XDG-compliant desktops. The entry will appear under "Current Desktop Entries".

To add an application menu entry, select an "Executable", input an "Entry Label", and click the "+Add Menu Entry" button. The generated ''.desktop'' file will appear under "Current Menu Entries".

==== External-Links ====

This tab, shown in Figure 8.1h, is used to customize how the specified binary starts.

'''Figure 8.1h: Configuring Custom Links for the PBI'''

[[Image:Easypbi7a.png]]

To customize how a binary starts, highlight it and click the "Action" drop-down menu. The possible actions are:

* '''binary:''' indicates that this is an executable. EasyPBI will automatically create the necessary wrapper and PATH links for you.

* '''linux:''' indicates that this is a Linux executable. EasyPBI will automatically create the necessary Linux wrapper and PATH links for you.

* '''keep:''' instructs the PBI to ''' ''not'' ''' overwrite an existing binary when linking a file into the LOCALBASE. By default, LOCALBASE is set to ''/usr/local''.

* '''replace:''' instructs the PBI to overwrite an existing binary when linking a file into the LOCALBASE.

* '''nocrash:''' disables the crashhandler GUI from running on this PBI. Note that the glue for the crash handler is not built into the base system yet.

If you select an "Action", use the up arrow to add it. If you change your mind, click the "Clear Changes" button.

=== Submit the Module ===

Once you are satisfied with the PBI, go to the "Module Editor" tab and use the "Select Module" button to select the PBI's module. Then click the "Package Module" button. A pop-up window will indicate that the module has been compressed and that a ''.tar.gz'' file has been added to the PBI module directory. The file name for our example PBI is ''~dru/EasyPBI/Modules/trickle.tar.gz''.

If you send that file to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=pbi-dev mailing list}}, it will be added to the PC-BSD® build servers so that the 32- and 64-bit versions of the PBI can be built. Once the built PBIs are tested, they will be added to AppCafe® so that other PC-BSD® users can benefit from the PBI.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Control Panel]]
[[category:EasyPBI]]
[[category:webpage referred]]
</noinclude>

Bluetooth Manager

2012-12-19T06:50:29Z

Vater:

<noinclude>{{NavHeader|back=User Manager|forward=Mount Tray}}</noinclude>

PC-BSD® 9.1 introduces a Bluetooth Manager which can be used to configure Bluetooth device pairing (authentication) and provides a graphical front-end to support FreeBSD's {{citelink|url=http://www.freebsd.org/cgi/man.cgi?query=hcsecd|txt=hcsecd(8)}} daemon which controls the link keys and PIN codes which are used by Bluetooth pairing. FreeBSD supports all Bluetooth USB dongle devices that conform with Bluetooth specification v1.1. More information about FreeBSD's Bluetooth implementation can be found in the {{citelink|fbsdh|url=network-bluetooth.html|txt=Bluetooth section of the FreeBSD Handbook}}.

To launch Bluetooth Manager, either click its icon in Control Panel or type '''pc-su pc-bluetoothmanager.''' You will be prompted for the administrative password. If you plug in in a Bluetooth USB dongle device and click on the "New Devices" tab, it should be displayed as it appears in Figure 8.9a. If the device is not found, a message in the lower half of the screen will prompt you to put the device in discovery mode and then to rescan by clicking the "Scan" button.

'''Figure 8.9a: New Device Detected in Bluetooth Manager'''

[[File:Bluetooth.png]]

If the device, such as a cell phone, requires a PIN key in order to access a service, use the "Saved Devices" tab to view and modify the pairing configuration. In the example shown in Figure 8.9b, the first three entries (Default, Dummy, and Dummy) are three FreeBSD sample entries and the fourth entry is for the inserted device. The sample entries are included as they provide examples of valid link keys and PIN codes. You can remove any entry by highlighting it and clicking the "Remove Device" button.

'''Figure 8.9b: Configure Bluetooth Pairing'''

[[File:Bluetooth1.png]]

To modify an existing configuration, highlight the device and click the "Configure" button. In the screen shown in Figure 8.9c, input the PIN code required by the provider. The system will automatically generate the link key for you.

'''Figure 8.9c: Input the PIN Code'''

[[File:Bluetooth2.png]]

If you wish to add the Bluetooth Manager to the system tray, type '''pc-su pc-bluetoothtray''' and input the administrative password. The Bluetooth tray icon will only automatically appear in the system tray if the USB dongle is plugged in when you log into the system.

Since the developers do not have access to every possible Bluetooth device, it is possible that your device will not be recognized. If this is the case, please take the time to send the details about the device to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/testing|txt=testing mailing list}} so that the developers can work with you to fix the issue.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Common Tasks]] 
[[category:Bluetooth Manager]]
</noinclude>

Bluetooth Testing

2012-12-19T06:49:14Z

Vater:

{{NavHome}}

PC-BSD 9.1 will include a new GUI for managing bluetooth devices.

== Testing via v9.0 ==

If you would like to assist in testing this GUI, you can compile and install the code on your PC-BSD 9.0 system as follows:

First, make sure that these two development packages are showing as installed in ''[[Control Panel]]'' ➜ [[System Manager#Install/Uninstall Desktops and System_Components | ''System Manager'' ➜ ''System Packages'']] ➜ ''Development'':

* Development-VCS

* Development-Qt

As superuser, download the source and compile the Bluetooth Manager and Tray applications:

{{cli|xterm=
svn co <nowiki>svn://</nowiki>svn.pcbsd.org/pcbsd/current/src-qt4/ 
cd src-qt4/libpcbsd 
qmake-qt4 *.pro 
make && make install 
cd ../pc-bluetoothmanager 
qmake-qt4 *.pro 
make && make install 
cd ../pc-bluetoothtray 
qmake-qt4 *.pro 
make && make install 
}}

When finished, leave the superuser account and start the Bluetooth Manager:
{{cli|xterm=
pc-su pc-bluetoothmanager
|(will prompt for superuser password)
|width=58%
}}

Alternately, place the Bluetooth Manager in the system tray:
{{cli|xterm=
pc-su pc-bluetoothtray
|(will prompt for superuser password)
|width=58%
}}

Note that the Bluetooth Tray currently activates on right-click, but nothing activates on left-click as of yet.

If you try it out, let us know if you encounter any errors or need additional functionality. Feedback can be sent to the [http://lists.pcbsd.org/mailman/listinfo/testing testing mailing list]. The table below will assist those seeking to discover if their device will work.

== What currently works ==

'''Table: Bluetooth devices tested. How well does your bluetooth device work?'''

{{Tbl-init|width=100%}} 
{{Tbl-title|width=10%|'''Type'''}}
{{Tbl-title|width=23%|'''Name'''}}
{{Tbl-title|width=7%|'''Brand'''}}
{{Tbl-title|width=7%|'''Model'''}}
{{Tbl-title|width=53%|'''Comments'''}}
|-
{{tbl-cell|row=1|}}
{{tbl-cell|row=1|}}
{{tbl-cell|row=1|}}
{{tbl-cell|row=1|}}
{{tbl-cell|row=1|}}
|}

[[category:Bluetooth]]

Enlightenment

2012-12-19T06:46:46Z

Vater:

<noinclude>{{NavHeader|back=Awesome|forward=evilwm}}</noinclude>

{{citelink|url=http://www.enlightenment.org|txt=Enlightenment}} 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.

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.1. The icon on the far left of the iBar has been clicked in order to access the applications menu.

'''Figure 6.6a: Enlightenment Running on PC-BSD®'''

[[File:Enlightenment1.png]]

Enlightenment is very customizable. The {{citelink|url=http://trac.enlightenment.org/e/wiki/User_Guide e17|txt=User Guide}} describes how to configure windows, shelves, menus, wallpaper, and much more.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:desktops]]
[[category:enlightenment]]
</noinclude>

Awesome

2012-12-19T06:46:30Z

Vater:

<noinclude>{{NavHeader|back=XFCE4|forward=Enlightenment}}</noinclude>

{{citelink|url=http://awesome.naquadah.org/|txt=Awesome}} is a highly configurable and fast window manager that is primarily targeted at power users who prefer to use the command line within their graphical environment.

Figure 6.5a shows a screenshot of Awesome running on PC-BSD® 9.1. The user has right-clicked the desktop in order to launch the awesome application manager.

'''Figure 6.5a: Awesome Window Manager on PC-BSD®'''

[[File:Awesome2.png]]

If you click ''awesome'' ➜ ''manual'', the man page for awesome will open in a terminal. If you click ''awesome'' ➜ ''edit config'', the awesome configuration file will open in the '''ee''' text editor. The numbers in the upper left corner represent virtual desktops. For example, you can have different terminals open in each virtual desktop.

Bluetooth Manager (if the system has a Bluetooth interface), Update Manager, Wireless Configuration Manager (if your wireless card is detected), and Life Preserver are located in the system tray near the clock in the upper right corner. If you wish to access Control Panel type '''pc-controlpanel''' in a terminal. To launch AppCafe®, type '''appcafe''' in a terminal or use the [[PBI Manager#Command Reference|'''pbi_*''' commands]] to manage software from the command line.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:desktops]]
[[category:Awesome]]
</noinclude>

GNOME2

2012-12-19T06:46:04Z

Vater:

<noinclude>{{NavHeader|back=Desktops|forward=KDE4}}</noinclude>

{{citelink|url=http://library.gnome.org/misc/release-notes/2.32/|txt=GNOME2}} is a popular desktop environment that provides many built-in utilities.

'''NOTE:''' GNOME3 has not yet been ported to FreeBSD. Once it has, it may be added as a desktop component in the PC-BSD® installer.

Figure 6.1a shows a screenshot of GNOME2 on a PC-BSD® 9.1 system with the "Applications" menu open:

'''Figure 6.1a: GNOME2 on PC-BSD®'''

[[File:GNOME2-2.png]]

Each category in the "Applications" menu contains many applications and the "Settings" and "System" categories contain many utilities for configuring your system. If you are new to GNOME2, take some time to discover which applications best suit your needs. Some of the applications which are provided by GNOME include:

* '''{{citelink|url=http://projects.gnome.org/eog/|txt=Eye of GNOME}}:''' image viewer found in ''Graphics'' ➜ ''Image Viewer''.

* '''{{citelink|url=http://projects.gnome.org/epiphany/|txt=Epiphany}}:''' web browser found in ''Internet'' ➜ ''Epiphany Web Browser''.

* '''{{citelink|url=http://projects.gnome.org/brasero/|txt=Brasero}}:''' CD/DVD burning software found in ''Multimedia'' ➜ ''Brasero Disk Burner''.

* '''{{citelink|url=http://projects.gnome.org/totem/|txt=Totem}}:''' movie player found in ''Multimedia'' ➜ ''Movie Player''.

* '''{{citelink|url=http://projects.gnome.org/evolution/|txt=Evolution}}:''' email client with address book and calendar. Found in ''Office'' ➜ ''Evolution Mail and Calendar''.

* '''{{citelink|url=http://live.gnome.org/Nautilus|txt=Nautilus}}:''' file manager found in ''Utilities'' ➜ ''File Browser''.

'''NOTE:''' some games, such as Gnibbels, Lights Off, Quadrapassel, and Swell Foop, require 3D acceleration. If your video driver does not support this, you will not be able to launch those games.

You may or may not have installed all of GNOME's components during installation. You can view the installed components and check (to add) or uncheck (to delete) various components using ''[[Control Panel]]'' ➜ ''[[System Manager#Install/Uninstall Desktops and System Components | ''System Manager'' ➜ ''System Packages'']] ➜ ''[[Desktops]]'' ➜ ''[[GNOME2|GNOME]].

You can find additional themes and wallpapers at {{citelink|url=http://gnome-look.org/|txt=gnome-look.org}}.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:desktops]]
[[category:GNOME2]]
</noinclude>

What's New in 9.1

2012-12-19T06:45:53Z

Vater:

<noinclude>{{NavHeader|back=Goals and Features|forward=PC-BSD® Releases}}</noinclude>
The following features have been added to or improved for PC-BSD® 9.1:

* Based on FreeBSD 9.1, which includes improved Intel video support. The {{Citelink|url=http://www.freebsd.org/releases/9.1R/relnotes.html|txt=Release Notes for FreeBSD 9.1}} list the new features and drivers introduced in FreeBSD 9.1.

* The PC-BSD® installer has been revamped to separate pre-installation tasks from post-installation tasks. This makes it easier to automate the roll-out of multiple installations because the end-user can configure their account information and display settings before logging in for the first time.

* The PC-BSD® installer now sets its default settings according to the hardware installed. 64-bit systems containing over 2GB of RAM will default to the ZFS filesystem whereas 32-bit systems and any system containing less than 2GB of RAM will default to UFS+SUJ. Systems containing more than 2GB of RAM will default to the KDE desktop and all other systems will default to the LXDE desktop. A hardware compatibility icon within the installer allows the user to see at a glance if their video card, Ethernet card, wireless card, and sound card are compatible with PC-BSD®.

* The PC-BSD® installer now provides a [[Install a Server | wizard to install either a vanilla FreeBSD server or a TrueOS server]]. In addition to the base FreeBSD system provided by a vanilla FreeBSD server installation, the TrueOS server edition adds the command line versions of [[PBI Manager]], [[Update Manager]], and [[Warden®]].

* The ability to perform a network install has been removed from the graphical installer. The [[Creating an Automated Installation with pc-sysinstall | scriptable back-end]] still provides the variables needed for network installations.

* The ZFS section of the PC-BSD® installer now allows you to set ZFS properties such as compression and quotas, create datasets, and import existing ZFS pools.

* [[Multiple Boot Environments]] support allows systems formatted with ZFS to create alternate bootable snapshots. These can be used for testing purposes or to create a bootable backup of the boot environment before performing an upgrade.

* [[Warden®]] is now built into the operating system and available through Control Panel. It can now be used to manage multiple jails.

* Warden® now supports the creation of three types of jails: traditional FreeBSD jails for running network services, (a less secure) ports jail for safely installing and running FreeBSD ports/packages from your PC-BSD® system, and the installation of Linux within a jail.

* Warden® now supports the management of ZFS snapshots on a per-jail basis.

* [[Update Manager]] has been integrated into Warden®. Combined with the meta-package support, it is now easier than ever to install software into a jail and to keep that software up-to-date.

* [[Using AppCafe® | AppCafe®]] now shows the number of available PBIs and supports automatic updating.

* [[EasyPBI]] is now available through Control Panel, making it easier than ever to convert existing FreeBSD ports to PC-BSD® PBIs.

* An [[About]] icon has been added to the Control Panel, making it easy to determine the PC-BSD® version, which desktops, and the version of X that have been installed.

* An [[Active Directory & LDAP]] GUI has been added to Control Panel, allowing you to set the client information for connecting to Active Directory servers.

* A [[Hardware Compatibility]] icon has been added to the control panel, providing a quick overview of detected hardware devices.

* The [[GDM Configuration]] GUI has been added to Control Panel and can be used to configure auto-login and remote login through XDMCP.

* A [[Mount Tray]] icon has been added to the Control Panel and System Tray, allowing easy access to USB drives.

* A [[Sound Configuration]] icon has been added to the Control Panel and can be used to test sound or change the default audio device.

* [[Network Configuration]] manager now supports 802.1x authentication over Ethernet networks.

* [[Life Preserver]] now provides a browse button when creating an include or exclude filter.

* [[Thin Client]] now allows you to create a PXE Boot Desktop Server or a PXE Boot Installation Server.

* [[Bluetooth Manager]] has been added to the System Tray.

* [[PC-BSD® Live Mode]] is now a USB-only, read/write image.

* When ZFS formatting during installation, {{Citelink|url=http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html|txt=gnop 4K alignment}} is now used when creating the zpool. This results in a dramatic increase in performance. For this reason, it is recommended that users with existing ZFS installations re-install rather than upgrade in order to receive these performance benefits.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Introduction]]
[[category:What's New]]
</noinclude>

Thin Client

2012-12-19T06:44:37Z

Vater:

<noinclude>{{NavHeader|back=Remote Desktop|forward=ownCloud}}</noinclude>

The '''pc-thinclient''' script has been improved for PC-BSD® 9.1 by adding the following features:

* the ability to create an installation server. Now when you first initialize the '''pc-thinclient''' script, you will be asked if you want to setup a PXE Boot Desktop Server or a PXE Boot Install Server.

* when configuring a PXE Boot Install Server, all the necessary bits for PXE booting are taken care of, allowing you to prepare for PXE installs within minutes.

* the ability to create unattended installation scripts for the PXE Boot Install Server.

This section demonstrates how to configure and use both the PXE Boot Desktop Server and the PXE Boot Install Server.

=== Creating a PXE Boot Desktop Server ===

A PC-BSD® PXE Boot Desktop Server allows you to automatically configure a network of {{citelink|wp|url=Diskless_node|txt=diskless computers}} where each computer has a network interface card capable of {{citelink|wp|url=Preboot_Execution_Environment|txt=PXE}} booting. When a client boots from their network interface instead of their hard disk, they automatically connect to the PXE Boot Desktop Server and receive a login window. Once authenticated, they can use PC-BSD®, even if PC-BSD® is not installed on their own computer and even if their computer does not have a hard drive.

To prepare your PC-BSD® system for a PXE Boot Desktop Server configuration, perform these tasks first:
# If the diskless clients will require Internet access, install two network cards where one NIC is connected to the Internet and the other is connected to a private LAN from which the thin clients can PXE boot from. 
# The PC-BSD® system should have lots of RAM installed, especially if multiple clients will be connecting. It is recommended that you use a 64-bit system with as much RAM installed as possible. 
# If the ''/usr/ports/'' directory is empty or does not exist, install the ports collection using the "Fetch Ports Tree" button in the [[System Manager#Install FreeBSD Source and Ports|Tasks tab of System Manager]] or by typing '''portsnap fetch extract.''' 
# Set aside a few hours as the system will need to rebuild its world and the applications it needs in order to support the PXE environment. The script will automatically build a 32-bit environment (even on a 64-bit system) as most PXE boot clients are 32-bit.

To configure the PC-BSD® system as a PXE Boot Desktop Server, run the following script as the superuser:

'''pc-thinclient'''
/usr/local/bin/pc-thinclient will install the components to convert this system into a thin-client server.
Continue? (Y/N) '''y'''
Do you wish to make this a remote X desktop server or install server?
(r/i) '''r'''

If your intent is to install a PXE Boot Desktop Server, input '''r''' and press enter. If the DHCP server is not already installed, you will receive a configuration menu for compiling the DHCP port. You can press enter to accept the defaults. Once the DHCP server is installed, the tools needed in the PXE environment will be installed:

Fetching FreeBSD environment... This may take a while...
Extracting PC-BSD environment... This may take a while...
Copying /usr/ports -> /usr/home/thinclient/usr/ports
<snip very long output>
Setting up system for PXE booting...
What NIC do you wish DHCPD to listen on? (I.E. re0)
nic) '''em0'''

Input the FreeBSD device name of the interface that is attached to the local network containing the diskless workstations. This interface will run the DHCP server and should not be connected to a
network with another DHCP server running. In the example shown here, the user has input the ''em0'' interface. If you are unsure of the device name, type '''ifconfig''' from another terminal.

The script will now configure the specified interface and start the required services:

Starting /etc/rc.d/nfsd...OK
Starting /etc/rc.d/inetd...OK
Starting /usr/local/etc/rc.d/isc-dhcpd...OK

You will now need to enable remote desktop.
This can be done via the PC-BSD Control Panel -> GDM Configuration
or by manually editing /usr/local/etc/gdm/custom.conf

Your system is now setup to do PXE booting!

Go to ''[[Control Panel]]'' ➜ ''[[GDM Configuration]]'' and check the box ''Enable XDMCP''. If you forget this step, clients will not be able to receive an X session when they connect.

The installation creates a chroot directory that contains a small PXE image that is used by clients to launch Xorg and connect to the PXE Boot Desktop Server. You can access this chroot by typing this command as the superuser:

'''chroot /usr/home/thinclient'''

Running '''pkg_info''' within the chroot will show which X components and drivers are available. Should you need to install additional video drivers, use '''pkg_add''' within the chroot. When you are finished using the chroot, type '''exit''' to leave it.

The thin client script installs and configures the following services:

'''NFS:''' the Network File System is a protocol for sharing files on a network. It has been configured to allow clients on the network attached to the interface that you specified to connect to the thin client server. Its configuration file is located in ''/etc/exports''.

'''TFTP:''' the Trivial File Transfer Protocol is a light-weight version of FTP used to transfer configuration or boot files between machines. The PXE network cards on the diskless computers will use TFTP to receive their configuration information. This service was enabled in ''/etc/inetd.conf'' with a home directory of ''/home/thinclient''.

'''DHCP:''' the Dynamic Host Configuration Protocol is used to configure IP addressing info on the diskless workstations. It has been configured to assign addresses for the network attached to the interface that you specified. Its configuration file is located in ''/usr/local/etc/dhcpd.conf''.

The thin client script also creates the ''pxeboot'' user with the default password ''thinclient''. This username and password is used to save the working Xorg configuration files for each of the diskless computers. It is highly recommended that you change this password right away by running this command as the superuser:

'''passwd pxeboot'''

You will also need to create the users that will connect to the system. You can do so using [[User Manager]] or by typing '''adduser''' at the command line and following the prompts.

==== Connecting to the PXE Boot Desktop Server ====

After a successful installation and reboot of the PXE Boot Desktop Server, the DHCP service will be running on the NIC you specified. Make sure that this NIC and a PXE capable client are connected to the same hub or switch. When you boot up the client, PXE should automatically obtain an IP address and begin to load PC-BSD®. If it does not, review the boot order settings in the BIOS on the client to make sure that PXE is listed first.

After the boot process has finished, the client will be brought to this prompt:

No saved xorg-config for this MAC: <MAC_Address>
Do you wish to setup a custom xorg.conf for this system? (Y/N)

If you wait 10 seconds, this message will timeout, and the client will bring up X in 1024x768 mode. If this is not the resolution that you wish to use, type "Y" at the prompt and hit enter to bring up the Xorg Configuration screen. In this menu, you will be able to setup your own custom ''xorg.conf'' file, auto-detect settings, and test the new configuration. When finished, choose "Save working config" to send this configuration to the PXE Boot Desktop Server. This will prompt for the password of the pxeboot user. Once authenticated, the file will be saved by the client's MAC address in ''/home/pxeboot/mnt/xorg-config/<mac>.conf''. The next time you boot the client, it will automatically use the saved ''xorg.conf'' file and bring the system to the PC-BSD® login screen.

'''NOTE:''' in order for the login to succeed, the user account must already exist on the PXE Boot Desktop Server.

The client's boot environment is located in ''/home/pxeboot''. This is mounted read-only during the PXE boot process to allow the client to bootup and create an XDCMP connection to the server.

Once logged in to the PXE Boot Desktop Server, using PC-BSD® will be the same as if you had installed PC-BSD® on the client system. You will be able to use [[Using AppCafe®|AppCafe®]] to install software and to save and use the files in your home directory.

==== Uninstalling the PXE Boot Desktop Server ====

Use the '''-remove''' option if you wish to uninstall the PXE Boot Desktop Server:

'''pc-thinclient -remove'''
Removing /usr/home/thinclient

This will remove the PXE environment from the system. If you are finished using the PXE boot services, you can stop them using these commands:

'''service nfsd stop'''
'''service inetd stop'''
'''service isc-dhcpd stop'''

and prevent them from restarting by removing these lines from ''/etc/rc.conf:''

# pc-thinclient configuration
dhcpd_enable="YES"
dhcpd_ifaces="em0"
portmap_enable="YES"
nfs_server_enable="YES"
inetd_enable="YES"
ifconfig_em0="192.168.2.2"

Your interface name and IP address may differ from those in the example.

=== Creating a PXE Boot Install Server ===

A PC-BSD® PXE Boot Desktop Server can be used to install PC-BSD®, FreeBSD, or TrueOS™ onto computers who connect to the server using PXE. The installations can be interactive or fully automated. The PXE Boot Desktop Server supports multiple, concurrent installations with the only limiting factor being the server's disk I/O and the network's bandwidth.

The installation of the PXE Boot Install Server starts the same way, except this time you select '''i''' when prompted:
'''pc-thinclient'''
/usr/local/bin/pc-thinclient will install the components to convert this system into a thin-client server.
Continue? (Y/N) '''y'''
Do you wish to make this a remote X desktop server or install server?
(r/i) '''i'''

Fetching FreeBSD environment... This may take a while...
Extracting PC-BSD environment... This may take a while...
Setting up system for PXE booting...
What NIC do you wish DHCPD to listen on? (I.E. re0)
nic) '''em0'''
Starting /etc/rc.d/nfsd...OK
Starting /etc/rc.d/inetd...OK
Starting /usr/local/etc/rc.d/isc-dhcpd...OK

To perform system installations, place your custom pc-sysinstall scripts in:
/usr/home/thinclient/installscripts
An example script is provided in the above directory
For unattended installations, save your pc-sysinstall script as:
/usr/home/thinclient/installscripts/unattended.cfg
Your system is now setup to do PXE booting!

==== Connecting to and Customizing the PXE Boot Install Server ====

Once the PXE Boot Install Server is installed, try to PXE boot a client which is connected to the same network. If the client boots successfully, you will see the installation screen shown in Figure 9.8a.

'''Figure 9.8a: PXE Boot Installation Menu'''

[[File:Pxe.png]]

By default, selecting “install” from the boot menu will use the ''/usr/home/thinclient/installscripts/pc-sysinstall.example'' script which installs a basic FreeBSD system. In addition to starting an installation, this menu provides an emergency shell prompt. This can be useful if you have a system which can no longer boot and you wish to either access the disk's contents or attempt to repair the installation.

Any scripts that you create and place in the ''/usr/home/thinclient/installscripts/'' directory will be selectable as an installation option within the PXE client boot menu. Tables 5.4a and 5.4b in [[Creating an Automated Installation with pc-sysinstall]] summarize the available configuration options when creating an installation script. Alternately, every time you install PC-BSD, the installation script is automatically saved to ''/root/pc-sysinstall.cfg''. This means that if you wish to repeat an installation, you simply need to copy that file to the ''/usr/home/thinclient/installscripts/'' directory on the PXE Boot Install Server.

The PXE Boot Install Server also supports completely unattended installations. To perform fully-automated installations over the PXE interface, create a configuration script named ''/usr/home/thinclient/installscripts/unattended.cfg''. When a PXE client first boots, it checks for the existence of the ''unattended.cfg'' file, and if found, it will automatically use it for installation. Some caution should be taken when using this method since simply plugging a PXE boot client into the wrong LAN cable could cause it to be re-installed.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:Control Panel]]
[[category:Thin Client]]
</noinclude>

XFCE4

2012-12-19T06:44:02Z

Vater:

<noinclude>{{NavHeader|back=LXDE|forward=Awesome}}</noinclude>

{{citelink|url=http://www.xfce.org/|txt=Xfce}} is a lightweight desktop environment that aims to be low on system resources and fast, while still being visually appealing and user friendly.

The first time you start XFCE4, you will see the message shown in Figure 6.4a:

'''Figure 6.4a: Panel Welcome Message'''

[[File:welcomepanel.png]]

In XFCE, a {{citelink|url=http://www.xfce.org/projects/xfce4-panel|txt=panel}} is a bar which can hold many items such as application launchers, window lists, a clock, a notification area, and application menus. Your initial panel setup options are:

* '''Migrate old config:''' select this option if you wish to have a single panel with an application launcher and other icons as shown in Figure 6.4b. The application launcher menu may be reached from the upper left, or by right-clicking on the desktop.

* '''Use default config:''' this option will install a large panel across the top and a small, minimal panel centered on the bottom. The application launcher menu may be accessed by the fireball icon in the lower left, or by a right-click on the desktop.

* '''One empty panel:''' this option will install a panel with no icons. The application menu is available by right-clicking the desktop as shown in Figures 6.4b and 6.4c.

Figure 6.4b shows a screenshot of XFCE4 running on a PC-BSD® 9.1 with the application menu open:

'''Figure 6.4b: XFCE with Complete Panel Migrated From Old Config'''

[[File:XFCE4-2.png]]

'''Figure 6.4c: XFCE with Minimal Panel Using Default Config'''

[[File:XFCE4.png]]

If you wish to change your configuration choice at a later time, reset the panel using ''Applications'' ➜ ''Settings'' ➜ ''Settings Editor'', as shown in Figure 6.4d, then exit to the login prompt without saving session info. The next login to XFCE will present the panel configuration choice again.

'''Figure 6.4d: Using Settings Editor to Reset Panel

[[File:settingsEd.png]]

In addition to the PC-BSD® utilities, XFCE provides the following utilities:

* '''{{citelink|url=http://www.xfce.org/projects/xfdesktop|txt=Xdesktop}}:''' desktop manager found in ''Settings'' ➜ ''Desktop''. Sets the background image, provides a right-click menu to launch applications, and can show files (including application launchers) or iconified windows.

* '''{{citelink|url=http://www.xfce.org/projects/xfwm4|txt=Xfwm4}}:''' window manager found in ''Settings'' ➜ ''Window Manager''. It provides window decorations, virtual desktops, multiscreen mode, transparency and a keyboard shortcuts editor.

* '''{{citelink|url=http://goodies.xfce.org/projects/applications/ristretto|txt=Ristretto}}:''' fast and light-weight picture viewer found in ''Graphics'' ➜ ''Ristretto Photo Viewer''.

* '''{{citelink|url=http://www.twotoasts.de/index.php?/pages/midori_summary.html|txt=Midori}}:''' light-weight graphical browser found in ''Internet'' ➜ ''Midori''.

* '''{{citelink|url=http://goodies.xfce.org/projects/applications/xfburn|txt=Xfburn}}:''' CD/DVD burning tool found in ''Multimedia'' ➜ ''Xfburn''.

* '''{{citelink|url=http://www.kolumbus.fi/~w408237/orage/|txt=Orage}}:''' calendar and reminder daemon found in ''Office'' ➜ ''Orage Calendar''.

* '''{{citelink|url=http://www.xfce.org/projects/thunar|txt=Thunar}}:''' file manager found in ''System'' ➜ ''Thunar File Manager''.

* '''{{citelink|url=http://goodies.xfce.org/projects/applications/xfce4-taskmanager|txt=Task Manager}}:''' graphical task manager found in ''System'' ➜ ''Task Manager''.

A list of recommended applications for XFCE can be found on the {{citelink|url=http://wiki.xfce.org/recommendedapps|txt=XFCE Wiki}}.

=== Editing the Menu ===

XFCE no longer includes a graphical menu editor. The XFCE team recommends using alacarte which is included when you install XFCE4 on PC-BSD® and which can be started by typing '''alacarte''' within an xterm.

Figure 6.4e shows a screenshot of alacarte running on PC-BSD®.

'''Figure 6.4e: Using alacarte to Customize Applications Menu'''

[[File:alacarte.png]]

Any entry with a checkbox will appear in your menu. To remove an item from the menu, simply uncheck its box. To create a new menu category, either highlight a top-level menu (e.g. KDE Menu or System) or an existing category and click the "New Menu" button. To add a new entry, highlight the category where you wish the entry to appear and click the "New Item" button. Input a name for the entry, browse to the path of the application and press "OK".

=== XFCE Plugins ===

XFCE supports many plugins which provide additional applications that are separate from the official XFCE distribution. You can browse for plugins and read descriptions for each at the XFCE {{citelink|url=http://goodies.xfce.org/projects/start|txt=goodies website}}. If you find a plugin that is not available within AppCafe®, this {{citelink|url=http://forums.pcbsd.org/showthread.php?t=13642|txt=README}} explains how to determine if a FreeBSD port is available, how to request a PBI if a port is available, and how to request a port if one does not already exist.

After installing a plugin, go to ''Settings'' ➜ ''Panel'' ➜ ''Items'' and click the ''+'' button to see the "Add New Items" screen shown in Figure 6.4f.

'''Figure 6.4f: Adding a Plugin to the Panel'''

[[File:addtopanel-2.png]]

Simply select your new plugin from the list, and click the "+Add" button. It will immediately be added as an icon in the panel.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:desktops]]
[[category:XFCE4]]
</noinclude>

Preface

2012-12-19T06:43:45Z

Vater:

<noinclude>{{NavHeaderFirst|forward=Introduction}}</noinclude>

; PC-BSD® Users Handbook

written by users of the [http://www.pcbsd.org PC-BSD® operating system].

Version 9.1

Published {{#dateformat:30 Nov 2012}}

Copyright © 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, The PC-BSD® Project.

Welcome to PC-BSD®! This Handbook covers the installation and use of PC-BSD® 9.1. This Handbook is a work in progress and relies on the contributions of many individuals. If you are interested in assisting with the Handbook, visit {{http}}wiki.pcbsd.org and create a login account for yourself. If you use IRC Freenode, you are welcome to join the #pcbsd channel where you will find other PC-BSD® users.

Previous versions of the Handbook in various formats and languages are available from [ftp://ftp.pcbsd.org/pub/handbook/ ftp://ftp.pcbsd.org/pub/handbook/]. Errata may be found at [[Errata|{{http}}wiki.pcbsd.org/index.php/Errata]]. 
The PC-BSD® Users Handbook is freely available for sharing and redistribution under the terms of the {{citelink|url=https://creativecommons.org/licenses/by/3.0/|txt=Creative Commons Attribution License}}. This means that you have permission to copy, distribute, translate, and adapt the work as long as you attribute the PC-BSD® Project as the original source of the Handbook.

PC-BSD® and the PC-BSD® logo are registered trademarks of {{citelink|url=https://www.ixsystems.com/|txt=iXsystems}}. If you wish to use the PC-BSD® logo in your own works, ask for permission first from ''marketing'' at ''ixsystems'' dot ''com''.

; Trademarks

AMD is a trademark of Advanced Micro Devices, Inc.

Apache is a trademark of The Apache Software Foundation.

AppCafe® is a registered trademark of iXsystems.

Asus® and Eee PC® are registered trademarks of ASUSTeK® Computer Inc.

Facebook® is a registered trademark of Facebook Inc.

Flash® is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries.

FreeBSD® is a registered trademark of the {{citelink|url=http://www.freebsdfoundation.org|txt=FreeBSD Foundation}}.

FreeNAS® is a registered trademark of iXsystems.

IBM® is a registered trademark of International Business Machines Corporation.

Intel, the Intel logo, Pentium Inside, and Pentium are trademarks of Intel Corporation in the U.S. and/or other countries.

Java™ is a trademark of Oracle America and/or its affiliates in the United States and other countries.

Lenovo® is a registered trademark of Lenovo.

LinkedIn® is a registered trademark of LinkedIn Corporation.

Linux® is a registered trademark of Linus Torvalds.

Mac and Mac OS are trademarks of Apple Inc., registered in the U.S. and other countries.

MacBook® is a registered trademark of Apple Inc.

MySQL is a trademark of Oracle.

NVIDIA® is a trademark and/or registered trademark of NVIDIA Corporation in the U.S. and other countries.

PostgreSQL® is a registered trademark of the PostgreSQL Global Development Group.

ThinkPad® is a registered trademark of Lenovo.

TrueOS™ is a trademark of iXsystems.

Twitter is a trademark of Twitter, Inc. in the United States and other countries.

UNIX® is a registered trademark of The Open Group.

VirtualBox® is a registered trademark of Oracle.

VMWare® is a registered trademark of VMWare, Inc.

Warden® is a registered trademark of iXsystems.

Windows® is a registered trademark of Microsoft Corporation in the United States and other countries.

; Typographic Conventions

The PC-BSD® 9.1 Handbook uses the following typographic conventions:

'''bold text:''' represents a command written at the command line. In usage examples, the font is changed to Courier 10 with any command output displayed in unbolded text.

''italic text:'' used to represent device names or file name paths.

''' ''bold italic text:'' ''' used to emphasize an important point.

<noinclude>{{refheading}}</noinclude>
<noinclude>
[[category:handbook]]
[[category:preface]]
</noinclude>

PC-BSD® Live Mode

2012-12-19T06:43:14Z

Vater:

<noinclude>{{NavHeader|back=Burning the Installation Media|forward=Using VirtualBox|custompagename=PC-BSD{{r}} Live Mode|custompagecategory={{PAGENAME}}}}</noinclude>

Beginning with PC-BSD® 9.1, Live Mode is a read-write live image that is only available for USB media. The uncompressed live image is about 4GB in size, but you will want to write it to a USB device that will provide sufficient room for the files that you wish to save and any applications that you wish to install.

'''NOTE:''' the speed of Live Mode is dependent upon the quality of the USB device. If you are purchasing a device, look for one that is advertised as "high speed".

To use PC-BSD® Live Mode, download the live USB version. Once you have [[Burning the Installation Media#Writing an IMG File to USB|written the image file to a USB media]], boot the system with the USB device inserted. Assuming your BIOS has been set to boot from that device, you should see some startup messages followed by the PC-BSD® graphical boot menu, shown in Figure 2.6a.

'''Figure 2.6a: PC-BSD® Graphical Boot Menu'''

[[File:Boot1.jpeg]]

The options in this menu are described in [[Booting Into PC-BSD®]]. If you press enter or wait 10 seconds, the system will continue to boot. If this is the first time you have booted into the image, the boot will pause with this message:

Trying to mount root from ufs:mdo []...
tput: no terminal type specified and no TERM environmental variable.
Do you want to expand the file-system for this LIVE media?
This process may take up to 15 minutes.
Resize? (y/n):

This step grows the filesystem so that it can use the entire capacity of the USB device. Press '''y''' to expand the filesystem and reboot into live mode:

Resizing file-system da0a on da0, this may take a few minutes...
Adjusting partition tables on da0...
Running growfs on da0a, this may take a while...
Cleaning up...
Rebooting...

You will know that you have successfully entered live mode when you are asked to accept the graphics resolution mode that is considered to be optimal for your hardware.

If this is your first boot, you will then proceed through the [[Post Installation Configuration and Installation Troubleshooting| post-installation configuration screens]], ending in the [[Logging In]] screen.

When logging in, use the user account and password that you were prompted to create. Three desktops are available: [[Fluxbox]], [[LXDE]], and [[Openbox]].

<noinclude>
[[category:handbook]]
[[category:Pre-Installation Tasks]]
[[category:PC-BSD® Live Mode]]
</noinclude>

PC-BSD® Users Handbook

2012-12-19T06:38:11Z

Vater:

{{swapTitle|custompagename=PC-BSD{{r}} Users Handbook|custompagecategory={{PAGENAME}}}}


This is the wiki area for the collaborative editing of the ''' ''upcoming edition (version 9.2)'' ''' of the PC-BSD® Users Handbook. If you are beta testing the upcoming 9.2 release or would like to assist in documenting this release, use this wiki version of the PC-BSD® 9.2 Handbook. Otherwise, you instead want to use the version of the PC-BSD® Users Handbook that matches your version of PC-BSD®.

<onlyinclude>Beginning with PC-BSD® version 8.2, a PDF of the Users Handbook matching the released version is included as an icon on the PC-BSD® desktop. In addition, the Users Handbook is published in various formats as listed below. Translations of the Handbook are added as they become available and any downloadable file name will indicate the language with a [http://reference.sitepoint.com/html/lang-codes 2-letter ISO code]. If you are interested in translating a released version of the documentation, send an email to the [http://lists.pcbsd.org/mailman/listinfo/translations PC-BSD® translations mailing list].

<blockquote style="border: 2px solid #666; padding: 10px; background-color: #ccc;">
<h2>Published Versions (in reverse chronological order):</h2>

'''PC-BSD® 9.1''' was released on {{#dateformat:30 Nov 2012}}. The 9.1 Users Handbook is available in the following formats:

* [ftp://ftp.pcbsd.org/pub/handbook/9.1/handbook_en_ver9.1.epub EPUB (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.1/handbook_en_ver9.1.html HTML (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.1/handbook_en_ver9.1.pdf PDF (English)]

'''PC-BSD® 9.0''' was released on {{#dateformat:13 Jan 2012}}. The 9.0 Users Handbook is available in the following formats:

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_en_ver9.0.epub EPUB (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_en_ver9.0.html HTML (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_en_ver9.0.pdf PDF (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_in_ver9.0.epub EPUB (Indonesian)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_in_ver9.0.html HTML (Indonesian)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_in_ver9.0.pdf PDF (Indonesian)]

* For those who prefer to purchase a copy of the Handbook for their Kindle, "PC-BSD® 9.0 Handbook (English Version)" is available from Amazon. The ASIN is B006W0EHN8 and this version is text-to-speech enabled.

* For those who prefer a "dead tree" version of the Handbook, the [http://www.freebsdmall.com/cgi-bin/fm/pcbsdhbk9.0?id=wrKa8VE5&mv_pc=95 book version] as well as a [http://www.freebsdmall.com/cgi-bin/fm/pcbsdhbk.bn?id=wrKa8VE5&mv_pc=51 book and DVD bundle] are available from FreeBSD Mall. The ISBN for the book is 1-57176-398-8.

'''PC-BSD® 8.2''' was released on {{#dateformat:24 Feb 2011}}. The 8.2 Users Handbook is available in the following formats:

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_en_ver8.2.epub EPUB (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_in_ver8.2.epub EPUB (Indonesian)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_en_ver8.2.html HTML (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_in_ver8.2.html HTML (Indonesian)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_en_ver8.2.odt ODT (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_in_ver8.2.odt ODT (Indonesian)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_en_ver8.2.pdf PDF (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_in_ver8.2.pdf PDF (Indonesian)]

* For those who prefer to purchase a copy of the Handbook for their Kindle, "PC-BSD® 8.2 Handbook (English Version)" is available from Amazon. The ASIN is B004SP6PXY and this version is text-to-speech enabled.

</blockquote>

{{:License}}</onlyinclude>

The Handbook grows into a useful resource when users (meaning you!) contribute to it. You do not have to write large sections of the Handbook in order to be a contributor. You also do not need to have a lot of time on your hands. You simply have to create a login account in order to assist with any of the following tasks:

* proofread existing pages and fix any typos, grammos, or unclearly worded sections.

* add to sections containing missing, outdated, or incomplete content.

* update any screenshots that are out of date.

* every page has a Discussion tab. You can use this if you would like to suggest further information that should appear in that section of the Handbook.

* create a new section for content that is not yet covered in the Handbook. If you are not sure where to do this, ask on a semi-related Discussion tab.

We are emailed whenever edits are made and will contact you for clarification if an edit is unclear. You can also be notified when specified pages are edited--simply click the "my preferences" or "my watchlist" links whenever you are logged into the wiki.

''<center>Copyright 2011, 2012, The PC-BSD® Project. PC-BSD® and the PC-BSD® logo are trademarks of [http://www.ixsystems.com iXsystems].</center>''
''<center>All other content within the PC-BSD® Users Handbook is freely available for sharing under the terms of the [http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution License].</center>''
 
Work in Progress: PC-BSD{{r}} 9.2 Users Handbook

''' ''If the information and screenshots on the wiki do not match what you are seeing on your PC-BSD® system, it means it has changed between your version and the upcoming 9.2 version. You should instead refer to the Users Handbook that came with your version of PC-BSD®.'' '''
 
= Table of Contents =
{{hierB|title=Preface}}
{{hierB|1.|title=Introduction}}
{{hier|1.1|title=Goals and Features}}
{{hier|1.2|title=What's New in 9.2}}
{{hier|1.3|title=PC-BSD® Releases}}
{{hier|1.4|title=PC-BSD® for Linux Users}}
{{hierB|2.|title=Pre-Installation Tasks}}
{{hier|2.1|title=Hardware Requirements}}
{{hier|2.2|title=Laptops}}
{{hier|2.3|title=Partitioning the Hard Drive}}
{{hier|2.4|title=Obtaining PC-BSD®}}
{{hier|2.5|title=Burning the Installation Media}}
{{hier|2.6|title=PC-BSD® Live Mode}}
{{hier|2.7|title=Using VirtualBox}}
{{hierB|3.|title=Installing PC-BSD®}}
{{hier|3.1|title=Starting the PC-BSD® Installation}}
{{hier|3.2|title=Language Selection Screen}}
{{hier|3.3|title=System Selection Screen}}
{{hier|3.4|title=Disk Selection Screen}}
{{hier|3.5|title=Installation Progress Screen}}
{{hier|3.6|title=Installation Finished Screen}}
{{hierB|4.|title=Post Installation Configuration and Installation Troubleshooting}}
{{hier|4.1|title=Booting Into PC-BSD®}}
{{hier|4.2|title=Language Screen}}
{{hier|4.3|title=Time Zone Selection Screen}}
{{hier|4.4|title=Set Root Password Screen}}
{{hier|4.5|title=Create a User Screen}}
{{hier|4.6|title=Connect to a Wireless Network}}
{{hier|4.7|title=Post Install Finished Screen}}
{{hier|4.8|title=Logging In}}
{{hier|4.9|title=Installation Troubleshooting}}
{{hierB|5.|title=Advanced Installation Topics}}
{{hier|5.1|title=Install a Server}}
{{hier|5.2|title=Dual Booting}}
{{hier|5.3|title=Multiple Boot Environments}}
{{hier|5.4|title=Upgrading PC-BSD®}}
{{hier|5.5|title=Creating an Automated Installation with pc-sysinstall}}
{{hierB|6.|title=Desktops}}
{{hier|6.1|title=GNOME2}}
{{hier|6.2|title=KDE4}}
{{hier|6.3|title=LXDE}}
{{hier|6.4|title=XFCE4}}
{{hier|6.5|title=Awesome}}
{{hier|6.6|title=Enlightenment}}
{{hier|6.7|title=evilwm}}
{{hier|6.8|title=Fluxbox}}
{{hier|6.9|title=FVWM}}
{{hier|6.10|title=i3}}
{{hier|6.11|title=IceWM}}
{{hier|6.12|title=Openbox}}
{{hier|6.13|title=Ratpoison}}
{{hier|6.14|title=spectrwm}}
{{hier|6.15|title=WindowLab}}
{{hier|6.16|title=Window Maker}}
{{hierB|7.|title=Installing Applications and Keeping PC-BSD® Updated}}
{{hier|7.1|title=Using AppCafe®}}
{{hier|7.2|title=PBI Manager}}
{{hier|7.3|title=Update Manager}}
{{hier|7.4|title=Meta Package Manager}}
{{hier|7.5|title=Create Your Own PBI Repository}}
{{hierB|8.|title=Control Panel}}
{{hier|8.1|title=EasyPBI}}
{{hier|8.2|title=About}}
{{hier|8.3|title=Active Directory & LDAP}}
{{hier|8.4|title=Hardware Compatibility}}
{{hier|8.5|title=GDM Configuration}}
{{hier|8.6|title=Service Manager}}
{{hier|8.7|title=System Manager}}
{{hier|8.8|title=User Manager}}
{{hier|8.9|title=Bluetooth Manager}}
{{hier|8.10|title=Mount Tray}}
{{hier|8.11|title=Sound Configuration}}
{{hier|8.12|title=Display}}
{{hier|8.13|title=Printing}}
{{hier|8.14|title=Scanner}}
{{hier|8.15|title=Network Configuration}}
{{hier|8.16|title=Firewall Manager}}
{{hier|8.17|title=Life Preserver}}
{{hier|8.18|title=Adobe Flash Player preferences}}
{{hier|8.19|title=Warden®}}
{{hierB|9.|title=Using PC-BSD®}}
{{hier|9.1|title=Java, Flash, and Fonts}}
{{hier|9.2|title=Multimedia}}
{{hier|9.3|title=Files and File Sharing}}
{{hier|9.4|title=MythTV}}
{{hier|9.5|title=XBMC}}
{{hier|9.6|title=Windows Emulation}}
{{hier|9.7|title=Remote Desktop}}
{{hier|9.8|title=Thin Client}}
{{hier|9.9|title=ownCloud}}
{{hier|9.10|title=Security}}
{{hier|9.11|title=Accessibility}}
{{hierB|10.|title=Finding Help}}
{{hier|10.1|title=PC-BSD® Forums}}
{{hier|10.2|title=IRC Channel}}
{{hier|10.3|title=Mailing Lists}}
{{hier|10.4|title=FreeBSD Handbook and FAQ}}
{{hier|10.5|title=Social Media}}
{{hier|10.6|title=Search and Portals}}
{{hier|10.7|title=Other Resources}}
{{hierB|11.|title=Supporting PC-BSD®}}
{{hier|11.1|title=Become a Beta Tester}}
{{hier|11.2|title=Become a Translator}}
{{hier|11.3|title=Become a Developer}}
{{hier|11.4|title=Report Bugs}}
{{hier|11.5|title=Submit PBI Requests}}
{{hier|11.6|title=Test PBIs}}
:[[PBI Module Builder Guide|11.7 Create PBIs]] 
{{hier|11.8|title=Purchase PC-BSD® Swag}}
{{hier|11.9|title=Host a Mirror}}
{{hier|11.10|title=Seed a Torrent}}
{{hier|11.11|title=Become an Advocate}}

<noinclude>
[[category:PC-BSD® Wiki]]
[[category:Handbook]]
</noinclude>

PC-BSD® Users Handbook

2012-12-19T06:35:28Z

Vater:

{{swapTitle|custompagename=PC-BSD{{r}} Users Handbook|custompagecategory={{PAGENAME}}}}


This is the wiki area for the collaborative editing of the ''' ''upcoming edition (version 9.2)'' ''' of the PC-BSD® Users Handbook. If you are beta testing the upcoming 9.2 release or would like to assist in documenting this release, use this wiki version of the PC-BSD® 9.2 Handbook. Otherwise, you instead want to use the version of the PC-BSD® Users Handbook that matches your version of PC-BSD®.

<onlyinclude>Beginning with PC-BSD® version 8.2, a PDF of the Users Handbook matching the released version is included as an icon on the PC-BSD® desktop. In addition, the Users Handbook is published in various formats as listed below. Translations of the Handbook are added as they become available and any downloadable file name will indicate the language with a [http://reference.sitepoint.com/html/lang-codes 2-letter ISO code]. If you are interested in translating a released version of the documentation, send an email to the [http://lists.pcbsd.org/mailman/listinfo/translations PC-BSD® translations mailing list].

<blockquote style="border: 2px solid #666; padding: 10px; background-color: #ccc;">
<h2>Published Versions (in reverse chronological order):</h2>

'''PC-BSD® 9.1''' was released on {{#dateformat:XX December 2012}}. The 9.1 Users Handbook is available in the following formats:

* [ftp://ftp.pcbsd.org/pub/handbook/9.1/handbook_en_ver9.1.epub EPUB (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.1/handbook_en_ver9.1.html HTML (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.1/handbook_en_ver9.1.pdf PDF (English)]

'''PC-BSD® 9.0''' was released on {{#dateformat:13 January 2012}}. The 9.0 Users Handbook is available in the following formats:

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_en_ver9.0.epub EPUB (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_en_ver9.0.html HTML (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_en_ver9.0.pdf PDF (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_in_ver9.0.epub EPUB (Indonesian)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_in_ver9.0.html HTML (Indonesian)]

* [ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_in_ver9.0.pdf PDF (Indonesian)]

* For those who prefer to purchase a copy of the Handbook for their Kindle, "PC-BSD® 9.0 Handbook (English Version)" is available from Amazon. The ASIN is B006W0EHN8 and this version is text-to-speech enabled.

* For those who prefer a "dead tree" version of the Handbook, the [http://www.freebsdmall.com/cgi-bin/fm/pcbsdhbk9.0?id=wrKa8VE5&mv_pc=95 book version] as well as a [http://www.freebsdmall.com/cgi-bin/fm/pcbsdhbk.bn?id=wrKa8VE5&mv_pc=51 book and DVD bundle] are available from FreeBSD Mall. The ISBN for the book is 1-57176-398-8.

'''PC-BSD® 8.2''' was released on {{#dateformat:24 February 2011}}. The 8.2 Users Handbook is available in the following formats:

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_en_ver8.2.epub EPUB (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_in_ver8.2.epub EPUB (Indonesian)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_en_ver8.2.html HTML (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_in_ver8.2.html HTML (Indonesian)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_en_ver8.2.odt ODT (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_in_ver8.2.odt ODT (Indonesian)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_en_ver8.2.pdf PDF (English)]

* [ftp://ftp.pcbsd.org/pub/handbook/8.2/handbook_in_ver8.2.pdf PDF (Indonesian)]

* For those who prefer to purchase a copy of the Handbook for their Kindle, "PC-BSD® 8.2 Handbook (English Version)" is available from Amazon. The ASIN is B004SP6PXY and this version is text-to-speech enabled.

</blockquote>

{{:License}}</onlyinclude>

The Handbook grows into a useful resource when users (meaning you!) contribute to it. You do not have to write large sections of the Handbook in order to be a contributor. You also do not need to have a lot of time on your hands. You simply have to create a login account in order to assist with any of the following tasks:

* proofread existing pages and fix any typos, grammos, or unclearly worded sections.

* add to sections containing missing, outdated, or incomplete content.

* update any screenshots that are out of date.

* every page has a Discussion tab. You can use this if you would like to suggest further information that should appear in that section of the Handbook.

* create a new section for content that is not yet covered in the Handbook. If you are not sure where to do this, ask on a semi-related Discussion tab.

We are emailed whenever edits are made and will contact you for clarification if an edit is unclear. You can also be notified when specified pages are edited--simply click the "my preferences" or "my watchlist" links whenever you are logged into the wiki.

''<center>Copyright 2011, 2012, The PC-BSD® Project. PC-BSD® and the PC-BSD® logo are trademarks of [http://www.ixsystems.com iXsystems].</center>''
''<center>All other content within the PC-BSD® Users Handbook is freely available for sharing under the terms of the [http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution License].</center>''
 
Work in Progress: PC-BSD{{r}} 9.2 Users Handbook

''' ''If the information and screenshots on the wiki do not match what you are seeing on your PC-BSD® system, it means it has changed between your version and the upcoming 9.2 version. You should instead refer to the Users Handbook that came with your version of PC-BSD®.'' '''
 
= Table of Contents =
{{hierB|title=Preface}}
{{hierB|1.|title=Introduction}}
{{hier|1.1|title=Goals and Features}}
{{hier|1.2|title=What's New in 9.2}}
{{hier|1.3|title=PC-BSD® Releases}}
{{hier|1.4|title=PC-BSD® for Linux Users}}
{{hierB|2.|title=Pre-Installation Tasks}}
{{hier|2.1|title=Hardware Requirements}}
{{hier|2.2|title=Laptops}}
{{hier|2.3|title=Partitioning the Hard Drive}}
{{hier|2.4|title=Obtaining PC-BSD®}}
{{hier|2.5|title=Burning the Installation Media}}
{{hier|2.6|title=PC-BSD® Live Mode}}
{{hier|2.7|title=Using VirtualBox}}
{{hierB|3.|title=Installing PC-BSD®}}
{{hier|3.1|title=Starting the PC-BSD® Installation}}
{{hier|3.2|title=Language Selection Screen}}
{{hier|3.3|title=System Selection Screen}}
{{hier|3.4|title=Disk Selection Screen}}
{{hier|3.5|title=Installation Progress Screen}}
{{hier|3.6|title=Installation Finished Screen}}
{{hierB|4.|title=Post Installation Configuration and Installation Troubleshooting}}
{{hier|4.1|title=Booting Into PC-BSD®}}
{{hier|4.2|title=Language Screen}}
{{hier|4.3|title=Time Zone Selection Screen}}
{{hier|4.4|title=Set Root Password Screen}}
{{hier|4.5|title=Create a User Screen}}
{{hier|4.6|title=Connect to a Wireless Network}}
{{hier|4.7|title=Post Install Finished Screen}}
{{hier|4.8|title=Logging In}}
{{hier|4.9|title=Installation Troubleshooting}}
{{hierB|5.|title=Advanced Installation Topics}}
{{hier|5.1|title=Install a Server}}
{{hier|5.2|title=Dual Booting}}
{{hier|5.3|title=Multiple Boot Environments}}
{{hier|5.4|title=Upgrading PC-BSD®}}
{{hier|5.5|title=Creating an Automated Installation with pc-sysinstall}}
{{hierB|6.|title=Desktops}}
{{hier|6.1|title=GNOME2}}
{{hier|6.2|title=KDE4}}
{{hier|6.3|title=LXDE}}
{{hier|6.4|title=XFCE4}}
{{hier|6.5|title=Awesome}}
{{hier|6.6|title=Enlightenment}}
{{hier|6.7|title=evilwm}}
{{hier|6.8|title=Fluxbox}}
{{hier|6.9|title=FVWM}}
{{hier|6.10|title=i3}}
{{hier|6.11|title=IceWM}}
{{hier|6.12|title=Openbox}}
{{hier|6.13|title=Ratpoison}}
{{hier|6.14|title=spectrwm}}
{{hier|6.15|title=WindowLab}}
{{hier|6.16|title=Window Maker}}
{{hierB|7.|title=Installing Applications and Keeping PC-BSD® Updated}}
{{hier|7.1|title=Using AppCafe®}}
{{hier|7.2|title=PBI Manager}}
{{hier|7.3|title=Update Manager}}
{{hier|7.4|title=Meta Package Manager}}
{{hier|7.5|title=Create Your Own PBI Repository}}
{{hierB|8.|title=Control Panel}}
{{hier|8.1|title=EasyPBI}}
{{hier|8.2|title=About}}
{{hier|8.3|title=Active Directory & LDAP}}
{{hier|8.4|title=Hardware Compatibility}}
{{hier|8.5|title=GDM Configuration}}
{{hier|8.6|title=Service Manager}}
{{hier|8.7|title=System Manager}}
{{hier|8.8|title=User Manager}}
{{hier|8.9|title=Bluetooth Manager}}
{{hier|8.10|title=Mount Tray}}
{{hier|8.11|title=Sound Configuration}}
{{hier|8.12|title=Display}}
{{hier|8.13|title=Printing}}
{{hier|8.14|title=Scanner}}
{{hier|8.15|title=Network Configuration}}
{{hier|8.16|title=Firewall Manager}}
{{hier|8.17|title=Life Preserver}}
{{hier|8.18|title=Adobe Flash Player preferences}}
{{hier|8.19|title=Warden®}}
{{hierB|9.|title=Using PC-BSD®}}
{{hier|9.1|title=Java, Flash, and Fonts}}
{{hier|9.2|title=Multimedia}}
{{hier|9.3|title=Files and File Sharing}}
{{hier|9.4|title=MythTV}}
{{hier|9.5|title=XBMC}}
{{hier|9.6|title=Windows Emulation}}
{{hier|9.7|title=Remote Desktop}}
{{hier|9.8|title=Thin Client}}
{{hier|9.9|title=ownCloud}}
{{hier|9.10|title=Security}}
{{hier|9.11|title=Accessibility}}
{{hierB|10.|title=Finding Help}}
{{hier|10.1|title=PC-BSD® Forums}}
{{hier|10.2|title=IRC Channel}}
{{hier|10.3|title=Mailing Lists}}
{{hier|10.4|title=FreeBSD Handbook and FAQ}}
{{hier|10.5|title=Social Media}}
{{hier|10.6|title=Search and Portals}}
{{hier|10.7|title=Other Resources}}
{{hierB|11.|title=Supporting PC-BSD®}}
{{hier|11.1|title=Become a Beta Tester}}
{{hier|11.2|title=Become a Translator}}
{{hier|11.3|title=Become a Developer}}
{{hier|11.4|title=Report Bugs}}
{{hier|11.5|title=Submit PBI Requests}}
{{hier|11.6|title=Test PBIs}}
:[[PBI Module Builder Guide|11.7 Create PBIs]] 
{{hier|11.8|title=Purchase PC-BSD® Swag}}
{{hier|11.9|title=Host a Mirror}}
{{hier|11.10|title=Seed a Torrent}}
{{hier|11.11|title=Become an Advocate}}

<noinclude>
[[category:PC-BSD® Wiki]]
[[category:Handbook]]
</noinclude>