Changeset 48494e9


Ignore:
Timestamp:
03/04/15 10:58:55 (3 months ago)
Author:
dlavigne <dru@…>
Branches:
master, enter/10, releng/10.1.2
Children:
d1718ea
Parents:
a88635f
Message:

More cleanup of update chapter.

Location:
docs
Files:
1 added
1 edited
13 moved

Legend:

Unmodified
Added
Removed
  • docs/update.rst

    ra88635f r48494e9  
    279279============== 
    280280 
    281 Update Manager provides a graphical interface for keeping the PC-BSD®  This utility can be started from Control Panel or by typing **pc-updategui**. 
    282 It can also be accessed from its icon in the system tray, if you are logged into a desktop that provides a system tray. 
    283  
    284  
    285 The status of the icon lets you determine at a glance if any of your installed applications are out-of-date, if a system update is available, or if a new version of the operating system is available. 
    286 Table 7.2a summarizes the possible statuses of this icon. 
    287  
    288  
    289 .. image:: images/picture_93.png 
    290  
    291 +------------------+--------------------------------------------------------------------------------------------------------------+ 
    292 |                  | \|picture_98\|your system is up\-to\-date                                                                    | 
    293 +------------------+--------------------------------------------------------------------------------------------------------------+ 
    294 |                  | \|picture_177\|the system is currently checking for updates and patches                                      | 
    295 +------------------+--------------------------------------------------------------------------------------------------------------+ 
    296 |                  | your operating system is out\-of\-date and system update(s) or patch(es) are available                       | 
    297 +------------------+--------------------------------------------------------------------------------------------------------------+ 
    298 | \|picture_92\|   | \|picture_195\|newer versions of installed applications are available                                        | 
    299 +------------------+--------------------------------------------------------------------------------------------------------------+ 
    300 |                  | \|picture_137\|the system was unable to check for updates, meaning you should check your Internet connection | 
    301 +------------------+--------------------------------------------------------------------------------------------------------------+ 
    302 |                  | the system is currently updating                                                                             | 
    303 +------------------+--------------------------------------------------------------------------------------------------------------+ 
    304 | \|picture_147\|  | the system needs to restart in order for the newly installed update to take effect                           | 
    305 +------------------+--------------------------------------------------------------------------------------------------------------+ 
    306  
    307 If you right-click the icon, you will see the menu shown in Figure 7.2a. As seen in the menu, Update Manager will automatically track updates to software installed using either the graphical or command line equivalents of  and .  
    308  
    309 **Figure 7.****2****a: Right-click Menu for Update Manager**  
    310  
    311 .. image:: images/picture_186.png 
    312  
    313 By default, updates are checked every 24 hours or 20 minutes after booting the system. 
    314 However, the system won't check for updates more than once per day should you reboot multiple times within a day. 
    315 You can check for updates now by selecting “Check for Updates”. To disable the update check when the system boots, uncheck the “Run at Startup” box. 
    316 To disable the pop-up message over the icon when an update becomes available, uncheck the “Display Notifications” box. 
    317 To also be notified when updates are available to running jails, check the “Check Jails” box. 
    318 To remove Update Manager from the system tray, click “Quit”. You can put the icon back into the tray by typing **pc-systemupdatertray &**. 
     281Update Manager provides a graphical interface for keeping the PC-BSD® operating system and its installed applications up-to-date. This utility can be started 
     282from :ref:`Control Panel` or by typing :command:`pc-updategui`. It can also be accessed from its icon in the system tray, if you are logged into a desktop 
     283that provides a system tray. 
     284 
     285The status of the icon lets you determine at a glance if any of your installed applications are out-of-date, if a system update is available, or if a new 
     286version of the operating system is available. The possible statuses are as follows: 
     287 
     288.. image:: images/update1.png  
     289Your system is up-to-date. 
     290 
     291.. image:: images/update2.png  
     292The system is currently checking for updates and patches. 
     293 
     294.. image:: images/update3.png  
     295Your operating system is out-of-date and system update(s) or patch(es) are available. 
     296 
     297.. image:: images/update4.png  
     298Newer versions of installed applications are available. 
     299 
     300.. image:: images/update5.png  
     301The system was unable to check for updates, meaning you should check your Internet connection. 
     302 
     303.. image:: images/update6.png 
     304The system is currently updating. 
     305 
     306.. image:: images/update7.png  
     307The system needs to restart in order for the newly installed update to take effect. 
     308 
     309If you right-click the icon, you will see the menu shown in Figure 7.2a. As seen in the menu, Update Manager will automatically track updates to software 
     310installed using either the graphical or command line equivalents of :ref:`AppCafe®` and :ref:`Warden®`. 
     311 
     312**Figure 7.2a: Right-click Menu for Update Manager**  
     313 
     314.. image:: images/update8.png 
     315 
     316By default, updates are checked every 24 hours or 20 minutes after booting the system. However, the system won't check for updates more than once per day 
     317should you reboot multiple times within a day. You can check for updates now by selecting "Check for Updates". To disable the update check when the system 
     318boots, uncheck the "Run at Startup" box. To disable the pop-up message over the icon when an update becomes available, uncheck the "Display Notifications" 
     319box. To also be notified when updates are available to running jails, check the "Check Jails" box. To remove Update Manager from the system tray, click 
     320"Quit". You can put the icon back into the tray by typing :command:`pc-systemupdatertray &`. 
    319321 
    320322.. index:: updates 
     
    324326--------------------------- 
    325327 
    326 The PC-BSD® update mechanism provides several safeguards to ensure that updating the operating system or its software is a low-risk operation. 
    327 Beginning with version 10.1.1, the following steps occur automatically during an update:  
    328  
    329 - the update automatically creates a copy of the current operating system, known as a snapshot or boot environment, and mounts that snapshot in the background. 
    330   All of the updates then occur in the snapshot. 
    331   This means that you can safely continue to use your system while it is updating as no changes are being made to the operating system or any of the applications currently in use. 
    332   Instead, all changes are being made to the mounted copy. 
    333    
    334  
    335 - once the update is complete, the new boot environment, or updated snapshot, is added as the first entry in the boot menu and activated so that the system will boot into it, unless you pause the boot menu and specify otherwise. 
    336   A pop-up message, shown in Figure 7.2b, will indicate that a reboot is required. 
    337   You can either finish what you are doing and reboot now into the upgraded snapshot, or ask the system to remind you again at a later time. 
    338   To configure the time of the next warning, click the “Next Reminder” drop-down menu where you can select 1, 5, 12, or 24 hours, 30 minutes, or never (for this login session). 
    339   Note that the system will not apply any more updates or allow you to start another manual update or install additional software using AppCafe® until you reboot. 
    340    
    341  
    342 - as the update is running, a log is written to */var/log/pc-updatemanager.log* and is then saved to */var/log/pc-updatemanager-auto.log* when the update is complete. 
    343   This way you can see which software is being updated and if there are any updating errors. 
    344   The logs can also be viewed in the “View Log” tab of the graphical Update Manager utility, shown in Figure 7.2c.  
    345  
    346 - you no longer need to initiate updates manually. 
    347   PC-BSD® now uses an automated updater that automatically checks for updates, no more than once per day, 20 minutes after a reboot and then every 24 hours. 
    348   You can configure what gets updated using the “Configure Automatic Updates” tab of Update Manager, shown in Figure 7.2d. Choices are “Security & Packages” (all updates), “Security” (only security patches and operating system updates), “Packages” (only installed software), or “Nothing” (disables automatic updating). 
    349  
    350 Figure 7.2b: Managing the Reboot After Update 
    351  
    352 .. image:: images/picture_136.png 
    353  
    354 Figure 7.2c: Viewing the Update Log 
    355  
    356 .. image:: images/picture_26.png 
    357  
    358 Figure 7.2d: Configuring What to Update 
    359  
    360 .. image:: images/picture_154.png 
    361  
    362 Updates can still be initiated manually using either a GUI or a command-line application. 
    363 The rest of this section demonstrates how to manually update using either the GUI or the command-line method. 
     328The PC-BSD® update mechanism provides several safeguards to ensure that updating the operating system or its software is a low-risk operation. Beginning with 
     329version 10.1.1, the following steps occur automatically during an update:  
     330 
     331* the update automatically creates a copy of the current operating system, known as a snapshot or boot environment, and mounts that snapshot in the 
     332  background. All of the updates then occur in the snapshot. This means that you can safely continue to use your system while it is updating as no changes are 
     333  being made to the operating system or any of the applications currently in use. Instead, all changes are being made to the mounted copy. 
     334 
     335* once the update is complete, the new boot environment, or updated snapshot, is added as the first entry in the boot menu and activated so that the system 
     336  will boot into it, unless you pause the boot menu and specify otherwise. A pop-up message, shown in Figure 7.2b, will indicate that a reboot is required. 
     337  You can either finish what you are doing and reboot now into the upgraded snapshot, or ask the system to remind you again at a later time. To configure the 
     338  time of the next warning, click the "Next Reminder" drop-down menu where you can select 1, 5, 12, or 24 hours, 30 minutes, or never (for this login 
     339  session). Note that the system will not apply any more updates or allow you to start another manual update or install additional software using AppCafe® 
     340  until you reboot. 
     341 
     342* as the update is running, a log is written to :file:`/var/log/pc-updatemanager.log` and is then saved to :file:`/var/log/pc-updatemanager-auto.log` when the 
     343  update is complete. This way you can see which software is being updated and if there are any updating errors. The logs can also be viewed in the "View Log" 
     344  tab of the graphical Update Manager utility, shown in Figure 7.2c.  
     345 
     346* you no longer need to initiate updates manually. PC-BSD® now uses an automated updater that automatically checks for updates, no more than once per day, 20 
     347  minutes after a reboot and then every 24 hours. You can configure what gets updated using the "Configure Automatic Updates" tab of Update Manager, shown in 
     348  Figure 7.2d. Choices are "Security & Packages" (all updates), "Security" (only security patches and operating system updates), "Packages" (only installed 
     349  software), or "Nothing" (disables automatic updating). 
     350 
     351**Figure 7.2b: Managing the Reboot After Update** 
     352 
     353.. image:: images/update9.png 
     354 
     355**Figure 7.2c: Viewing the Update Log** 
     356 
     357.. image:: images/update10.png 
     358 
     359**Figure 7.2d: Configuring What to Update** 
     360 
     361.. image:: images/update11.png 
     362 
     363Updates can still be initiated manually using either a GUI or a command-line application. The rest of this section demonstrates how to manually update using 
     364either the GUI or the command-line method. 
    364365 
    365366.. index:: updates 
     
    369370--------------------------- 
    370371 
    371 Beginning in version 10.1.1, the automatic updater will automatically keep your system up-to-date. 
    372 You will know that an update has completed when the pop-up menu, shown in Figure 7.2b, indicates that a reboot is needed to complete the update process. 
    373 The automatic updater will only update what it has been configured to update. 
    374 If you would like to double-check or change what gets updated, start Update Manager, enter your password, and use the drop-down menu in the “Configure Automatic Updates” screen shown in Figure 7.2d.  
    375  
    376 Due to its schedule, the automatic updater will never check for new updates more than once in a 24 hour period. 
    377 To manually check for updates, right-click the Update Manager in system tray and click “Check for Updates”. Alternatively, start Update Manager. 
    378 If any updates are available, an “Updates Available” tab will appear, as seen in the example in Figure 7.2e. If no updates are available, this tab will not appear. 
    379  
    380  
    381 Figure 7.2e: System Updates are Available 
    382  
    383 .. image:: images/picture_130.png 
    384  
    385 In this example, the system has been configured to automatically update “Security & Packages” and a security update is available. 
    386 Click the “Start Updates” button to manually start the update. 
    387 When prompted, reboot so that the system can boot into the newly patched operating system. 
    388  
    389  
    390 Figure 7.2f shown an example of a system that has package updates available. 
    391 The user has clicked the “View Package Updates” box to see which packages will be upgraded. 
    392  
    393  
    394 Figure 7.2e: Package Updates are Available 
    395  
    396 .. image:: images/picture_270.png 
    397  
    398 **NOTE: **how often package updates are available depends upon the “Repository Settings” set in AppCafe® → Configure. 
    399 The default setting of “Production” will only provide package updates every 3 months whereas a setting of “Edge” will provide package updates as soon as a new version is available. 
    400 If you need application stability, stay on “Production”. If you can handle some application breakage in favor of having the latest software, change to “Edge”. Also, if you select “Security” or “Nothing” in the “Configure Automatic Updates” tab of Update Manager, packages will only get updated with the next software release which happens every 3 months. 
    401  
    402  
    403 **DANGER!** package updates will update **all**** **installed software, even if you have placed a lock on it in using **pkg** or an older version of AppCafe®. If you prefer to lock certain applications against being updated, select “Security” or “Nothing” in the “Configure Automatic Updates” tab of Update Manager and manually update software as needed using **pkg**. 
    404 Note that updating the operating system will still update any locked applications. 
     372Beginning in version 10.1.1, the automatic updater will automatically keep your system up-to-date. You will know that an update has completed when the pop-up 
     373menu, shown in Figure 7.2b, indicates that a reboot is needed to complete the update process. The automatic updater will only update what it has been 
     374configured to update. If you would like to double-check or change what gets updated, start Update Manager, enter your password, and use the drop-down menu in 
     375the "Configure Automatic Updates" screen shown in Figure 7.2d.  
     376 
     377Due to its schedule, the automatic updater will never check for new updates more than once in a 24 hour period. To manually check for updates, right-click the 
     378Update Manager in system tray and click "Check for Updates". Alternatively, start Update Manager. If any updates are available, an "Updates Available" tab 
     379will appear, as seen in the example in Figure 7.2e. If no updates are available, this tab will not appear. 
     380 
     381**Figure 7.2e: System Updates are Available** 
     382 
     383.. image:: images/update12.png 
     384 
     385In this example, the system has been configured to automatically update "Security & Packages" and a security update is available. Click the "Start Updates" 
     386button to manually start the update. When prompted, reboot so that the system can boot into the newly patched operating system. 
     387 
     388Figure 7.2f shown an example of a system that has package updates available. The user has clicked the "View Package Updates" box to see which packages will be 
     389upgraded. 
     390 
     391**Figure 7.2e: Package Updates are Available** 
     392 
     393.. image:: images/update13.png 
     394 
     395.. note:: how often package updates are available depends upon the "Repository Settings" set in :menuselection:`AppCafe® --> Configure`. The default setting 
     396   of "Production" will only provide package updates every 3 months whereas a setting of "Edge" will provide package updates as soon as a new version is 
     397   available. If you need application stability, stay on "Production". If you can handle some application breakage in favor of having the latest software, 
     398   change to "Edge". Also, if you select "Security" or "Nothing" in the "Configure Automatic Updates" tab of Update Manager, packages will only get updated 
     399   with the next software release which happens every 3 months. 
     400 
     401.. warning:: package updates will update **all** installed software, even if you have placed a lock on it in using :command:`pkg` or an older version of 
     402   AppCafe®. If you prefer to lock certain applications against being updated, select "Security" or "Nothing" in the "Configure Automatic Updates" tab of 
     403   Update Manager and manually update software as needed using :command:`pkg`. Note that updating the operating system will still update any locked 
     404   applications. 
    405405 
    406406.. index:: updates 
     
    410410--------------------------- 
    411411 
    412 TrueOS® users, or those who prefer to use a command-line utility, can use **pc-updatemanager** to manually apply updates. 
    413 If you type **pc-updatemanager**, it will show its available options:  
    414  
    415 pc-updatemanager 
    416  
    417 /usr/local/bin/pc-updatemanager - Usage 
    418  
    419 ---- 
    420  
    421 branches - List available system branches 
    422  
    423 chbranch <tag> - Change to new system branch 
    424  
    425 check - Check for system updates 
    426  
    427 install <tag>,<tag2> - Install system updates 
    428  
    429 pkgcheck - Check for updates to packages 
    430  
    431 pkgupdate - Install packages updates  
    432  
    433 syncconf - Update PC-BSD pkgng configuration  
    434  
    435 confcheck - Check PC-BSD pkgng configuration 
    436  
    437 -j <jail> - Operate on the jail specified 
    438  
    439 To determine if any system updates are available, type the following command:  
    440  
    441 sudo pc-updatemanager check 
    442  
    443 Checking for FreeBSD updates... The following updates are available:  
    444  
    445 -------------------------------------------------------------------- 
    446  
    447 NAME: FreeBSD system update  
    448  
    449 TYPE: System Update  
    450  
    451 Install: "freebsd-update fetch && freebsd-update install"  
    452  
    453 NAME: Remove fdescfs  
    454  
    455 TYPE: PATCH  
    456  
    457 TAG: fdesc-rollback-02132014  
    458  
    459 DETAILS: http://trac.pcbsd.org/wiki/patch-20140211-fdesc  
    460  
    461 DATE: 02-13-2014  
    462  
    463 SIZE: 1Mb  
    464  
    465 To install: "pc-updatemanager install fdesc-rollback-02132014"  
    466  
    467 NAME: PKG conflict detection bug fixes  
    468  
    469 TYPE: PATCH  
    470  
    471 TAG: pkgng-conflict-03122014  
    472  
    473 DETAILS: http://trac.pcbsd.org/wiki/patch-20140312-updater  
    474  
    475 DATE: 03-12-2014  
    476  
    477 SIZE: 1Mb  
    478  
    479 To install: "pc-updatemanager install pkgng-conflict-03122014" 
    480  
    481 If any updates are available, follow the instructions to install each update. 
    482 For example, this will apply the “Remove fdescfs” patch:  
    483  
    484 **sudo pc-updatemanager install fdesc-rollback-02132014**  
    485  
    486 DOWNLOADING: fdesc-rollback-02132014 /usr/local/tmp/patch-fdesc-rollback-02132014.t100% of 312 B 14 kBps 00m00s  
    487  
    488 DOWNLOADFINISHED: fdesc-rollback-02132014  
    489  
    490 Creating new boot-environment...  
    491  
    492 GRUB configuration updated successfully  
    493  
    494 Created successfully  
    495  
    496 Pruning old boot-environments...  
    497  
    498 TOTALSTEPS: 3  
    499  
    500 SETSTEPS: 1  
    501  
    502 umount: /dev/fd: not a file system root directory  
    503  
    504 SETSTEPS: 3  
    505  
    506 INSTALLFINISHED: fdesc-rollback-02132014  
    507  
    508 If no system updates are available, the **check** command will indicate “Your system is up to date!”.  
    509  
    510 To determine if package updates are available, use this command:  
    511  
    512 sudo pc-updatemanager pkgcheck 
    513  
    514 Updating repository catalogue 
    515  
    516 Upgrades have been requested for the following 253 packages: 
    517  
    518 <list of packages snipped> 
    519  
    520 The upgrade will require 70 MB more space 
    521  
    522 439 MB to be downloaded 
    523  
    524 To start the upgrade run "/usr/local/bin/pc-updatemanager pkgupdate" 
    525  
    526 In this example, newer versions are available for 253 packages. 
    527 The list of package names was snipped from the sample output. 
    528 If no updates were available, the output would have instead said “All packages are up to date!”.  
    529  
    530 If updates are available, you can install them with this command:  
    531  
    532 sudo pc-updatemanager pkgupdate 
    533  
    534 Updating repository catalogue 
    535  
    536 snip downloading and reinstalling output 
    537  
    538 [253/253] Upgrading pcbsd-base from 1374071964 to 1378408836... done 
    539  
    540 Extracting desktop overlay data...DONE 
    541  
    542 While the output has been snipped from this example, the update process will download the latest versions of the packages which need updating, displaying the download progress for each file. 
    543 Once the downloads are complete, it will display the reinstallation process for each file. 
    544 The last step of the update process is to extract the desktop (or server) overlay and then to return the prompt. 
    545 After performing any updates, reboot the system. 
     412TrueOS® users, or those who prefer to use a command-line utility, can use :command:`pc-updatemanager` to manually apply updates. If you type 
     413:command:`pc-updatemanager`, it will show its available options:: 
     414 
     415 pc-updatemanager 
     416 /usr/local/bin/pc-updatemanager - Usage 
     417 ---- 
     418 branches - List available system branches 
     419 chbranch <tag> - Change to new system branch 
     420 check - Check for system updates 
     421 install <tag>,<tag2> - Install system updates 
     422 pkgcheck - Check for updates to packages 
     423 pkgupdate - Install packages updates  
     424 syncconf - Update PC-BSD pkgng configuration  
     425 confcheck - Check PC-BSD pkgng configuration 
     426 -j <jail> - Operate on the jail specified 
     427 
     428To determine if any system updates are available, type the following command:: 
     429 
     430 sudo pc-updatemanager check 
     431 Checking for FreeBSD updates... The following updates are available:  
     432 -------------------------------------------------------------------- 
     433 NAME: FreeBSD system update  
     434 TYPE: System Update  
     435 Install: "freebsd-update fetch && freebsd-update install"  
     436 NAME: Remove fdescfs  
     437 TYPE: PATCH  
     438 TAG: fdesc-rollback-02132014  
     439 DETAILS: http://trac.pcbsd.org/wiki/patch-20140211-fdesc  
     440 DATE: 02-13-2014  
     441 SIZE: 1Mb  
     442 
     443 To install: "pc-updatemanager install fdesc-rollback-02132014"  
     444 NAME: PKG conflict detection bug fixes  
     445 TYPE: PATCH  
     446 TAG: pkgng-conflict-03122014  
     447 DETAILS: http://trac.pcbsd.org/wiki/patch-20140312-updater  
     448 DATE: 03-12-2014  
     449 SIZE: 1Mb  
     450 To install: "pc-updatemanager install pkgng-conflict-03122014" 
     451 
     452If any updates are available, follow the instructions to install each update. For example, this will apply the "Remove fdescfs" patch:: 
     453 
     454 sudo pc-updatemanager install fdesc-rollback-02132014 
     455 DOWNLOADING: fdesc-rollback-02132014 /usr/local/tmp/patch-fdesc-rollback-02132014.t100% of 312 B 14 kBps 00m00s  
     456 DOWNLOADFINISHED: fdesc-rollback-02132014  
     457 Creating new boot-environment...  
     458 GRUB configuration updated successfully  
     459 Created successfully  
     460 Pruning old boot-environments...  
     461 TOTALSTEPS: 3  
     462 SETSTEPS: 1  
     463 umount: /dev/fd: not a file system root directory  
     464 SETSTEPS: 3  
     465 INSTALLFINISHED: fdesc-rollback-02132014  
     466 
     467If no system updates are available, the **check** command will indicate "Your system is up to date!".  
     468 
     469To determine if package updates are available, use this command:: 
     470 
     471 sudo pc-updatemanager pkgcheck 
     472 Updating repository catalogue 
     473 Upgrades have been requested for the following 253 packages: 
     474 <list of packages snipped> 
     475 The upgrade will require 70 MB more space 
     476 439 MB to be downloaded 
     477 To start the upgrade run "/usr/local/bin/pc-updatemanager pkgupdate" 
     478 
     479In this example, newer versions are available for 253 packages. The list of package names was snipped from the sample output. If no updates were available, 
     480the output would have instead said "All packages are up to date!".  
     481 
     482If updates are available, you can install them with this command:: 
     483 
     484 sudo pc-updatemanager pkgupdate 
     485 Updating repository catalogue 
     486 snip downloading and reinstalling output 
     487 [253/253] Upgrading pcbsd-base from 1374071964 to 1378408836... done 
     488 Extracting desktop overlay data...DONE 
     489 
     490While the output has been snipped from this example, the update process will download the latest versions of the packages which need updating, displaying the 
     491download progress for each file. Once the downloads are complete, it will display the reinstallation process for each file. The last step of the update 
     492process is to extract the desktop (or server) overlay and then to return the prompt. After performing any updates, reboot the system. 
    546493 
    547494.. index:: updates 
     
    551498-------------------------- 
    552499 
    553 PC-BSD® has switched to ZFS-only. 
    554 This means that you can not upgrade a system that is either 32-bit or formatted with UFS. 
    555 If the hardware supports 64-bit, you will need to backup your important data to another system or external drive and then perform a new installation. 
    556 The new installation will perform a format of the selected disk(s) with ZFS. 
    557  
    558 The boot loader and default ZFS layout has changed to support  and ZFS snapshot management with . For this reason, 9.x users should backup their important data to another system or external drive and then perform a new installation which will create the required ZFS layout. 
     500PC-BSD® has switched to ZFS-only. This means that you can **not** upgrade a system that is either 32-bit or formatted with UFS. If the hardware supports 
     50164-bit, you will need to backup your important data to another system or external drive and then perform a new installation. The new installation will perform 
     502a format of the selected disk(s) with ZFS. 
     503 
     504The boot loader and default ZFS layout has changed to support :ref:`Boot Manager` and ZFS snapshot management with :ref:`Life Preserver`. For this reason, 9.x 
     505users should backup their important data to another system or external drive and then perform a new installation which will create the required ZFS layout. 
    559506 
    560507.. index:: updates 
     
    564511----------------------------- 
    565512 
    566 Upgrading from any 10.x version to 10.1.1 is the same as applying any package update. 
    567 This means that the update to 10.1.1 will either appear in Update Manager as a package update, for both “Edge” and “Production” users, or in the listing of **pc-updatemanager pkgcheck**. 
    568  
    569  
    570 **N****OTE:** **a ****fresh install, rather than an update, is required if you wish to take advantage of any of the following features: UEFI boot (on a current non-UEFI installation), disk encryption, or the ****.**** **This means that you will have to backup your data to an external drive or another system, perform the install, than restore your data from backup. 
     513Upgrading from any 10.x version to 10.1.1 is the same as applying any package update. This means that the update to 10.1.1 will either appear in Update 
     514Manager as a package update, for both "Edge" and "Production" users, or in the listing of :command:`pc-updatemanager pkgcheck`. 
     515 
     516.. note:: a fresh install, rather than an update, is required if you wish to take advantage of any of the following features: UEFI boot (on a current non-UEFI 
     517   installation), disk encryption, or the 
     518   `improved encryption key generation provided by GELIv7 <https://github.com/freebsd/freebsd/commit/38de8ef1dd0e468ff1e3ec1c431f465e270beba3>`_. This means 
     519   that you will have to backup your data to an external drive or another system, perform the install, than restore your data from backup. 
    571520 
    572521.. index:: software 
     
    578527PBI Manager is a suite of command line utilities which can be used to install, remove, and manage PBIs. 
    579528 
    580  
    581 This chapter provides an overview of the commands that are installed by PBI Manager. 
    582 When using these commands, note that single character options can not be stacked. 
    583 As an example, you must type **pbi_add -i -v** as **pbi_add -iv** will fail with a syntax error. 
     529This chapter provides an overview of the commands that are installed by PBI Manager. When using these commands, note that single character options can not be 
     530stacked. As an example, you must type :command:`pbi_add -i -v` as :command:`pbi_add -iv` will fail with a syntax error. 
    584531 
    585532.. index:: PBI Manager 
     
    589536--- 
    590537 
    591 The **pbi** meta-command can be used to install, uninstall, and get information about PBIs. 
    592 Unlike the other **pbi_*** commands, it uses a space instead of an underscore. 
    593 For example, **pbi add** is equivalent to **pbi_add **and either command can be used to install a PBI. 
    594  
    595 This meta-command expects to be given a sub-command, and then a suitable option for that sub-command. 
    596 To see the available options for a sub-command, use the built-in help system. 
    597 For example, to see the available options for the **add** sub-command, type **pkg help add**. 
     538The :command:`pbi` meta-command can be used to install, uninstall, and get information about PBIs. Unlike the other :command:`pbi_` commands, it uses a space 
     539instead of an underscore. For example, :command:`pbi add` is equivalent to :command:`pbi_add` and either command can be used to install a PBI. 
     540 
     541This meta-command expects to be given a sub-command, and then a suitable option for that sub-command. To see the available options for a sub-command, use the 
     542built-in help system. For example, to see the available options for the **add** sub-command, type :command:`pkg help add`. 
    598543Table 7.3a summarizes the available sub-commands. 
    599544 
    600 Table 7.3a: pbi Sub-Commands 
    601  
    602 +--------------+--------------------------------------------------------------------------------+ 
    603 | Sub\-Command | Description                                                                    | 
    604 +==============+================================================================================+ 
    605 | add          | installs the specified PBI                                                     | 
    606 +--------------+--------------------------------------------------------------------------------+ 
    607 | delete       | uninstalls the specified PBI                                                   | 
    608 +--------------+--------------------------------------------------------------------------------+ 
    609 | help         | shows the options for the specified sub\-command                               | 
    610 +--------------+--------------------------------------------------------------------------------+ 
    611 | icon         | adds or deletes the PBI's desktop icon, menu icon, or MIME registration        | 
    612 +--------------+--------------------------------------------------------------------------------+ 
    613 | info         | shows all available PBIs or lists the packages installed into a specified jail | 
    614 +--------------+--------------------------------------------------------------------------------+ 
    615 | install      | equivalent to **add**                                                          | 
    616 +--------------+--------------------------------------------------------------------------------+ 
     545**Table 7.3a: pbi Sub-Commands** 
     546 
     547+------------------+--------------------------------------------------------------------------------+ 
     548| Sub-Command      | Description                                                                    | 
     549+==================+================================================================================+ 
     550| **add**          | installs the specified PBI                                                     | 
     551+------------------+--------------------------------------------------------------------------------+ 
     552| **delete**       | uninstalls the specified PBI                                                   | 
     553+------------------+--------------------------------------------------------------------------------+ 
     554| **help**         | shows the options for the specified sub-command                                | 
     555+------------------+--------------------------------------------------------------------------------+ 
     556| **icon**         | adds or deletes the PBI's desktop icon, menu icon, or MIME registration        | 
     557+------------------+--------------------------------------------------------------------------------+ 
     558| **info**         | shows all available PBIs or lists the packages installed into a specified jail | 
     559+------------------+--------------------------------------------------------------------------------+ 
     560| **install**      | equivalent to **add**                                                          | 
     561+------------------+--------------------------------------------------------------------------------+ 
    617562 
    618563.. index:: PBI Manager 
     
    622567------- 
    623568 
    624 The **pbi_add** command is used to install a specified PBI. 
    625 Table 7.3b summarizes the available options. 
    626  
    627 **Table 7.****3b****: pbi_add Options** 
    628  
    629 +------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ 
    630 | Switch                 | Description                                                                                                                           | 
    631 +========================+=======================================================================================================================================+ 
    632 | **\-f**                | force installation, overwriting an already installed copy of the application                                                          | 
    633 +------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ 
    634 | **\-i**                | display information about specified PBI; if combined with **\-v**, will display all of the files that will be installed with the PBI  | 
    635 +------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ 
    636 | **\-****j <jailname>** | installs the PBI into the specified jail                                                                                              | 
    637 +------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ 
    638 | \-J                    | used to create a new jail and install specified PBI into it                                                                           | 
    639 +------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ 
    640 | **\-****l**            | display *LICENSE* text for specified PBI                                                                                              | 
    641 +------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ 
    642 | **\-v**                | enable verbose output                                                                                                                 | 
    643 +------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ 
    644 | \-\-licagree           | if the PBI has a license, agree to it                                                                                                 | 
    645 +------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ 
    646  
    647 The following example installs the alpine PBI. 
    648 When prompted, input your password. 
    649  
    650  
    651 **sudo pbi_add alpine**  
    652  
    653 Password: 
    654  
    655 Updating repository catalogue  
    656  
    657 Installing: alpine The following 2 packages will be installed:  
    658  
    659 Installing pico-alpine: 2.00_1 
    660  
    661 Installing alpine: 2.00_4 
    662  
    663 The installation will require 9 MB more space  
    664  
    665 2 MB to be downloaded  
    666  
    667 pico-alpine-2.00_1.txz 100% 314KB 313.9KB/s 313.9KB/s 00:01  
    668  
    669 alpine-2.00_4.txz 100% 1701KB 1.7MB/s 1.4MB/s 00:01  
    670  
    671 Checking integrity... done The following 2 packages will be installed:  
    672  
    673 Installing pico-alpine: 2.00_1 
    674  
    675 Installing alpine: 2.00_4 
    676  
    677 The installation will require 9 MB more space  
    678  
    679 0 B to be downloaded  
    680  
    681 Checking integrity... done  
    682  
    683 [1/2] Installing pico-alpine-2.00_1... done  
    684  
    685 [2/2] Installing alpine-2.00_4... done ****************************************************************  
    686  
    687 *** To use GnuPG with Alpine, take a look at the mail/pine-pgp-filters port ***  
    688  
    689 ****************************************************************  
     569The :command:`pbi_add` command is used to install a specified PBI. Table 7.3b summarizes the available options. 
     570 
     571**Table 7.3b: pbi_add Options** 
     572 
     573+------------------------+-----------------------------------------------------------------------------------------------------------------------------------+ 
     574| Switch                 | Description                                                                                                                       | 
     575+========================+===================================================================================================================================+ 
     576| **-f**                 | force installation, overwriting an already installed copy of the application                                                      | 
     577+------------------------+-----------------------------------------------------------------------------------------------------------------------------------+ 
     578| **-i**                 | display information about specified PBI; if combined with **-v**, will display all of the files that will be installed with the   | 
     579|                        | PBI                                                                                                                               | 
     580+------------------------+-----------------------------------------------------------------------------------------------------------------------------------+ 
     581| **-j <jailname>**      | installs the PBI into the specified jail                                                                                          | 
     582+------------------------+-----------------------------------------------------------------------------------------------------------------------------------+ 
     583| **-J**                 | used to create a new jail and install specified PBI into it                                                                       | 
     584+------------------------+-----------------------------------------------------------------------------------------------------------------------------------+ 
     585| **-l**                 | display :file:`LICENSE` text for specified PBI                                                                                    | 
     586+------------------------+-----------------------------------------------------------------------------------------------------------------------------------+ 
     587| **-v**                 | enable verbose output                                                                                                             | 
     588+------------------------+-----------------------------------------------------------------------------------------------------------------------------------+ 
     589| **--licagree**         | if the PBI has a license, agree to it                                                                                             | 
     590+------------------------+-----------------------------------------------------------------------------------------------------------------------------------+ 
     591 
     592The following example installs the alpine PBI. When prompted, input your password:: 
     593 
     594 sudo pbi_add alpine 
     595 Password: 
     596 Updating repository catalogue  
     597 Installing: alpine The following 2 packages will be installed:  
     598 Installing pico-alpine: 2.00_1 
     599 Installing alpine: 2.00_4 
     600 The installation will require 9 MB more space  
     601 2 MB to be downloaded  
     602 pico-alpine-2.00_1.txz 100% 314KB 313.9KB/s 313.9KB/s 00:01  
     603 alpine-2.00_4.txz 100% 1701KB 1.7MB/s 1.4MB/s 00:01  
     604 Checking integrity... done The following 2 packages will be installed:  
     605 Installing pico-alpine: 2.00_1 
     606 Installing alpine: 2.00_4 
     607 The installation will require 9 MB more space  
     608 0 B to be downloaded  
     609 Checking integrity... done  
     610 [1/2] Installing pico-alpine-2.00_1... done  
     611 [2/2] Installing alpine-2.00_4... done  
     612 ****************************************************************  
     613 *** To use GnuPG with Alpine, take a look at the mail/pine-pgp-filters port ***  
     614 ****************************************************************  
    690615 
    691616.. index:: PBI Manager 
     
    695620-------- 
    696621 
    697 The **pbi_*** commands support several environment variables which can be stored in the ASCII text configuration file, */usr/local/etc/pbi.conf*. 
    698 These proxy variables are only needed if the system uses a proxy server to access the Internet. 
    699 Table 7.3c lists the supported variables. 
    700  
    701  
    702 Table 7.3c: pbi.conf Variables 
     622The :command:`pbi_` commands support several environment variables which can be stored in the ASCII text configuration file, :file:`/usr/local/etc/pbi.conf`. 
     623These proxy variables are only needed if the system uses a proxy server to access the Internet. Table 7.3c lists the supported variables. 
     624 
     625**Table 7.3c: pbi.conf Variables** 
    703626 
    704627+----------------+--------------------------------------------------+ 
     
    722645----------- 
    723646 
    724 The pbi_delete command removes an installed PBI from the system. 
    725 Table 7.3d summarizes its one available option:  
    726  
    727 Table 7.3d: pbi_delete Options 
    728  
    729 +------------+---------------------------------------------------------------------------------+ 
    730 | Switch     | Description                                                                     | 
    731 +============+=================================================================================+ 
    732 | \-f        | force the removal of the application, even if other applications depend upon it | 
    733 +------------+---------------------------------------------------------------------------------+ 
    734 | \-j <jail> | deletes the application from the specified jail                                 | 
    735 +------------+---------------------------------------------------------------------------------+ 
    736 | **\-v**    | enable verbose output                                                           | 
    737 +------------+---------------------------------------------------------------------------------+ 
    738  
    739 The following example uninstalls the previously installed alpine PBI:  
    740  
    741 **sudo pbi_delete alpine**  
    742  
    743 Password:  
    744  
    745 Updating repository catalogue  
    746  
    747 Deinstallation has been requested for the following 1 packages:  
    748  
    749 alpine-2.00_4 
    750  
    751 The deinstallation will free 8 MB  
    752  
    753 [1/1] Deleting alpine-2.00_4... done  
    754  
    755 Deinstallation has been requested for the following 2 packages:  
    756  
    757 openjpeg-2.1.0 
    758  
    759 pico-alpine-2.00_1 
    760  
    761 The deinstallation will free 2 MB  
    762  
    763 [1/2] Deleting openjpeg-2.1.0... done  
    764  
    765 [2/2] Deleting pico-alpine-2.00_1... done 
     647The :command:`pbi_delete` command removes an installed PBI from the system. Table 7.3d summarizes its one available option:  
     648 
     649**Table 7.3d: pbi_delete Options** 
     650 
     651+---------------+---------------------------------------------------------------------------------+ 
     652| Switch        | Description                                                                     | 
     653+===============+=================================================================================+ 
     654| **-f**        | force the removal of the application, even if other applications depend upon it | 
     655+---------------+---------------------------------------------------------------------------------+ 
     656| **-j <jail>** | deletes the application from the specified jail                                 | 
     657+---------------+---------------------------------------------------------------------------------+ 
     658| **-v**        | enable verbose output                                                           | 
     659+---------------+---------------------------------------------------------------------------------+ 
     660 
     661The following example uninstalls the previously installed alpine PBI:: 
     662 
     663 sudo pbi_delete alpine 
     664 Password:  
     665 Updating repository catalogue  
     666 Deinstallation has been requested for the following 1 packages:  
     667 alpine-2.00_4 
     668 The deinstallation will free 8 MB  
     669 [1/1] Deleting alpine-2.00_4... done  
     670 Deinstallation has been requested for the following 2 packages:  
     671 openjpeg-2.1.0 
     672 pico-alpine-2.00_1 
     673 The deinstallation will free 2 MB  
     674 [1/2] Deleting openjpeg-2.1.0... done  
     675 [2/2] Deleting pico-alpine-2.00_1... done 
    766676 
    767677.. index:: PBI Manager 
     
    771681-------- 
    772682 
    773 The **pbi_icon** command provides a number of options for adding desktop icons, menu entries, and MIME data for an installed PBI. 
    774 Not all PBIs will contain desktop/menu/MIME data. 
    775 Additionally, the window manager must be -compliant to understand a PBI's icon and MIME settings. 
    776 Table 7.3e summarizes this command's options:  
    777  
    778 **Table 7.****3e****: pbi_icon Options** 
     683The :command:`pbi_icon` command provides a number of options for adding desktop icons, menu entries, and MIME data for an installed PBI. Not all PBIs will 
     684contain desktop/menu/MIME data. Additionally, the window manager must be `XDG <http://en.wikipedia.org/wiki/Xdg>`_-compliant to understand a PBI's icon and 
     685MIME settings. Table 7.3e summarizes this command's options:  
     686 
     687**Table 7.3e: pbi_icon Options** 
    779688 
    780689+-------------------+-------------------------------------------------------+ 
    781690| Switch            | Description                                           | 
    782691+===================+=======================================================+ 
    783 | **add\-desktop**  | installs desktop icon; should be run as regular user  | 
     692| **add-desktop**   | installs desktop icon; should be run as regular user  | 
    784693+-------------------+-------------------------------------------------------+ 
    785 | **add\-mime**     | installs mime information; should be run as root      | 
     694| **add-mime**      | installs mime information; should be run as root      | 
    786695+-------------------+-------------------------------------------------------+ 
    787 | **add\-menu**     | installs menu icons; should be run as root            | 
     696| **add-menu**      | installs menu icons; should be run as root            | 
    788697+-------------------+-------------------------------------------------------+ 
    789 | **del\-desktop**  | removes desktop icon; should be run as regular user   | 
     698| **del-desktop**   | removes desktop icon; should be run as regular user   | 
    790699+-------------------+-------------------------------------------------------+ 
    791 | **del\-menu**     | removes menu icons; should be run as root             | 
     700| **del-menu**      | removes menu icons; should be run as root             | 
    792701+-------------------+-------------------------------------------------------+ 
    793 | **del\-mime**     | removes mime information; should be run as root       | 
     702| **del-mime**      | removes mime information; should be run as root       | 
    794703+-------------------+-------------------------------------------------------+ 
    795704 
     
    800709--------- 
    801710 
    802 The **pbi_info** command is used to determine which PBIs are currently installed. 
    803 Table 7.3f summarizes the available options. 
    804  
    805 Table 7.3f: pbi_info Options 
     711The :command:`pbi_info` command is used to determine which PBIs are currently installed. Table 7.3f summarizes the available options. 
     712 
     713**Table 7.3f: pbi_info Options** 
    806714 
    807715+------------------------+------------------------------------------------------------------------------------------+ 
    808716| Switch                 | Description                                                                              | 
    809717+========================+==========================================================================================+ 
    810 | **\-a**                | list all PBIs installed on the system; same as running **pbi_info** without an argument  | 
     718| **-a**                 | list all PBIs installed on the system; same as running **pbi_info** without an argument  | 
    811719+------------------------+------------------------------------------------------------------------------------------+ 
    812 | **\-****j <jailname>** | list PBIs installed in the specified jail                                                | 
     720| **-j <jailname>**      | list PBIs installed in the specified jail                                                | 
    813721+------------------------+------------------------------------------------------------------------------------------+ 
    814 | **\-v**                | includes verbose information about each PBI                                              | 
     722| **-v**                 | includes verbose information about each PBI                                              | 
    815723+------------------------+------------------------------------------------------------------------------------------+ 
    816724 
     
    821729------------- 
    822730 
    823 This command is used to make the INDEX for a custom PBI repository which can then be used in AppCafe®. Refer to  for instructions on how to create a custom repository. 
     731This command is used to make the INDEX for a custom PBI repository which can then be used in :ref:`AppCafe®`. Refer to 
     732:ref:`Create Your Own PBI Repository` for instructions on how to create a custom repository. 
    824733 
    825734.. index:: PBI Manager 
     
    829738--------------- 
    830739 
    831 To check for a newer version of the PC-BSD® *PBI-INDEX.txz* file, type **sudo** **pbi_updateindex **and input your password when prompted. 
    832 If a newer version is available, this command fetches and extracts it so that the system has the most recent list of available PBIs. 
     740To check for a newer version of the PC-BSD® :file:`PBI-INDEX.txz` file, type :command:`sudo pbi_updateindex` and input your password when prompted. If a 
     741newer version is available, this command fetches and extracts it so that the system has the most recent list of available PBIs. 
    833742 
    834743.. index:: software 
     
    838747============================== 
    839748 
    840 By default, AppCafe® displays the PBIs which are available from the official PC-BSD® repository. 
    841 It also supports custom repositories. 
     749By default, AppCafe® displays the PBIs which are available from the official PC-BSD® repository. It also supports custom repositories. 
    842750 
    843751In order to create a custom repository, you need to: 
    844752 
    845 - create the OpenSSL signing key which will be used to sign the repository's *INDEX*  
    846  
    847 - create the customized modules using EasyPBI  
    848  
    849 - generate the custom *INDEX* and sign it with the key  
    850  
    851 - import the repository into AppCafe® or configure PBI Manager to use the custom repository  
     753* create the OpenSSL signing key which will be used to sign the repository's :file:`INDEX`  
     754 
     755* create the customized modules using :ref:`EasyPBI`  
     756 
     757* generate the custom :file:`INDEX` and sign it with the key  
     758 
     759* import the repository into :ref:`AppCafe®` or configure :ref:`PBI Manager` to use the custom repository  
    852760 
    853761This section describes these steps in more detail. 
     
    859767----------------------- 
    860768 
    861 The *INDEX* of a PBI repository must be digitally signed for security and identification purposes. 
    862 In order to sign the *INDEX*, first create an OpenSSL key pair using the following commands:  
    863  
    864 openssl genrsa -out privkey.pem 4096 
    865  
    866 Generating RSA private key, 4096 bit long modulus 
    867  
    868 ..................++ 
    869  
    870 .............................................................................++ 
    871  
    872 e is 65537 (0x10001) 
    873  
    874 openssl rsa -in privkey.pem -pubout > pub.key 
    875  
    876 writing RSA key 
    877  
    878 These commands will create the files *privkey.pem* and *pub.key*. 
     769The :file:`INDEX` of a PBI repository must be digitally signed for security and identification purposes. In order to sign the :file:`INDEX`, first create an 
     770OpenSSL key pair using the following commands:: 
     771 
     772 openssl genrsa -out privkey.pem 4096 
     773 Generating RSA private key, 4096 bit long modulus 
     774 ..................++ 
     775 .............................................................................++ 
     776 e is 65537 (0x10001) 
     777 
     778 openssl rsa -in privkey.pem -pubout > pub.key 
     779 writing RSA key 
     780 
     781These commands will create the files :file:`privkey.pem` and :file:`pub.key`. 
    879782 
    880783.. index:: software 
     
    884787------------------------------ 
    885788 
    886 To create the customized PBI modules, follow the instructions in  and . If the repository directory is ~/myrepo/, make sure that all of the custom modules are listed as subdirectories of that directory. 
    887  
    888 Next, configure a FTP, HTTP, or HTTPS server to host the directory containing the custom PBI modules. 
    889 The server can be a public URL on the Internet or a private LAN server, as long as it is accessible to your target audience. 
    890 Ensure that this directory is browsable by an FTP client or web browser from a client system before moving on to the next step. 
     789To create the customized PBI modules, follow the instructions in :ref:`Bulk Module Creator`. If the repository directory is :file:`~/myrepo/`, make sure that 
     790all of the custom modules are listed as subdirectories of that directory. 
     791 
     792Next, configure a FTP, HTTP, or HTTPS server to host the directory containing the custom PBI modules. The server can be a public URL on the Internet or a 
     793private LAN server, as long as it is accessible to your target audience. Ensure that this directory is browsable by an FTP client or web browser from a client 
     794system **before** moving on to the next step. 
    891795 
    892796.. index:: software 
     
    896800------------------------- 
    897801 
    898 To generate the signed *INDEX*, **cd** to the directory containing the PBI modules and run **pbi_makeindex**, specifying the path to the private key. 
    899 In this example, the PBI modules are located in *~/myrepo* and the key is located in the user's home directory (*~*). 
    900 Be patient as it will take a few minutes to generate the *INDEX* and return the command prompt. 
    901  
    902  
    903 cd ~/myrepo 
    904  
    905 fetch https://github.com/pcbsd/pcbsd/raw/master/pbi-modules/PBI-categories 
    906  
    907 pbi_makeindex ../privkey.pem 
    908  
    909 Building PBI-INDEX... This may take a few moments... 
    910  
    911 Fetching PBI ratings file... 
    912  
    913 /tmp/.PBI.19956/.ratings 100% of 71 kB 134 kBps 00m00s 
    914  
    915 Adding additional package information to PBI-INDEX... 
    916  
    917 Compressing PBI-INDEX... 
    918  
    919 This will create the files *PBI-INDEX.txz* and *PBI-INDEX.txz.sha1*. 
     802To generate the signed :file:`INDEX`, :command:`cd` to the directory containing the PBI modules and run :command:`pbi_makeindex`, specifying the path to the 
     803private key. In this example, the PBI modules are located in :file:`~/myrepo` and the key is located in the user's home directory (:file:`~`). Be patient as 
     804it will take a few minutes to generate the :file:`INDEX` and return the command prompt. 
     805:: 
     806 
     807 cd ~/myrepo 
     808 
     809 fetch https://github.com/pcbsd/pcbsd/raw/master/pbi-modules/PBI-categories 
     810 
     811 pbi_makeindex ../privkey.pem 
     812 Building PBI-INDEX... This may take a few moments... 
     813 Fetching PBI ratings file... 
     814 /tmp/.PBI.19956/.ratings 100% of 71 kB 134 kBps 00m00s 
     815 Adding additional package information to PBI-INDEX... 
     816 Compressing PBI-INDEX... 
     817 
     818This will create the files :file:`PBI-INDEX.txz` and :file:`PBI-INDEX.txz.sha1`. 
    920819 
    921820.. index:: software 
     
    925824--------------------- 
    926825 
    927 To configure  to use the custom repository, go to Configure → Repository Settings. 
    928 Click “Custom” in the screen shown in Figure 7.4a, then the “+” button. 
    929 Input the URL to the repository and click “OK”.  
    930  
    931 Figure 7.4a: Add the Custom Repository to AppCafe® 
    932  
    933 .. image:: images/picture_194.png 
    934  
    935 It will take a few minutes for AppCafe® to read in the *INDEX* for the custom repository. 
     826To configure  to use the custom repository, go to :menuselection:`Configure --> Repository Settings`. Click "Custom" in the screen shown in Figure 7.4a, then 
     827the "+" button. Input the URL to the repository and click "OK".  
     828 
     829**Figure 7.4a: Add the Custom Repository to AppCafe®** 
     830 
     831.. image:: images/repo1.png 
     832 
     833It will take a few minutes for AppCafe® to read in the :file:`INDEX` for the custom repository. 
    936834 
    937835.. index:: software 
Note: See TracChangeset for help on using the changeset viewer.