The PC-BSD Users Handbook is freely available for
sharing and redistribution under the terms of the 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 iXsystems. If you wish to
use the PC-BSD logo in your own works, please ask for permission
first at marketing@ixsystems.com.

Double-click the word Empty, which represents your
DVD reader. If you wish to access the PC-BSD installer from your DVD
reader, double-check that the Slot is pointing to the correct
location (e.g. IDE Secondary Master) and use the drop down menu to
change it if the location is incorrect. Click the CD/DVD Device drop
down menu to change it from empty to the Host Drive value.

If you prefer to use an ISO that is stored on your
hard disk, click the folder icon to access the Virtual Media Manager
screen seen in Zdjęcie 2.8.1h.

Click the Add icon to navigate to the installation
ISO you wish to use. Once you press OK, it will show as the CD/DVD
device. Click OK to save your changes.

Note: the selected ISO/DVD can be 32-bit,
even if you're using VirtualBox on a 64-bit system. Depending upon
the extensions available in your CPU, you may or may not be able to
run a 64-bit ISO on a 64-bit system. If you receive the error "your
CPU does not support long mode" when you try to boot a 64-bit
ISO, your CPU either does not have the required extension or
AMD-V/VT-x is disabled in the system BIOS.

3
Instalacja PC-BSD

PC-BSD can be installed from the installation media
directly onto a hard drive or into a virtual machine using
virtualization software such as VmWare
Hypervisor or Virtualbox.
You can also try PC-BSD without installing it by selecting Live Mode
when you boot the installation media.

The PC-BSD installer has made installing PC-BSD as
easy as installing Microsoft Windows. The installation of PC-BSD is a
fast, easy and straight-forward process. The graphical installer will
take you step-by-step through the whole process by asking a few
simple questions. Within a short period of time, your PC-BSD system
will be installed, configured, and ready to use. Section 3 will walk
you through a default install which will be suitable for most users.
Users who wish to go beyond a default installation will also want to
read Section 4 for Advanced Installation Topics.

3.1 Uruchamianie
instalacji PC-BSD

Insert either the installation DVD into the
computer's DVD drive or insert the USB drive containing the
installation media into a USB port. Boot the system and the
installation should begin. If the computer instead boots into an
existing operating system, reboot and check your computer's BIOS
program to ensure that the drive containing the installation media is
listed first in the boot order. Save your BIOS changes and reboot.

After a couple of seconds, a series of lines of code
will scroll down the screen, meaning that PC-BSD is being loaded.
Soon after, you should see a screen similar to Zdjęcie 3.1a.

There are 8 options to choose from:

Boot Installer [default] - Starts the
installation program with all standard options enabled. This is the
default if you don't select anything else within 10 seconds.

Boot Installer with ACPI disabled - This
disables power management, which may be useful for certain BIOS's and laptops. If the installation program hangs
while probing your hardware, restart the computer and see if
selecting this option makes a difference.

Boot in Live Mode - Select this option
if you want to try out PC-BSD without installing it.

Boot in Safe Mode - Select this option
if the installation still hangs when probing your hardware and
option #2 did not help. It will boot with a forced PIO mode
(disabling the use of DMA), disable write caching for all IDE hard
drives and CD ROM drives, disable the probing of EISA slots (as very
few systems have them), and (on i386 systems) disables the use of
ACPI and APICs.

Boot with verbose logging - Select this
option if you would like to see more detailed messages during the
boot process. This can be useful if you are troubleshooting which
piece of hardware is causing the installation to hang.

Boot to emergency console - Advanced
users can use this option to fix critical system failures.

Run X in VESA mode - If the installation
program is unable to load your video driver, restart the computer
and select this option. The installer will default to VESA mode
which will work on any system with a video card.

Escape to loader prompt - Advanced users
can select this option to issue advanced commands, such as changing
kernels or loading kernel modules.

Zapamiętaj: If you are installing from a
flash or removable USB device, the installation will fail unless you
select the Network/Internet option as the boot-only install needs to
access files on the Internet to complete the installation. See
Section 4.4 on Installing PC-BSD Over a Network for a demonstration
on how to perform the installation over a network.

However, if you plan to share the computer with a
Linux distribution, you want to check this box. Even though you will
probably use the Linux boot loader, this option will create the
partition table info that other boot loader will need.

The PC-BSD/FreeBSD boot loader is extremely basic
and wasn't designed to look fancy or to be customized. If you select
to install it and decide later on to replace it with another boot
loader, see Section 4.7 on Dual Booting for other boot loader
alternatives.

The "Partition with GPT for full disk install"
checkbox needs to be checked if your hard drive is greater than 2 TB
in size. You can learn more about this option in Section 4.5, Using a
Custom Partition Layout.

3.1.6 Ekran
wyboru strefy czasowej

There is also a check box that allows your PC-BSD
system to automatically connect to a time server on the Internet to
ensure it is keeping accurate time. Accurate time is sometimes needed
by time-sensitive applications, such as logging into a server that
uses Active Directory. You can uncheck this box if you don't think
you need it or if your system isn't always connected to the Internet.

If your native language is English and you don't
want to install other language support (which does take up disk
space), check the box "Remove all other language support files".

3.1.9
Ekran postępu instalacji

How long the installation takes depends upon the
speed of your hardware, the installation type you selected, and
whether or not any additional software components will be installed.
A typical installation takes between 15 and 30 minutes.

3.1.10
Ekran zakończonej instalacji

This screen, seen in Zdjęcie 3.1.10a, appears once
the installation is complete.

As
seen in Zdjęcie 4.1a, the installer should detect the current
installation of PC-BSD and display a short description in the "Select
the system to upgrade" box. In this example, PC-BSD 8.0 is
currently installed and the user booted using the PC-BSD 8.1
installation DVD.

Highlight the detected version that you wish to
upgrade. If you wish to keep the data in your home directory, check
the box "Keep current users desktop configuration".

UWAGA: As with any operating system upgrade it is
always wise to backup important files and data beforehand to an
external backup device such as a removable USB drive.

After clicking Next, you will be presented with the
Components Ekran wyboru where you can choose which new PBIs to
install.

The update will now take place, preserving the home
data, installed PBIs, /usr/local and user accounts. When the
installation is finished, simply reboot and you will booted into the
new version of your PC-BSD operating system.

4.2
Odtwarzanie PC-BSD z backup'u

If you have previously made a full backup of a
PC-BSD system using Life Preserver (described in Section 7.7) and
have a network connection, you can restore a system from the backup.
If you select the "Restore from backup" option in the
System screen of the PC-BSD installer, it will prompt you for your
backup settings:

Zdjęcie 4.2a: Selecting to Restore from an Existing Life
Preserver Backup During Installation

When you click Next, the installer will attempt to
login to the specified server. If the login is successful, a pop-up
window will display the available backups. Choose the desired backup
from the drop down menu and click the Select button to exit the
pop-up widow. The installer will move on to the Disk screen so you
can select which disk/partition to restore to. Once you click Next,
the installer will skip to the Installation Summary screen. Click
Next to start the restore.

Simply select FreeBSD and go through the rest of the
installation screens. The only difference from a PC-BSD installation
is that the Components screen will only allow you to select two
components:

FreeBSD ports
collection

FreeBSD source

You'll find that this is a very quick install,
taking only a few minutes. Once the installation is complete, you
will be prompted to click Finish and to remove the installation
media. The system will then boot to a FreeBSD login where you can log
into a FreeBSD command prompt. If you wish to do any
post-configuration, type sysinstall as the superuser.

4.4
Instalacja PC-BSD poprzez sieć

If you are installing PC-BSD from a boot-only media,
you will need an Internet connection to finish the install. When you
get to the System screen of the installation, shown in Zdjęcie 4.4a,
select Network/Internet:

Zdjęcie 4.4a: Preparing the System for a Network Install

If
you receive your IP address from a DHCP server, leave the Network
Interface setting at AUTO-DHCP and click the Next button. Otherwise,
click AUTO-DHCP to select the network interface from the drop down
menu, then input the values for your network in the IP address,
Netmask, Nameserver, and Gateway fields.

Once you click Next, the installer will attempt to
use the network; if the connection is successful, you will see a
pop-up screen similar to Zdjęcie 4.4b:

Zdjęcie 4.4b:

Zapamiętaj: if this screen remains
greyed out, that means the installer was unable to connect to the
network. Double-check your network settings and try again.

Once the network connection is active, you can click
the drop down mirrors menu to select a mirror close to your
geographic region, then click the Select button to proceed with the
installation as usual.

If your company has created a custom installation of
PC-BSD that you wish to install from, select "Install from
specified server" and input the IP address of the server hosting
the installation files and the path to those files. The server can
provide the installation files through either FTP or HTTP.

4.5 Niestandardowy
układ partycji

A PC-BSD installation assumes that you have an
existing primary partition to install into. If your computer has only
one disk and PC-BSD will be the only operating system, it is fine to
accept the default partitioning scheme. However, if you will be
sharing PC-BSD with other operating systems, care has to be taken
that PC-BSD is installed into the correct partition; otherwise, you
may inadvertently overwrite an existing operating system. See Section
4.7 on Dual Booting if you plan to install PC-BSD onto a computer
with multiple operating systems.

During the installation, advanced users have the
flexibility of selecting alternate filesystems and to manually set
their sizes and mount points. Again, this is optional as the default
disk partitioning scheme should work just fine. However, if you are
already familiar with the feature Różnice pomiędzy various
filesystems or would like to try out different filesystems, this
section is for you.

Zapamiętaj: PC-BSD uses the same disk
terminology as FreeBSD, which is different than the terminology used
by Windows or Linux. In FreeBSD, the portion of the disk the
operating system is installed into is called a "partition".
That partition is then sliced up into "slices", with each
slice containing a filesystem and a mount point.

Zdjęcie 4.5a shows the Disk screen of the
installation. In this example, the user has selected "Customized
Disk Partitions (Advanced)", then the "Auto Setup"
button:

Zdjęcie 4.5a: Automatyczny podział na partycje przyciskiem Auto Setup

Using Auto Setup is a good way to see the default
partitioning scheme so that you can decide if you wish to keep or
edit the default values. The actual sizes of the slices created by
auto setup will vary, depending upon the size of the disk, but always
follow this logic:

the default size of the / (root) slice
will be 2 GB; this slice holds the root user's home directory as
well as the files needed by the operating system. You should not use
a size less than 1 GB. Also, it is not a good idea to store large
files on the root slice (as it should really be reserved for the
operating system files), so you are safe to leave it at the default
size.

the default size of the swap partition
will be RAM (physical memory) size times 2. You can increase this if
you want a larger swap partition (also known as a Paging File or
Virtual Memory in Windows).

the default size of the /var slice will
be 1 GB. This slice holds data that varies such as logs, printer
queues, and the FreeBSD packages database. You can safely increase
the size of this partition, though this is usually not needed on a
desktop system.

the rest of the disk space will go to /usr.
This slice holds everything else, such as users' home directories
and installed applications.

you must have a root slice as it holds the
operating system; make sure it is at least 1 GB in size.

you really do want a swap partition.

you can have one big root slice (plus a swap
partition); if you decide to do this, the installation will make
/var and /usr directories within that slice as they are needed by
applications. This is often discouraged on server systems, but is an
option on desktop systems.

you can divide the space given to /usr into
multiple slices. For example, some users like to create separate
slices to hold their video files, artwork, work files, etc. When
creating multiple slices, use names that makes sense to you (e.g.
/usr1, /usr2 or /video, /work) and set sizes that makes sense for
the amount of content that the slice will hold. If you decide to
take this approach, you should still make a good sized /usr
(otherwise it will be placed on root which will quickly fill up the
/ slice). The size of /usr should be sufficient to store any
software you install.

Why do some users create multiple slices or
discourage the use of one big slice? The usual answer deals with
backups (some people prefer to backup specified, smaller filesystems
rather than specified directories) or filesystem corruption (if you
lose a filesystem, you haven't lost everything). Since there are many
ways to perform backups and it is rare to corrupt a filesystem beyond
repair, it becomes a matter of personal preference.

If you click the + (add) or highlight a slice and
click the / (edit) button, you will see a screen similar to Zdjęcie
4.5b.

set the size by
either moving the slider, typing in a value, or using the up/down
arrows. Note that this won't work if there isn't any free space
leftover in the partition; if this is the case, delete a slice and
try again.

check the "Enable Encryption" box if
you wish to do so. See Section 4.6 on Disk Encryption for more
information on this topic.

Once you have reviewed your slices, you need to
determine whether or not to check the boxes at the bottom of the
screen:

Install PC-BSD bootloader: if PC-BSD will be
the only operating system on your computer, you can leave this box
unchecked. Check this box if you plan to use the grub bootloader,
described in Section 4.7.3, on a multi-boot system. Check this box if
a Windows system is already installed and you wish to use the PC-BSD
boot loader to select between operating systems. However, if you wish
to use EasyBCD, described in Rozdział 4.7.4, to select between
Windows and PC-BSD, do not check this box.

Partition with GPT for full disk install:GPTis a partition table layout that supports larger partition sizes than
the traditional MBR layout. If any of your slices are larger than 2
TB, this box must be checked. If your computer BIOS supports EFI
(most modern systems do), you can also check this box. The only time
you should not check this box is on a system with an older
motherboard--if it does not understand GPT, the installation will
fail and you'll have to try again with the box unchecked. If you're
unsure, leave the box unchecked.

When you are finished with your selections, press
Next to continue the installation.

4.6
Szyfrowanie dysku

The PC-BSD installer allows you to encrypt any or
all slices using the FreeBSD GELIframework. This is often desired on laptops that contain confidential
information. A cryptographic key is used to encrypt the data and this
encryption occurs automatically. In order to access the data on the
filesystem, you need to know the passphrase that was used when the
key was created. This means that it is important to remember your
passphrase, to make the passphrase difficult to guess, and to not
give that passphrase to others.

Zapamiętaj: be careful if you have changed
your keyboard variant and layout. At this time, GELI only supports
QWERTY passphrases, so don't use any characters not found on a QWERTY
keyboard.

If you decide to encrypt any slices, you will need
to watch your boot messages when the system boots as PC-BSD will
prompt you to enter the required passphrase(s) so it can mount the
encrypted filesystem(s) and finish booting into PC-BSD.

Zapamiętaj: While it may sound logical that
encrypting every slice will increase the security of your system,
this is actually not the case. Since most of the data on / and /usr
is known (these slices contain your operating system and default
applications), encrypting these partitions provides extra
cryptographic data which can be used to bypass the encryption. It is
usually recommended that only the home directory, which typically
contains the data you wish to keep private, is encrypted. If this is
your goal, you should create a separate slice called /home using the
instructions in Section 4.5, Using a Custom Partition Layout, and
encrypt that slice. Additionally, since the / slice contains the
encryption keys, it is further recommended not to encrypt this slice.
It is possible to do so, but will require you to store the keys on a
removable USB drive; if this drive is lost, the operating system will
be unbootable.

To encrypt a slice, click "Customize Disk
Partitions (Advanced)" in the Disk screen of the installer. You
can either click the "Auto Setup" button, as demonstrated
in Zdjęcie 4.6a, or manually create your partitions using the
instructions in Section 4.5, Using a Custom Partition Layout.

Once you have confirmed your passphrase, click the
Save button to return to the previous screen. You can repeat this
process for all of the slices you wish to encrypt.

Zapamiętaj: passphrases are
case-sensitive and can contain spaces. The passphrase should be
memorable to you (e.g. a line from a song or piece of literature),
but hard to guess (i.e. people who know you should not be able to
guess your favourite line from a song or piece of literature). If you
encrypt multiple slices, you can use the same or different
passphrases. If you use different passphrases, make sure you can
remember them all.

If you encrypt any slices, you will see the message
shown in Zdjęcie 4.6c when you click Next to proceed to the next
installation screen.

Zdjęcie 4.6c: Remember to Take a Backup of your Encryption Keys
After the Installation is Complete

It is important to remember to make a backup copy of
your keys either to another system or to a removable media such as a
USB thumb drive. You should do so after your first boot into PC-BSD.

Gdy instalacja się zakończy, sprawdzamy informacje bootowania. When the PC-BSD splash screen loads, press any key so you
can continue to see the boot messages. Right after the hard drive is
probed, you should see a message similar to this:

4.7 Kilka systemów na
jednym dysku

If you wish to install multiple operating systems on
your computer, you will need the following:

a partition for each operating system. Many
operating systems, including PC-BSD, can only be installed into a
primary partition. This means that you will need to use partitioning
software capable of creating multiple primary partitions. We
recommend Parted Magic as it
is freely available and easy to use. If your hard drive already has
an operating system that is using the entire hard drive, Parted
Magic can be used to shrink the existing partition in order to
create space to create new partitions. When creating the new
partition, it does not matter what filesystem is used (as PC-BSD
will overwrite it). However, it is important to make sure that the
new partition is created as a primary partition. Keep track of the
size and order of the partitions that you create so that you can
install PC-BSD into the desired partition.

a boot loader that allows you to select which
operating system you wish to boot. Depending upon the choice of boot
loader and the operating systems that you install, you may or may
not have to configure the boot loader to list all of the installed
operating systems. Also, depending upon the order that you install
the operating systems, the existing MBR data may be overwritten.
This section will describe the configuration of several different
boot loaders and how to restore an overwritten MBR.

a backup of any existing data--this backup
should not be stored on your computer's hard drive but on another
computer or on a removable media such as a USB drive or burnt onto a
DVD media. If you're careful in your installations, everything
should go fine. However, you'll be glad that you made a backup
should something go wrong.

When installing PC-BSD onto a computer that is to
contain multiple operating systems, care must be taken to select the
correct partition in the Disk Ekran wyboru of the installation. This
screen is described in Sections 3.1.4 and 4.5. On a system containing
multiple partitions, each partition will be listed. Highlight the
partition that you wish to install into and make sure that you do not
select a partition that already contains an operating system.

Zapamiętaj: Make sure that the "Use
Entire Disk" box is not checked. If you check this box,
the installer will overwrite all of the partitions that exist on the
disk!

You will also want to pay attention to the "Install
PC-BSD bootloader" check box at the bottom of the installer's
Disk Setup screen. Whether or not you should check this box depends
upon your choice of boot loader:

if you plan to use the PC-BSD boot loader as
described in Section 4.7.1, this box must be checked. This is
a good choice when Windows is already installed and PC-BSD is to be
the only other operating system as both entries should automatically
be created for you.

if you plan to use the GAG boot loader as
described in Section 4.7.2, you can leave this box unchecked. It
will not hurt to check the box, but you will end up being prompted
by two boot loaders whenever you boot PC-BSD.

>if you plan to use the grub boot loader as
described in Section 4.7.3, this box must be checked so that
grub can find the PC-BSD boot code.

if you plan to add PC-BSD to the Windows boot
loader using EasyBCD as described in Section 4.7.4, do not check this box.

The rest of this section will describe these boot
loaders in more detail.

4.7.2
GAG, graficzny boot manager

GAG is a
versatile boot manager, capable of booting many different operating
systems. Once you have finished installing all of your operating
systems, you can configure GAG to present you with a boot menu
containing an entry for each operating system.

After downloading and unzipping GAG, burn the
cdrom.iso file to a CD. Insert the CD and reboot the system to
configure GAG. You will be presented with the initial GAG screen,
shown in Zdjęcie 4.7.2a.

Zapamiętaj: Your mouse won't work in
GAG. Instead, use the key representing the number or letter of the
option that you wish to select.

Press the 4 key in order to "Install GAG".
The next screen will prompt you to choose your keyboard type by
pressing the associated number key. The next screen will prompt you
to choose your language by pressing the associated number or letter
key. Once your selections have been made, you'll see a screen similar
to Zdjęcie 4.7.2b.

Wybieramy Press the letter representing the icon that you wish
to associate with the operating system--it will be displayed next to
the description in the boot menu. For example, you could press F to
associate the FreeBSD Beastie icon next to the "PC-BSD 8.2"
description. Once you press enter, you will be returned to the main
menu. Press A again to add another operating system and repeat this
process for each operating system that you wish to boot.

Zdjęcie 4.7.2d: Wybieramy ikonę dla systemu widoczną w Boot
Menu

When you are finished, press H to "Save in Hard
disk". You should receive a pop-up message indicating that "GAG
installed successfully". You can now press R to "Return to
main menu". You'll note that the screen shown in Zdjęcie 4.7.2b
now contains the entries for the operating systems that you added.
Remove the CD and press the key associated with the operating system
you wish to boot.

Now, whenever you reboot your system, this same menu will appear.
It will always contain the S option so that you can add or delete
operating system entries, set the boot passwords, or set the boot
timer.

Click the "Add New Entry" button to add an
entry for your PC-BSD installation. In the Linux/BSD tab, click the
"Type" drop down menu and select FreeBSD from the list.
Type in something useful in the "Name" field; whatever you
type here will show up in the boot menu. Click the "Device"
drop down menu and select the partition holding your PC-BSD
installation. It won't have a drive letter and will have a filesystem
type other than NTFS or FAT32. The entry will also show its size so
you can find it if you have other non-Windows partitions. An example
is seen in Zdjęcie 4.7.4b.

4.8 Rozwiązywanie
problemów związanych z instalacją

4.8.1
Niepowodzenie instalacji

The PC-BSD installer creates a log which keeps a
record of all the steps that completed as well as any errors. Should
the installation fail, you can access this log to see what went
wrong. To access a terminal, right-click an area on the desktop
outside of the installation window and select xterm from the menu.
You can read the log with this command:

more /tmp/.pc-sysinstall/pc-sysinstall.log

If you can't figure out how to fix the error or believe that you have
discovered an installation bug, you can send this log to the Supportmailing list. You'll probably want to get a copy of the log onto a
working system so you can send an email using your favourite email
program. One way to do this is to copy the log to a USB thumb drive.
This command assumes that the thumb drive has been inserted and is
formatted with the FAT filesystem:

If your network connection is active (you can check with ifconfig),
you can sftp the file to an SSH server. In this example, the user has
an account on the SSH server with an IP address of 10.0.0.1 and
wishes to copy the log file to their Downloads directory:

4.8.2 Brak ekranu
powitalnego

If you can't get to the boot screen, seen in Zdjęcie
4.8a, try unplugging as many devices as possible, such as webcams,
scanners, printers, USB mice and keyboards. If this solves the
problem, plug in one piece of hardware at a time, then reboot. This
will help you pinpoint which device is causing the problem.

It could be that your BIOS is set to prefer your
built-in graphics capability or a non-existent graphics card. On some
systems it is determined by the order of the devices listed, the
preferred device should be first in the series. If you cannot see
your BIOS settings you may need to move a jumper or remove a battery
to make it revert to the default of built-in graphics, if applicable.
Check your manual or contact your manufacturer for details.

Zdjęcie 4.8a: PC-BSD Welcome Screen

4.8.3 ACPI

4.8.4 Zawieszanie się komputera

If your computer freezes after the installation boot
menu (while probing hardware) and unplugging extra devices or
disabling ACPI does not fix the problem, it is possible that the
installation media is corrupt. If the MD5 on the file you downloaded
was correct, try reburning the file and double-check that you are
using your burning software correctly (e.g. are not choosing a
burning speed faster than your DVD drive supports).

If the system freezes after the PC-BSD boot splash
screen loads and you suspect that configuring the video card is
causing the system to freeze, review your system's BIOS settings. If
there is a setting for video memory, set it to its highest value.

If that change did not help, try rebooting and
selecting option 7 from the boot menu. This will open the boot loader
prompt where you can type the following commands:

That will disable the vesa splash screen and boot the system to an
emergency console. From there you can try vesa mode, or drop to a
shell and modify /etc/X11/xorg.conf to change settings.

4.8.5 LBA

A not uncommon cause for problems is the LBA
(Logical Block Addressing) setting in the BIOS. If your PC is not
booting up before or after installation, check your BIOS and turn LBA
off (don't leave it on automatic).

4.8.6 Wykrywanie
monitora

It is possible to rerun the display settings utility
again if PC-BSD starts up with the wrong resolution or video card
driver. To rerun this utility, reboot the computer and select "7.
Run the Display Wizard" from the welcome to PC-BSD menu. This
will toggle the "disabled" to "enabled". After
making this selection, press enter to continue booting the system.

Zapamiętaj: PC-BSD 9.0 will add a
control panel setting to change your display, meaning that you will
no longer have to reboot to access this utility.

If none of the above has fixed your problem, search
the PC-BSD forums to see if a
solution exists, try a Google search, or check Section 8 on Finding
Help.

4.9
Zautomatyzowana instalacja z wykorzytaniem pc-sysinstall

PC-BSD provides a set of scripts that allow advanced
users to create automatic or customized PC-BSD installations.
pc-sysinstall is the name of the master script; it reads a
customizable configuration file and uses dozens of backend scripts to
perform the installation. All of the scripts are Bourne shell
scripts, making them fairly easy to read and understand.

Everything used by the pc-sysinstall script can be found in the
/PCBSD/pc-sysinstall/ directory:

Tip: if you wish to start a customized installation from a
non-PCBSD system, you can install this directory by running the
following command. Note that all files will be copied to the current
directory. This command assumes that you are on a Unix-like system
(e.g. Linux or Mac OS X) and that subversionis installed. You can install a Unix-like environment on a Windows
system using Cygwin.

svn co svn://svn.pcbsd.org/pcbsd/stable/pc-sysinstall

Here is a quick overview of the contents of the /PCBSD/pc-sysinstall/
directory:

backend/ contains the scripts used by
the PC-BSD installer. Scripts have been divided by function such as
functions-bsdlabel.sh and functions-installcomponents.sh. If you've
ever wondered how the PC-BSD installer works, read through these
scripts. This directory also contains the parseconfig.sh and
startautoinstall.sh scripts which pc-sysinstall uses to parse the
configuration file and begin the installation.

backend-partmanager/ contains the
scripts which are used by the installer to create and delete
partitions.

backend-query/ contains the scripts
which are used by the installer to detect (e.g. detect-nics.sh) and
configure (e.g. enable-net.sh) hardware.

components/ contains subdirectories, one
for each software component that is available for installing with
the operating system (e.g. firefox, openoffice). Each subdirectory
contains the description (component.cfg), an example of a translated
description (component.cfg.uk), a logo (component.png), and the
installation script for the software (install.sh).

conf/ contains the configuration file
for pc-sysinstall (pc-sysinstall.conf). It also contains a file
indicating which localizations are available (avail-langs), a list
of files which aren't touched during an upgrade
(exclude-from-upgrade), and a licenses subdirectory containing text
files of applicable licenses (e.g. bsd-en.txt and nvidia-en.txt).

doc/ contains the help text that is seen
if you run pc-sysinstall without any arguments.

examples/ contains several example
configuration files for different scenarios (e.g. upgrade,
fbsd-netinstall). The README file in this directory should be
considered as mandatory reading before using pc-sysinstall.

pc-sysinstall this is the script that is
used to perform a customized installation.

To create a custom installation, perform the
following steps:

1. Determine which variables you wish to customize.

2. Create a customized configuration.

3. Create a custom installation media.

These steps are discussed in more detail below.

4.9.1 Decydowanie, którą zmienną należy zmodyfikować

A list of possible variables can be found in
/PCBSD/pc-sysinstall/examples/README and in Table 4.9.1. Note that
the Table is meant as a quick reference to determine which variables
are available. The README file contains more complete descriptions
for each variable.

Table 4.9.1: Available Variables for Customizing a PC-BSD
Installation

4.9.2 Tworzenie
konfiguracji użytkownika

Read through the configuration examples in
/PCBSD/pc-sysinstall/examples/ to find the one that most closely
matches your needs. Copy that file (to any location) and customize it
so that it includes the variables and values you would like to use in
your installation.

If you wish to perform a fully automated
installation that does not prompt for any user input, you will also
need to review and customize the
/PCBSD/pc-sysinstall/examples/pc-autoinstall.conf file.

Table 4.9.2 shows some additional variables that are
available for fully automatic installations. Descriptions can be
found in the /PCBSD/pc-sysinstall/examples/pc-autoinstall.conf file.
Note that the variables in this file use a different syntax than
those in Table 4.9.1 (e.g. values follow a colon and space rather
than the equals sign).

Table 4.9.2.: Dodatkowe zmienne automatycznej instalacji

Zmienna

Opcje

Opis

confirm_install

yes

should be set, otherwise booting the wrong disk will result in
a system wipe

shutdown_cmd

shutdown -p now

good idea to run a shutdown, but can be any command/script you
wish to execute post-install

nic_config

dhcp-all or <interface name>

will attempt dhcp on all found NICs until the installation file
can be fetched or will setup specified interface

nic_dns

IP address of DNS server to use during fetch

nic_gateway

IP address of default gateway to use during fetch

4.9.3 Tworzenie
zmodyfikowanego nośnika instalacyjnego

The installation media can be a CD, DVD, USB, or a
directory on an HTTP, FTP, or SSH+rsync server.

The easiest way to create a custom installation
media is to modify an existing installation image. For example, if
you have downloaded an ISO (CD or DVD) for the PC-BSD version that
you wish to customize, the superuser can access the contents of the
ISO as follows:

Zapamiętaj: if you are using an HTTP, FTP, or SSH server
as the installation media, untar or copy the files to a directory on
the server that is accessible to http/ftp/ssh users. Be sure to
configure the server so that the installation files are accessible to
the systems that you wish to install.

If you are creating an automated installation, copy
your customized /PCBSD/pc-sysinstall/examples/pc-autoinstall.conf to
/tmp/custominstall/boot/.

Copy your customized configuration file to
/tmp/custominstall/. Double-check that the installMedium= variable in
your customized configuration file is set to the type of media that
you will be installing from.

You may also need to add some extra files if you set
the following variables in your custom configuration file:

installComponents= make sure that any extra
components you wish to install exist in extras/PBI/ (if they end in
the .pbi extension) or extras/components/ (if they end in .tbz)

runCommand= make sure the command exists in
the specified path

runScript= make sure the script exists in the specified
path

runExtCommand= make sure the command exists in the
specified path

If the installation media is a CD or DVD, you will
need to create a bootable media that contains the files in your
directory. To create a bootable ISO:

Use caution and refer to your monitor's
documentation if you make any changes here. If you're not sure what
you're doing, leave the default values as-is.

If your computer is connected to two monitors, check
the box "Enable Dual-Head support".

When you are finished, click the "Apply"
button for your settings to be saved and tested. If anything goes
wrong during testing, you should be taken back to this "Display
Settings" screen, so you can amend the details. If you're happy
with the resolution, click "Yes" in the next step. Click
"No" to return to the "Display Settings" screen
and try other settings.

If you wish to return to this screen at a later
time, you will need to reboot the computer and select "7. Run
the Display Wizard" from the boot menu, as seen in Zdjęcie 5.1c.
This will toggle the "disabled" to "enabled".
After making this selection, press enter to continue booting the
system.

Zapamiętaj: PC-BSD 9.0 will add a
control panel setting to change your display, meaning that you will
no longer have to reboot to access this utility.

If you wish to log into a different window manager,
click the session button in the lower left corner (it is a circle
with 3 lines). This will present a menu of installed window managers;
simply select the desired window manager and input your password to
login. The login manager will assume that you wish to log into the
last window manager used, unless you select a different one from the
session manager menu.

If you wish to install another window manager, see
if it exists in the Window Managers category of Software Manager.. If
you install another window manager using Software Manager, it will
automatically add it to the session manager window for you.

Klick the download button to install the fonts PBI.
It will automatically setup your system to use these fonts.

If you already have a collection of fonts that you
have downloaded or purchased, you can configure your PC-BSD system to
use these as well using the Font Installer utility.

Click the KDE menu → System Settings →
Font Installer to start this utility. In zdjęcie5.3b, "All
Fonts" is currently selected under the Group column, showing all
of the fonts installed on this system.

To install your fonts, highlight "Personal
Fonts" under the Group column, then click the +Add button. This
will allow you to browse to the font you wish to add. You can add
multiple fonts in the same directory by holding down the Ctrl key
while making your selection. Click the Open button, which will
install the font for you. When it is finished, you will see the
message in zdjęcie 5.3c.

Your newly installed font(s) should now show up in
the "Personal Fonts" section in the Groups column and be
available to the applications you use.

Zdjęcie 5.3b: Instalacja fontów True Type za pomocą Font
Installer'a

Zdjęcie 5.3c: Zainstalowano nowe fonty

5.4
Java i Flash

PC-BSD installs and configures the Adobe Flash
player (version 10) plugin for you. This means that flash should
"just work" when browsing the web. You'll find several web
browsers in the Web Browsers category of Software Manager, including
Firefox, Opera, and Chromium.

Software Manager also allows you to install the Java
Development Kit (JDK, used by Java developers) and the Java Runtime
Environment (JRE, used by java applications). Simply search for
"java" within Software Manager if you wish to install these
applications.

In this example, the user can choose to play the CD
using VLC (which was installed with Software Manager), with KsCD
(which was installed with PC-BSD), or to browse the contents of the
CD using File Manager. The user can also choose to click the eject
button (circle with up arrow), which will open the media tray so the
CD can be removed. You'll find additional media players in
Application Launcher -> Applications -> Multimedia.

While web browsing, you should be able to play most
media formats, including Youtube videos, Internet radio, and many
trailer and movie sites.

Zapamiętaj: If you happen to come across
a file that you can not play in a web browser or media player, it is
probably because it is in a proprietary format that requires a
licensing fee or restricts distribution of the codec that is required
to play that media format.

The Multimedia category of Software Manager contains
several dozen applications for playing and editing multimedia. It
includes these popular applications (click the links to view
screenshots):

Amarok: music player that includes integrated support for many web services
such as Last.fm, Magnatune, Echo Nest, Ampache, MP3Tunes, Jamendo,
OPML, and Librivox.

5.6
KDE Desktop

The first time you login to PC-BSD, you'll be
presented with the KDE desktop
environment. KDE 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. If you find KDE too slow for your
needs or prefer to use a leaner desktop environment, you can logout
and select another window manager as described in Section 5.2 on
Logon to PC-BSD.

This page will describe the default desktop. Note
that any KDE application can be started from another window manager
if you issue the command from a command line or add the path to the
command to the window manager's application launcher menu.

Ports
Jail: used by advanced users to install FreeBSD ports or
packages. See Section 6.2 on Using Ports Jail for more details.

Software
Manager: used to install, uninstall, and upgrade PBIs. See
Section 6.1 on Using Software Manager for more details.

Users
Handbook: provides quick access to the online version of the
PC-BSD Users Handbook (this document).

5.6.1
KDE Panel

The taskbar, also known as the KDE panel, is located
at the bottom of the desktop. It contains the following icons and
areas, going from left to right. If you hover over an icon with your
mouse, it will display its name and description. If you right-click
an icon, you can access its settings or remove it from the panel.

The
middle section of the panel doesn't contain anything by default. When
you open an application, its icon is placed here, allowing you to see
which applications are currently open. Click an application's icon to
minimize its window or to bring its window back onto the desktop.

Pager:used to switch between virtual desktops; click on the square
representing the desktop you wish to switch to. Each virtual desktop
can have its open windows. This allows you to group your tasks into
logical workspaces; for example, some users may do their gaming on
one virtual desktop, their graphics design in another, and their
homework on yet another.

Device
Notifier: if you hover over this icon it will show you any
inserted media (e.g. a USB thumb drive or a DVD) as well as any
recognized filesystems (e.g. a FAT32 filesystem from a Windows
installation on a dual-boot computer). A pop-up menu will appear over
device notifier when a media is inserted. If you click device
notifier, you can access the media or eject it as described in
Section 5.5 on Multimedia.

Show
the Plasma Dashboard: if you click this icon a small item labeled
"Widget Dashboard" will appear at the top of your screen
and your panel will temporarily disappear. If you right-click this
item, a pop-up menu will appear that allows you to configure icons,
widgets, panels, and activities. The Plasma
Guide can get you started with these configurations, but you will
probably find that some experimentation will let you discover the
features that you are interested in. When you are finished, click the
red X to close the widget dashboard and return to the panel.

Show
Desktop: clicking this icon will minimize all open windows and
show only the desktop. Click the icon again to return to the open
windows.

Clock:if you hover over the clock, it will display the current date and
time. A click over it will show the calendar. Right-click the clock
to change the time, timezone or set its appearance.

System
Tray: the system tray itself is the area to the right of the
clock. Depending upon the number of icons in the tray, they may or
may not all be displayed. Click the arrow button to enable or disable
the viewing of all the system tray icons.

Notifications
and Jobs: when the system has a message for you (for example, a
new device is detected or a download is complete), a pop-up message
will momentarily appear over this icon and the icon will change
slightly to indicate that there is a new message. Click the icon to
read the message. If you click the X in the upper right corner of the
message to remove the notification the icon will return to its
original state.

Network
Device: if any network interfaces were detected during
installation, an icon for each will appear in the system tray.
Hovering over the icon will shows the current settings for the
interface; for example, if it is connected and if it has an IP
address. You can add or remove icons for your network devices in
Application Launcher -> System Settings -> System Network
Configuration. Highlight the desired interface and check or uncheck
the "Display system tray icon".

IBus
input method framework: if you right-click this icon and select
Preferences, you can select the input method for your native
language. You can learn more about IBus here.

Update
Manager: the look of this icon will change depending on whether
or not the PC-BSD operating system and any installed PBIs are
up-to-date. The various update icons and how to use Update Manager
are described in Section 6.1.

Klipper:is a utility that keeps a history of your latest cuts/copies so that
you can paste them. Right-click the icon to view your history; if you
click on a history item it will allow you to paste it. You may want
to review the "Configure Klipper" menu item as it allows
you to set the size of the history. If you want to paste images as
well as text, uncheck the "Text selection only" box while
in the "Configure Klipper" menu. The Help menu option will
open the Klipper Handbook where you can learn more about using
Klipper.

KMix:click this icon to see a bar that lets you increase/decrease the
sound level. It also provides a Mixer button which you can click to
configure your audio channels. If you press F1 while in KMix, it will
open the KMix Handbook which shows you how to use this utility.

Keyboard
Layout Switcher: this icon will indicate the keyboard layout that
was selected during installation. To change the layout or variant,
right click the icon and select Configure from the menu. Click F1
while in this menu to read the Kxkb Handbook and learn more about the
layout configuration options.

Desktop
Search: if you right-click this icon and select "Configure
File Indexer" from the menu, you can view and configure yourStrigi settings.
Pressing F1 while in this menu will open up the Nepomuk Desktop
Search Configuration Handbook which will describe these settings.
Nepomuk allows you to tag and comment files in Dolphin and to find
files by searching their metadata.

KOrganizer:is KDE's organizer utility and reminder daemon. If you double-click
this icon, you can view a calendar and create reminders, events, and
to-do lists. Pressing F1 while in this menu will open a comprehensive
KOrganizer Handbook so you can learn how to get the most out of this
utility.

Battery
Monitor: if you hover over this icon on a laptop it will show the
percentage of battery power and whether or not the battery is
online/charging.

Trash:if you delete a file in Dolphin, it isn't deleted immediately.
Instead, it is stored in the trash can. Your trash can icon will
change slightly if there are items in it. If you hover over the icon,
it will tell you how many items are in the trash can. Right-click the
icon to open or empty the trashcan or to modify its settings.Zapamiętaj: if you delete a file at the command line it doesnot go to the trash can; instead it is immediately deleted.

Panel
Tool Box: if you click or right-click this icon, you can add or
lock widgets, add or edit the panel, add spacers or change the size
of the panel, or access even more settings. This pagecan get you started; again, you will want to experiment to see what
features/settings you like.

Zapamiętaj: should you delete the
original panel, you will have to manually re-add all of its icons and
widgets if you decide to create another panel.

5.6.2 Uruchamianie
aplikacji

The icon for the PC-BSD application launcher looks
different from the traditional KDE icon as it uses the PC-BSD flame
logo. Simply click this icon whenever you want to search for or start
applications.

If you click the application launcher icon, you'll
see the following five icons, with each icon representing a menu tab
of items:

Favorites: programs that are marked as
favorites are listed here. You can add any program you find in
application launcher to the Favorites menu by right-clicking the item
and clicking "Add to Favorites". Having your favorite
programs listed on this first tab saves you time browsing through the
applications menu.

Applications: this menu is divided into
categories that contain all of the applications that come with PC-BSD
as well as any software that you installed using Software Manager.
Click on a category name to view the applications within that
category. If you wish to return to the categories, click on the arrow
on the left side of the menu. To launch an application, simply click
its name. Alternately, if you right-click an application's name, you
will have the option to add it to the favorites menu, to create a
desktop icon, and/or to add an icon to the panel. Any of these
options will allow you to quickly see and launch your favorite
applications.

Computer: this menu provides shortcuts to
system settings, the run command, your home folder, network shares,
root's home folder, and the trash can.

Recently Used: this menu shows a list of the
last few opened documents and applications.

Leave: this menu is used to log out of your
current KDE session, lock your session, switch user, put the system
into sleep or hibernate mode, or restart or shutdown the computer.

Every application launcher menu provides a search
bar at the top of the menu. If you type the first few letters of an
application's name, application launcher will list all of the
applications that apply. This is a quick way to find applications
without searching through the categories.

5.7 Praca
z plikami i katalogami

If you're running PC-BSD with the default KDE
desktop environment, you can easily access your files and view the
directories on your system using the Dolphin file manager. To launch
Dolphin, use Application Launcher -> Dolphin. Zdjęcie 5.8a shows a
screenshot of Dolphin.

Dolphin will show the contents of the user's home
directory by default. This is where the user should create and store
their personal files. Dolphin provides many features for manipulating
files such as comments, tags, search, encryption, dealing with zipped
archives, and more. Simply click F1 while in Dolphin to access the
Dolphin Handbook to learn how to use its features.

The Root folder in Dolphin can be used to browse all
of the directories on the PC-BSD system. It is important to realize
that anything outside of your home folder came with the operating
system. This means that you should not delete or modify the contents
or permissions of any of these directories unless you know what you
are doing. When in doubt, leave the directory or file as-is.

Like other Unix-like operating systems, the root
folder is the top level of the directory structure. You can read more
about the layout of the FreeBSD directory structure by running man
hier at the command line. If you prefer to read manpages in
Dolphin, click the View menu -> Location Bar -> Editable
location. This will add a location bar where you can type inman:/hier. If you wish to read this man page while you are in
Konqueror, simply type in the same command in the area where you
typically type in a URL to a website.

Table 5.8.1 summarizes the contents of the directory structure on
a PC-BSD system.

If you dual boot your PC-BSD system, Dolphin will
display the filesystems from the other operating systems as Volumes.
Simply double-click the volume name to view its data. Depending upon
the type of filesystem, you may or may not be able to copy or edit
files between the volume and your PC-BSD system.

5.8.1 Łączenie
do innego pulpitu w wykorzystaniem Remote Desktop

If the other computer you are connecting to is a
Windows system, the connection can be made using the remote
desktop protocol (RDP). While remote desktop has been available
since Windows XP, not every edition of Windows provides a fully
functional version--for example, it may not be fully supported in a
home edition of Windows. If the full version of RDP is included,
remote access may or may not be enabled by default. If you have
trouble connecting using RDP, do a Google search for "remote
desktop" and the name of the version of Windows you are using to
find out how to configure its remote desktop settings. If you still
can't connect, you will need to download, install and configure VNC
server software on the system.

If the other computer you are connecting to is a
Mac, Linux, or BSD system, you will have to first install eitherrdesktop or a VNCserver on the other system. Depending upon the operating system,
either software may or may not already be installed. If it is not,
check the software repository for the operating system or use Google
to find out how to install and configure one of these applications on
that operating system. If you are connecting to another PC-BSD
system, rdesktop is already installed for you.

If the remote system is protected by a firewall, you
will need to check that it allows connections to the TCP port
required by the type of connection that you will be using:

RDP: uses port 3389

VNC: uses port 5900 (for the first connection, 5901 for the second
connection, etc.)

If you need to manually add a firewall rule, it is
best to only allow the IP address of the computer that will be
connecting. It is also more secure to remove or disable this firewall
rule after the connection is finished so that other computers don't
try to connect to the computer. Since your PC-BSD system is
considered to be the client and will be initiating the connection,
you do not have to modify the firewall on the PC-BSD system.

Once the other computer has the software it needs
for the connection, you can initiate a connection request using KRDC.
To launch this application, go to Application Launcher -> Internet
-> Remote Desktop Client. You can also launch this application by
typing krdc at the command line. If you click F1 while in KRDC
you can access the Remote Connection Desktop Handbook to learn more
about how to use this application.

Zdjęcie5.9a shows the initial KRDC screen which
allows you to specify which system you wish to connect to.

Zdjęcie 5.9a: Tworzenie zdalnego połączenia za pomocą KRDC

Use
the drop down menu to indicate whether the remote system is using RDP
or VNC for the connection. Then type in the IP address of the system
you wish to connect to. If you are connecting to a VNC system, the IP
address needs to be followed by a colon and a number indicating the
number of the session. Typically, the number will be 1 unless the VNC
server is hosting multiple simultaneous connections. Once you press
enter, the connection will be initiated and you will see the screen
shown in Zdjęcie 5.9b:

Zdjęcie 5.9b: Ustawienia zdalnego połączenia

Here is a quick overview of the settings:

Desktop resolution: since the contents of the
screen are sent over the network, select the lowest resolution that
still allows you to see what is happening on the other system. If you
have a very fast network connection, you can choose a higher
resolution; if you find that the other system is very slow to refresh
its screen, try choosing a lower resolution.

Color depth: choose the lowest color depth
that allows you to see the other system; you can choose a higher
color depth if the network connection is fast.

Keyboard layout: this drop down menu allows
you to select the desired keyboard layout.

Sound: this drop down menu allows you to
choose whether any sounds heard during the connection are produced on
this system, the remote system, or to disable sound during the
connection.

Console login: if you are connecting to a
Unix-like system, you can check this box if you wish to have access
to the other system's command line console.

Extra options: allows you to specify rdesktop
switches that aren't covered by the other options in this screen.

Show this dialog again for this host: if you
plan on using the same settings every time you connect to this
computer, you can uncheck this box. If you need to change the
settings at a later time, you can right-click the connection (which
will appear in a list as a past connection) and choose Settings from
the right-click menu.

Remember password:KWalletis KDE's password storage system. If this box stays checked, you will
only need to input the password the first time you make this
connection as it will be saved for you. If this is the first time you
have stored a password using KWallet, it will prompt you for some
information to set up your wallet.

Once you press OK, a connection will be initiated
and you will receive pop-up messages asking for a username then a
password; the details you provide must match a user account on the
system you are connecting to. Once your authentication details are
confirmed, you should see the desktop of the other system. If you
move your mouse, it will move on the other desktop as well. Click the
"View Only" button in the top toolbar whenever you wish to
disable this mouse behaviour. When you are finished your session, you
can click the "Disconnect" button in the top toolbar.

Personal Invitation: if you click this button
it will display the hostname that the other person will use to
connect, a temporary password to use for the connection, and an
connection request expiration time of one hour. It will include a
warning reminding you to only give this information to the person you
wish to connect as anyone can connect using that information. The
connection itself can be made from any VNC client. If the person is
using PC-BSD, they can use KRDC as described above. On other
operating systems, they will need to check if VNC is installed and
download a VNC client if it is not. Once you press the Close button,
the invitation expiry date will be listed in the main screen.

Email Invitation: if you click this button it
will display a warning that anyone who reads the email containing the
invitation can connect. Once you click the Continue button, the
default email program will open up containing the invitation so that
you can input the email address of the recipient and send the email.

Zdjęcie 5.9c: Inicjowanie żądania połączenia za pomocą Krfb

It should be noted that the most secure way to
convey the invitation information is through an alternate
communications channel such as a phone call. Ideally, you are
speaking to the other person as they connect so you can walk them
through the problem you are experiencing and they can let you know
what they are doing to your system as you watch them do it. Zdjęcie
5.9d shows an example of a personal invitation:

Zdjęcie 5.9d: Connection Invitation Created Using Krfb

Once the other person has the invitation, they
should input the information in the invitation into their VNC client
(also called a VNC viewer) in order to start a connection. You will
know when they try to connect as a pop-up message will appear on your
screen similar to Zdjęcie 5.9e:

In this example, a computer with an IP address of
192.168.1.111 is trying to connect. Buttons are provided to either
accept or refuse the connection. You can also check or uncheck the
box to "allow remote user to control keyboard and mouse".
If you accept the connection, the other user will be prompted to
input the invitation password. Once the password is accepted, they
will see your desktop.

Software Manager provides an intuitive, graphical
method for managing software. Binary packages and ports use
command-line tools and require previous knowledge or some time to
learn how to use the tools.

This section demonstrates how to use Software
Manager which is the recommended way to install and manage
applications and to keep your PC-BSD system up-to-date.

It also introduces the following topics for advanced
users. These advanced topics are meant for users who are already
familiar with compiling FreeBSD kernels and ports and who wish to
continue to do so on their PC-BSD system. If you decide to use the
instructions in those topics as a learning exercise, we recommend
that you use a test system rather than your primary desktop or that
you practice using Ports Jail. Make a backup of your important data
before proceeding, just in case something goes wrong.

Using Ports Jail to Manage FreeBSD Packages and Ports

Keeping Ports Up-to-date

Managing Packages/Ports

Rebuilding World

6.1 Korzystanie
z Software Manager'a

PC-BSD provides a unique file format known as a PBI
(push button installer). PBI files end with the .pbi extension and
are self-contained installation programs. When a PBI is installed
using PC-BSD's Software Manager, the application and all the files
and libraries it needs are placed in a subfolder of /Programs and
linked into the system. This means that even novice users can safely
install and uninstall PBIs without inadvertently overwriting or
deleting files needed by the operating system or other applications.
Software Manager automatically adds newly installed software to the
KDE menu and creates application shortcuts on the KDE desktop.

6.1.1 Instalowanie i odinstalowywanie pakietów PBI

To install a PBI, start Software Manager by
double-clicking its icon on the Desktop or going to Application
Launcher -> System Settings -> Software & Updates. You will
be prompted for the administrative password as only the superuser can
install software on a PC-BSD system. Once the password is accepted,
the Software Browser will launch, as seen in Zdjęcie 6.1a:

If
you know the name of the application you would like to install, type
its name into the Search bar. Alternately, you can click on a
software category (for example, Chat-IM) to browse for available
software. Use the Software Browser's forward and back arrows to
navigate within the browser.

Once you find a PBI that you would like to install,
click on its Download icon. Software Browser will automatically
detect your PC-BSD version and architecture and download the correct
PBI for you. When the installation is complete, the new PBI will be
displayed in the Installed Software tab. Zdjęcie 6.1b shows a
screenshot of this tab from a system with several PBIs installed.

If the installer did not ask if you would like to
start the application, you can launch the application using KDE's
Application Launcher. Type its name into the KDE menu's Search bar to
find its location in the menu. Once you find the application, you can
right-click its name to add an icon to the Favorites tab of the KDE
menu, your Desktop, or your panel's taskbar. You can also create a
desktop icon from the Installed Software tab. Simply right-click the
application's name and select "Install Desktop Icons" from
the menu.

To uninstall a PBI, simply highlight it in the
Installed Software tab and click the Remove button. In the example
shown in Zdjęcie 6.1b, the VirtualBox PBI is selected for removal.
Software Manager will prompt you to confirm that you wish to
uninstall the application. Software Manager will then remove the
application's subdirectory within /Programs, as well as its entry in
the KDE menu. If you have created any desktop or panel icons, you
should remove those manually.

Selecting "Start the Update Manager" from
the right-click menu or double-clicking the icon will open Software
Manager so that you can review the available update(s).

The System Updates tab, seen in Zdjęcie 6.1e, allows
you to easily apply security patches and update system drivers. If
system updates are available, they will be listed; if your system is
fully up-to-date, there won't be any entries in this tab.

Though the installation of updates is recommended as
they make your system more secure, add more functionality, and fix
bugs, system updates are not mandatory. For example, if you don't
wish to apply an NVIDIA update because your system uses a different
video driver, simply right-click the entry and choose "Ignore
this update" to remove it from the menu. If you check the "Show
ignored updates" box, the ignored updates will be displayed.

To receive more information about an available
update, highlight the entry and click the "View Details"
button. This will open up a web browser and display the details
regarding what the update addresses and whether any special
instructions are required, such as a reboot after applying the
update.

To install an update, highlight the online update(s)
you wish to install and click the "Install selected updates"
button. You can watch the update's progress as seen in Zdjęcie 6.1f.

If the update requires a reboot, you will be
notified to do so after the update has been installed. If a reboot is
needed, clicking the OK button at the informational message won't
reboot the system. Software Manager won't automatically reboot,
meaning you can continue to use your computer for other tasks while
the system is being updated. Finish whatever you're doing and reboot
the computer at a time that is convenient for you.

Zdjęcie 6.1f: Instalowanie uaktualnień systemu

If you're curious as to where Software Manager
stores its information regarding updates, check out the contents of
the following subdirectories:

In this example, five updates have been issued since 8.1 was
released. Each update ends in the .upd.sig extension and is dated and
signed. Files that end in .upd are the details for an update; these
files are ASCII text so can be sent to a pager or text editor:

6.1.4 Konfiguracja
Software Manager'a

If you click the Configuration button within
Software Manager, a window will open that has four tabs, as seen in
Zdjęcie 6.1g:

Zdjęcie 6.1g: Zakładki konfiguracyjne w Software
Manager'rze

The Mirrors tab allows you to configure which PC-BSD
mirror is used in order to check for and install updates to the
operating system or installed PBIs. The default selection is to use
the default US mirror. Occasionally, this mirror is busy or may not
contain the PBI or update that you wish to install. Also, there may
be other mirrors that are closer to your geographic location. If you
would like to change the default mirror, click the "Select
Mirror from list" button and select a mirror from the drop-down
list.

If your company maintains its own repository of PBIs
or updates, you can select the "Specify a custom mirror"
button and input the IP address of the company's server.

The Software tab, seen in Zdjęcie 6.1h, allows you
to configure the following options:

Automatically update software: check
this box if you would like Software Manager to automatically upgrade
your PBIs for you whenever an update is available. Otherwise,
Software Manager will wait for you to highlight the software that
you would like to upgrade in the Installed Software tab.

Automatically create desktop icons: uncheck this box if you don't want a desktop icon to be created
whenever you install a PBI.

Keep downloaded software in temporary
directory: check this box if you find yourself uninstalling then
reinstalling software or if you want to install the same PBI on
several systems. Rather than having to download the PBI each time,
you can double-click the saved PBI in Dolphin in order to reinstall
it. You can configure the directory that PBIs are saved to using the
Misc tab.

Zapamiętaj: zaawansowani użytkownicy którzy lubią zmieniać swój system powinni wiedzieć, że porty więzienia jail wymagają reguł nat w domyślnych regułach firewalla PC-BSD. Jeśli usunie się te reguły lub wyłączy pf, więzienie ports jail nie wystartuje. Advanced FreeBSD
users can continue to use FreeBSD packages and ports on their PC-BSD
installation without using ports jail. However, if you do not
consider yourself to be an advanced FreeBSD user, you should
experiment learning how to use ports and packages within the ports
jail utility. That is, do not run the commands described in this
section from a command prompt; only run these commands from within
the ports jail console.

The jail itself is like a self-contained FreeBSD
installation. You can see what this means if you spend a few minutes
comparing the outputs of commands such as ls /, pkg_info,
and more /etc/rc.conf between the ports jail and a regular
konsole. It should be noted that "self-contained" does
impose limitations. For example, any ports you compile within the
jail will not exist outside of the jail. If your goal is to install
applications to use on your PC-BSD system, you should be using
Software Manager instead. If your goal is to learn more about FreeBSD
packages and ports, use ports jail.

6.2.1 Instalowanie pakietów FreeBSD

A FreeBSD package is an installation file that
contains an application as well as installation information useful to
the operation system, such as a list of dependencies (other software
required by the application). Packages have been pre-tested for
FreeBSD, meaning that they should be fairly easy to install and
should work once installed. There are currently over 22,000 FreeBSD
packages to choose from. FreshPortsis an excellent place to browse for packages and to research the
files that get installed with a FreeBSD package.

pkg_add: used to install packages. If you
have never used this command before, take the time to read man
pkg_add to get an overview of how this command works.

pkg_delete: used to uninstall packages. If
you have never used this command before, take the time to read man
pkg_delete to get an overview of how this command works.

pkg_info: used to get more information about
the packages that have been installed. This command provides many
useful switches so it is well worth your time to read through man
pkg_info and to experiment with various switches.

To install a package, become the superuser from
within ports jail and use the remote (-r) switch to install the
specified package from the FreeBSD packages repository. For example,
this command will install the electric package:

You should receive a message indicating that the package was
successfully fetched, then your prompt back. Depending upon what is
already installed in your ports jail, your messages may indicate that
dependent packages were also fetched. Some packages include
post-installation instructions that will be displayed in the message.
Occasionally you will see a warning about a version mismatch; you can
ignore these as they do not affect the installation of the package.
Unless the message includes an error indicating that the system was
unable to fetch or install the package, the installation was
successful.

Since the command is issued from within ports jail,
the installed package will not appear as an entry in the KDE menu or
as an icon on the PC-BSD desktop.

Most packages install their binary (executable) in
/usr/local/bin and configuration files in /usr/local/etc/. You can
find out exactly what was installed using the -L (list) switch. If
you include -x, you will not have to type in the entire name and
version of the package as pkg_info will match any installed
packages containing your query string.

The pkg_delete command can be used to uninstall either a
package or a port from within ports jail. If you include the -x
switch, you don't have to give the full name and version of the
software. Be sure to give enough of a name so that you don't
inadvertently uninstall other software matching the name:

pkg_delete -x electric

If you just get the command prompt back, the delete was successful.
You can verify this by checking that the package no longer exists in
the package database:

pkg_info | grep electric

You will just get your prompt back if no installed software matches
that name.

If the software has other applications that depend
upon it, pkg_delete will refuse to uninstall it. If you wish
to override this setting, you can use the -xf switch to force
the delete. However, use the force switch with caution as forcibly
removing software can adversely affect the applications that required
it as a dependency.

6.2.2
Kompilowanie portów FreeBSD

A FreeBSD port is a set of instructions (contained
within a Makefile) for successfully compiling the source code for an
application on a FreeBSD system. The FreeBSD ports collection has
been arranged into a series of software categories; each category
contains a subdirectory for each application in that category. The
application's directory contains the application's Makefile as well
as any other files needed to compile and install the application. If
you click on the CVSWeb link of an application at FreshPorts, you can
read the port's Makefile. Zdjęcie 6.2b shows the CVSweb info for the
electric port. To navigate to this page in your browser, go toFreshPorts, search for
"electric", then click the link for electric 7.0.0_3, then
click on CVSWeb.

If you click the link for Makefile, you can read the
commit messages for every version of the Makefile; this can give you
a good idea of how long the port has been available, how often it is
updated, and any major changes that have occurred. Alternately, to
view the current Makefile, click on the Rev. number--in this case,
1.22. The distinfo contains the checksums for the source files;
again, you can either read the current revision or scroll through the
list of commits. The pkg-descr contains a description of the
software; if you read the revision, it will begin with the commit
message. The pkg-plist contains a list of what is installed (i.e. it
is the equivalent of running pkg_info -Lx as described in the
FreeBSD packages section). When reading this list, mentally replace
anything between %% markers with "/usr/local/".

If you wish to learn how to compile ports, you will
need to first install the ports collection into the ports jail. There
are several ways to accomplish this so you should select one of the
following methods. You will know that you have the ports collection
when /usr/ports/ is populated with many subdirectories, each
representing a category of software.

How long this command will take can range from a few minutes to many
hours, depending upon the size of the application and the speed of
your system. The make command will spit out many messages,
most of which you can ignore as they are simply indications of what
source is currently being compiled. Occasionally a menu will appear
asking you to select from a list of options. When in doubt, keep the
default options. If you understand the options, you can use your
arrow and enter keys to toggle an option on or off. When finished,
use the tab key to navigate to OK and press enter to continue the
compilation process. Occasionally, make will encounter an
error and will stop with an error message. If the solution for the
error is not obvious to you, try Googling for the keywords in the
error message. Keep in mind that this is a learning exercise and that
you may be forced to learn some things along the way.

include this line if you wish to keep your
source up-to-date. Source is needed if you wish to recompile your
kernel, update the operating system by rebuilding world, or to
recompile the latest version of a driver. Source will be put into
/usr/src and takes up about 600MB of disk space.

include this line if you wish to keep your
installed ports/packages up-to-date. Ports will be put into
/usr/ports/ and takes up about 1.2GB of space. That amount of disk
space will grow as you upgrade your ports since downloaded source
files for the software will be added to /usr/ports/distfiles/.

Once you have a supfile, you can sync your src
and/or ports using the following command. If the command is
successful, you'll see messages indicating that you are connected and
can watch the progress as new and modified files are downloaded:

6.3.3 Czytamy /usr/ports/UPDATING

Before upgrading any ports, always read
through /usr/ports/UPDATING first. This file contains any gotchas or
special instructions that are needed to upgrade certain ports. Ports
maintainers add to this file as new gotchas are discovered. However,
you will want to start reading the file at the entry that is closest
to the date that your version of PC-BSD was released (if you have not
upgraded anything yet) or the date you last upgraded, and read your
way up to the top of the file.

20100715:
AFFECTS: users of lang/perl*
AUTHOR: skv@FreeBSD.org lang/perl5.12 is out. If you want to switch to it from, for example
lang/perl5.10, that is:

as it is for the 15th of July of 2010, the first entry nearest to
July 20. As you read through the entries from that date up to the
last entry at the beginning of the file, make note of any entries
that match the software you have installed. If you are unsure of what
software is installed, this command will tell you:

Zapamiętaj: if there have been major
changes or there are a lot of entries that affect you, you should
decide if it is worth your time to upgrade or if you prefer to wait
until the next version of PC-BSD is released (as each release
contains the most updated software as of the release date). The more
software there is up to update, the longer the time required to
complete the upgrade process.

If your ports are already up-to-date and you prefer
to be notified as new entries are added to /usr/ports/UPDATING,
consider subscribing to its RSS
feed.

6.3.4Przeprowadzamy upgrade

After using the csup command to update your
ports and reading /usr/ports/UPDATING, you are ready to upgrade your
installed software.

If you are using portupgrade, you need to
first update the ports database and check to see which ports need
updating. Note that the following commands are installed for you when
you install portupgrade:

===>>> Gathering distinfo list for installed ports
===>>> Starting check of installed ports for available updates
<snip some output>
===>>> The following actions will be taken if you choose to proceed:
Upgrade mpg123-1.12.3 to mpg123-1.12.5
Upgrade p5-Object-InsideOut-3.69 to p5-Object-InsideOut-3.72
Upgrade linkchecker-5.3 to linkchecker-5.4
Upgrade tomcat-6.0.29 to tomcat-6.0.29_1
===>>> Proceed? y/n [y]

If you press enter to accept the default of yes, the upgrade will
begin. If any of the ports have configuration options, you will be
presented with some menus to make your selections. As each upgrade
completes, you will be asked if you want to delete the tar.gz of the
source for the old version of the software (which can save disk
space); you can include -D or -d if you don't want to
see this prompt. There are many switches available for portmasterso it is a good idea to man portmaster to see which ones
interest you.

Once all of your ports are up-to-date, consider
scheduling your upgrade process. The csup command works nicely
as a cron job; you can then run the portmaster command at your
leisure. Some portupgrade users create a simple script to run
the csup, portsdb and portversion commands and
to have the results emailed to the root user account. They can then
run portupgrade manually as ports need to be upgraded.

6.4 Przebudowa
świata

If you csup src, as demonstrated in Section
6.3, you can choose to rebuild your world (operating system) without
waiting for the next version of the operating system to be released.
This process can be desirable if a hardware driver you use is fixed
or given new features or if new functionality is added to the
operating system and you want to start using it right away.

How do you know what changes have been made to the
src of your operating system? One way is to read /usr/src/UPDATING or
to subscribe to its RSS
feed. If this is your first time reading this file, scroll down
to the COMMON ITEMS section towards the end of the file as it
contains useful advice. Similar to /usr/ports/UPDATING, you want to
skim through this file from the most recent entry down to the date
closest to when you installed or last upgraded the operating system
to see if any entries affect you. If so, be sure to follow the
instructions. Another way to find changes in src is to get in the
habit of reviewing the messages csup displays in order to see
which src files are added or modified.

If you are only interested in updating one driver or
system binary, you may or may not have to rebuild your world,
depending upon if the driver or binary depends on any changes that
have been made to the operating system source. The safest (but
longer) way is to always rebuild world; however, you can try just
recompiling the driver or binary to see if it works. If you receive
an error indicating that your "userland and kernel are out of
sync", this means that you must go through the build world
process in order for the new functionality to work.

To build just the driver or binary, cd into
its location in src. In this example, we'll rebuild the kdump
utility:

cd /usr/src/usr.bin/kdumpmake && make install

To rebuild the operating system, you will issue the following
commands as the superuser. If you have built world or your kernel
before on this system, you should first clean out the obj directory:

rm -Rf /usr/obj/*

You can now build the world. This process will take some time,
depending upon the speed of your processor.

cd /usr/srcmake buildworld

When that is finished, you will want to make sure to incorporate the
PC-BSD kernel options into the new kernel. If your system is 32-bit:

cp /PCBSD/conf/PCBSD /usr/src/sys/i386/conf

or, if your system is 64-bit:

cp /PCBSD/conf/PCBSD /usr/src/sys/amd64/conf

Then, build and install the kernel, install the built world, and
reboot into the upgraded operating system:

Should you be unable to boot into the new kernel, review the If
Something Goes Wrong section of the FreeBSD Handbook. It will
show you how to boot into the previously working kernel so that you
can access PC-BSD and figure out why the new kernel failed.

Zapamiętaj: zwykle nie trzeba edytować reguł firewall'a. If you disable the firewall
or remove the nat rule, ports jail will cease to work. You should not
remove any existing rules unless you fully understand what the rule
does. Similarly, you should only add rules if you understand the
security implications of doing so, especially if the rule allows
connections to your computer.

To access the Firewall Manager, go to Application
Launcher -> System Settings -> Firewall. Zdjęcie 7.1a shows the
initial screen when you launch this utility:

Zdjęcie 7.1a: Narzędzia Firewall Manager

The General Settings tab of this utility allows you
to:

determine whether or not the firewall starts
when the system boots; unless you have a reason to do so and
understand the security implications, this box should remain checked
so that your system is protected by the firewall

start, stop, or restart the firewall: if you
add, delete, or modify a firewall rule, you should restart the
firewall for your changes to take effect

restore default configuration: this button
allows you to return to the original, working configuration should
you not like the changes you make to your firewall rules

To view or modify the firewall rules, click on the
Exceptions tab, seen in Zdjęcie 7.1b:

service or port number: you can either select
the name of the service you wish to allow or block from the drop
down menu or type in the number of the port used by the service.
Which you choose does not matter as the firewall will match the name
and number for you and display both after you save the rule.

policy: you need to choose whether to allow or
block this service/port

direction: use the drop down menu to determine
whether the policy applies to incoming or outgoing connections; the
direction is from the perspective of your computer i.e. do you want
others to connect to your service (incoming) or do you want to
connect the service running on another system (outgoing)

protocol: use the drop down menu to select
whether the service uses the TCP or UDP protocol

interface: use the drop down menu to select the
interface that will make or receive the connection

7.2
Networking Manager

Setting up your local network to access the Internet
is easy with PC-BSD. During installation, PC-BSD configures your
network interfaces to use DHCP. In most cases, this means that your
connected interfaces should automatically work whenever you boot your
system. You still have the ability to view or manually configure your
network settings using the graphical System Network Configuration
module, seen in Zdjęcie 7.2a:

Zdjęcie 7.2a: Narzędzia do konfiguracji System Network
Configuration

To access this utility, either double-click the
network interface icon in your system tray or go to Application
Launcher -> System Settings -> System Network Configuration.

The main screen of the System Network Configuration
utility will display the list of network interfaces that PC-BSD
recognizes. In the example seen in Zdjęcie 7.1a, this system has one
Realtek Ethernet interface that uses the re driver and a wireless
interface that uses the wlan driver.

Zapamiętaj: the 0 next to each driver
name indicates that it is the first interface that uses that driver.
If, for example, the system had two Realtek cards, the second
interface would be labeled as re1. You can learn more about the
capabilities of a driver by reading its manpage (without the number).
In this example, the associated man pages are man re and man
wlan.

We'll now go through each tab of the System Network
Configuration utility to demonstrate how to configure and view the
network settings for both Ethernet and wireless drivers.

7.2.1
Ustawienia sieci Ethernet

If you highlight an Ethernet interface displayed in
the System Network Configuration utility and click the Configure
button in the Devices tab, or if you double-click an Ethernet
interface, you will be prompted for the administrative password. Once
the password is accepted, a popup Configuration window appears where
you can view and adjust the Ethernet card's network settings. Zdjęcie
7.2.1a provides an example of clicking on the Ethernet interface
named "re0".

If you wish to manually configure your Ethernet
interface, there are two ways to do so:

using DHCP. This assumes that your Internet
provider or network assigns your addressing information
automatically using the DHCP protocol. Most networks are already
setup to do this for you. This method is recommended as it should
"just work".

manually type in the IP addressing information.
This method requires you to understand the basics of TCP/IP
addressing or to know which IP address you should be using on your
network. If you don't know what IP address or subnet mask to use,
you will have to ask your Internet provider or network
administrator.

By default, the "Obtain IP automatically (DHCP)
option is selected. If you wish to manually type in your IP address,
uncheck this box. Type in the IP address, using the right arrow key
or the mouse to move between octets. Then, double-check that the
subnet mask (Netmask) is the correct value and change it if it is
not.

By default, the "Disable this network device"
box is unchecked. If you do not want this interface card to be
configured whenever you boot your computer, uncheck this box. If you
decide later that you do want to use this network card, you can go
back into the System Network Configuration utility and recheck this
box.

Zdjęcie 7.2.1a: Network Settings for the re0 Ethernet Interface

The Advanced tab, seen in Zdjęcie 7.2.1b, allows
advanced users to change their MAC
address and to use DHCP to automatically obtain an IPv6
address. Both boxes should remain checked unless you are an
advanced user who has a reason to change the default MAC or IPv6
address and you understand how to input an appropriate replacement
address.

The Info tab, seen in Zdjęcie 7.2.1c, will display
the current network address settings and some traffic statistics. If
you check the checkbox to disable the network device, it will
immediately stop the interface from using the network. The interface
will stay inactive until this checkbox is unchecked.

If you make any changes within any of the tabs,
click the Apply button to activate them. Click the OK button when you
are finished to go back to the main System Network Configuration
window.

You can repeat this procedure for each network
interface that you wish to view or configure.

7.2.2 Ustawienia
łącza bezprzewodowego

If you highlight a wireless interface displayed in
the System Network Configuration utility and click the Configure
button in the Devices tab, or if you double-click a wireless
interface, you will be prompted for the administrative password. Once
the password is accepted, a popup Configuration window appears where
you can view and adjust the wireless card's network settings. Zdjęcie
7.2.2a demonstrates that this system's wireless interface is
currently not associated with any wireless networks as there aren't
any listed in the "Wireless network profiles" section.

Zapamiętaj: if your internal wireless is activated or
your external wireless card is inserted but does not appear as a wlan
device, read Section 7.2.4 on Troubleshooting Network Settings.

To associate with a wireless network, click the Add
button which will open the window seen in Zdjęcie 7.2.2b.

Zdjęcie 7.2.2a: Okno konfiguracji połączenia bezprzewodowego

Zdjęcie 7.2.2b: Dodawanie profilu połączenia bezprzewodowego

Click the Scan button to receive the list of
possible wireless networks to connect to. Alternately, if the scan is
unable to find any networks and you know the SSIDfor the network you wish to connect to, you can manually type in the
SSID.

Highlight the network you wish to associate with. If
the network is open and does not require a key to authenticate, you
can simply click the Add button once the desired network is
highlighted. If the network uses privacy, you will need to select an
option other than "Disabled", then click the Configure
button. The possible options are:

WEP: this type of network can be
configured to use either a hex or plaintext key. You will be
prompted to type in the key twice to verify it. If the key is
complex, you can check the "Show Key" box to make sure the
passwords match. A wireless access point that uses WEP can store up
to 4 keys; the number in the key index indicates which key you wish
to use.

WPA Personal: you will be prompted to
type in the key twice to verify it. If the key is complex, you can
check the "Show Key" box to make sure the passwords match.

WPA Enterprise: you will be prompted to
select the authentication method (EAP-TLS, EAP-TTLS, or EAP-PEAP)
and to input the EAP identity, to browse for the CA certificate,
client certificate (EAP-TLS only), and private key file (EAP-TLS
only), and to input and verify the password.

Zapamiętaj: If you are unsure if the
network is using WEP or WPA, ask the person who setup the wireless
router what type of encryption is being used, the value of the
key/password, and the value of any other settings described above.
You can check the type of encryption using the ifconfigcommand, but you will still have to ask the administrator for the key
and any other settings if you are unsure of the correct values.

Once you have input the correct values, click the
Close button, then the Add button. Your entry should now show as a
wireless profile. If needed, you can view or modify the settings in
the profile using the Edit button. Highlight your entry and check the
"Obtain IP automatically (DHCP) box if the wireless network uses
DHCP. Otherwise, leave the box unchecked and type in the correct IP
address and Netmask. Again, if you are unsure of these values, ask
the person who setup the wireless network. When you are finished,
click the Apply button to return to the main Network System
Configuration window.

If all went well, there should be an IP address and
status of "Active" when you highlight the wlan0 entry. If
this is not the case, double-check your configuration values and read
Section 7.2.4 on Troubleshooting Network Settings.

The Advanced tab, seen in Zdjęcie 7.2.2c, allows you
to input a custom MAC address--similar to this setting for an
Ethernet interface, this setting is meant for advanced users who
understand why and how to change a MAC address. This tab also
provides a checkbox to disable the wireless interface. This setting
can be desirable if you want to temporarily prevent the wireless
interface from connecting to untrusted wireless networks.

Zdjęcie 7.2.2c: Zakładka Advanced bezprzewodowego interface'su

The Info tab, seen in Zdjęcie 7.2.2d, shows the
current network status and statistics for the wireless interface.

7.2.3 Zaawansowane
ustawienia sieci oraz PPPoE

The Network Configuration (Advanced) tab of the
System Network Configuration utility is seen in Zdjęcie 7.2.3a.

This tab is divided into two sections. If you wish
manually edit the settings in the "System configuration
settings" section, be sure that the interface that you wish to
configure is highlighted in the Devices tab. If the settings are
greyed out, it means that the settings were automatically obtained
from a DHCP server. If they are empty, it means that you need to
input the information manually. To add or override the existing
settings, click the "Change Configuration" button and input
the administrative password when prompted. A window will open that is
similar to Zdjęcie 7.2.3b.

The "PPPOE Configuration" section is used
to configure a modem connection to a PPP or PPPoE network. If you
connect to a network using a dialup or DSL modem, your Internet
provider will provide you with a username and password. To configure
your modem connection, check the "Enable PPPoE on this system"
check box. This will un-grey out the following settings so you can
input the required values:

Login: Your provider will provide you with a
username; input that value here.

Hasło: Your provider will provide you with a
password; input that value here.

Nazwa serwisu (opcjonalnie): Some providers
will provide you with a service name. If you have one, input it here;
otherwise, leave this field empty.

PPPoE Device: Click the drop down menu to
select the device name for your modem. If it is a dialup modem, the
device name will begin with cua. If it is a PPPoE connection, select
the name of the Ethernet device attached to the modem.

Zawsze połączony: do not check this box if
you are charged by the amount of time that you are connected.

Udostępnianie połączenia internetowego: if
you wish to share your Internet connection with the rest of the
computers in your network, check this box.

The Misc section contains one configurable option:

Enable Lagg wired/wireless failover: thelagginterface allows you to seamlessly
switch between using an Ethernet interface and a wireless interface.
If you want this functionality, check this box.

Zapamiętaj:some
users experience problems using lagg. If you have problems connecting
to a network using an interface that previously worked, uncheck this
box and remove any references to "lagg" in your
/etc/rc.conf file.

If you make any changes within this window, click
the Save button to apply them.

7.2.4 Rozwiązywanie
problemów z siecią

While ethernet networking usually "just works"
on a PC-BSD system, users sometimes encounter problems, especially
when connecting to wireless networks. Sometimes the problem is due to
a configuration error; sometimes a driver is buggy or is not yet
available. This section is meant to help you pinpoint the problem so
that you can either fix it yourself or give the developers the
information they need to fix or create the driver.

When troubleshooting your network configuration, you
need to be aware of the following files and commands:

/etc/rc.conf

This file is read when the system boots up. In order
for the system to configure an interface at boot time, an entry must
exist for it in this file. Entries are automatically created for you
during installation for each interface that is active. An entry can
be added (if it does not exist) or modified (if it exists and you
enter different information) when you enter the Configuration section
of an interface using the system network configuration utility.

Here is an example of the rc.conf entries for an
ethernet driver (re0) and a wireless driver (run0):

ifconfig_re0="DHCP"
wlans_run0="wlan0"
ifconfig_wlan0="WPA"

When reading through your own file, look for lines that begin with
"ifconfig". For a wireless interface, also look for lines
containing 'wlan".

Zapamiętaj: unlike Linux interface
driver names, FreeBSD/PC-BSD interface driver names indicate the type
of chipset. Each driver name has an associated man page where you can
learn which devices use that chipset and if there are any
configuration options or limitations for the driver. When reading the
man page, don't include the interface number. In the above example,
you could read man re and man run.

/etc/wpa_supplicant.conf

This file is used by wireless interfaces and
contains the information needed to connect to a WPA network. If this
file does not exist, it is created for you when you enter the
Configuration screen of a wireless interface using the system network
configuration utility.

ifconfig

This command shows the current state of your
interfaces. When reading through its output, you want to check if
your interface is listed, has a status of "active", and has
an IP address. Here is a sample ifconfig output showing the
entries for the re0 ethernet interface and the run0 wireless
interface:

In this example, the ethernet interface (re0) is active and has an IP
address. However, the wireless interface (run0 which is associated
with wlan0) has a status of "no carrier" and does not have
an IP address. In other words, it has not yet successfully connected
to the wireless network.

If your interface does not show up in ifconfigor dmesg, it is possible that a driver for this card is not
provided with the operating system. If the interface is built into
the motherboard of the computer, you can use the pciconfcommand to find out the type of card. Here is an example:

In this example, there is a built-in ethernet device that uses a
driver that supports the RTL8168/8111/8111c chipsets. As we saw
earlier, that driver is re0. The built-in wireless device was also
found but the ? indicates that a driver for the RTL8191SE
chipset was not found. A Google search for "FreeBSD RTL8191SE"
will give an indication if a driver exists (perhaps in a version of
FreeBSD that has not been released yet) or if a driver is being
developed. You can also use Google to locate a Windows driver and try
using the ndisgen command, as described below, to convert it
to a FreeBSD driver.

ndisgen

If your driver does not exist, you may be able to
convert a Windows driver to a FreeBSD driver using the instructions
on the Wireless
Testing page. If your chipset is not listed in Table 1, please
add an entry indicating whether or not you were able to successfully
convert and use the driver for your architecture.

If you are still unable to get your network
interface to work, see Section 8 on Finding Help. When describing
your problem, include the following information:

the version and architecture of PC-BSD you are
using (e.g. PC-BSD 8.1, 32-bit)

the name of the chipset used by the interface

the applicable entries in /etc/rc.conf

if you include your /etc/wpa_supplicant.conf,
sanitize the psk value so you don't tell the world what the password
is on your wireless network (e.g. replace the actual password with
***** or something similar)

7.3 Konfiguracja
drukarki

Like many open source operating systems, PC-BSD uses
the Common Unix Printing System (CUPS)
to manage printing. If you are planning to purchase a printer or
would like to know if a driver is available for your existing
printer, you can look up the vendor and model in the Open
Printing Database. This is an excellent way to see if the model
is supported and if there are any known caveats with the print
driver.

Once you know that your printer is supported, it is
easy to setup your printer on PC-BSD. Make sure that the printer is
plugged into your computer, or if the printer is a network printer,
that it is connected to the network. Then, go to Application Launcher
-> System Settings -> Printer Configuration. You will see a
window similar to Zdjęcie 7.3a:

Before adding a new printer, you should review the
"Basic Server Settings" options:

Pokaż drukarki udostępnianie przez inne systemy:check this box if you would like to use a printer that is connected
to another computer on your network.

Udostępnik upublicznione drukarki podłączone do
tego systemu: check this box if you would like other computers in
your network to use the printer connected to your computer.

Zezwól na drukowanie z Internetu:this box will be greyed out unless you first select the "Shared
published printers" box. If you decide to check this box, you
should configure the firewall that protects your network to only
allow the computers you wish to be able to print from the Internet
(e.g. if you would like your work computer to be able to send print
jobs to your home printer).

Zezwól na zdalną administrację: if this
box stays unchecked, only the computer connected to the printer will
be able to edit the printer configuration or manage the print queue.

Zapisz informacje debugowania problemu: check
this box if you are having problems using the printer. This will add
more verbose messages to the print log which is located in ls
/var/log/cups/error_log.

If you make any changes, click the Apply button.
You're now ready to create a printer.

Nowa drukarka sieciowa: to jest zwykle przycisk z którego korzystamy. Despite its name and description, clicking this
button will allow you to connect to any of the following types of
printers: a printer cabled to your computer, a network printer, or a
printer connected to another computer on your network.

In this example, the printer configuration utility
has found an HP Deskjet F4200 series printer attached to the
computer's USB port. The wizard should find any supported printer
that is attached to the computer or network and list it as the first
entry in the Select Connection frame. If it finds your printer,
simply click Forward to continue with the printer configuration
wizard.

If it doesn't automatically list your printer, you
will need to highlight and configure the type of connection to the
printer:

USB: this entry will only appear if a printer
is plugged into a USB port and the number of entries will vary
depending upon the number of USB ports on the system. If there are
multiple USB entries, highlight the one that represents the USB port
your printer is plugged into.

AppSocket/HP JetDirect select this option if
you are connecting to an HP network printer. You will need to input
the IP address of the printer in the Host field and change the port
number if the printer is using a port other than 9100.

IPP: select this option if you are connecting
to a printer cabled to another computer (typically running a
Microsoft operating system) that is sharing the printer using IPP.
You will need to input the IP address of the printer in the Host
field and the name of the print queue. You can then click the Verify
button to ensure that you can connect to the print queue.

LPD/LPR: select this option if you are
connecting to a printer which is cabled to a Unix computer that is
using LPD to share the printer. You will need to select the hostname
and queue name from the drop down menus.

Inne: if you are having problems configuring
your printer, you can manually type in the URI to the printer. A list
of possible URIs is available here.

If the configuration wizard found your printer in
the previous menu, the printer's manufacturer name will be
highlighted for you. In this example, HP is highlighted. If your
printer was not automatically found, you have 2 choices:

Highlight the name of the printer manufacturer
and click Forward to proceed to the next screen.

or

Highlight the "Provide PPD file"
button then click the Browse button to browse to the location of
this file. A PPD is a file that contains instructions on how to
print to a specific device. You'll find PPD files in the following
locations: /usr/local/share/cups/model/gutenprint,
/usr/local/share/foomatic/db/source/PPD, and /usr/local/share/ppd.
When browsing for a PPD, look for the manufacturer name, then the
model number that most closely matches your printer.

Zdjęcie 7.3.1c: Wybór producenta drukarki lub pliku PPD

When finished, click Forward to proceed to the next screen, shown
in Zdjęcie 7.3.1d.

This screen is used to select the printer model, and
thus the driver to use for printing. If the wizard automatically
found your printer, it will highlight the recommended driver for the
printer. You can also manually select the driver in the left frame.

Zapamiętaj: while the wizard is pretty
good at finding the best driver, it is not perfect. If the selected
driver does not match your printer model, see if it is listed in the
left frame. If it is not, use the Back button and see if you can
browse for a PPD file that matches your printer model. If you can't
find an exact match, try the recommended driver or the model number
that most closely matches your printer.

Zdjęcie 7.3.1d: Wybór modelu drukarki

After highlighting your selection, click the Forward
button to proceed to the screen shown in Zdjęcie 7.3.1e.

Changing the contents of this screen is optional. If
you will be using the printer in utilities that require you to type
in the printer name (e.g. xpdf), you can change the suggested printer
name to something shorter. If you have multiple printers, you may
wish to type in a description for the printer. You should leave the
location as-is.

Zdjęcie 7.3.1e: Dodawanie opisu drukarki

When finished, click the OK button to finish
creating the printer. You will then be returned to the main screen
and your new printer will be listed in the left frame, as seen in
Zdjęcie 7.3.1f.

To determine that the printer is working correctly,
click the "Print Test Page" button. If all went well, the
test page will print. This means that the printer should now work
within all of your PC-BSD applications (e.g. Okular, OpenOffice, your
browser, etc.) If you can not print a successful test page, see the
next section on Printer Troubleshooting.

You may wish to take a few minutes to review the
settings in the Policies, Options, and Job Options tabs as these
allow you to configure options such as print banners, the default
paper size, double-sided printing, etc.

Zdjęcie 7.3.1f: Podgląd ustawień dodanej drukarki

7.3.2 Rozwiązywanie
problemów z drukarką

If you have followed the instructions in the
previous section but still can't successfully print, you may find
your answer here. Here are some solutions to common printing
problems:

Strona się drukuje, ale nie tak jak powinna: this typically means that you are using the wrong driver. If your
specific model was not listed, click the Change button in the "Driver
Details" section of the Settings tab of the printer and try
choosing another driver model that is close to your model number. If
trial and error does not fix the problem, see if there are any
suggestions for your model in the Open
Printing database. A Google search for the word freebsd followed
by the printer model name may also help you to find the correct
driver to use.

Przy próbie drukowania nic się nie dzieje: in
this case it is useful to review the messages in the print error log
which is located at /var/log/cups/error_log. A useful test is to typetail -f /var/log/cups/error_log in a konsole and then to try
printing. Any new messages will be printed to the konsole. If the
solution is not obvious from the error messages, try Googling the
error message. If you're still stuck, post the error, the model of
your printer, and your version of PC-BSD to either the Hardware
Support forum or the Support
Mailing List.

7.4
Services Manager

Services Manager, seen in Zdjęcie 7.4a, provides an
easy-to-use graphical utility for managing some KDE and PC-BSD
services. The listed services can be enabled/disabled at system
startup and their current status can be toggled to stopped or
running. To access this utility, go to Application Launcher ->
System Settings -> Services Manager. You will be prompted to input
the administrative password.

Zdjęcie 7.4a: Zarządzanie serwisami za pomocą Services
Manager'a

The following services can be managed with this GUI:

ACPI notebook module: this service
should be enabled on laptops and can be disabled on PCs.

Avahi: KDE uses this service to discover
printers and folders that are shared on the local network.

cpufreq: a control framework installed
with PC-BSD to adjust CPU speed and voltage on the fly. This can
save battery power because the lower the clock speed, the less power
the CPU consumes. It is recommended for laptop users. You can learn
more about this framework by reading man cpufreq.

Denyhosts: this script is installed with PC-BSD and analyzes log messages to
determine what hosts are attempting unauthorized SSH access to your
system.

NFS: the Network File System is
installed with PC-BSD and used to share files between computers.

PF: the default PC-BSD firewall. It's recommended to keep the PF
firewall enabled. Advanced users may be interested in reading the
section on the Firewall
Manager.

SSH a network protocol that allows data to be exchanged over a secure
channel between two computers by using data encryption. SFTP and (SCP)
capabilities are also handled through the SSH protocol.

swap monitor: a PC-BSD script that
monitors swap space usage and activates 256MB increments as needed.
The script itself is located in /usr/PCBSD/Scripts/swapmonitor.sh.

Zapamiętaj: PC-BSD 9 will include a
control panel module that allows you to view every service on the
system, configure their start-time behaviour, their current status,
and to start/stop the service.

7.5
System Manager

The System Manager, shown in Zdjęcie 7.5a, is
launched by clicking Application Launcher -> System Settings ->
System Manager. You will have to input the administrative password to
allow the System Manager window to open.

This screen allows you to add or remove accounts.
Zdjęcie 7.6c shows the add user account creation screen--click the
Add button to open this screen.

The accounts that you did not create are known as
system accounts and are needed by the operating system or installed
applications. This means that you should not delete any accounts that
you did not create yourself; doing so may cause a previously working
application to stop working. Advanced view provides additional
information associated with each account, such as the user ID number,
full name (description), home directory, default shell, and primary
group. System accounts usually have a shell of "nologin"
for security reasons, meaning that an attacker can't try to login to
the system using that account name.

Login: this is the name the user will use
when they log in to the system; it is case sensitive and can not
contain any spaces. If you are creating a system account needed by an
application, use the name provided by the application's installation
instructions. If the name that you type in already exists as an
account, it will be highlighted in red and the utility will prompt
you to use another name.

Pełna nazwa: this field provides a description
of the account and can contain spaces. If it is a user account, use
the person's first and last name. If it is a system account, you can
input a description to remind you which application uses the account.

Katalog domowy: you can leave this field
empty for a user account as the system will automatically create a
home directory for them under /home/username. However, if you are
creating a system account it is important to override this default by
typing in /var/empty or /nonexistent unless the application's
installation instructions specify that the account needs a specific
home directory.

Shell: this drop down menu contains the
shells that are available for user accounts when they work from a
command prompt. You can either keep the default or select a shell
which the user prefers.

Grupa podstawowa: if you leave the default
button of "New Group" selected, a group will be created
with the same name as the user. This is usually what you want unless
you are creating a system account and the installation instructions
specify a different group name. Note that the drop down menu for
specifying a group name will only show existing groups, but you can
quickly create a group as described in the groups tab below.

Hasło: the password is case-sensitive and
needs to be typed in twice in order to confirm the password.

Once you have made your selections, press the Ok
button to create the account.

If you click the Groups tab, you can view all of the
groups on the system, as seen in Zdjęcie 7.6d:

To add an account to a group, highlight the group
name in the first column. Then, highlight the account name in the
available column. Click the right arrow and the selected account will
show in the members column. You should only add user accounts to
groups that you create yourself or when an application's installation
instructions indicate that an account needs to be added to a group.

If you click the Add button, a pop-up menu will
prompt you for the name of the new group. Once you press OK, the
group will be added to the groups column.

If you click the Remove button, that group will
automatically be deleted after you press the Apply button, so be sure
to do this with care. Again, don't remove any groups that you did not
create yourself or applications that used to work may stop working.

7.7 Tworzenie
backupu systemu korzystając z Life Preserver

The built-in Life Preserver utility allows you to
make a full backup of your PC-BSD system and store it on a remote
system; for the purposes of this section, we'll refer to the remote
system as a backup server. Life Preserver uses SSH and rsync, meaning
that the remote system must have SSH and rsync installed. If the
backup server is another PC-BSD system, these are already installed
and configured for you. If the remote system is running another
operating system, you will have to ensure that SSH and rsync are
installed and that SSH is listening for connections.

Life Preserver is not the only way to make a backup
on your system. For example, you may find it easier to drag and drop
the files/directories that you wish to backup to an external device,
such as a USB drive, using Dolphin. You'll also find a few PBIs of
backup utilities using Software Manager. The advantage of Life
Preserver is that it allows you to easily schedule backups to a
backup server and the PC-BSD installation media supports restoring
your system from a Life Preserver backup.

7.7.1
Creating a Backup

To make a system backup, go to Applications ->
System -> Life Preserver Backup. Once you have input the
administrative password, you will see the screen in Zdjęcie 7.7a.

By default, there aren't any preservers (backups)
listed. To create a backup, go to File -> New Preserver which will
launch the add new life preserver wizard. Click the Next button to
get started and to see the screen in Zdjęcie 7.7b.

Zdjęcie 7.7a: Initial Life Preserver Screen, Before Creating a
Backup

Zdjęcie 7.7b: Remote Device Configuration Screen

You will need to input the following information:

Host Name: of the remote system that will
store your backup. If the backup server is on your local network, the
host name must be in your hosts file or in the database of the local
DNS server. You may find it easier to instead input the IP address of
the backup server as this will eliminate any host name resolution
problems.

User Name: this user must have permission to
log in to the system that will hold the backup. If the account does
not already exist, you should create it first on the backup server.

SSH Port: port 22, the default port used by
SSH is selected for you. You only need to change this if the remote
system is using a non-standard port to listen for SSH connections. In
that case, use the up/down arrows to change the port number.

Zapamiętaj: if there is a firewall
protecting the remote system, make sure that it allows connections to
the specified port number from the IP address of the system that you
wish to backup. If the backup server is running PC-BSD, you can use
Firewall Manager to add an entry for SSH.

Once you click the Next button, you can decide
whether or not to schedule regular backups, as seen in Zdjęcie 7.7c:

By default, automatic backups are disabled, meaning
you will have to manually start a backup when you wish to do so. If
you decide to automate backups, you can choose to backup daily or
weekly. Select a time (e.g. early morning) when you don't expect
heavy network traffic between your computer and the backup server.
After making your selection, click Next and you will see the
informational message in Zdjęcie 7.7d.

This entry indicates the username and IP address of
the backup server, no previous backup has been made, automatic
backups are disabled, and a backup is not currently in progress
(running). To create a backup, click the Start button. Life Preserver
will automatically connect to the backup server and the Status will
change to Running. The backup will take some time as the entire
system will be backed up.

Zapamiętaj: Backups will be quite
large--about 6 GB in size, not counting the files that you have
created--so you will want to choose a time when the network isn't
being heavily used. If you are on a slow network, the backup will
take some time. It is also important to make sure that the backup
server has sufficient disk space to store your backup.

The backup will be stored on the remote system in
the home directory of the user that was used by Life Preserver to
login. The contents of the backup will be found in the
life-preserver/<backup>/ subdirectory where is
named according to the date and time stamp of the backup. The
contents of the directory will mirror the directory structure of your
PC-BSD system, making it very easy to find and restore individual
files or directories from the backup server to your PC-BSD system.
Here is an example listing of a backup on a remote server:

7.7.2 Troubleshooting and
Configuration Options

If there is a problem with the backup, you will find
the Life Preserver logs in
/PCBSD/lifePreserver/preservers/<host>/logs/, where is the name of the preserver entry--in this example,dru@192.168.1.111. The log files will be dated and time stamped and
will end with a .bz2 extension, indicating that they are compressed.
You can read a compressed log file by typing bzcat in front of
the log file name as seen in this example:

bzcat back-2011-01-05T13_45_22.log.bz2 | more

If the backup fails right away and there is only a few lines in the
log file, the connection attempt was unsuccessful. Check that your
network connection is up, that SSH is running on the remote server
and that the SSH connection is not being being blocked by a firewall.
If it is a non-PC-BSD system, double-check that rsync is installed on
the backup server and that there is sufficient space to hold the
backup.

If the backup proceeds for a while then ends with a
Failed message in the "Last Backup" section of the entry,
rsync found a file that it cannot backup. You'll know that this is
the case if the log file includes the error message "rsync
error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c". Typically, this is not a problem but more
of an indication that the rsync algorithm encountered a temporary
file or file lock that disappeared before it could back it up.
However, Life Preserver's default behaviour is to remove failed
backups from the server in order to preserve disk space, meaning that
the backup will have "disappeared" from the backup server.
To change this default in order to preserve a backup that is marked
as failed, right-click the preserver, select Edit, and uncheck the
box "Remove incomplete or failed backups". This box is
shown in Zdjęcie 7.7g:

Zdjęcie 7.7g: Life Preserver Settings

Press OK to save your configuration change and repeat the backup.

You can also modify the following settings seen in Zdjęcie 7.7g:

Number of backups to keep: make sure that
there is enough disk space on the SSH server to store this amount of
backups. If you do daily backups, a setting of 7 will keep a week's
worth. If you do weekly backups, a setting of 4 or 5 will keep about
a month's worth.

Remove incomplete or failed backups: by
default, Life Preserver attempts to conserve disk space on the backup
server by removing any failed backups. Uncheck this box if you are
troubleshooting Life Preserver.

Disable automatic backups: if this is
selected, a backup will only occur when you manually press the Start
button.

Backup daily: if this is selected, a backup
will occur every day at the time you select.

Backup weekly: if this is selected, a backup
will occur on the day of the week and time you select.

Remote directory: a subdirectory with the
name you specify will be created in the home directory of the user
that logs in to the SSH server; this is where backups will be stored.
The default subdirectory name is life-preserver.

Modify exclude list: provides a graphical
interface for adding files/directories to exclude from backups.
Clicking this button will open the screen seen in Zdjęcie 7.7h:

Zdjęcie 7.7h: Adding Entries to the Exclude List

Be sure to use the full pathname to the file or
directory that you wish to exclude from the backup. Type it into the
"Custom Exclude List" then click Add to save the entry. To
delete an entry from the list, highlight it and click the Remove
button.

If you read your backup logs, you'll note that Life
Preserver already has its own exclude list. This list is stored in
the hidden file
/PCBSD/lifePreserver/preservers/<host>/.working-exclude-list.
When you add your own entries, they do not affect this file. Instead,
a file named exclude-list is created for you in the same directory.

If you just input the name of the file or directory
and click the Restore button, it will be restored to its original
location. For example, the backup version of /etc/rc.conf would
overwrite the current version of /etc/rc.conf on your PC-BSD system.
This can be handy if you mess up this file on your PC-BSD system and
wish to restore the original, working version.

The Warden is available for PC-BSD in the PBI format
and a package s available for FreeBSD systems. Use Software Manager to install the
PBI on a PC-BSD system. Zdjęcie 7.8a shows a search for warden within
Software Manager.

Once the PBI is installed, you can launch The Warden
by clicking on Application Launcher -> Utilities -> Warden. You
will be prompted for the administrative password as only the
superuser can create and manage jails.

To install and initiate The Warden on a FreeBSD system, use these
commands as the superuser:

Using for jails
This
can be changed by running the following command at a later date:
pbreg set /PC-BSD/TheWarden/NIC <nic>
Reminder:
You will need to create a default world environment for creating new
jails!
To
do so, use the following commands in your /usr/src (or alternate
source dir)

IP Address: this is the address you will use
to SSH into the jail and access its contents. Choose an address that
is not already in use on your network by another computer or jail.
Use your arrow keys to move between the octets of the address as you
type it in.

Hostname: you can change the default of
"Jailbird" to another value. The hostname must be unique on
your network.

Include system source: if you check this box,
/usr/src/ will be populated with FreeBSD source. Source is needed if
you wish to build world or recompile the kernel (both are described
in Section 6.4, within this jail.

Include ports tree: if you check this box,
the ports tree will be installed into /usr/ports/. This will allow
you to compile FreeBSD ports within this jail, as described in
Section 6.2.2.

Start jail at system bootup: if this box is
checked, the jail will be started (become available) whenever you
boot your main system. If the box is not checked, you can manually
start the jail whenever you wish to access it using The Warden.

When you are finished, click the Create button. You
will be prompted to set the root password and create a user account
for this jail, as seen in Zdjęcie 7.8d. Since the jail will be
accessible using SSH, both of the passwords should be secure.

Zdjęcie 7.8d: Ustawianie danych logowania do więzienia (Jail)

Once you click the Save button, The Warden will
display status messages as it builds the new jail, as seen in Zdjęcie
7.8e. If you chose the options to include the FreeBSD source and/or
ports tree it may take some time before the messages indicate that
the jail was successfully created. When it is finished, a Close
button will appear that you can click on to return to the main
screen.

Once the jail is created, it will be listed in the
main screen. In the example shown in Zdjęcie 7.8f, there is one jail
with an IP address of 192.168.0.23 and a hostname of Jailbird. This
jail is currently stopped and it is not set to automatically start
when the PC-BSD system boots.

To view the jail's configuration, highlight its
entry then select Jails -> Configuration. Zdjęcie 7.8g shows an
example of this jail's configuration:

Zdjęcie 7.8f: Przeglądanie bieżącego stanu więzienia (Jail)

Zdjęcie 7.8g: Przeglądanie konfiguracji więzienia (Jail)

The following information is configurable:

Jail Network Interface: Warden will
automatically select the interface that is connected to the network
containing the jail's IP address. In this example, the IP address is
on an internal, private network attached to the re0 Ethernet address.

Jail Directory: this is the directory on the
PC-BSD system that contains the jail's filesystem. There will be a
sub-directory for each jail with the same name as the jail's IP
address. If you ever wish to backup your jail, this is the directory
to backup.

Temp Directory this is the directory that
will hold any temporary files created by the jail.

To start a jail, right-click its entry and select
"Start this Jail" from the menu seen in Zdjęcie 7.8h. Once
the jail has been started, you will be able to SSH to its IP address
using the username and password you provided. You may need to open
firewall port 22 using Firewall Manager, described in Section 7.1, if
you are unable to connect to the jail. Once you have logged into the
jail, you can do anything that you could do on a FreeBSD system. This
is a good way to learn how to use FreeBSD without affecting your
PC-BSD desktop. The FreeBSD
Handbook is a handy reference for learning how to perform almost
any task on a FreeBSD system.

Zdjęcie 7.8h: Dostępne opcje dla więnienia (Jail)

A jail's right-click menu contains the following options:

Start this Jail: will change a jail's Status
from Stopped to Running. You will not be able to SSH into a jail
until it is Running.

Toggle Autostart: will toggle a jail's
Autostart between Disabled (does not automatically start when the
PC-BSD system is booted) and Enabled (will start the jail when the
PC-BSD system is booted).

Install Inmate into jail: inmates are
described in the next section.

View installed packages: will show the output
of pkg_info to determine which software, if any, has been
installed within the jail.

Export jail to .wdn file: this type of file is described in
the Exporting/Importing Jails section.

Delete Jail: this will remove the jail and all of its
contents from the PC-BSD system.

7.8.1 Instalacja Inmates

An inmate is a pre-configured software installation
that allows you to quickly get a service up and running within a
jail. Software Manager can be used to find and download inmates.
Zdjęcie 7.8.1a shows the results of searching for "inmate"
within Software Manager's software browser:

In this
example inmates are available to install an Apache/PHP environment
and a Joomla/Apache/MySQL environment. Installing an inmate can save
a lot of time installing the individual packages needed to setup
either of these environments. Once installed, you will still be able
to customize the configuration of the installed software to suit the
jail's purpose.

Zapamiętaj: before downloading an
inmate, it is important to make sure that Software Manager is
configured to save downloaded files. To do so, click the
Configuration button -> Software tab. Make sure the box "Keep
downloaded software in temporary directory" is checked. The
location of this temporary directory can be viewed and edited in the
Misc tab.

Click on the inmate you wish to install and select
its Download icon. Once the download is complete, highlight the jail
in The Warden and select "Install Inmate into jail" from
the right-click menu. This will open up a screen where you can browse
to the location of the .wit file that you downloaded using Software
Manager. Once the inmate is installed, you can verify which software
was installed by right-clicking the jail and selecting "View
installed packages". You can now configure the installed
packages to meet your needs.

7.8.2 Eksportowanie/Importowanie Jail (więzienia)

Exporting a jail allows you to save the jail (and
all of its software, configuration, and files) as a .wdn file. This
allows you to quickly clone a pre-configured jail to a new jail.

To create a .wdn file, right-click the jail and
select "Export jail to a .wdn file". You will be prompted
to choose the directory in which to store the backup. A progress bar
will indicate that the backup is in progress. Creating the .wit file
may take some time, especially if you have installed src or ports or
have installed inmates or other software.

Zapamiętaj: you should not be logged
into the jail while exporting it as Warden will need to stop the jail
in order to back it up. If your jail is running services (e.g. a
webserver), you should select to export the jail at a time that will
least impact network connections to the jail.

The exported jail will end with a .wdn extension and
the filename will be the IP address of the jail.

To create a new jail using the .wdn backup, select
File -> Import Jail. You will be prompted to browse to the
location of the .wdn file. Once selected, you will be prompted
whether or not to use the same IP address for the new jail. If you
are creating a new jail on the same system that still has the
original jail installed, select No and input the IP address for the
new jail. However, if you have deleted the original jail or need to
restore that same jail on another computer (for example, there was a
hardware failure on the system containing the original jail), you can
choose to use the same IP address. You will then be prompted whether
or not to use the same hostname. Again, only say Yes if that hostname
is no longer in use; otherwise, select No and input a unique hostname
for the jail. Warden will then recreate the jail with all of the
original settings. Whether or not those settings include the original
IP address and hostname depends upon your selections.

8 Gdzie
znaleźć pomoc ?

While professional PC-BSD support is available fromiXsystems, most users turn to
the Internet for help. We are doing our best to make PC-BSD as easy
as possible for newcomers. Should you need help, there are plenty of
ways to get in touch with the PC-BSD community. This section
discusses the following help resources:

PC-BSD Forums

FAQS

IRC Channel

Mailing lists

FreeBSD Handbook and FAQ

Forums

Social Media

Search and Portals

Other Resources

8.1 Fora
PC-BSD

The PC-BSD Forumscontain a wealth of information, tips and solutions which you can
access from a web browser. There are many active members and you will
find that most questions are replied to quickly. If you are having
problems with something on your PC-BSD system, try using the forum's
search utility. You'll often find that someone else has posted a
similar question and that other users have responded with a fix or a
how-to.

The Forums have been categorized, allowing users to
skim through the categories that interest them while learning some
things along the way. You do not have to create a login account in
order to search or read through the forums. However, if you wish to
ask or answer a question on a forum or subscribe to a forum or a
thread (to be automatically notified when a new post is added), you
will need to be logged in. To subscribe to a forum, open the page for
the forum and select Forum Tools -> Subscribe to this Forum. You
will be prompted to choose how often to be notified whenever a post
is added to the forum. If you wish to subscribe to a specific post,
open the post and select Thread Tools -> Subscribe to this Thread.
You will be notified whenever someone responds to that post.

The current categories and the forum descriptions
are described below:

The General category contains the following forums:

Announcements:
this is a read only forum containing announcements of new releases
and news related to PC-BSD. Subscribing to this forum is a good way
to keep up-to-date with the latest news about PC-BSD.

General
Questions: use this forum if your question does not fit into any
of the other forum categories.

The
Lounge: this is a general discussion area for PC-BSD users.
Posts in this forum are not of a technical nature. Posts should be
of interest to other PC-BSD users and not contain any mature or
slanderous content.

Books
on PC-BSD: this forum contains errata and discussion for
published books about PC-BSD.

PBI developers subscribe to the PC-BSD Software (PBI
files) category to become aware of any problems with current PBIs and
to receive requests for software that should be made into a PBI. If
you start a post a in any of these forums, you should subscribe to it
so you can be notified of any responses to your post. The forums in
this category include:

PBI
Discussion: a general discussion area for resolving PBI problem
reports. If you have a problem installing or using a PBI, post the
details in this forum.

PBI
Requests: do you have a favourite software that is not currently
available as a PBI? You can request it in this forum. Be sure to
read the Readme
first post if this is your first PBI request.

Finished
PBIs: once a new PBI is created as the result of a PBI request,
the original request is moved to this forum.

Port
Requests: do you have a favourite software that is not currently
available as a FreeBSD port? You can request it here; if someone
does make a port it can also be converted into a PBI as PBIs are
based on FreeBSD ports. Again, read the Readme
first file if this is your first port request.

The Support category deals with the following types
of support questions. PC-BSD developers are subscribed to this list
so they can help determine what is causing the problem, and if a fix
is made available, can commit it for the next version of PC-BSD. If
you start a post a in any of these forums, you should subscribe to it
so you can be notified of any responses to your post.

General
Bug Reports: if you are having a problem on your PC-BSD system
that does not match any of the other forum categories, you can
report it here. Read any posts marked as "sticky" (they
will always be at the top of the forum) if this is your first bug
report.

Installing
PC-BSD: if you are having problems installing PC-BSD, post the
details of your problem to this forum.

Startup
Bug Reports: if you have been able to install PC-BSD but are
having problems booting into PC-BSD, post the details of your
problem in this forum.

Usage
Bug Reports: if you are having problems performing a task or
using the software that was installed with your PC-BSD system, post
the details of your problem to this forum.

The Hardware Support category is for reporting
hardware-related problems. PC-BSD developers are subscribed to this
list so they can help determine what is causing the problem, and if a
fix is made available, can commit it for the next version of PC-BSD.
If you start a post a in any of these forums, you should subscribe to
it so you can be notified of any responses to your post. Be sure to
read the README
first before posting.

General
Support: if your hardware problem does not match any of the
other forum categories, post the details of your problem in this
forum.

Graphics
Cards: if you are having problems with your video card settings,
post the details of your problem to this forum.

Sound
and Multimedia: if you are having problems with sound or in
playing multimedia such as CDs or videos, post the details of your
problem to this forum.

Networking:
if you are having problems using or configuring a network interface,
post the details of your problem to this forum.

Laptops:
if you are having problems with power management or other
laptop-specific issues, post the details of your problem to this
forum.

Drives:
if you are having problems accessing or formatting CD, DVD, USB or
hard drives, post the details of your problem to this forum.

PC-BSD
Installer: this is a discussion area for feature requests and
testing of the PC-BSD installation program.

The Testing category is for PC-BSD beta testers to
report problems found in upcoming versions of PC-BSD. It contains the
following forums:

General
Testing: if your problem is not related to one of the following
desktop environments, report the problem in this forum. Be sure to
read the sticky threads first as they contain useful information
about beta testing and any known issues with the testing snapshot.

KDE:
if your problem is related to the KDE desktop or KDE applications,
report the problem in this forum. Be sure to read README
first for instructions before posting.

Gnome:
if your problem is related to the GNOME desktop or GNOME
applications, report the problem in this forum. Be sure to read
README
first for instructions before posting.

XFCE:
if your problem is related to the XFCE desktop, report the problem
in this forum. Be sure to read README
first for instructions before posting.

LXDE:
if your problem is related to the LXDE desktop, report the problem
in this forum. Be sure to read README
first for instructions before posting.

Fluxbox:
if your problem is related to the Fluxbox desktop, report the
problem in this forum. Be sure to read README
first for instructions before posting.

Ports
Testers: if your problem is related to a FreeBSD package or
port, you can report the problem in this forum. Be sure to read
README
first for instructions before posting.

The International category contains forums for
non-English speakers for PC-BSD related discussions in their native
language. Each forum has its own categories for organizing posts. The
following forums are available:

While logged into the forums, a link called UserCP
will appear in the upper left hand corner. This is your control panel
and it contains many settings to customize your forums experience.
You should review the settings in your Control Panel.

Before asking a question on the forums or starting a
new thread, first use the search utility to see if a similar thread
already exists. If one does, you can add to the conversation by using
the Reply button. If you find a thread useful, feel free to click the
Thanks button to let the original poster know that you benefited from
their knowledge.

If a similar thread doesn't already exist, review
the forum categories to determine which one is the best fit for your
post. When creating a new thread, use a useful Title name to describe
your problem or question--remember, other users may be researching a
similar issue and you want them to find your thread. Include enough
details in your message so that others can quickly understand what
you are experiencing--otherwise, they will have to ask you additional
questions to understand your problem. Make sure you are subscribed to
your thread so that you will receive a notification when someone
responds to it.

You can ask a question by clicking on the "New
Thread" button in the forum category that most closely matches
your question. For example, if you are having problems with your
video settings, you should create a new thread in the Graphics Card
forum. If you don't see a category that matches your question, try
the General Support category.

In addition to the forums available from the PC-BSD
Forums website, the following forums may assist you in
troubleshooting your PC-BSD system:

FreeBSD
Forums: many PC-BSD problems are related to the underlying
FreeBSD operating system. The FreeBSD forums are very active and
full of useful information that can apply to your PC-BSD system.

BSD
Nexus: contains categories for each of the BSD operating systems
as well as general BSD information.

BSD
Foren: these forums are in German and contain many categories
for each of the BSD operating systems.

BSD
Guru PC-BSD Forum: this forum is in Polish and is specific to
PC-BSD. Additional Polish forums for the other BSD operating systems
are available here.

8.2
FAQ

The acronym FAQ stands for Frequently Asked
Question. For that reason, you should always check the FAQS before
asking a question, just in case it has been answered many times
before.

You can find the most current version of the PC-BSD
FAQS here.
The FAQs are currently a work in progress as we migrate the older
FAQS and ensure that their answers work on current versions of
PC-BSD. You can suggest an FAQ that you would like to see answeredhere.

8.3
Kanał IRC

Like many open source projects, PC-BSD has an IRC
channel to connect supporters and users. To get connected, use
the following information in your IRC client:

Server name: irc.freenode.net

Channel name: #pcbsd

Software Manager has a "Chat -IM" category
where you can find PBIs for IRC clients. If unsure which IRC client
to use, we suggest KVirc orXChat.

IRC is a great way to chat with other users and get
answers to your questions. A few things to keep in mind if you ask a
question on IRC:

Most of the regular
users are always logged in, even when they're away from their
computer or are busy doing other computing tasks. If you don't get
an answer right away, don't get mad, leave the channel and never
come back again. Stick around for a while to see if anyone responds.

IRC users represent
many different time zones. It is quite possible that it is late at
night or very early in the morning for some users when you ask a
question.

Don't post error
messages in the channel as the IRC software will probably kick you
out. Instead, use a pasting service such as pastebin and refer to the URL on channel. If you prefer to paste an image of
your error, you can upload it to a temporary screenshot hosting
service such as Upload
Screenshot and post the URL to your uploaded image.

Be polite and don't
demand that others answer your question.

It is considered
rude to DM (direct message) someone who does not know you. If no one
answers your question, don't start DMing people you don't know.

The first time you join a channel, it is okay
to say hi and introduce yourself.

8.4
Listy mailingowe

Mailing lists are a handy way to discuss problems,
solutions, and requested features as they create a searchable archive
of discussions. The PC-BSD Project offers the following mailing
lists to cover a wide variety of discussion topics:

Announcements: a read-only, low frequency list used by the PC-BSD team to make
announcements to the community.

Commits: lists SVN commits as PC-BSD code is added or modified by developers.

Each mailing list includes a description of topics
suitable for discussion on that list and indicates if it is read only
or available for user discussion. Anyone can read the archives for a
list. If you wish to send an email to mailing list, you will need to
first subscribe to the list. The link for each mailing list provides
an interface for subscribing to that list. When you send an email to
the list, remember to use the mailing address that you used when you
subscribed to the list.

Several of the mailing lists are archived at gmane.
Gmane allows you to read the archives in several different formats.
It also provides RSS feeds in various formats for keeping up-to-date
on new messages and topics.

Apart from these official mailing lists, there's
also a number of non-official mailing lists set up by PC-BSD users.
Many of these lists are designed for discussion in other languages. A
list of alternative PC-BSD mailing lists can be found here.

8.5
Podręcznik FreeBSD oraz FAQ

PC-BSD has FreeBSD as its underlying operating
system, so everything in the FreeBSD
Handbook and FreeBSD
FAQ applies to PC-BSD as well. Both are very comprehensive and
cover nearly every task you can accomplish on a FreeBSD system. They
are also an excellent resource for learning how things work "under
the hood" of your PC-BSD system.

Zapamiętaj: some configurations
described in the FreeBSD Handbook already "just work" on
your PC-BSD system as they have been pre-configured for you. In these
instances, reading that FreeBSD Handbook section can help you to
understand how your system was configured and how it works.

8.6 Portale
społecznościowe

The PC-BSD project maintains several social media
sites to help users to keep up-to-date with what is happening and to
provide venues for developers and users to network with each other:

9 Jak
możesz wspomóc PC-BSD

PC-BSD is a community project and relies on
involvement from its users and supporters. This section lists some
ideas for becoming involved. We also have a list of Tasks
Looking for People if you are looking for a specific task to
assist with.

zostać betatesterem

zostać tłumaczem

zostać developerem

zgłaszać błędy

zgłaszać zapotrzebowanie na określone pakiety PBI

testować pakiety PBI

tworzyć pakiety PBI

wpłacić pieniądze na rozwój projektu

prowadzić serwer lustrzany

informować o PC-BSD

9.1
Zostań betatesterem

If you like playing around with operating systems
and have a bit of spare time, one of the most effective ways you can
assist the project is by reporting problems you encounter using the
current release of PC-BSD.

If you have a spare system or virtual machine, you
can also download and try out the latest alpha, beta or release
candidate snapshots. These versions are still in testing and haven't
been officially released yet. Having as many people as possible using
PC-BSD on many different hardware configurations assists the project
in finding and fixing bugs. This makes using PC-BSD better for
everyone.

Zapamiętaj: As of November, 2010, alpha
testing snapshots for the upcoming 8.2 and 9.0 releases are available
and are updated every few weeks to address bug reports. PC-BSD
releases occur shortly after the FreeBSD release to allow for some
extra testing. Currently, the projected release date for 8.2 is
January 2011 and for 9.0 is June or July 2011. Subscribing to thePC-BSD blog is a good way to
keep up-to-date on the availability of testing snapshots and any
major bugs that are found within a snapshot.

If becoming a tester interests you, subscribe to thetesting
mailing list. As new testing versions become available they will
be announced on this list. You will also be able to see what problems
other testers are finding and can check to see if the problem exists
on your hardware as well. You can also subscribe to Gmane's
RSS feeds if you want a quick way to keep up with the subjects
being discussed on the testing mailing list.

Anyone can become a beta tester. Follow these tips
so that you can accurately describe your findings so they can be
fixed as soon as possible:

before sending an
email, search the testing mailing list to see if anyone else has
reported a similar problem.

when reporting a new
issue, use a descriptive subject in your email that includes the
error and the version of PC-BSD. Ideally, the subject is short (8 or
less words) and contains key words about the error. An example would
be "Warden on 8.1 fails to export jail".

ensure that the body
of your email includes the PC-BSD version and architecture (e.g. 8.1
RC2, 64 bit version).

give a short (2-3
sentences) description of how to recreate the error (e.g. when I
right click a jail in warden and select Export jail to a .wdn file,
it lets me select a file name, but then it freezes). If there is an
error message, include its text.

include any other
info that may be useful (e.g. this seems to work on my 32 bit system
or this used to work on 8.0).

if the problem appears to be hardware related,
include a copy of /var/run/dmesg.boot as this file shows the
hardware that was probed the last time the PC-BSD system booted.

9.2
Zostań tłumaczem

PC-BSD uses Pootlefor managing localization of the menu screens used by the installer
and the PC-BSD utilities. Pootle makes it possible to find out if
your native language has been fully localized for PC-BSD. Pootle also
makes it easy for users to check and submit translated text as it
provides a web editor and commenting system. This means that
translators can spend their time making and reviewing translations
rather than learning how to use a translation tool.

The localizations PC-BSD users have requested are listed
alphabetically on the left. If your language is missing and you would
like to help in its translation, send an email to the translations
mailing list so it can be added.

The green bar in the Overall Completion column indicates the
percentage of PC-BSD menus that have been localized. If a language is
not at 100%, it means that the menus that currently aren't translated
will appear in English instead of in that language.

If you click on a language name then click on the
pcbsd hyperlink under the "Name" column, you'll see each
menu item that is available for translation. The example shown in
Zdjęcie 9.2b is for the Greek localization:

Zdjęcie 9.2b: Przegląd postępu prac nad tłumaczeniem kolejnych
plików

In this example, the menu for CrashHandler is
complete, but the one for LifePreserver is not.

If you click on the Review tab, you'll see a list of
statistics as seen in Zdjęcie 9.2c. This page will indicate the
results of Pootle's quality checks, helping translators to notice any
problematic items. A description of each quality check can be foundhere.

If you wish to help localize your language, you
should first join the translations
mailing list and introduce yourself and which language(s) you can
assist with. This will allow you to meet other volunteers as well as
keep abreast of any notices or updates that may affect the
translations. You will also need to create a Pootle login account.

Once you are logged in to Pootle, navigate to the
menu item that you wish to translate. Zdjęcie 9.2d continues the
earlier example by clicking on the link for the Greek version of
LifePreserver.po.

Zdjęcie 9.2c: Przegląd Reviewing a Language's Quality Checks

In this example, the first string (the word
Disabled) has been translated but is failing 2 of the quality checks.
The translator can check the correctness of the translation as well
as fix the whitespace and double-spacing issue. Once finished, the
translator can click the "Add Comment" link to type in an
optional comment then press the "Submit" button to save any
changes. Each text field (string) in the menu is numbered--click on
the hyperlink associated with the number to open that text field in
the Pootle editor, or use the Next and Previous links to navigate
between text fields.

If you need help
with a translation or using the Pootle system, you can ask for help
on the translations mailing list or in the PC-BSD
Translations Forum.

9.3
Zostań developerem

If you like programming, and especially coding on
FreeBSD, we'd love to see you join the PC-BSDTeam as a
PC-BSD committer. Developers who want to help improve the PC-BSD
codebase are always welcome! If you would like to take part in core
development, and possibly earn a commit bit, a good place to get
started is by signing up for the developers
mailing list. Once you've signed up feel free to browse our
active TODO
list, or search for bugs that need fixing in the PC-BSD Trac
database. If you see something of interest you want to work on,
or have a proposal for a project you wish to add to PC-BSD, please
feel free to let us know via the developers list and we'll be happy
to help get you started.

Most of the PC-BSD specific GUI tools are developed
in C++ using the QT Libraries, and other non-GUI development is done
using standard Bourne shell scripts. There may be cases where other
languages or libraries are needed, but those will be evaluated on a
case-by-case basis, so feel free to let us know your proposals on the
developers mailing list.

The first is a packaging bug, which is when you
cannot install the application or it simply crashes on startup. For
these types of bugs, please report them on our Trac
Database (after logging in) and for the Type, select "PBI
Packaging Bug". Please provide as much detail as possible about
the bug, such as:

Name of Program

What version of PC-BSD you are
running

What architecture you are using
(32bit or 64bit)

Detailed description of the bug, including a copy of the
crash logfile, if generated

Application Runtime Bug

An application runtime bug occurs when an
application installs and is able to start successfully, but during
use, it crashes or displays some other type of undesired behavior. An
example would be OpenOffice failing to import a type of document
properly or a chat client unable to keep a connection to a network.
These types of bugs are best reported to the developers of the
application. The best way to locate them is by searching for your
application in Software Manager, then clicking the "Vendor"
link. Most software sites have a "bug report" link or
another way to contact the original developer to report your issue.

A system bug is any bug which prevents the initial
installation of PC-BSD or issues with hardware. Some examples would
be a non-bootable system, failed installation, missing drivers for
your hardware, or a non-functional desktop after installation. To
report this type of issue, please follow the instructions below for
your type of system bug:

System Driver Bugs

An example of a driver bug would be a missing
network driver, no sound output, or no disk drives detected. Most of
these types of issues are directly related to the FreeBSD base upon
which PC-BSD is built, and are best fixed by discussing them with the
FreeBSD team directly. Reporting a bug to FreeBSD can be done using
the Send PR page.
You should also search the FreeBSD mailing lists as other users may
have already discovered the bug or have a work-around for your
particular hardware. Below are some of the related mailing lists:

9.5 Uzupełnij
listę życzeń PBI

Is an application that you need not currently
available as a PBI? Making a PBI request is an excellent way to let
PBI developers know which applications are most useful to PC-BSD
users. Before requesting a PBI, please do the following:

check in Software
Manager to see if a PBI already exists. If one does but you want to
request a more recent version, please say so in your request.

search at Freshports to see if there is an existing FreeBSD package as it is much easier
and quicker to make a PBI from an existing package. If a package
does not already exist, please say so in your request.

To make your request, start a new thread in the PBI
Requests Forum. If this is your first forum post, you will need
to use the Register hyperlink to create a username and password so
you can login to make your request.

Zapamiętaj: you don't need to login to
read the content in the PC-BSD forums; you do have to login in order
to start a new thread or respond to an existing one.

Once you have submitted your request, click the
Thread Tools link -> Subscribe to this Thread -> and select
your Notification Type so that you can be notified of any responses
to your request. If you would like to receive notifications about all
of the PBI requests in this forum, click Forum Tools -> Subscribe
to this Forum while in the forum.

When creating a new forum thread, include the name
of the PBI you are requesting in the thread name. That way it is easy
for PBI developers and other PC-BSD users to know which applications
have been requested.

People who create PBIs are subscribed to both the
PBI Requests forum. Usually, someone will respond to a request within
a few days either indicating that they are working on creating the
PBI or with an explanation if creating a PBI will be problematic. The
PBI process is as follows:

once the PBI is built, PBI testers test for
basic functionality such as verifying that the application starts
and its menus appear to be present and working

once the PBI is tested, the PBI is uploaded to
PBIDir so it can be available
in Software Manager

once the PBI is uploaded, the PBI request is
moved from the PBI Requests Forum to the Finished
PBIs forum

Please note that it takes at least 2-7 days for a
new PBI to go from step 3 to step 7 as it needs to be fully tested.
If there is a delay, that usually means that a problem was found in
the PBI and that the testers are trying to resolve the problem.

The next section explains how you can assist in the
PBI testing process.

If you wish to be notified whenever a new PBI is
added or an existing one is upgraded to a newer version, subscribe to
the Latest
PBI RSS feed.

9.6
Testowanie paczek PBI

The previous section indicated that new PBI modules
are uploaded to the PBI build server. There are actually several
build locations, according to PC-BSD version and architecture:

First, if you wish to help test a PBI before it has
been approved, go to the build location for your version and
architecture. Find the name of the PBI you wish to test in the Module
column and click its hyperlink. You can then download the file with
the .pbi extension. If you double-click the downloaded PBI in
Dolphin, it will install the PBI for you. If you find any problems
with the PBI, send an email to the PBI-devmailing list describing how to recreate the problem. Include the text
of any error messages you receive.

Zdjęcie 9.6a: Przeglądanie statusu paczek PBI na Build Server

Second, you can try to resolve PBI modules that have
a Build Status of FAILED. If you click on the name of a failed
module, you can download the build.log.bz2 for that module. To access
this file, you can either:

bunzip2 build.log.bz2 to unzip the file so you can send it
to a text processor to read it.

lub

bzcat build.log.bz2 to read the file without
unzipping it. It will scroll down to the end, where the error
occurred. Use bzcat build.log.bz2 | more if you prefer to
scroll through the file.

If you think you know the cause of the problem after
reading the error messages, you will need the module itself to try to
resolve the problem. Modules are located in the PC-BSD subversion
repository. To download the module, you can use the svncommand. To give an example, the math/scilab PBI was flagged as
FAILED in Zdjęcie X-XX. To download that module, cd to a suitable
directory and issue the following command. Note that the svncommand uses the svn:// URI (instead of http://) and does not include
the /browser/ section you see in the URL if you use your web browser
to browse the modules.

svn co
svn://svn.pcbsd.org/pbibuild/modules/math/scilab

This example command will create a directory called
scilab and place the module's files in that directory. If you make
changes to these files to correct the problem, create a tar.gz of the
directory and send the tarball to the PBI-devmailing list so the changes can be uploaded to the build server.

9.8 Wpłać
dotację

To help the PC-BSD project financially, why not
consider making a donation if you're happy with our product?
Alternatively you can buy your PC-BSD installation CD/DVD and cool
stuff from FreeBSD
Mall, PC-BSD's sister company. Companies may consider buying
professional support from iXsystems.

Zapamiętaj: You don't have to run a server to help
increase download speeds for other users. PC-BSD is also distributed
as a torrent and you can help us
with seeding, especially the first two weeks after a new release. If
you're new to seeding, check out the FAQ.

Mirrors are the lifeblood of any open source project such as
PC-BSD. If you have a system with a high-speed connection, 150-200GB
of space, and the ability to rsync with a host, then we need
you!

Jeśli uruchomisz proces rsync, to proszę nas o tym poinformować drogą mailową kris@pcbsd.org letting him know of the
mirror URL so the new mirror can get listed and become available to
users.

9.10 Propaguj
projekt PC-BSD

So you love PC-BSD? Why not tell the world about it?
Your family, your friends, fellow students and colleagues? You won't
be the only one that likes a free, virus-free, spyware-free and
adware-free operating system. Here are some suggestions to get you
started: